← Back to Dashboard
6344
Pages Scanned
1232
Pages Flagged
6344
Changed Pages
19.4%
% Pages Flagged

Live Progress

🔴 Connecting...
46%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08 Scan started

Scan Information

Started At: 2026-01-12 00:00:08

Finished At: 2026-01-12 05:20:00

Status: cancelled

Target Repo: Azure

Current Phase: discovery

Files Queued: 13829

Files Completed: 6344

Problematic Pages

1232 issues found
Active Directory B2C Request an access token in Azure Active Directory B2C ...ob/main/articles/active-directory-b2c/access-tokens.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Microsoft PowerShell as an example HTTP client for testing the POST request, without referencing any Linux or cross-platform alternatives. No Linux command-line tools (such as curl or wget) are suggested, and PowerShell is mentioned before any other tool, implying Windows as the default environment.
Recommendations
  • Include examples using cross-platform tools such as curl or wget for making HTTP requests.
  • Explicitly mention that any HTTP client can be used, and provide sample commands for both Windows (PowerShell) and Linux/macOS (curl).
  • Avoid listing Windows-specific tools first; present cross-platform or OS-neutral options before platform-specific ones.
  • Add a note clarifying that the instructions apply equally to Linux, macOS, and Windows environments.
GitHub Create Pull Request
Active Directory B2C Set up OAuth 2.0 client credentials flow .../active-directory-b2c/client-credentials-grant-flow.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias in several areas. The only explicit tool mentioned for generating GUIDs is Microsoft PowerShell, with no Linux or cross-platform alternatives provided or prioritized. The scripting example for obtaining an access token is given first in PowerShell, before the cURL (Linux-friendly) example. Windows tools and patterns are referenced without equal mention of Linux equivalents, and the order of examples favors Windows-first presentation.
Recommendations
  • When mentioning GUID generation, include Linux/macOS alternatives such as 'uuidgen' or 'openssl rand -hex 16', and provide example commands.
  • Present cross-platform examples (e.g., cURL) before or alongside Windows-specific ones like PowerShell.
  • Explicitly mention that all steps (including manifest editing and API calls) can be performed on Linux/macOS, and provide relevant command-line or tool references.
  • Avoid referencing Windows tools exclusively; always provide parity for Linux/macOS users.
  • Consider adding a table or section listing equivalent commands/tools for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Saviynt with Azure Active Directory B2C .../main/articles/active-directory-b2c/partner-saviynt.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias in the section on enabling Saviynt to delete users. It exclusively instructs users to install and use the Microsoft Graph PowerShell module on a Windows workstation or server, with no mention of Linux or cross-platform alternatives. Only PowerShell commands are provided, and there is no guidance for performing the same tasks on Linux or macOS, nor are platform-agnostic tools (such as Microsoft Graph CLI or REST API) mentioned.
Recommendations
  • Provide equivalent instructions for Linux and macOS environments, including installation and usage of Microsoft Graph CLI or REST API.
  • Include examples using platform-agnostic tools (e.g., Microsoft Graph CLI, curl commands for REST API) alongside PowerShell examples.
  • Explicitly state cross-platform options for all steps involving command-line tools.
  • Rephrase steps to avoid assuming a Windows environment by default (e.g., 'On your workstation' instead of 'On a Windows workstation or server').
  • Add a note clarifying that PowerShell Core is available on Linux/macOS and provide installation instructions if PowerShell is still preferred.
GitHub Create Pull Request
Active Directory B2C IDology integration with Azure Active Directory B2C .../main/articles/active-directory-b2c/partner-idology.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions for publishing the API. There are no examples or guidance for deploying the API from Linux environments, nor are alternative tools or workflows (such as VS Code, CLI, or GitHub Actions) mentioned. The documentation assumes the use of Windows tooling and does not provide parity for Linux users.
Recommendations
  • Include instructions for deploying the API using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code.
  • Add Linux-specific deployment examples (e.g., using dotnet CLI or zip deploy from Linux/macOS).
  • Mention alternative editors and IDEs (such as VS Code) alongside Visual Studio.
  • Ensure that all referenced documentation and samples are accessible and applicable from Linux environments.
  • Review and update any screenshots or UI references to avoid Windows-only terminology.
GitHub Create Pull Request
Active Directory B2C Call a REST API by using Azure AD B2C custom policy ...-directory-b2c/custom-policies-series-call-rest-api.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a bias towards Windows by providing only PowerShell examples for testing the REST API, referencing Microsoft PowerShell as the HTTP client, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The instructions and tooling references (e.g., Visual Studio Code) are cross-platform, but the testing and client interaction sections are Windows-centric.
Recommendations
  • Provide equivalent Linux/macOS command-line examples for testing the REST API, such as using curl or HTTPie.
  • When referencing PowerShell, clarify that it is available cross-platform, but also offer alternative commands for users on Linux/macOS.
  • List cross-platform or Linux-native tools (e.g., curl, wget, HTTPie) before or alongside Windows tools when suggesting HTTP clients.
  • Explicitly mention that Visual Studio Code and Node.js are cross-platform, and that all steps can be performed on Linux/macOS as well as Windows.
  • Consider including a table or section summarizing how to perform key steps on Windows, Linux, and macOS.
GitHub Create Pull Request
Active Directory B2C Configure a force password reset flow in Azure AD B2C .../articles/active-directory-b2c/force-password-reset.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias by exclusively providing PowerShell examples for configuring password expiry duration, referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent Linux or cross-platform CLI instructions. All procedural steps assume use of the Azure portal or PowerShell, with no mention of Bash, Azure CLI, or other Linux-friendly approaches. Windows tools and patterns are presented first and exclusively, with no parity for Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands for all operations currently demonstrated with PowerShell.
  • Include Bash or shell script snippets where applicable, especially for REST API calls (e.g., using curl for PATCH requests).
  • Explicitly mention cross-platform compatibility for all steps, clarifying which tools can be used on Linux, macOS, and Windows.
  • Add a section or note highlighting how Linux/macOS users can perform the same tasks without PowerShell, including installation and usage of Microsoft Graph CLI or REST API.
  • Ensure that tool recommendations and examples are presented in a platform-neutral order, or grouped by platform, rather than defaulting to Windows/PowerShell first.
GitHub Create Pull Request
Active Directory B2C Add AD FS as an OpenID Connect identity provider by using custom policies ...rticles/active-directory-b2c/identity-provider-adfs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a clear Windows bias. All instructions for configuring AD FS are given using Windows-specific tools (Server Manager, AD FS Management), with no mention of Linux alternatives or cross-platform approaches. The examples and screenshots exclusively reference Windows environments, and there are no PowerShell scripts or command-line alternatives provided, but the reliance on GUI tools is itself Windows-centric. No Linux-based AD FS equivalents or instructions are offered, nor is there guidance for users who might be running AD FS or similar identity providers on non-Windows platforms.
Recommendations
  • Provide command-line (PowerShell and/or Windows CMD) instructions for AD FS configuration to support automation and remote management.
  • Explicitly state that AD FS is a Windows Server feature and clarify platform requirements early in the documentation.
  • Mention and link to cross-platform alternatives (such as using Azure AD, Keycloak, or other OpenID Connect providers that run on Linux) for users who do not have access to Windows Server.
  • If possible, include steps or references for configuring OpenID Connect providers on Linux, or provide parity documentation for equivalent scenarios.
  • Add a note about the lack of Linux support for AD FS, and suggest alternative identity providers for Linux environments.
GitHub Create Pull Request
Active Directory B2C Deploy custom policies with Azure Pipelines .../active-directory-b2c/deploy-custom-policies-devops.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exclusively uses PowerShell scripts and tasks for deploying Azure AD B2C custom policies in Azure Pipelines, with no mention of Linux-compatible alternatives (such as Bash or cross-platform scripting). All example scripts and pipeline tasks are PowerShell-based, and there is no guidance for users on Linux agents or those preferring non-Windows tooling. The documentation implicitly assumes a Windows-centric workflow and does not provide parity for Linux users.
Recommendations
  • Provide equivalent Bash script examples for deploying policies using curl or similar tools, suitable for Linux agents.
  • Explicitly mention that Azure Pipelines supports both Windows and Linux agents, and guide users on how to adapt the deployment process for Linux environments.
  • Include instructions for running deployment tasks using Bash or cross-platform scripting languages (e.g., Python), and show how to configure these in the pipeline.
  • Add a section comparing PowerShell and Bash approaches, highlighting any differences and considerations for cross-platform compatibility.
  • Avoid assuming PowerShell as the default; present both Windows and Linux options side-by-side where possible.
GitHub Create Pull Request
Active Directory B2C Enable authentication in a SPA application by using Azure Active Directory B2C building blocks .../active-directory-b2c/enable-authentication-spa-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias. The only explicit command-line example for running the application uses PowerShell syntax (npm ./index.js), which is not valid on Linux/macOS shells. There is no mention of Linux or macOS environments, nor are equivalent Bash commands provided. The instructions and examples implicitly assume a Windows environment, especially in the final 'Run your SPA application' step.
Recommendations
  • Provide equivalent Bash commands for Linux/macOS users, such as 'node index.js' or 'npm start', and clarify cross-platform compatibility.
  • Avoid using PowerShell-specific syntax unless explicitly targeting Windows users; use generic commands where possible.
  • Add a note or section indicating that the instructions apply to Windows, Linux, and macOS, and specify any platform-specific differences.
  • Include troubleshooting tips for common issues on Linux/macOS (e.g., port binding, permissions).
GitHub Create Pull Request
Active Directory B2C Define an ID token hint technical profile in a custom policy ...ob/main/articles/active-directory-b2c/id-token-hint.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing PowerShell-only examples for key generation and certificate creation, referencing Windows-specific tools (PowerShell cmdlets), and omitting equivalent Linux/macOS commands or tools. The instructions for generating a self-signed certificate explicitly mention PowerShell and do not offer alternatives for non-Windows platforms. The sample code and walkthroughs are Windows-centric, with no mention of cross-platform approaches.
Recommendations
  • Provide equivalent command-line examples for Linux and macOS, such as using openssl for key and certificate generation.
  • Mention cross-platform tools and approaches (e.g., dotnet CLI, openssl) alongside Windows/PowerShell instructions.
  • Add notes or sections clarifying how developers on non-Windows platforms can perform the same steps.
  • Ensure that sample code and walkthroughs reference platform-neutral or cross-platform solutions where possible.
  • Order examples so that Windows and Linux/macOS approaches are presented together or Linux/macOS is not always secondary.
GitHub Create Pull Request
Active Directory B2C Add AD FS as a SAML identity provider by using custom policies ...es/active-directory-b2c/identity-provider-adfs-saml.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented towards Windows environments, specifically AD FS on Windows Server. All configuration and troubleshooting steps reference Windows-only tools such as Server Manager, AD FS Management snap-in, Event Viewer, and PowerShell cmdlets. There are no Linux equivalents or cross-platform alternatives mentioned, and all examples and procedures assume a Windows administrative context.
Recommendations
  • Add notes clarifying that AD FS is a Windows-only technology, and suggest alternatives for Linux environments (e.g., Shibboleth, SimpleSAMLphp) where possible.
  • Provide guidance or links for integrating non-Windows SAML providers with Azure AD B2C custom policies.
  • Where troubleshooting steps reference Windows tools (Event Viewer, AD FS Management), mention that these are not available on Linux and suggest alternative logging or debugging strategies for non-Windows SAML providers.
  • If PowerShell is used for configuration, offer equivalent commands or scripts for other platforms where feasible, or clarify that these steps are Windows-specific.
  • Consider including a section on cross-platform SAML integration to improve parity and help Linux administrators understand their options.
GitHub Create Pull Request
API Management How to use role-based access control in Azure API Management | Microsoft Docs ...management/api-management-role-based-access-control.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for custom role creation and assignment, without any equivalent Azure CLI or REST API examples. PowerShell is a Windows-centric tool, and its exclusive use may disadvantage Linux users. Additionally, references to role assignment tools mention PowerShell before CLI and REST, further reinforcing a Windows-first approach.
Recommendations
  • Add equivalent Azure CLI examples for custom role creation and assignment to ensure Linux parity.
  • Include REST API sample requests for role management tasks.
  • When listing tools, alternate or balance the order of PowerShell and CLI/REST to avoid Windows-first perception.
  • Explicitly mention cross-platform compatibility of Azure CLI and REST API, and link to their documentation.
  • Consider adding notes or sections highlighting how Linux/macOS users can perform the same tasks.
GitHub Create Pull Request
App Service Discover .NET Apps to Azure App Service ...cles/app-service/app-service-migration-discover-net.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page focuses exclusively on discovery of ASP.NET web apps hosted on IIS servers, which are Windows-specific. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps running on Linux. All tooling and patterns referenced (Azure Migrate appliance, IIS) are Windows-centric, and Linux equivalents are absent.
Recommendations
  • Add sections or examples for discovering .NET web apps hosted on Linux servers (e.g., Apache, Nginx).
  • Mention whether Azure Migrate supports discovery for Linux-based .NET deployments, and provide guidance if available.
  • Include parity in dashboard features and error remediation for Linux scenarios.
  • Explicitly state platform limitations if Linux discovery is not supported, and link to alternative solutions for Linux users.
GitHub Create Pull Request
App Service Restore Deleted Apps ...blob/main/articles/app-service/app-service-undelete.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows-centric tools and patterns. All command-line instructions use PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native workflows. The documentation does not provide equivalent examples for Linux users or alternative cross-platform approaches, and PowerShell is introduced before any other automation tool (which are not mentioned at all).
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell is available on Linux and macOS, but also provide Bash/CLI alternatives for users who prefer native Linux tools.
  • Include guidance for restoring deleted apps using REST API calls or Azure SDKs, which are platform-agnostic.
  • Reorganize sections so that cross-platform tools (e.g., Azure CLI) are presented before or alongside PowerShell, not after or omitted.
  • Add notes or links to documentation on installing and using Azure CLI or PowerShell on Linux/macOS, to improve accessibility for non-Windows users.
GitHub Create Pull Request
App Service Customize Sign-ins and Sign-outs ...vice/configure-authentication-customize-sign-in-out.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias in the 'Authorize or deny users' section, where server-level authorization is described exclusively for Windows apps using IIS and web.config, with no equivalent guidance for Linux apps. Windows tools (IIS, web.config, Kudu) are mentioned, and Linux alternatives are not provided or discussed. The ordering also places Windows-specific instructions before any general or identity provider-level guidance.
Recommendations
  • Provide equivalent examples for Linux apps, such as how to implement server-level authorization using nginx, Apache, or application-level middleware.
  • Explicitly mention that Linux apps require different configuration approaches and link to relevant resources or sample code.
  • Balance the ordering by presenting cross-platform or Linux-specific guidance alongside Windows instructions, rather than focusing on Windows first.
  • Avoid exclusive references to Windows tools (IIS, web.config, Kudu) without offering Linux alternatives or clarifying platform limitations.
GitHub Create Pull Request
App Service Install a TLS/SSL Certificate for Your App ...main/articles/app-service/configure-ssl-certificate.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows a moderate Windows bias. It references Windows-specific tools (IIS, Certreq.exe) for certificate export, provides PowerShell examples alongside Azure CLI, and refers to Windows container support in FAQs. Linux alternatives (such as Linux-based certificate management tools) are not mentioned, and Windows tools are listed before or instead of Linux equivalents. There are no explicit Linux-focused examples or guidance, and automation examples are split between Azure CLI and PowerShell, but not Bash or other Linux-native scripting.
Recommendations
  • Add explicit Linux-based instructions and examples for certificate export, such as using OpenSSL on Linux, and clarify steps for Linux users.
  • Include Bash scripting examples for automation alongside Azure CLI and PowerShell.
  • Mention Linux container support and limitations in the FAQ sections, not just Windows containers.
  • When listing tools (e.g., IIS, Certreq.exe), also list Linux alternatives (e.g., OpenSSL, certbot) and provide links to relevant documentation.
  • Ensure that examples and instructions are presented in a cross-platform manner, or provide tabs for Windows and Linux workflows where appropriate.
GitHub Create Pull Request
App Service Configure Managed Instance on Azure App Service (Preview) ...ain/articles/app-service/configure-managed-instance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is heavily Windows-centric, with all examples, configuration patterns, and terminology tailored exclusively to Windows environments. Only Windows tools (PowerShell, MSI, Registry, RDP) are referenced, and there are no Linux equivalents or cross-platform considerations. The configuration script must be a PowerShell script named Install.ps1, and all customization scenarios (IIS, registry, ACLs, Windows features) are Windows-specific. Remote access is described solely in terms of RDP/Bastion, and troubleshooting/logging paths use Windows filesystem conventions. There is no mention of Linux support, examples, or alternative tooling.
Recommendations
  • Clearly state in the introduction that Managed Instance on Azure App Service is Windows-only, if that is the case. If Linux support is planned or possible, provide equivalent Linux instructions and examples.
  • For each configuration area (scripts, storage, registry, remote access), include Linux-specific guidance or explicitly note if not supported.
  • If configuration scripts are required to be PowerShell, clarify that Bash or other scripting languages are not supported, and consider adding support for Bash scripts for Linux parity.
  • For storage mounts, mention Linux mount patterns (e.g., mounting Azure Files via SMB/NFS on Linux) if/when supported.
  • For remote access, mention SSH as the Linux equivalent to RDP/Bastion, or state that only RDP is supported.
  • For registry keys, clarify that this is a Windows-only concept and provide Linux alternatives (such as environment variables or configuration files) if applicable.
  • In FAQs and troubleshooting, provide Linux file paths and logging conventions if Linux is or will be supported.
  • Review keywords and metadata to ensure Linux-related terms are included if cross-platform support is intended.
GitHub Create Pull Request
App Service Geo-Distributed Scale ...-service-app-service-environment-geo-distributed-scale.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing PowerShell examples for configuring Azure Traffic Manager and App Service Environments. There are no CLI (az), Bash, or Linux-native instructions or examples. The use of PowerShell is presented as the 'easiest way' without mention of alternatives, and no Linux tools or cross-platform patterns are discussed.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to create and configure Traffic Manager profiles and endpoints using Bash or other shells.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and link to cross-platform tool documentation.
  • Provide screenshots or terminal output from Linux environments where relevant (e.g., DNS lookups using dig or host).
  • Avoid language that implies PowerShell is the only or preferred method; present CLI and PowerShell options side-by-side.
  • Include a section on platform-agnostic automation approaches (e.g., ARM templates, Terraform) for advanced users.
GitHub Create Pull Request
Active Directory B2C Create & delete Azure AD B2C consumer user accounts in the Azure portal ...n/articles/active-directory-b2c/manage-users-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias in the section on revoking a consumer user's session, where only Microsoft Graph PowerShell (specifically in 'Windows PowerShell') is provided as an example. There is no mention of Linux-compatible alternatives (such as Bash, Azure CLI, or direct REST API usage), nor is there guidance for running PowerShell cross-platform. The instructions and terminology assume a Windows environment, potentially excluding Linux and macOS users.
Recommendations
  • Provide equivalent examples using Bash, Azure CLI, or direct REST API calls for session revocation.
  • Clarify that Microsoft Graph PowerShell is cross-platform and provide instructions for installation and usage on Linux and macOS.
  • Avoid specifying 'Windows PowerShell' unless the example is truly Windows-specific; use 'PowerShell' or 'terminal' for cross-platform inclusivity.
  • Wherever PowerShell is used, offer alternative command-line or scripting examples suitable for Linux users.
  • Review other sections for similar platform assumptions and ensure parity in instructions and tooling for Linux environments.
GitHub Create Pull Request
Active Directory B2C Tutorial to enable secure hybrid access for applications with Azure Active Directory B2C and F5 BIG-IP .../blob/main/articles/active-directory-b2c/partner-f5.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by referencing IIS as the example application for testing, providing a link to IIS setup instructions, and omitting equivalent Linux web server examples (such as Apache or Nginx). Windows tooling (IIS) is mentioned exclusively, and no Linux alternatives or parity guidance are provided for users who may want to test or deploy with Linux-based applications.
Recommendations
  • Add Linux-based web application examples (e.g., Apache, Nginx) alongside IIS for testing the integration.
  • Provide setup instructions or reference links for configuring header-based authentication with popular Linux web servers.
  • Ensure troubleshooting and configuration steps include notes or guidance relevant to Linux environments where applicable.
  • Explicitly state that the solution is platform-agnostic and provide parity in examples and references for both Windows and Linux.
  • Review all references to Windows-specific tools and add Linux equivalents where possible.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Azure Active Directory B2C with Jumio ...ob/main/articles/active-directory-b2c/partner-jumio.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell scripts for certificate creation and random string generation, with no equivalent Linux or cross-platform examples (e.g., OpenSSL, Bash). The instructions reference Visual Studio for deployment, a Windows-centric tool, and do not mention alternatives like VS Code or CLI-based deployment methods. The use of Windows certificate store paths and lack of mention of Linux certificate management further reinforce the bias.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation (e.g., OpenSSL commands) and random string generation (e.g., Bash or Python scripts).
  • Include deployment instructions using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions, not just Visual Studio.
  • Reference certificate storage and management for Linux (e.g., PEM files, local file system) alongside Windows certificate store.
  • Present examples and instructions for both Windows and Linux platforms, or use platform-agnostic language and tooling where possible.
GitHub Create Pull Request
App Service Quickstart: Deploy an ASP.NET web app ...lob/main/articles/app-service/quickstart-dotnetcore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: Visual Studio (Windows-only) is presented as the primary IDE, with detailed steps and screenshots. PowerShell is given its own section, with explicit recommendations for Windows hosting, while Linux deployment is relegated to Azure CLI or other tools. Many examples and instructions (such as file paths and compression commands) use Windows conventions, and some steps (e.g., .NET Framework 4.8) are only available for Windows. In some places, Linux options are mentioned but not shown in detail, and Windows tools or patterns are introduced before Linux equivalents.
Recommendations
  • Provide equal detail and screenshots for Linux workflows, including using Linux-native editors and shell commands.
  • Include explicit Linux file path and command examples (e.g., using zip/tar instead of Compress-Archive, showing bash syntax).
  • Where PowerShell is recommended for Windows, offer Bash or other Linux-native alternatives for Linux users.
  • Clarify which steps are cross-platform and which are Windows-only, and avoid presenting Windows-first unless justified by usage data.
  • Expand instructions for deploying to Azure App Service on Linux, including troubleshooting and configuration tips.
  • For .NET Framework sections, clearly state Windows-only limitations and suggest .NET Core/10 alternatives for Linux users.
GitHub Create Pull Request
App Service Use Private Endpoints for Apps ...main/articles/app-service/overview-private-endpoint.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. In the 'Related content' section, Windows-centric tools and examples (Azure PowerShell, ARM templates) are listed before Linux-friendly options (Azure CLI, Terraform). There is a dedicated PowerShell quickstart, but no Bash or Linux shell example. The DNS examples and instructions reference Windows-style host file editing and do not mention Linux equivalents. No explicit Linux command-line examples or Linux-specific troubleshooting are provided.
Recommendations
  • Add explicit Linux/Bash shell examples alongside PowerShell, especially for DNS configuration and endpoint creation.
  • Mention Linux tools and patterns (such as editing /etc/hosts for DNS testing) when discussing host file modification.
  • Ensure parity in quickstart guides: provide Bash/CLI scripts and troubleshooting steps for Linux users.
  • List cross-platform tools (Azure CLI, Terraform) before Windows-specific tools (PowerShell, ARM templates) in 'Related content'.
  • Include notes or links for Linux-specific considerations, such as SELinux, firewall configuration, or systemd-resolved DNS integration.
GitHub Create Pull Request
App Service Create a scheduled WebJob with prebuilt samples ...s/blob/main/articles/app-service/quickstart-webjobs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Windows as the first platform in prerequisites and examples, providing more Windows-specific sample types (CMD, Batch, PowerShell, F#) than Linux, and including Windows-only scripting languages and tools. Linux examples are limited to cross-platform languages and Bash, with no Linux equivalents for CMD, Batch, PowerShell, or F#. The structure and ordering prioritize Windows users and tools, potentially making Linux users feel secondary.
Recommendations
  • Present Linux and Windows platforms with equal prominence in prerequisites and sample tables.
  • Add Linux equivalents for Windows-specific samples where possible (e.g., provide shell scripts for tasks shown in CMD/Batch/PowerShell).
  • Include Linux-specific scripting languages or tools (e.g., Perl, Ruby, or shell variants) to match the breadth of Windows examples.
  • Ensure that instructions and examples for both platforms are parallel in detail and order.
  • Consider starting with a cross-platform introduction before splitting into OS-specific tabs.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses Microsoft Graph as the user | Azure ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing installation instructions using Visual Studio's Package Manager Console (PowerShell) and referencing Visual Studio tooling before mentioning cross-platform .NET CLI commands. There are no explicit Linux or cross-platform editor instructions, and the examples assume a Windows development environment. No Linux-specific package installation or editor guidance is provided.
Recommendations
  • Add explicit instructions for installing NuGet packages using the .NET CLI first, emphasizing its cross-platform nature.
  • Include examples for popular Linux-based editors (e.g., VS Code, JetBrains Rider) and terminal usage.
  • Clarify that all .NET CLI commands work on Linux, macOS, and Windows, and provide a section on developing and running the sample on Linux.
  • Avoid referencing Visual Studio tooling (like Package Manager Console) before cross-platform alternatives.
  • Add troubleshooting notes or links for Linux-specific issues (e.g., permissions, environment setup).
GitHub Create Pull Request
Active Directory B2C Secure APIs used for API connectors in Azure AD B2C .../main/articles/active-directory-b2c/secure-rest-api.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily in the certificate creation section, where only PowerShell is mentioned as the method for preparing a self-signed certificate. There is no mention of Linux or cross-platform alternatives (such as OpenSSL) for certificate generation. The rest of the documentation is largely platform-neutral, focusing on Azure portal UI and XML configuration, but the lack of Linux/macOS command-line examples for certificate management is a notable omission.
Recommendations
  • Add instructions and examples for generating self-signed certificates using OpenSSL, which is available on Linux, macOS, and Windows.
  • Explicitly mention that certificate creation can be performed on any OS and provide links or steps for both PowerShell and OpenSSL.
  • Where PowerShell is referenced, clarify that it is one option and suggest alternatives for non-Windows users.
  • Review any referenced includes (such as active-directory-b2c-create-self-signed-certificate.md) to ensure Linux/macOS parity.
  • Consider adding a table or section comparing certificate creation methods across platforms.
GitHub Create Pull Request
App Testing Tutorial: Run end-to-end tests with Playwright Workspaces ...playwright-workspaces/tutorial-run-end-to-end-tests.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively using PowerShell syntax for command-line examples (e.g., 'cd', 'git clone', 'npm install'), without providing Linux/macOS shell equivalents. There is no mention of Linux-specific instructions, nor are alternative shell commands (such as Bash) shown. The prerequisites and environment setup steps do not address platform differences, and Windows-centric tools and patterns (such as PowerShell prompt style) are used throughout.
Recommendations
  • Provide command-line examples using both PowerShell (Windows) and Bash (Linux/macOS) syntax, or use a neutral format where possible.
  • Explicitly mention platform differences in prerequisites and installation steps (e.g., Azure CLI installation commands for Linux, macOS, and Windows).
  • Include notes or sections for Linux/macOS users, such as alternative commands for navigation and environment setup.
  • Avoid using only PowerShell code blocks for generic commands; use 'shell' or 'bash' where appropriate.
  • Clarify that the instructions are cross-platform and provide links or guidance for platform-specific issues.
GitHub Create Pull Request
Application Gateway Tutorial: Configure an Application Gateway with TLS termination using the Azure portal ...main/articles/application-gateway/create-ssl-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows environments. All certificate creation and export steps use Windows PowerShell cmdlets (New-SelfSignedCertificate, Export-PfxCertificate), with no mention of Linux or cross-platform alternatives. The VM creation steps exclusively use Windows Server images, and IIS installation is performed via PowerShell. There are no examples or instructions for Linux users (e.g., using OpenSSL for certificates, deploying Linux VMs, or installing Apache/Nginx). Windows tools and patterns are mentioned exclusively and first, with no Linux parity.
Recommendations
  • Provide equivalent instructions for Linux users, such as using OpenSSL to create and export self-signed certificates.
  • Include examples for deploying Linux-based backend VMs (e.g., Ubuntu, CentOS) and installing a web server like Apache or Nginx.
  • Offer cross-platform command-line examples (e.g., Bash, Azure CLI) alongside PowerShell.
  • Mention Linux tools and patterns (e.g., file paths, certificate management) where relevant.
  • Clearly indicate that both Windows and Linux backend servers are supported, and provide parity in documentation steps.
GitHub Create Pull Request
Application Gateway Private Application Gateway deployment ...tion-gateway/application-gateway-private-deployment.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell examples and references before Azure CLI, and by using terminology and screenshots that are closely aligned with Windows-centric workflows (e.g., Azure portal navigation, PowerShell cmdlets). There are no explicit Linux shell or Bash examples, and the CLI instructions are less detailed compared to PowerShell. The documentation also references Windows tools and patterns (PowerShell, Azure portal) more prominently than cross-platform or Linux-native alternatives.
Recommendations
  • Provide Bash/Linux shell examples alongside PowerShell, especially for Azure CLI commands.
  • Ensure CLI instructions are as detailed and prominent as PowerShell instructions, including output examples and troubleshooting notes.
  • Include screenshots or instructions for Azure portal navigation on non-Windows platforms (e.g., browser on Linux/macOS).
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide platform-specific tips where relevant.
  • Consider adding ARM template and Terraform examples for key configuration steps, as these are cross-platform and popular in Linux environments.
  • Review terminology to avoid Windows-centric language and ensure parity for Linux administrators.
GitHub Create Pull Request
Application Gateway Manage traffic to App Service ...main/articles/application-gateway/configure-web-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides extensive PowerShell-based examples for all configuration steps, but does not include equivalent Linux shell (Bash/CLI) commands or scripts. All command-line automation is shown using Azure PowerShell, which is most commonly used on Windows. There is no mention of Azure CLI (az), Bash, or Linux-native tooling, and no examples for Linux users. This creates a bias toward Windows users and workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for each configuration step alongside PowerShell scripts.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance for Linux/macOS users.
  • Include Bash script examples for testing (e.g., using curl instead of Invoke-WebRequest).
  • Reference cross-platform tools and patterns where possible, rather than Windows-centric ones.
  • Ensure troubleshooting and testing instructions include Linux-compatible commands.
GitHub Create Pull Request
Application Gateway Troubleshoot Bad Gateway errors - Azure Application Gateway ...ion-gateway/application-gateway-troubleshooting-502.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples and referencing Windows-centric tools and patterns (e.g., IIS, PowerShell cmdlets, classic VM endpoints). There are no CLI (az), Bash, or Linux-specific troubleshooting commands or examples. Windows tools and terminology are mentioned before or instead of Linux equivalents, and Linux troubleshooting steps are missing throughout.
Recommendations
  • Add Azure CLI (az) and Bash examples alongside PowerShell for all resource queries and configuration checks.
  • Include troubleshooting steps and examples for Linux-based backend servers (e.g., Apache, Nginx), not just IIS.
  • Reference Linux firewall tools (e.g., iptables, ufw) and commands for checking port and network connectivity.
  • Provide parity in endpoint configuration guidance for Linux VMs, not just classic Windows VM endpoints.
  • Ensure that documentation language and examples are platform-neutral or explicitly cover both Windows and Linux scenarios.
GitHub Create Pull Request
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples for registering/unregistering the preview and installing backend software use Azure PowerShell and Windows-specific tools (e.g., Add-WindowsFeature for IIS). The virtual machine creation steps exclusively use Windows Server as the example OS, with no mention of Linux alternatives or equivalent commands for Bash/CLI. There are no Linux VM setup instructions, nor examples for installing a web server on Linux. Windows tools and patterns are presented exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
  • Provide equivalent Azure CLI (az) commands for registering/unregistering the preview, alongside PowerShell examples.
  • Include Linux VM creation steps in the backend pool section, such as creating Ubuntu or other Linux VMs.
  • Add instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs, using Bash scripts or Azure VM extensions.
  • Show how to add Linux VMs to the backend pool, and demonstrate testing the application gateway with Linux-based backends.
  • Ensure screenshots and walkthroughs are OS-neutral or include both Windows and Linux variants.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend servers, and provide parity in documentation examples.
GitHub Create Pull Request
Active Directory B2C Manage directory size quota in Azure Active Directory B2C ...ive-directory-b2c/tenant-management-directory-quota.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides only a PowerShell script for monitoring directory quota usage, with no equivalent example for Linux or cross-platform tools. The use of PowerShell and Windows-specific scripting patterns is presented as the sole method, implicitly prioritizing Windows environments and omitting guidance for Linux or macOS administrators.
Recommendations
  • Add equivalent examples using cross-platform tools such as curl and jq, or provide a Bash script for Linux/macOS users.
  • Explicitly mention that the API call can be made from any platform and provide generic HTTP request instructions.
  • Include notes or links to platform-agnostic Microsoft Graph SDKs (e.g., Python, Node.js) for broader accessibility.
  • Present Windows and Linux/macOS instructions side-by-side or in separate tabs to ensure parity and avoid platform bias.
GitHub Create Pull Request
Active Directory B2C Access and review audit logs .../main/articles/active-directory-b2c/view-audit-logs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page provides only a PowerShell script example for accessing Azure AD B2C audit logs programmatically, with no equivalent example for Linux users (e.g., Bash, curl, Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) indicate a Windows-centric approach. No Linux-native tools or cross-platform alternatives are mentioned, and the scripting section is introduced without consideration for non-Windows environments.
Recommendations
  • Add a Bash/curl example for querying the Microsoft Graph API to retrieve audit logs, demonstrating authentication and pagination.
  • Include a Python script example using the 'requests' library to show cross-platform programmatic access.
  • Explicitly mention that the API can be accessed from any platform and provide guidance for Linux and macOS users.
  • Reference Linux-native tools (e.g., curl, wget) and provide sample commands for downloading and processing logs.
  • Reorder or parallelize scripting examples so that Windows and Linux approaches are presented together, ensuring parity.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the SQL backend, referencing SQL Server Management Studio (a Windows-only tool) for client connectivity, and omitting any mention of Linux-based SQL server deployment or Linux-compatible client tools. All examples and screenshots are based on Windows environments, with no guidance for Linux users.
Recommendations
  • Include instructions for deploying SQL Server on Linux (e.g., Ubuntu) as an alternative backend VM.
  • Provide examples of connecting to the Application Gateway using Linux-compatible SQL clients such as sqlcmd, Azure Data Studio, or DBeaver.
  • Add screenshots and command-line examples for Linux environments where appropriate.
  • Explicitly mention cross-platform options and parity in prerequisites and tool recommendations.
  • Ensure that resource cleanup instructions cover both Windows and Linux scenarios.
GitHub Create Pull Request
Application Gateway Configure Request and Response Buffers ...lob/main/articles/application-gateway/proxy-buffers.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides configuration examples using Azure CLI, PowerShell, and ARM templates. PowerShell examples are detailed and cover both creation and update scenarios, while no equivalent Linux shell (bash) or cross-platform scripting examples are given. PowerShell is a Windows-centric tool, and its usage is emphasized with multiple code blocks and update scenarios. There is no mention of Linux-specific tools or patterns, such as Bash scripting or Cloud Shell usage. The reference to Azure SDK for .NET further reinforces a Windows-centric approach.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for updating existing Application Gateways.
  • Clarify that Azure CLI commands work cross-platform and provide sample usage in Bash.
  • Include references to cross-platform SDKs (e.g., Python, Java) in addition to .NET.
  • Mention Azure Cloud Shell as a platform-neutral way to run CLI commands.
  • Balance PowerShell and CLI coverage, ensuring Linux users are not left out in update scenarios.
GitHub Create Pull Request
API Center Perform API linting and analysis - Azure API Center ...ain/articles/api-center/enable-api-analysis-linting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides command examples for both bash and PowerShell, but PowerShell syntax is consistently presented immediately after bash, and sometimes with more detail. There is a strong reliance on Azure CLI and Visual Studio Code, which are cross-platform, but the documentation does not mention Linux-specific tools or workflows (e.g., native Linux editors, package managers, or automation patterns). Portal instructions assume familiarity with the Azure Portal UI, which is platform-agnostic but often used on Windows. No explicit Linux desktop screenshots or references are present. There are no examples using Linux-native shells (e.g., zsh, fish), nor are there troubleshooting tips for Linux environments.
Recommendations
  • Present bash/Linux shell examples before PowerShell, or alternate the order to avoid implicit Windows-first bias.
  • Include explicit references to Linux environments, such as using Linux package managers (apt, yum) for installing prerequisites.
  • Add troubleshooting notes for common Linux issues (e.g., file permissions, environment variables).
  • Mention or show usage with Linux-native editors (e.g., Vim, Emacs) and terminal emulators.
  • Include screenshots or instructions from a Linux desktop environment where relevant.
  • Clarify that all CLI commands work on Linux, and provide guidance for any platform-specific differences.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exhibits a strong Windows bias. All migration instructions, examples, and scripts are provided exclusively using PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. Script installation and usage patterns are tailored to Windows/PowerShell environments, and there is no guidance for Linux or macOS users. The documentation assumes familiarity with PowerShell and Windows-centric workflows, omitting equivalent steps for cross-platform or Linux-native environments.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands and scripts, including examples for Linux/macOS terminals.
  • Include Bash script samples or instructions for running migration tasks on Linux.
  • Document how to use Azure Cloud Shell (Bash) for migration, not just PowerShell.
  • Explicitly state cross-platform compatibility of scripts, or provide platform-specific instructions where needed.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, module installation).
  • List prerequisites and installation steps for Linux and macOS environments alongside Windows.
  • Ensure all downloadable scripts are tested and supported on Linux/macOS PowerShell (pwsh) and Azure CLI.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using a Resource Manager template .../articles/application-gateway/quick-create-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell commands for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting Linux-based examples or alternatives (such as using Apache/Nginx or Bash/Azure CLI for resource management). No Linux-specific instructions or parity is offered for users deploying or validating on Linux VMs.
Recommendations
  • Provide equivalent resource cleanup instructions using Azure CLI (az group delete) and Bash shell commands.
  • Include validation steps for Linux VMs, such as installing Apache or Nginx and testing with curl or a browser.
  • Offer examples for both Windows and Linux VM configurations in the ARM template and validation sections.
  • Ensure that references to tools (e.g., IIS, PowerShell) are balanced with Linux alternatives and not presented as the default or only option.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts for migration tasks, without mentioning or providing examples for Azure CLI, Bash, or other cross-platform tools. There are no Linux or platform-agnostic migration instructions or examples, and the only automation guidance is centered on PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands or scripts for all migration steps, ensuring Linux and macOS users have clear guidance.
  • Explicitly mention that migration can be performed from any OS, and clarify if PowerShell Core (cross-platform) is supported, or provide Bash alternatives.
  • Include examples or references for Bash scripts or automation using other cross-platform tools (e.g., Terraform, ARM templates) where applicable.
  • Reorder or supplement sections to present cross-platform options (Azure CLI, Bash) before or alongside PowerShell, to avoid implying Windows is the primary or only supported environment.
GitHub Create Pull Request
Application Gateway Redirect overview for Azure Application Gateway ...main/articles/application-gateway/redirect-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias by referencing only Windows-centric tools and workflows (e.g., Azure portal, PowerShell tutorial), and omitting Linux-specific examples or CLI instructions. The 'Next steps' section links exclusively to a PowerShell-based tutorial, with no mention of Azure CLI or Bash alternatives. There is no guidance for Linux users or parity in example commands.
Recommendations
  • Add equivalent Azure CLI and Bash examples for configuring redirects, alongside PowerShell instructions.
  • Include links to tutorials for Linux users, such as 'Configure URL redirection using Azure CLI' or 'Configure URL redirection using Bash'.
  • Ensure that references to configuration steps do not prioritize Windows tools (PowerShell, Azure portal) over cross-platform options.
  • Explicitly mention that Application Gateway configuration can be performed from Linux, macOS, and Windows environments, and provide parity in documentation.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of equivalent Linux or cross-platform approaches. There are no Bash, Azure CLI, or Linux-native certificate generation examples, and prerequisites assume a Windows/PowerShell environment. This may exclude or inconvenience users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Azure CLI (az) examples alongside PowerShell for each step.
  • Include Linux/macOS instructions for generating self-signed certificates (e.g., using openssl).
  • Clarify that Azure PowerShell can be used cross-platform, but also offer Bash/CLI alternatives.
  • Mention and link to platform-agnostic tools and documentation where possible.
  • Reorder or parallelize examples so that Windows and Linux approaches are presented together, not Windows first.
GitHub Create Pull Request
API Center Synchronize APIs from Azure API Management instance ...articles/api-center/synchronize-api-management-apis.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Azure CLI examples are described as runnable in both PowerShell and bash, but the explicit mention of PowerShell first and the lack of concrete bash-specific examples or Linux shell screenshots suggest a Windows-first approach. There are no Linux-specific instructions or troubleshooting notes, and portal instructions are generic but the CLI section does not show parity for Linux users (e.g., variable syntax differences, environment setup).
Recommendations
  • Provide explicit bash/Linux shell examples alongside PowerShell, especially where syntax differs.
  • Include screenshots or instructions that reflect Linux environments (e.g., terminal screenshots, common Linux shell usage patterns).
  • Add troubleshooting notes or prerequisites relevant to Linux users (e.g., package dependencies, environment setup for Azure CLI on Linux).
  • Ensure that references to running CLI commands do not prioritize PowerShell over bash; consider listing bash first or equally.
  • Mention any platform-specific considerations (e.g., authentication, managed identity setup) for Linux users.
GitHub Create Pull Request
API Center Quickstart - Create Your Azure API Center - ARM Template .../articles/api-center/set-up-api-center-arm-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates, but PowerShell is a Windows-centric tool and is presented alongside CLI without clarifying platform parity. There is no mention of Linux-specific patterns (e.g., Bash scripting, native Linux tools), and instructions for uploading files reference Azure Cloud Shell generically, without explicit Linux guidance. The page does not offer Linux-first or Linux-specific examples, and PowerShell is given equal prominence despite its Windows bias.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused (though available on Linux, but less commonly used).
  • Provide Linux-specific instructions for uploading files (e.g., using scp, curl, or native shell commands) to Azure Cloud Shell or local environments.
  • Add Bash script examples for ARM template deployment, especially for Linux users.
  • Clarify in the prerequisites section which tools are recommended for Linux users (e.g., Azure CLI, Bash) and which are Windows-centric (PowerShell).
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) to reduce Windows-first bias.
GitHub Create Pull Request
API Center Workflow automation after API registration - Azure API Center ...in/articles/api-center/set-up-notification-workflow.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Azure portal and Microsoft Teams, both of which are primarily Windows-centric tools. All workflow steps are described using the Azure portal UI, with no mention of CLI, REST API, or automation options that would be more accessible to Linux users. There are no examples using bash, Azure CLI, or Linux-native tools, and all notification workflows are shown with Microsoft Teams, with no mention of alternatives like Slack or email. Power Automate is referenced, but only as a similar option, not as an example. The documentation assumes use of the Azure portal, which is most fully featured on Windows, and does not provide parity for Linux users who may prefer command-line or non-GUI approaches.
Recommendations
  • Provide equivalent workflow automation steps using Azure CLI and/or REST API, with bash script examples for Linux users.
  • Include instructions for setting up event subscriptions and managed identities using command-line tools.
  • Offer notification workflow examples using open standards (e.g., email via SMTP, Slack webhooks) in addition to Microsoft Teams.
  • Reference and demonstrate automation options that are platform-agnostic, such as using curl, jq, or other Linux-native utilities.
  • Explicitly mention cross-platform compatibility and provide links to documentation for Linux/macOS users.
  • Where possible, show both GUI (portal) and CLI/automation approaches side by side.
GitHub Create Pull Request
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
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are given first and in greater detail, with variable setup and multiple access scenarios. The CLI (Bash) examples are present but are listed after PowerShell, and REST API examples are provided as well. The documentation references Azure PowerShell as a prerequisite and mentions installing it, but does not mention Linux-specific tools or shell environments. There is no mention of Linux-specific considerations, nor are there examples using native Linux scripting tools (e.g., shell scripts, cron for automation). The use of PowerShell and its cmdlets is emphasized, which may be less familiar to Linux users.
Recommendations
  • Present CLI (Bash) examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Expand CLI (Bash) examples to include managed identity scenarios, matching the detail given to PowerShell.
  • Add notes or examples for automating backup/restore using native Linux tools (e.g., shell scripts, cron jobs).
  • Reference Linux environments explicitly in prerequisites, mentioning that Azure CLI and REST API methods work cross-platform.
  • Consider including troubleshooting notes or tips for Linux users (e.g., permissions, environment variables).
  • Balance the depth of PowerShell and CLI examples to ensure Linux users have equal guidance.
GitHub Create Pull Request
API Management Add a Custom CA Certificate - API Management | Microsoft Docs ...api-management/api-management-howto-ca-certificates.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, with no mention of Linux-native tools or cross-platform alternatives (such as Azure CLI or REST API usage). This suggests a bias towards Windows environments and tools, potentially making it less accessible for Linux users.
Recommendations
  • Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux.
  • Include REST API example calls for certificate management, which can be used from any OS.
  • Explicitly mention Linux-compatible workflows and tools, such as using curl for REST API calls or az CLI commands.
  • Reorder or parallelize examples so that Windows and Linux methods are presented together, rather than Windows-first.
  • Clarify that PowerShell commands can be run on Linux (if true), or provide Bash equivalents.
GitHub Create Pull Request
API Management Use API Management in a virtual network with Azure Application Gateway ...pi-management-howto-integrate-internal-vnet-appgateway.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Azure PowerShell for all example commands and automation steps. All code samples are written in PowerShell, and file paths use Windows conventions (e.g., C:\Users\Contoso\). There is no mention of Bash, Azure CLI, or Linux shell alternatives, nor are Linux/macOS file path conventions or certificate management tools discussed. The prerequisites explicitly require Azure PowerShell, and no Linux-native tools or cross-platform approaches are presented.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all resource creation and configuration steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash shell script examples alongside PowerShell, especially for variable setting and automation.
  • Use generic or Linux/macOS-friendly file paths in examples (e.g., /home/contoso/) or note both Windows and Linux conventions.
  • Discuss certificate management using OpenSSL or Linux-native tools, and provide instructions for generating and handling certificates on Linux.
  • Explicitly state that all steps can be performed on Linux/macOS and link to cross-platform tool installation guides.
  • Add a section on troubleshooting and verification using Linux tools (e.g., dig, nslookup, curl) and mention hosts file locations for Linux/macOS (/etc/hosts).
  • Where PowerShell is required, clarify that PowerShell Core is available on Linux/macOS, and provide installation instructions.
GitHub Create Pull Request
API Management How to Log Events to Azure Event Hubs in Azure API Management | Microsoft Docs .../api-management/api-management-howto-log-event-hubs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples exclusively for command-line logger creation, mentioning Azure PowerShell as a primary tool, and omitting equivalent Linux/Unix CLI examples (such as Azure CLI or Bash). Windows-centric tools and patterns (PowerShell, portal navigation) are referenced before or instead of cross-platform alternatives, leaving Linux users without direct guidance for command-line operations.
Recommendations
  • Add Azure CLI examples for logger creation and management, alongside PowerShell, to ensure parity for Linux/macOS users.
  • Explicitly mention cross-platform tools (Azure CLI, Bash scripting) in the 'Create an API Management logger' section and provide usage examples.
  • Where PowerShell is referenced, clarify that it is Windows-specific and offer alternative instructions for Linux/macOS environments.
  • Review portal navigation instructions to ensure terminology and steps are not Windows-centric and are applicable to all platforms.
  • Include a note or table summarizing tool availability and platform compatibility for each example.
GitHub Create Pull Request
API Management Secure API Management Backend Using Client Certificate Authentication ...management/api-management-howto-mutual-certificates.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by providing PowerShell cmdlet examples (New-AzApiManagementBackend, Set-AzApiManagementBackend) for disabling certificate chain validation, without offering equivalent instructions or examples for Linux users (e.g., Azure CLI, Bash, or other cross-platform tools). Windows-specific tooling is referenced exclusively in the example, and no alternative is presented for Linux or macOS users.
Recommendations
  • Add Azure CLI examples for certificate management and backend configuration, especially for disabling certificate chain validation.
  • Include Bash or shell script equivalents for relevant operations.
  • Explicitly mention cross-platform options and tools, and provide guidance for Linux/macOS users alongside PowerShell instructions.
  • Ensure that REST API examples are accompanied by sample requests using curl or similar cross-platform tools.
  • Review and update documentation to present Windows and Linux options in parallel, rather than focusing on Windows tools first or exclusively.
GitHub Create Pull Request
API Management Deploy Azure API Management Instance to External Virtual Network ...icles/api-management/api-management-using-with-vnet.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by referencing Azure portal (a GUI often used on Windows) as the first and main method for configuration, and by linking to related VPN Gateway documentation that specifically mentions PowerShell (a Windows-centric tool) in its title. There are no explicit Linux CLI (e.g., Bash, Azure CLI) examples or instructions, nor are Linux tools or patterns mentioned. The Resource Manager template method is platform-agnostic, but no Linux-specific guidance is provided.
Recommendations
  • Add step-by-step instructions for enabling virtual network connectivity using Azure CLI (az commands), which are cross-platform and commonly used on Linux.
  • Where PowerShell is referenced in related links, provide equivalent Bash/Azure CLI examples or link to Linux-focused documentation.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and clarify any platform-specific differences.
  • Include troubleshooting steps or network configuration examples using Linux tools (e.g., curl, dig, ip, netcat) for verifying connectivity.
  • Ensure that screenshots and UI references are supplemented with CLI alternatives for users who do not use the Azure portal.
GitHub Create Pull Request
API Management Use Managed Identities in Azure API Management | Microsoft Docs ...t/api-management-howto-use-managed-service-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for CLI-based operations, referencing PowerShell installation, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell approach is presented before any mention of Linux-friendly alternatives, and no Linux-specific tools or shell commands are discussed. This may disadvantage users on Linux or macOS platforms who prefer or require Azure CLI or Bash scripting.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including resource creation, identity assignment, and updates.
  • Explicitly mention that Azure CLI is cross-platform and provide installation instructions or links for Linux/macOS users.
  • Where PowerShell is referenced, also reference Bash or shell scripting for parity.
  • Ensure that ARM template examples are accompanied by instructions for deploying them using Azure CLI (az deployment), not just PowerShell.
  • Review all sample code and walkthroughs to ensure Linux/macOS users are not required to use Windows-specific tools.
  • Consider reordering sections so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside PowerShell.
GitHub Create Pull Request
API Management Revisions in Azure API Management | Microsoft Docs ...in/articles/api-management/api-management-revisions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) as the only command-line automation examples, with no mention of Azure CLI, Bash, or other cross-platform tools. There are no Linux-specific or cross-platform command-line instructions, and the only automation guidance is through PowerShell, which is most commonly associated with Windows environments.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell cmdlets mentioned, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell Core is available cross-platform, if PowerShell examples are retained, and provide installation guidance for non-Windows users.
  • Add Bash or shell script examples where applicable, especially for common automation tasks.
  • Reorder automation tool references so that cross-platform tools (Azure CLI) are mentioned before or alongside PowerShell.
  • Include a note or section addressing Linux/macOS users, ensuring parity in instructions and tool recommendations.
GitHub Create Pull Request
API Management Securely Access Products and APIs - Microsoft Entra Applications - Azure API Management ...docs/blob/main/articles/api-management/applications.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell scripts for token generation and API calls, with no equivalent examples for Linux or cross-platform tools such as curl or bash. The instructions and screenshots are centered around the Azure Portal, which is primarily accessed via a web browser but is often associated with Windows workflows. There is no mention of Linux command-line alternatives, nor are there examples using platform-neutral tools. The PowerShell requirement is explicitly stated, and no parity is offered for Linux users.
Recommendations
  • Provide equivalent examples using curl and bash for token generation and API calls, suitable for Linux/macOS environments.
  • Add notes clarifying that the Azure Portal is accessible from any OS/browser, and highlight any CLI alternatives (e.g., Azure CLI commands) for steps that can be performed outside the portal.
  • Include troubleshooting steps or references for Linux users, such as handling authentication with open-source tools.
  • Ensure that examples are presented in a platform-neutral way, or provide both Windows (PowerShell) and Linux (bash/curl) options side-by-side.
  • Review and update any references to Windows-specific tools or workflows to include Linux equivalents where possible.
GitHub Create Pull Request
API Management Manage Azure API Management using Azure Automation ...les/api-management/automation-manage-api-management.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively references Azure PowerShell cmdlets and PowerShell workflow scripts for managing Azure API Management with Azure Automation. There are no examples or mentions of Linux-friendly alternatives such as Azure CLI, Bash scripts, or cross-platform automation tools. The links and samples provided are PowerShell-centric, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Include examples using Azure CLI for managing API Management within Azure Automation.
  • Provide Bash or Python script samples that can be used in Azure Automation runbooks.
  • Mention cross-platform compatibility and clarify whether Azure Automation supports non-PowerShell runbooks.
  • Add links to documentation or tutorials for Linux/macOS users, highlighting equivalent automation workflows.
  • Ensure that references to PowerShell are balanced with references to other tools, and avoid presenting PowerShell as the only or primary option.
GitHub Create Pull Request
API Management Set up basic authentication to developer portal ...pi-management/developer-portal-basic-authentication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell cmdlets (specifically New-AzApiManagementUser) as the only CLI example for adding users, without mentioning cross-platform alternatives such as Azure CLI or REST API. The use of PowerShell is Windows-centric, and no Linux-specific or platform-neutral command-line instructions are provided. The Azure portal UI is also referenced, which is platform-agnostic, but the only automation example is Windows-oriented.
Recommendations
  • Add equivalent examples using Azure CLI (az apim user create) if available, which is cross-platform and widely used on Linux.
  • Include REST API instructions for user creation to provide a platform-neutral automation option.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be referenced, and provide installation guidance.
  • Present CLI examples in parallel (PowerShell and Azure CLI) or prioritize platform-neutral options before Windows-specific tools.
  • Review other sections for similar patterns and ensure Linux parity in all automation and scripting guidance.
GitHub Create Pull Request
API Management Self-Host the API Management Developer Portal .../articles/api-management/developer-portal-self-host.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily in the instructions for uploading static files to Azure Blob Storage, where it explicitly mentions 'Windows Command Prompt, PowerShell, or other command shell' and does not provide Linux-specific examples or mention Linux terminals first. The general pattern is to mention Windows tools and environments before Linux equivalents, and there are no explicit Linux-specific instructions or troubleshooting tips provided. While most commands are cross-platform (npm, git, Azure CLI), the narrative and examples tend to assume a Windows environment.
Recommendations
  • Explicitly mention Linux and macOS terminals alongside Windows Command Prompt and PowerShell when referring to command shells.
  • Provide Linux/macOS-specific examples or notes where commands or paths may differ (e.g., file paths, shell syntax).
  • Add troubleshooting tips for common Linux/macOS issues (such as permissions, environment variables, etc.).
  • Ensure parity by listing Linux instructions first or equally with Windows, especially in sections where OS-specific tools are referenced.
  • Include screenshots or UI references for Azure Portal that are OS-agnostic or show both Windows and Linux browsers.
  • Clarify that all CLI commands are cross-platform and highlight any OS-specific caveats.
GitHub Create Pull Request
API Management Azure API Management - API version retirements (June 2024) | Microsoft Docs ...nt/breaking-changes/api-version-retirement-sep-2023.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell (a Windows-centric tool) prominently alongside Azure CLI, and providing detailed PowerShell commands before or in addition to cross-platform alternatives. There is a lack of explicit Linux-specific guidance, and Windows tools/patterns (PowerShell, Azure portal) are mentioned without highlighting Linux equivalents or usage nuances. No Linux shell examples (e.g., Bash) are provided, and the update instructions focus on PowerShell and Azure CLI, which, while cross-platform, are often associated with Windows workflows.
Recommendations
  • Include explicit Linux/Bash shell examples for checking and updating Azure CLI and SDK versions.
  • Clarify that Azure CLI and Terraform are cross-platform and provide sample commands for Linux/macOS environments.
  • Add guidance for updating tools and SDKs on Linux, including package manager instructions (e.g., apt, yum, Homebrew).
  • Balance PowerShell instructions with equivalent Bash or shell commands where possible.
  • Mention any platform-specific considerations for the Azure portal or REST API usage on non-Windows systems.
GitHub Create Pull Request
API Management Manage Connections for End Users - Azure API Management | Microsoft Docs ...es/api-management/credentials-how-to-user-delegated.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell commands for provisioning the service principal, referencing the AzureAD PowerShell module, and omitting equivalent instructions for Linux/macOS users (e.g., Azure CLI or Bash). The use of PowerShell is assumed throughout, and no alternative cross-platform tooling or examples are provided. The prerequisites and steps focus on Windows-centric tools and patterns, with no mention of Linux or macOS workflows.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash shell examples for command-line steps, especially for service principal provisioning and authentication.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide links or guidance for installing and using Azure CLI on those platforms.
  • Where PowerShell is referenced, clarify that it is available on Linux and macOS, or provide alternative commands for those environments.
  • Review all steps for assumptions of Windows-only tools and add parity for Linux/macOS users.
GitHub Create Pull Request
API Management Developer portal - Frequently asked questions ...b/main/articles/api-management/developer-portal-faq.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for role assignment and management tasks, and by referencing a Windows batch script (cleanup.bat) for portal cleanup. No Linux shell (bash) or cross-platform CLI examples are provided for these operations, and Windows-specific tools and patterns (PowerShell, .bat files) are mentioned without Linux equivalents.
Recommendations
  • Provide Azure CLI or Bash script equivalents for all PowerShell examples, especially for role assignment and management tasks.
  • Include instructions for running cleanup operations on Linux/macOS, such as providing a .sh script or cross-platform commands.
  • Clearly indicate cross-platform compatibility for all scripts and tools, and mention any OS-specific requirements.
  • Where possible, use platform-neutral language and examples (e.g., Azure CLI, REST API calls) before or alongside Windows-specific tools.
GitHub Create Pull Request
API Management Import an OpenAPI specification to Azure API Management | Microsoft Docs ...ob/main/articles/api-management/import-api-from-oas.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides examples for Azure Portal (web), Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion as a first-class example (alongside CLI) reflects a Windows bias. There are no explicit Linux-specific examples, nor are Linux-native tools or shell patterns (e.g., bash, curl, scripting) mentioned. The PowerShell example is detailed and appears before any mention of Linux alternatives. The prerequisites section lists both Azure CLI and Azure PowerShell, but does not clarify platform parity or provide Linux-specific guidance.
Recommendations
  • Add explicit Linux shell/bash examples for importing OpenAPI specifications, such as using curl or wget in combination with Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide sample commands in bash/zsh syntax.
  • Mention that Azure PowerShell is available on Linux and macOS, but highlight any platform-specific differences.
  • Provide troubleshooting or environment setup notes for Linux users, such as package installation or authentication nuances.
  • Consider reordering examples to present CLI/bash first, then PowerShell, to avoid implicit Windows-first bias.
GitHub Create Pull Request
API Management Defend API Management Against DDoS Attacks ...rticles/api-management/protect-with-ddos-protection.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell-specific instructions (for enabling DDoS IP Protection) and linking to a PowerShell-based guide, without providing equivalent Linux/CLI examples. The instructions for enabling DDoS Protection focus on the Azure portal, which is platform-agnostic, but when command-line automation is referenced, only PowerShell is mentioned. There are no Bash/Azure CLI examples or explicit Linux guidance.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell instructions for enabling DDoS IP Protection.
  • Explicitly mention that both Windows and Linux users can use the Azure portal for configuration.
  • Where automation is discussed, provide Bash/Linux shell scripts or Azure CLI equivalents to PowerShell commands.
  • Link to cross-platform documentation for command-line operations, not just PowerShell guides.
GitHub Create Pull Request
API Management Import SOAP API to Azure API Management | Microsoft Docs ...s/blob/main/articles/api-management/import-soap-api.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but the PowerShell example is given equal prominence and detail as the CLI example. The prerequisites section lists Azure PowerShell as a required tool alongside Azure CLI, which may imply parity, but PowerShell is a Windows-centric tool (despite cross-platform support, most users associate it with Windows). There are no Linux-specific instructions, nor is there mention of Linux-native tools or shell scripting alternatives. The documentation does not clarify that both CLI and PowerShell are cross-platform, nor does it provide guidance for Linux users who may not use PowerShell.
Recommendations
  • Explicitly state that both Azure CLI and Azure PowerShell are available cross-platform, and clarify installation steps for Linux and macOS users.
  • Provide Linux shell (bash) examples for common tasks, or at least mention that Azure CLI commands work natively in Linux terminals.
  • Reorder examples to present Azure CLI before PowerShell, or clarify that CLI is the recommended cross-platform approach.
  • Add a note for Linux users that PowerShell Core is available for Linux, with installation instructions or links.
  • Consider including troubleshooting tips or environment setup guidance for Linux users, such as file path conventions and authentication differences.
GitHub Create Pull Request
API Management Quickstart - Create Azure API Management instance - Terraform ...b/main/articles/api-management/quickstart-terraform.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but does not include explicit Linux shell examples (e.g., bash) or mention Linux-specific tools. PowerShell is presented as a primary option alongside Azure CLI, which is cross-platform, but the PowerShell example uses Windows-style variable assignment and syntax. There is no mention of Linux-specific patterns, nor are Linux shell commands (such as bash or sh) shown. The prerequisites mention Azure PowerShell requirements before showing any Linux alternatives.
Recommendations
  • Add explicit bash/Linux shell examples for verification steps, using standard bash variable assignment and command syntax.
  • Clarify that Azure CLI is cross-platform and provide examples of running commands on Linux/macOS terminals.
  • Include notes or sections for Linux users, such as installing Terraform and Azure CLI on Linux.
  • Avoid Windows-centric variable assignment (e.g., $var=...) in PowerShell examples when presenting cross-platform instructions; consider showing bash equivalents.
  • Ensure that prerequisites and tooling instructions mention Linux/macOS options with equal prominence to Windows/PowerShell.
GitHub Create Pull Request
API Management Azure API Management policy reference - set-backend-service | Microsoft Docs .../articles/api-management/set-backend-service-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell as a management tool for backend entities, without referencing equivalent Linux-native tools (such as Azure CLI or Bash scripting). No Linux or cross-platform examples are provided for backend management. The only management tooling examples are Windows-centric, and there is no parity in example coverage for Linux users.
Recommendations
  • Add references and links to Azure CLI commands for backend management alongside PowerShell.
  • Include example commands for backend management using Bash or shell scripting, where applicable.
  • Explicitly state that backend management can be performed on Linux, macOS, and Windows, and provide parity in documentation for all platforms.
  • Ensure that management API examples are shown in a platform-neutral way (e.g., using curl or HTTP requests).
  • Review other documentation sections for similar bias and update them to include Linux and cross-platform tooling.
GitHub Create Pull Request
API Management Azure API Management virtual network injection - network resources .../api-management/virtual-network-injection-resources.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows subtle Windows bias by referencing PowerShell in the related content section and by mentioning Azure portal UI actions (which are often Windows-centric) for network configuration. There are no explicit Linux CLI (az CLI, Bash) examples or references, and Windows/PowerShell tools are mentioned before any Linux alternatives. The lack of Linux-specific instructions or parity in examples may hinder Linux users.
Recommendations
  • Add equivalent az CLI and Bash examples alongside PowerShell references, especially in related content and operational instructions.
  • Explicitly mention that all operations can be performed using cross-platform tools (az CLI, REST API), not just PowerShell or Azure portal.
  • Provide links to Linux-focused documentation or examples for common tasks such as network configuration and DNS setup.
  • Ensure that instructions for applying network configuration updates include az CLI and REST API methods, not just PowerShell and portal UI.
  • Review related content to balance Windows and Linux tool references, ensuring Linux users are equally supported.
GitHub Create Pull Request
API Management VNet configuration settings | Azure API Management ...n/articles/api-management/virtual-network-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_update_endpoints ⚠ī¸ windows_defender_endpoints ⚠ī¸ kms_windows_only ⚠ī¸ windows_first
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific infrastructure and endpoints (such as KMS for Windows VM activation, Windows Update, and Windows Defender), and includes instructions and port requirements that are only relevant for Windows-based virtual machines. There is no mention of Linux equivalents for these services, nor are Linux-specific considerations or examples provided. The only explicit example of a deployment model is a link to a PowerShell-based guide, with no Bash/CLI or Linux-focused alternatives. The ordering of information also places Windows requirements before any mention of Linux or cross-platform needs.
Recommendations
  • Add explicit guidance for Linux-based VM scenarios, such as activation or update mechanisms relevant to Linux distributions.
  • Include Linux-specific endpoints or port requirements (e.g., for package repositories, security updates, or monitoring agents).
  • Provide cross-platform examples for network configuration, such as Azure CLI/Bash commands alongside PowerShell.
  • Clarify which requirements are Windows-only and which are applicable to all platforms.
  • Add links to Linux-focused documentation for deploying and managing API Management in VNets.
GitHub Create Pull Request
App Service Migrate .NET Apps to Azure App Service .../articles/app-service/app-service-asp-net-migration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias throughout. All migration tools and examples focus exclusively on Windows environments, specifically IIS servers and PowerShell scripts. There is no mention of Linux-based .NET hosting (e.g., Kestrel, Apache/Nginx), nor are there migration paths or tools for .NET apps running on Linux. Windows tools and patterns (IIS, PowerShell, MSI installers) are referenced exclusively and repeatedly, with no Linux equivalents or guidance provided.
Recommendations
  • Add migration guidance and examples for .NET apps hosted on Linux (e.g., Kestrel, Apache, Nginx).
  • Include Linux-compatible migration tools or document how to migrate from Linux environments.
  • Provide Bash or shell script equivalents for PowerShell-based migration steps.
  • Mention containerization options for Linux-based .NET apps and how to migrate them to Azure App Service (Linux).
  • Clarify tool/platform support (Windows-only vs. cross-platform) in tool descriptions.
  • Add documentation links and resources for Linux users, including troubleshooting and best practices for Linux migrations.
GitHub Create Pull Request
App Service Configure Premium v4 Tier ...s/app-service/app-service-configure-premium-v4-tier.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-related information and tools. Windows SKU availability is presented before Linux, and Azure PowerShell (a Windows-centric tool) is featured alongside Azure CLI. There are no Linux shell (bash) or scripting examples, and no mention of Linux-specific deployment patterns or tools beyond the Azure CLI flag for Linux workers. The automation section lacks parity for Linux-native scripting, and the overall flow assumes familiarity with Windows tools and the Azure portal, which is more commonly used by Windows users.
Recommendations
  • Provide bash or shell script examples for Linux users alongside PowerShell examples.
  • Present Linux and Windows SKU availability commands together, or alternate their order to avoid Windows-first bias.
  • Include guidance for Linux-native automation (e.g., using bash, curl, or other Linux tools) in addition to Azure CLI and PowerShell.
  • Explicitly mention Linux deployment patterns and tools where relevant, such as using VS Code Remote, GitHub Actions, or other CI/CD options popular in Linux environments.
  • Clarify any differences in the portal experience for Linux vs. Windows app service plans, if applicable.
GitHub Create Pull Request
App Service Hybrid Connections in Azure App Service ...articles/app-service/app-service-hybrid-connections.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools (such as PowerShell and GUI usage) are frequently presented first or exclusively, with Linux equivalents sometimes missing or less detailed. Troubleshooting and connectivity testing rely on Windows-specific tools (PowerShell), and GUI management is only available for Windows. Some examples and screenshots are Windows-centric, and legacy support is only for Windows clients.
Recommendations
  • Provide Linux-first or parallel examples for all installation, configuration, and troubleshooting steps.
  • Include Linux-native troubleshooting commands (e.g., 'nc', 'telnet', or 'ss') alongside PowerShell examples for connectivity testing.
  • Expand documentation on Linux CLI usage, including more detailed step-by-step instructions and screenshots where possible.
  • Clarify feature parity and limitations for Linux (e.g., explicitly state GUI is unavailable, but CLI is fully supported).
  • Offer guidance for common Linux distributions and package managers beyond apt (e.g., yum, dnf, zypper).
  • Where legacy or advanced features are Windows-only, provide alternative recommendations or workarounds for Linux users.
GitHub Create Pull Request
App Service Node.js Best Practices and Troubleshooting ...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation is heavily focused on Windows-specific tooling and patterns, particularly IIS and iisnode, which are not available on Linux. All configuration examples and troubleshooting steps reference Windows concepts (e.g., web.config, named pipes, Win32 error codes, DLLs, d:\home\LogFiles), and there are no Linux equivalents or cross-platform alternatives provided. The documentation assumes the use of node.exe and does not mention node on Linux or App Service Linux environments.
Recommendations
  • Add equivalent guidance for Node.js apps running on Linux-based Azure App Service (e.g., using PM2, Nginx, or Kestrel).
  • Provide Linux-specific troubleshooting steps and log file locations.
  • Include configuration examples for Linux environments (e.g., environment variables, process managers, startup scripts).
  • Mention differences between Windows and Linux App Service environments and clarify which instructions apply to each.
  • Avoid assuming the presence of Windows-only concepts (web.config, named pipes, Win32 errors) and offer alternatives for Linux.
  • Balance examples and recommendations between Windows and Linux to ensure parity.
GitHub Create Pull Request
App Service Configure Sign in with Apple (Preview) ...app-service/configure-authentication-provider-apple.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides a code example for generating the Apple client secret JWT using C# and the Microsoft.IdentityModel.Tokens NuGet package, which is Windows-centric and assumes a .NET development environment. There are no equivalent examples or guidance for Linux or cross-platform environments (e.g., using OpenSSL, Python, or Node.js). The documentation also references application settings and configuration in a way that may be more familiar to Windows/Azure users, without acknowledging Linux-native workflows.
Recommendations
  • Provide equivalent code samples for generating the client secret JWT using cross-platform tools such as Python (with PyJWT), Node.js (with jsonwebtoken), or OpenSSL command-line utilities.
  • Explicitly mention that the JWT signing step can be performed on any OS and provide links or examples for Linux/macOS users.
  • Avoid referencing only Windows-specific libraries or tools (such as Microsoft.IdentityModel.Tokens) without alternatives.
  • Include a section or callout for Linux users, outlining the steps and tools they can use to accomplish the same tasks.
  • Ensure that application setting configuration instructions are OS-agnostic or provide Linux-specific guidance where relevant.
GitHub Create Pull Request
App Service App Service Managed Certificate (ASMC) Changes – July 28, 2025 ...e/app-service-managed-certificate-changes-july-2025.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively providing a PowerShell script for identifying impacted Traffic Manager endpoints, with no equivalent Bash, Azure CLI, or Linux-native example. Instructions for running the script assume a Windows environment (PowerShell), and there is no mention of Linux or cross-platform alternatives. The mitigation steps reference REST API and Azure CLI for certificate management, but the only resource discovery example is PowerShell-based, which may disadvantage Linux users.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for identifying impacted Traffic Manager endpoints, ensuring Linux and macOS users can follow the guidance without requiring PowerShell.
  • Explicitly mention cross-platform options and clarify which steps are OS-agnostic (e.g., Azure CLI, REST API).
  • Add notes or links to Linux installation and usage instructions for Azure CLI and scripting tools.
  • Where PowerShell is referenced, offer alternative commands or scripts for Bash/zsh environments.
  • Review all examples and ensure parity between Windows and Linux, especially for resource discovery and automation tasks.
GitHub Create Pull Request
App Service Tutorial: ASP.NET app with Azure SQL Database ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. All instructions, screenshots, and tooling references assume the user is on Windows, with no mention of Linux or cross-platform alternatives. Examples use PowerShell and Visual Studio-specific features, and Azure App Service (Windows) is selected by default, with no guidance for Linux-based App Service or development workflows. There are no Linux or CLI-based examples, and tools like SQL Server Object Explorer and Package Manager Console are exclusive to Visual Studio on Windows.
Recommendations
  • Add instructions and examples for deploying ASP.NET apps to Azure App Service (Linux), including relevant screenshots and steps.
  • Provide equivalent workflows using cross-platform tools such as Visual Studio Code, Azure CLI, and .NET CLI.
  • Include SQL database management steps using Azure CLI, az sql commands, or Data Studio, rather than only Visual Studio and PowerShell.
  • Present both Windows and Linux options for each step, or clearly indicate platform-specific instructions.
  • Mention and link to documentation for developing and deploying from macOS and Linux environments.
  • Offer guidance for using cross-platform editors and tools (e.g., VS Code, JetBrains Rider) where possible.
GitHub Create Pull Request
App Service Configure an App Service App ...ocs/blob/main/articles/app-service/configure-common.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several instances of Windows bias. Many features (default documents, virtual directory mapping, handler mappings) are explicitly stated as Windows-only, with no Linux alternatives or workarounds suggested. Examples and terminology (such as IIS, D:\home paths, and PowerShell cmdlets) are Windows-centric. In sections where both Windows and Linux are supported, Windows-specific patterns (like .NET config files) are mentioned first or exclusively. There is a lack of Linux-specific examples or explanations for equivalent functionality, especially for advanced configuration scenarios.
Recommendations
  • Clearly indicate feature parity and limitations for Linux and Windows throughout the documentation, especially at the start of each section.
  • For Windows-only features (default documents, handler mappings, virtual directories), suggest Linux alternatives or provide guidance for achieving similar outcomes (e.g., using startup commands, web server config files like nginx.conf, or Dockerfile ENTRYPOINT/CMD for custom containers).
  • Add Linux-specific examples and command-line patterns where applicable, such as showing how to configure environment variables, default documents, or directory mappings in Linux-based App Service apps.
  • Avoid using Windows-centric terminology (IIS, D:\home paths) without Linux equivalents or explanations.
  • Where PowerShell is used, provide Bash or shell script equivalents for Linux users, especially for bulk editing and advanced configuration.
  • Consider reordering sections or examples so that Linux and cross-platform approaches are presented before or alongside Windows-specific instructions.
GitHub Create Pull Request
App Service Manage App Service Certificates ...s/app-service/configure-ssl-app-service-certificate.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing Azure PowerShell examples and mentioning PowerShell in the FAQ, while not offering equivalent Linux-specific or Bash examples. The ordering of examples places Azure CLI (cross-platform) before PowerShell, but there is no explicit mention of Linux-specific certificate management patterns or tools. The instructions and screenshots are portal-centric and do not address platform-specific nuances for Linux users. There are no references to Linux-native certificate handling (e.g., OpenSSL, Linux file permissions) or troubleshooting steps for Linux environments.
Recommendations
  • Add Linux-specific examples for certificate export and management, such as using OpenSSL to handle .pfx files after export.
  • Include troubleshooting steps or notes relevant to Linux environments (e.g., file permissions, certificate import paths).
  • Provide parity in FAQ and guidance for common Linux issues, not just PowerShell-centric problems.
  • Explicitly state that Azure CLI commands are cross-platform and provide sample Bash scripts for Linux users.
  • Where PowerShell is mentioned, also mention Bash or other Linux-native tools to ensure equal visibility.
GitHub Create Pull Request
App Service Disable Basic Authentication for Deployment ...n/articles/app-service/configure-basic-auth-disable.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows a moderate Windows bias. It references Windows-centric deployment tools and patterns (FTP, Web Deploy, Visual Studio, MSBuild) without providing Linux-specific equivalents or examples. The monitoring section only mentions FTP and Web Deploy, both traditionally Windows-heavy. The deployment table and troubleshooting notes prioritize Visual Studio and Web Deploy, with additional detail for Windows agents, while Linux agents are mentioned only in passing. There are no explicit Linux/Powershell/Bash command examples for deployment, troubleshooting, or monitoring, and no mention of Linux-native deployment tools (e.g., rsync, SCP, SFTP) or workflows.
Recommendations
  • Add Linux-specific deployment examples, such as using SFTP, SCP, or rsync, and clarify how disabling basic authentication affects these methods.
  • Include troubleshooting and monitoring instructions for Linux-native tools and workflows.
  • Provide parity in deployment tables, listing both Windows and Linux agent behaviors and requirements.
  • Reference cross-platform deployment tools (e.g., Git, Azure CLI) with explicit examples for both Windows and Linux environments.
  • Clarify whether disabling basic authentication impacts Linux users differently, and provide guidance for Linux-based CI/CD pipelines.
GitHub Create Pull Request
App Service Configure gateway-required virtual network integration for your app ...service/configure-gateway-required-vnet-integration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exhibits a Windows bias by explicitly stating that gateway-required virtual network integration only works for Windows plans and cannot be used from a Linux app. All examples and troubleshooting steps reference Windows tools (e.g., PowerShell's Test-NetConnection, netstat -aon), with no Linux equivalents provided. There are no Linux-specific instructions or parity in examples, and the documentation does not mention how to perform similar actions on Linux-based environments.
Recommendations
  • Clearly state early in the document that gateway-required virtual network integration is not supported for Linux apps, and provide a prominent link to Linux-supported alternatives (such as regional VNet integration).
  • Wherever Windows-specific tools or commands are mentioned (e.g., PowerShell, netstat), provide equivalent Linux commands (e.g., curl, nc, ss, netstat) and examples.
  • In troubleshooting sections, include Linux-based diagnostic steps and tools for network connectivity and DNS resolution (e.g., using dig, nslookup, or ping on Linux).
  • Add a comparison table or section summarizing feature support for Windows and Linux, with clear guidance for Linux users.
  • Ensure that all portal-based instructions are clearly marked as OS-agnostic or, if there are differences, provide Linux-specific guidance.
GitHub Create Pull Request
App Service Configure Data Sources for Tomcat, JBoss, or Java SE Apps ...es/app-service/configure-language-java-data-sources.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed, step-by-step instructions for configuring Tomcat data sources on Windows, including PowerShell scripts and Windows-specific environment variables and file paths. The Windows section is longer and more tool-specific (PowerShell, Windows paths), while the Linux section is shorter, relies on shell scripts, and omits some details (e.g., no equivalent to the PowerShell script for copying Tomcat and performing transforms). Windows tools and patterns (PowerShell, .cmd files, Windows environment variables) are emphasized, and Linux instructions are sometimes less explicit or detailed.
Recommendations
  • Provide Linux shell script equivalents for all Windows PowerShell examples, including copying Tomcat directories and performing XSL transforms.
  • Ensure Linux instructions are as detailed as Windows instructions, including troubleshooting steps and environment variable usage.
  • Mention Linux tools (e.g., bash, sh, xsltproc) before or alongside Windows tools, not after.
  • Include explicit Linux file paths and environment variable usage in all relevant examples.
  • Add parity in startup script examples: show a full Linux startup script that performs the same steps as the Windows PowerShell script.
  • Clarify any platform-specific limitations or differences at the beginning of each section.
GitHub Create Pull Request
App Service SSH Access for Linux and Windows Containers ...ticles/app-service/configure-linux-open-ssh-session.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ missing_windows_example ⚠ī¸ linux_tools ⚠ī¸ linux_first
Summary
The documentation provides detailed, step-by-step instructions and CLI examples for connecting to Linux containers via SSH, including Azure CLI commands and Linux SSH client usage. In contrast, Windows containers are only mentioned briefly, with no equivalent CLI or PowerShell examples, and it is stated that SSH via Azure CLI is not supported for Windows containers. The Linux workflow is described in detail and illustrated with screenshots and command outputs, while Windows is covered superficially.
Recommendations
  • Add equivalent step-by-step instructions for opening SSH sessions to Windows containers, including any supported tooling (e.g., PowerShell, Windows SSH clients, or browser-based SSH).
  • Clarify whether PowerShell or other Windows-native tools can be used for SSH access, and provide examples if possible.
  • If SSH via Azure CLI is not supported for Windows containers, explicitly state alternative methods and provide guidance.
  • Include screenshots or sample outputs for Windows container SSH sessions to match the Linux documentation depth.
  • Ensure both Linux and Windows sections have parity in detail, examples, and troubleshooting tips.
GitHub Create Pull Request
App Service Configure a Custom Container ...ain/articles/app-service/configure-custom-container.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific content and examples (such as PowerShell commands, Windows parent images, IIS/.NET Framework details, and Windows file paths) are often presented first or in greater detail than Linux equivalents. Some sections (e.g., customizing container memory, compute cores, health ping behavior) provide Windows-specific instructions and examples, while Linux equivalents are missing or less detailed. PowerShell commands are frequently included alongside Bash, but Linux-native tools and patterns are less emphasized. Windows tooling (Kudu, C:\home, IIS, .NET Framework) is referenced more extensively than Linux alternatives.
Recommendations
  • Ensure all configuration sections (e.g., memory limits, CPU cores, health ping behavior) include Linux-specific instructions and examples where applicable.
  • Present Linux and Windows examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
  • Expand Linux-specific content to match the detail provided for Windows (e.g., supported parent images, troubleshooting, diagnostic logs).
  • Include Linux-native commands and patterns (such as systemctl, journalctl, or Linux file paths) where relevant, not just Bash/az CLI.
  • Clarify platform differences explicitly, and provide parity in troubleshooting and advanced configuration guidance for both platforms.
GitHub Create Pull Request
App Service Configure ASP.NET Apps ...les/app-service/configure-language-dotnet-framework.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps in Azure App Service. All runtime version discovery and file system examples use Windows paths and tools (CMD, PowerShell, Kudu), with no mention of Linux equivalents or how to perform similar tasks in a Linux App Service environment. There are no Linux-specific instructions or examples, and Windows tools and patterns are always presented first and exclusively.
Recommendations
  • Add parallel instructions and examples for Linux-based App Service plans, including how to check .NET runtime versions and file locations on Linux.
  • Include Linux shell (bash) commands and file paths where appropriate, alongside Windows CMD/PowerShell examples.
  • Clarify in each section whether the instructions apply to Windows, Linux, or both, and provide links to Linux-specific documentation if available.
  • Mention and demonstrate how to use Kudu or SSH for Linux App Service environments, if applicable.
  • Ensure that deployment and configuration guidance covers both Windows and Linux hosting scenarios for ASP.NET apps.
GitHub Create Pull Request
App Service Configure ASP.NET Core apps .../articles/app-service/configure-language-dotnetcore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows-first bias by presenting Windows-specific instructions and tooling (such as Visual Studio and Kudu) before Linux equivalents. Windows tools and patterns (Kudu, PowerShell, Visual Studio publish) are mentioned prominently, while Linux alternatives are introduced later or in separate pivots. Some sections, such as deployment and runtime version inspection, emphasize Windows workflows and tools, with Linux instructions provided as secondary or alternative options. There is also a reliance on Windows-centric terminology and examples, such as referencing CMD/PowerShell and Visual Studio, which may not be as relevant for Linux users.
Recommendations
  • Ensure that Linux instructions and examples are presented with equal prominence and detail as Windows ones, possibly alternating the order or combining them where appropriate.
  • Provide Linux-native tooling and workflow examples (such as VS Code, CLI, or container-based deployment) alongside Visual Studio and Kudu references.
  • Avoid Windows-centric terminology when describing generic concepts; use platform-neutral language where possible.
  • Where Windows-specific tools are mentioned (e.g., Kudu, PowerShell), explicitly note Linux alternatives or clarify platform limitations.
  • Review all examples to ensure Linux parity, including build automation, environment variable access, and troubleshooting steps.
  • Consider adding a summary table or section comparing Windows and Linux workflows for common tasks.
GitHub Create Pull Request
App Service Configure Node.js Apps ...main/articles/app-service/configure-language-nodejs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a mild Windows bias. Windows-specific instructions, tools, and troubleshooting steps (e.g., IISNode, web.config, PowerShell) are often presented before or in more detail than their Linux equivalents. Some sections, such as Application Insights instrumentation, reference PowerShell for setup without mentioning Linux alternatives. Troubleshooting and configuration for Windows (e.g., web.config) are more extensive, while Linux sections are sometimes less detailed or refer to external includes. The use of Windows terminology and tools (IISNode, web.config, PowerShell) is more prominent than Linux-native equivalents.
Recommendations
  • Ensure that Linux examples and instructions are presented with equal prominence and detail as Windows ones, especially in troubleshooting and configuration sections.
  • Where PowerShell or Windows tools are referenced (e.g., for Application Insights instrumentation), provide equivalent Bash/Azure CLI/Linux-native instructions.
  • Expand Linux troubleshooting guidance to match the depth provided for Windows (e.g., common errors, configuration files, deployment issues).
  • When mentioning Windows tools (IISNode, web.config), explicitly state the Linux alternatives (e.g., PM2, startup scripts) and provide links or examples.
  • Review the order of presentation so that Windows and Linux content are balanced, or Linux is not consistently presented after Windows.
GitHub Create Pull Request
App Service Secure Your Domain with TLS/SSL ...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing PowerShell automation examples but omitting equivalent Linux shell (Bash/Azure CLI) scripts. The 'Automate with scripts' section lists PowerShell after Azure CLI, but only PowerShell code is shown inline, with no Bash or Linux-specific automation guidance. There is also a lack of Linux-specific tooling or workflow examples throughout the page, and no mention of Linux certificate management patterns (e.g., PEM files, OpenSSL usage).
Recommendations
  • Add Bash/Azure CLI script examples inline, not just as links, to match the PowerShell coverage.
  • Include Linux-specific certificate upload and management instructions, such as handling PEM files or using OpenSSL.
  • Provide parity in automation examples by showing both PowerShell and Bash/CLI workflows side-by-side.
  • Explicitly mention platform differences where relevant (e.g., certificate file formats, command-line tools).
  • Reference Linux documentation or guides for common tasks such as certificate generation and binding.
GitHub Create Pull Request
App Service Authentication Types by Deployment Methods ...in/articles/app-service/deploy-authentication-types.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools such as Azure PowerShell and Visual Studio are prominently featured, with dedicated sections and multiple reference links. Visual Studio (Windows-only) is listed before Visual Studio Code (cross-platform), and PowerShell is highlighted as a primary deployment method. There are no explicit Linux-specific deployment tools or examples (e.g., Bash scripts, Linux CLI workflows, or references to Linux-native editors). The documentation does not provide parity for Linux users in terms of examples, tooling, or workflow guidance.
Recommendations
  • Add explicit examples and guidance for Linux users, such as Bash scripts or Linux shell commands for deployment.
  • Include references to Linux-native editors (e.g., Vim, Emacs) or IDEs (e.g., JetBrains Rider) where relevant.
  • Provide parity in documentation for Visual Studio Code by listing it before or alongside Visual Studio, and clarify its cross-platform nature.
  • Mention and link to Linux-specific deployment workflows (e.g., using SCP, rsync, or Linux-based CI/CD pipelines).
  • Ensure that all PowerShell examples are accompanied by equivalent Bash or shell script examples.
  • Highlight the cross-platform nature of Azure CLI and provide Linux installation and usage instructions.
GitHub Create Pull Request
App Service Configure CI/CD with Azure Pipelines ...ob/main/articles/app-service/deploy-azure-pipelines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-based examples (e.g., Web Deploy) are presented without Linux equivalents, and Windows agent images are used or referenced first in key sections. Windows-specific deployment tools (Web Deploy, IIS/iisnode) are discussed in detail, while Linux deployment methods are less emphasized or omitted. Some error messages and troubleshooting sections focus on Windows agents, and Linux alternatives are not always provided or explained.
Recommendations
  • Provide equivalent Linux deployment examples for all Windows-specific scenarios, especially for Web Deploy (or clarify Linux alternatives such as zip deploy, FTP, or container-based deployment).
  • When mentioning agent specifications, list both 'ubuntu-latest' and 'windows-latest' together, or alternate their order to avoid Windows-first bias.
  • Include troubleshooting and FAQ sections for common Linux agent issues, not just Windows agent errors.
  • Expand documentation on Linux deployment tools and patterns, such as using Kudu REST API, container-based deployments, or native Linux build and deploy workflows.
  • Clarify which tasks and deployment methods are cross-platform, and explicitly state limitations or alternatives for Linux users.
GitHub Create Pull Request
App Service Use TLS/SSL Certificates in App Code ...icles/app-service/configure-ssl-certificate-in-code.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific instructions and code examples first and in greater detail. It focuses heavily on Windows certificate stores, provides C# and Java examples for Windows, and references Windows-specific tools and environment variables. Linux instructions and examples are less detailed, with only C# examples given for Linux containers and other languages (Node.js, PHP, Python, Java) are deferred to external documentation. There is minimal parity in example depth and guidance for Linux users.
Recommendations
  • Provide Linux-specific code examples for popular languages (Node.js, Python, Java, PHP) directly in the documentation, not just C#.
  • Balance the order of presentation: introduce Linux and Windows approaches side-by-side or in parallel tabs, rather than Windows-first.
  • Expand explanations of Linux certificate handling, including common patterns (e.g., using OpenSSL, environment variables, file permissions).
  • Reference Linux tools and commands (such as openssl, chmod, etc.) where appropriate.
  • Clarify differences and similarities in certificate management between Windows and Linux, including troubleshooting tips for both platforms.
  • Add explicit guidance for Linux users outside containers (e.g., App Service on Linux), not just container scenarios.
GitHub Create Pull Request
App Service Enable integration with an Azure virtual network ...icles/app-service/configure-vnet-integration-enable.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for enabling virtual network integration in Azure App Service. However, the PowerShell section is significantly more detailed, with step-by-step parameter preparation, delegation checks, and resource updates. PowerShell is a Windows-centric tool, and its prominence (with more granular instructions and notes) suggests a bias toward Windows users. There are no Linux shell (bash) examples, nor are Linux-specific tools or patterns mentioned. The CLI example is brief and lacks the depth of the PowerShell walkthrough.
Recommendations
  • Expand the Azure CLI section to include step-by-step instructions comparable to the PowerShell section, including parameter preparation, delegation checks, and resource updates.
  • Add bash shell examples for Linux users, demonstrating equivalent operations using Azure CLI.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, but provide parity in example depth and troubleshooting notes for CLI users.
  • Include troubleshooting steps or common issues for Linux environments, if applicable.
  • Avoid assuming PowerShell as the default automation tool by balancing documentation coverage for CLI and shell scripting.
GitHub Create Pull Request
App Service Manage Deployment Credentials ...n/articles/app-service/deploy-configure-credentials.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, but does not include any Linux- or macOS-specific shell examples (e.g., Bash scripting, curl, or FTP command-line usage). Azure PowerShell is highlighted as an option for several tasks, which is primarily a Windows-centric tool, and it is listed alongside Azure CLI without clarifying cross-platform differences. There are no explicit Linux tool examples, and the only mention of Linux shells is a brief note about escaping the dollar sign in Bash, rather than providing a full example. The documentation implicitly prioritizes Windows tooling and patterns.
Recommendations
  • Add explicit Bash (Linux/macOS) shell examples for relevant commands, especially for tasks like retrieving credentials or deploying via FTP/S.
  • Include examples using common Linux command-line tools (e.g., curl, lftp, git) for deployment and credential management.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, while Azure PowerShell is more commonly used on Windows.
  • Where PowerShell is mentioned, provide equivalent Bash or shell script examples for parity.
  • Consider a 'Linux/macOS' tab alongside 'Azure CLI', 'Azure PowerShell', and 'Azure portal' for each example section.
GitHub Create Pull Request
App Service Deploy Content Using FTP/S ...zure-docs/blob/main/articles/app-service/deploy-ftp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a Windows bias by prioritizing Windows-centric tools and examples. FTP/S client recommendations list Visual Studio and WinSCP (both Windows-focused) before cross-platform or Linux-native options. Troubleshooting and connection examples reference WinSCP documentation, and there are no explicit Linux command-line or tool examples (e.g., lftp, FileZilla, or Linux CLI usage). PowerShell is given its own tab for endpoint retrieval and configuration, but there is no mention of Linux shell equivalents or scripts. No Linux-specific troubleshooting or guidance is provided.
Recommendations
  • Add explicit Linux examples for connecting to FTP/S endpoints using common Linux tools (e.g., lftp, curl, ncftp, or FileZilla).
  • Include Linux shell (bash) command-line examples for retrieving publishing profiles and configuring FTPS state, in addition to Azure CLI and PowerShell.
  • List cross-platform or Linux-native FTP clients (such as FileZilla, lftp, or GNOME Files) alongside or before Windows-specific tools.
  • Provide troubleshooting steps and links relevant to Linux environments (e.g., firewall configuration, passive mode setup, permissions).
  • Balance the order of examples and tool recommendations so that Linux and cross-platform options are not always listed after or subordinate to Windows/PowerShell.
GitHub Create Pull Request
App Service Deploy From a Local Git Repository ...ocs/blob/main/articles/app-service/deploy-local-git.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure portal, but PowerShell is given a dedicated section with detailed steps, and references to Windows-specific tooling (e.g., Git Credential Manager, MSBuild, node-gyp errors on Windows) are present. There is a subtle Windows-first bias in troubleshooting and deployment steps, with more attention to Windows-specific issues and tools, and PowerShell is presented as a primary automation method alongside CLI, which is cross-platform. There are no explicit Linux-specific examples or troubleshooting notes, and some error messages reference Windows build issues without mentioning Linux equivalents.
Recommendations
  • Add explicit Linux/macOS terminal examples and troubleshooting notes, such as common errors with native modules on Linux.
  • Mention cross-platform alternatives to Windows tools (e.g., credential managers for Linux/macOS).
  • Balance troubleshooting by including Linux-specific issues (e.g., permissions, case sensitivity, native build tool errors).
  • Clarify that Azure CLI and Git commands work identically on Linux/macOS, and provide sample commands run in Bash/zsh.
  • When referencing build errors (e.g., node-gyp), note that similar issues may occur on Linux/macOS and link to relevant resources.
  • Avoid assuming PowerShell is available or preferred; highlight Bash/zsh usage where appropriate.
GitHub Create Pull Request
App Service Deploy Files ...zure-docs/blob/main/articles/app-service/deploy-zip.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific paths and tools (e.g., Kudu UI, PowerShell) are mentioned first or exclusively in several places. The Kudu UI ZIP deploy is noted as unavailable for Linux, but no equivalent Linux-native UI or workflow is described. PowerShell examples are provided, but Linux shell equivalents are not, and some features are marked as 'not supported' in PowerShell without clarifying Linux alternatives. Windows paths and terminology (e.g., D:\home\site\wwwroot) are often listed before Linux equivalents. There is limited discussion of Linux-specific deployment nuances or troubleshooting.
Recommendations
  • Provide Linux-specific deployment UI or workflow examples where Kudu UI is unavailable.
  • Ensure Linux paths and terminology are presented with equal prominence to Windows paths.
  • Where PowerShell is used, offer equivalent Bash or shell script examples for Linux users.
  • Clarify which features and tools are supported on Linux and provide alternatives or workarounds for unsupported scenarios.
  • Add troubleshooting and best practices sections for Linux deployments, especially where behavior differs from Windows.
  • Review the order of presentation to avoid listing Windows tools and paths before Linux equivalents unless contextually necessary.
GitHub Create Pull Request
App Service Getting started with Azure App Service ...docs/blob/main/articles/app-service/getting-started.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the .NET and Python sections. Windows-centric tools like Visual Studio and Azure PowerShell are listed first or exclusively, while Linux alternatives (such as CLI or VS Code on Linux) are often secondary or missing. The 'Next step' callout exclusively promotes an ASP.NET (Windows-centric) workflow, and some sections (e.g., Python) default to Windows tabs in their quickstart links. Linux-specific instructions and parity for tools are less visible or absent in several stacks.
Recommendations
  • Ensure all stacks provide both Windows and Linux examples for each action, especially in quickstart and deployment guides.
  • List cross-platform tools (e.g., VS Code, CLI) before Windows-only tools (e.g., Visual Studio, PowerShell) to avoid implicit prioritization.
  • Add Linux-specific deployment and management instructions where only Windows or PowerShell examples are given.
  • Balance the 'Next step' callout to include a Linux-based workflow or a neutral, cross-platform option.
  • Audit tab defaults and pivots to ensure Linux is equally represented and easily discoverable.
  • Where Windows tools are mentioned (e.g., Visual Studio, PowerShell), explicitly mention Linux equivalents (e.g., VS Code, Bash, Azure CLI).
GitHub Create Pull Request
App Service Set Up Staging Environments ...blob/main/articles/app-service/deploy-staging-slots.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. While Azure CLI examples (cross-platform) are provided alongside Azure PowerShell and portal instructions, several features and troubleshooting steps reference Windows-specific tools, patterns, or configuration files (such as Web.config and IIS applicationInitialization). PowerShell examples are given equal prominence to CLI, and some advanced warm-up and troubleshooting scenarios rely on Windows-centric concepts. There is limited mention of Linux-specific deployment patterns, and some features (like auto swap) are explicitly unavailable for Linux-based web apps, but this is only noted in passing.
Recommendations
  • Add explicit Linux-specific examples or notes where behaviors differ, especially for warm-up, swap, and troubleshooting steps.
  • Provide alternative configuration guidance for Linux-based web apps and containers (e.g., how to specify warm-up actions without Web.config).
  • Clarify which features are unavailable or behave differently on Linux, and suggest workarounds or alternatives.
  • Where PowerShell is referenced, ensure Bash or shell script equivalents are also provided for parity.
  • Highlight cross-platform deployment tools (such as Git, CI/CD pipelines) with examples for both Windows and Linux environments.
  • Consider reordering examples so that CLI (cross-platform) instructions appear before PowerShell, or group them by OS context.
GitHub Create Pull Request
App Service Certificates in App Service Environment ...icles/app-service/environment/overview-certificates.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas. The per-app private client certificate method is explicitly limited to Windows code apps, with no Linux equivalent or workaround described. All example commands for certificate verification and generation use PowerShell, and the Kudu console instructions are Windows-centric. There are no Linux shell or cross-platform examples for certificate management, verification, or generation in the private client certificate section. The documentation does acknowledge Linux support for the Root Certificate API, but practical examples and troubleshooting for Linux scenarios are missing.
Recommendations
  • Provide equivalent Linux shell (bash, openssl) examples for certificate verification and generation, especially in the private client certificate section.
  • Clarify whether there are any Linux-compatible alternatives for per-app root certificate configuration, or explicitly state the limitation.
  • Include troubleshooting and verification steps for Linux apps (e.g., how to check trust store contents in Linux containers).
  • Mention cross-platform tools and patterns where possible, not just Windows/PowerShell.
  • If features are Windows-only, offer guidance or workarounds for Linux users, or link to relevant feature requests or roadmap items.
GitHub Create Pull Request
App Service Prerequisites ...cludes/tutorial-microsoft-graph-as-app/introduction.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions first, referencing Visual Studio (a Windows-centric tool), and omitting Linux-specific examples or shell commands. The Azure CLI example is present, but PowerShell is prioritized and no explicit Linux workflow or troubleshooting is discussed.
Recommendations
  • Present Azure CLI (cross-platform) instructions before PowerShell, or side-by-side.
  • Include explicit Linux shell (bash) examples and notes for users deploying from Linux environments.
  • Reference cross-platform development tools (e.g., VS Code) alongside Visual Studio.
  • Add troubleshooting or environment notes for Linux users, especially regarding authentication and permissions.
  • Clarify that all steps can be performed from Linux/macOS terminals using Azure CLI.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjob-types.md ...es/app-service/includes/webjobs-create/webjob-types.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation lists Windows file types and tools (cmd, bat, exe, PowerShell) in detail and gives multiple examples for Windows, while Linux support is described more briefly, with only *.sh* scripts explicitly mentioned and fewer examples of supported file types. Windows examples and tools are presented first and in greater detail, with Linux equivalents either missing or less emphasized.
Recommendations
  • Provide a more comprehensive list of supported Linux file types (e.g., *.py*, *.pl*, *.rb*, *.js*, *.jar*, etc.) similar to the Windows section.
  • Include explicit examples for Linux, such as Python (*.py*), Perl (*.pl*), Ruby (*.rb*), and Java (*.jar*) scripts, not just *.sh*.
  • Balance the order and detail of Windows and Linux sections so that Linux is not always listed after Windows and receives equal coverage.
  • Mention Linux-specific tools or runtimes (e.g., bash, python, node, java) in the same way Windows tools (cmd, PowerShell) are highlighted.
  • Clarify that runtimes for various languages are installed for both Windows and Linux environments, not just Windows.
GitHub Create Pull Request
App Service Set Up Azure Arc for App Service, Functions, and Logic Apps .../articles/app-service/manage-create-arc-environment.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Bash and PowerShell examples for most steps, but PowerShell is given equal prominence throughout, which may signal a Windows bias. There are no Linux-specific examples (e.g., using native Linux tools or shell idioms), and no mention of Linux-specific issues, troubleshooting, or alternative patterns. The use of PowerShell tabs and examples may make the documentation feel Windows-centric, especially since PowerShell is not the default shell on most Linux distributions. There is also a lack of explicit guidance for Linux users, such as handling file paths, permissions, or package management differences.
Recommendations
  • Add explicit Linux troubleshooting notes, such as permissions, file paths, and package installation steps.
  • Clarify that Bash examples are intended for Linux/macOS users and PowerShell for Windows users.
  • Provide guidance for using native Linux tools (e.g., base64, grep, sed) where appropriate.
  • Consider removing PowerShell examples or moving them to a secondary position unless there is a clear user need.
  • Add notes about differences in Azure CLI usage on Linux vs. Windows, such as environment variable syntax and file system locations.
  • Include links to Linux-specific prerequisites (e.g., installing Azure CLI and kubectl on Ubuntu, CentOS, etc.).
GitHub Create Pull Request
App Service Supported platforms and file types ...includes/webjobs-create/webjobs-supported-platforms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation lists Windows hosting options before Linux and gives Windows-specific file types and tools (e.g., .exe, .cmd, .bat, PowerShell) before mentioning Linux equivalents (e.g., Bash scripts). PowerShell is highlighted as a script type, but no Linux shell alternatives (like zsh) are mentioned. The ordering and emphasis suggest a Windows-centric perspective.
Recommendations
  • List Linux hosting options and script types before or alongside Windows options to avoid implicit prioritization.
  • Include examples of Linux shell scripts beyond Bash, such as zsh or fish, to match the specificity given to PowerShell.
  • Mention Linux-specific tools or patterns (e.g., cron jobs, shell environments) where relevant.
  • Ensure parity in examples and explanations for both Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
App Service Back Up an App ...e-docs/blob/main/articles/app-service/manage-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific terminology and paths (e.g., %HOME%, D:\home\site\wwwroot) are used throughout, often without Linux equivalents or with Windows listed first. Instructions for file exclusion reference Windows paths and tools (Kudu DebugConsole, FTP to D:\home), and PowerShell is mentioned as a scripting option alongside Azure CLI, but no Linux shell (bash) or Linux-specific automation examples are provided. The documentation also references Windows-specific features (MySQL in-app for Web Apps (Windows)), and examples for file system access and backup filtering are Windows-centric. Linux equivalents are either missing or mentioned secondarily.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, including file paths (e.g., /home/site/wwwroot) and shell commands.
  • Include bash or shell script automation samples in addition to PowerShell.
  • When referencing tools like Kudu DebugConsole or FTP, clarify usage for both Windows and Linux environments.
  • Ensure that all file system instructions (such as creating _backup.filter) include both Windows and Linux paths and methods.
  • Avoid listing Windows examples or terminology first; present Windows and Linux options equally.
  • Explicitly mention how backup and restore processes differ or are the same for Linux-based App Service apps.
GitHub Create Pull Request
App Service Per-App Scaling for High-Density Hosting ...blob/main/articles/app-service/manage-scale-per-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for per-app scaling, with no equivalent examples for Linux-native tools or cross-platform CLI (such as Azure CLI or Bash). The use of PowerShell cmdlets and variables is specific to Windows environments, and there is no mention of Linux or cross-platform alternatives. The ordering also places Windows tooling first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Provide Bash script examples for configuring per-app scaling, or at least show how to use Azure CLI in Bash.
  • Explicitly mention that the PowerShell examples are for Windows users, and provide guidance for Linux/macOS users.
  • Ensure that documentation consistently includes both Windows and Linux/cross-platform instructions, or links to relevant sections.
  • Consider including a table or section comparing PowerShell and Azure CLI commands for common tasks.
GitHub Create Pull Request
App Service Migrate from gateway-based to regional virtual network integration .../app-service/migrate-gateway-based-vnet-integration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides Azure CLI, Azure PowerShell, and Azure Portal instructions for all major steps, but consistently lists Azure PowerShell examples after Azure CLI and before Linux-native alternatives (if any). Azure PowerShell is a Windows-centric tool, and its inclusion and prominence (including interactive code blocks) may indicate a bias toward Windows users. There are no Linux shell-specific examples (e.g., Bash scripts), and PowerShell is presented as a primary automation method, which is less common on Linux. The documentation does not mention Linux-specific tools or patterns, and does not provide parity for Linux-native scripting environments.
Recommendations
  • Add Bash shell script examples for each CLI step to demonstrate Linux-native automation.
  • Clarify that Azure PowerShell is available cross-platform, but recommend CLI and Bash for Linux users.
  • Explicitly mention Linux support and provide troubleshooting or migration tips for Linux-based App Service apps.
  • Reorder examples so that CLI/Bash instructions appear before PowerShell, or provide tabs for Linux and Windows workflows.
  • Include notes or links to Linux-specific documentation where relevant.
GitHub Create Pull Request
App Service Migrate Docker Compose to sidecars ...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by requiring PowerShell for the migration script, providing only PowerShell examples for key steps (such as base64 decoding), and referencing a migration script that is a PowerShell (.ps1) file. There are no Linux shell (bash/sh) equivalents or examples, and Linux tools for decoding or scripting are not mentioned. The prerequisites list PowerShell before Azure CLI and Docker, further reinforcing Windows-first patterns.
Recommendations
  • Provide bash/sh equivalents for all PowerShell commands, especially for base64 decoding and script execution.
  • Offer a migration script in bash or Python, or document how to run the PowerShell script on Linux (e.g., via pwsh).
  • List prerequisites in a cross-platform manner, e.g., 'PowerShell or bash', and clarify platform compatibility for scripts.
  • Include Linux-specific instructions and examples alongside Windows ones throughout the documentation.
  • Reference Linux tools (e.g., base64, curl, jq) where appropriate, and avoid assuming PowerShell as the default scripting environment.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation shows evidence of Windows bias, particularly in the 'Hybrid Connections' section, which exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux support or alternatives. The 'Gateway-required virtual network integration' feature is explicitly limited to Windows plans. There are no examples or instructions for Linux-based environments, and Windows tools and patterns are referenced without Linux parity.
Recommendations
  • Explicitly state whether features like Hybrid Connection Manager and Gateway-required virtual network integration support Linux, and provide Linux installation or usage instructions if available.
  • Add Linux-specific examples and guidance throughout the documentation, especially for networking scenarios and tool usage.
  • Where features are Windows-only, clearly indicate this and suggest Linux alternatives or workarounds where possible.
  • Ensure parity in documentation structure by presenting Linux options and examples alongside Windows ones, rather than focusing on Windows first or exclusively.
GitHub Create Pull Request
App Service Operating System Functionality in Azure App Service ...articles/app-service/operating-system-functionality.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page is heavily focused on Windows-based App Service environments. It describes file, network, and registry access using Windows terminology (e.g., %SystemDrive%, %ResourceDrive%, IIS, ASP.NET, COM components, PowerShell), and provides examples and explanations exclusively for Windows apps. Linux is mentioned only briefly and generically, with no Linux-specific examples, environment variables, or tooling discussed. Windows tools and patterns (IIS, ASP.NET, COM, PowerShell, registry, event logs) are referenced throughout, while Linux equivalents (e.g., /var, /etc, shell scripting, syslog, Linux file permissions) are absent.
Recommendations
  • Add parallel sections or callouts for Linux-based App Service environments, describing file system layout, environment variables (e.g., $HOME, /tmp), and access patterns.
  • Provide Linux-specific examples for file access, network access, and diagnostics (e.g., using Bash scripts, Linux logging mechanisms like syslog, accessing /proc or /etc).
  • Mention Linux tools and frameworks (e.g., Nginx, Apache, shell scripting) where appropriate, alongside Windows tools.
  • Clarify differences in process isolation, permissions, and diagnostic logging between Windows and Linux App Service environments.
  • Include a comparison table or summary highlighting key differences and similarities between Windows and Linux App Service functionality.
GitHub Create Pull Request
App Service Azure App Service Plans ...ob/main/articles/app-service/overview-hosting-plans.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page displays a Windows bias, particularly in the 'Managed Instance on Azure App Service (preview)' section, which is exclusively for Windows web apps and highlights Windows-specific features such as PowerShell scripts, RDP access, and legacy Windows component support. There are no equivalent Linux examples, tools, or parity notes for Linux users. The main documentation references both Windows and Linux as supported operating systems, but advanced features and examples focus on Windows, with Linux-specific guidance missing.
Recommendations
  • Add equivalent Linux-focused sections, especially for advanced hosting options, or explicitly state Linux limitations and roadmap.
  • Provide Linux-specific examples, tools, and configuration patterns (e.g., Bash scripts, SSH access, Linux middleware setup) alongside Windows examples.
  • Clarify feature parity between Windows and Linux App Service plans, including supported runtimes, networking, and storage options.
  • Include links to Linux documentation and migration guidance for users with Linux workloads.
  • Ensure that new features (such as Managed Instance) are described with Linux plans in mind, or provide clear messaging about future Linux support.
GitHub Create Pull Request
App Service Inbound/Outbound IP Addresses .../articles/app-service/overview-inbound-outbound-ips.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI, but there are no Bash or Linux shell equivalents for commands involving outbound IP discovery. Outbound IPv6 support is called out as available only for Windows apps, with Linux support explicitly missing. The documentation references Windows-specific tools and patterns (PowerShell, outbound IPv6 for Windows) before or instead of Linux alternatives, and does not provide parity in examples or tooling for Linux users.
Recommendations
  • Add Bash or Linux shell equivalents for all command-line examples, especially where PowerShell is used.
  • Clarify the availability of outbound IPv6 support for Linux apps and provide a roadmap or workaround for Linux users.
  • Ensure that examples using Azure CLI are presented before or alongside PowerShell, and explicitly note cross-platform compatibility.
  • Where features are Windows-only, provide clear guidance for Linux users, including alternative approaches or expected timelines for parity.
  • Include notes or examples for Linux-specific environments (e.g., WSL, native Linux terminals) when discussing command execution.
GitHub Create Pull Request
App Service Managed Instance on App Service overview (preview) ...main/articles/app-service/overview-managed-instance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation for Managed Instance on Azure App Service is heavily Windows-centric, with exclusive focus on Windows workloads, tools, and configuration patterns. All examples and features reference Windows technologies (PowerShell scripts, registry, COM, MSI, IIS, GAC, RDP), and there is no mention of Linux equivalents or parity. Linux and container support is explicitly excluded, and configuration, troubleshooting, and best practices are described only in Windows terms.
Recommendations
  • Add Linux-specific examples and configuration patterns where possible, or clarify the roadmap for Linux parity.
  • Include equivalent Linux tooling (e.g., Bash scripts, systemd services, Linux file system mounts) in configuration and troubleshooting sections.
  • Provide a comparison table highlighting feature gaps and planned Linux support.
  • Explicitly state the lack of Linux support at the beginning of the documentation to set expectations.
  • If Linux support is planned, include guidance for migration or future parity.
  • Offer links to Linux App Service documentation for users seeking non-Windows solutions.
GitHub Create Pull Request
App Service Overview of Azure App Service .../azure-docs/blob/main/articles/app-service/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several areas. Windows-specific features and tools (such as PowerShell scripts, COM, registry, MSI, drive mapping, and RDP) are described in detail, especially in the Managed Instance section, with little or no equivalent Linux information. Windows workloads and tools are mentioned first and more extensively, while Linux support is referenced only briefly or as 'not supported' in certain scenarios. There are no Linux-specific examples or guidance for Linux users, and command-line tooling mentions Azure PowerShell before Azure CLI.
Recommendations
  • Provide Linux-specific examples and guidance, especially for deployment, configuration, and troubleshooting.
  • Mention Azure CLI before or alongside Azure PowerShell when discussing command-line tools, as CLI is cross-platform.
  • Include information about Linux-supported features and limitations in parity with Windows, especially in sections discussing Managed Instance.
  • Add references to Linux-friendly tools and patterns (e.g., Bash scripts, SSH diagnostics, Linux file system access) where relevant.
  • Clarify which features are exclusive to Windows and suggest Linux alternatives or workarounds where possible.
GitHub Create Pull Request
App Service Kudu service overview ...-docs/blob/main/articles/app-service/resources-kudu.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a subtle Windows bias by referencing Windows-specific tools and deployment patterns (such as IIS diagnostic dumps, IIS processes, and deployment webhooks for Windows apps) without mentioning Linux equivalents or clarifying Linux support. There are no Linux-specific examples or references to Linux-based App Service environments, and Windows concepts are mentioned first or exclusively.
Recommendations
  • Include information about Kudu features and diagnostics relevant to Linux-based App Service environments, such as access to Docker logs, process management, and deployment options.
  • Clarify which features are Windows-only and which are available or different on Linux (e.g., IIS dumps/processes vs. Linux process management).
  • Provide Linux-specific examples or references alongside Windows ones, especially for deployment, diagnostics, and process management.
  • Add a section or notes about differences in Kudu functionality between Windows and Linux App Service plans.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured heavily as a primary automation tool, with detailed examples and scripts, while Linux-native alternatives (such as Bash or shell scripting) are absent. In tabbed sections, PowerShell is presented before ARM templates and after Azure CLI, but Linux shell scripting is never mentioned. The documentation assumes the use of Windows tools (PowerShell) for local scripting, and does not provide parity for Linux users who may prefer Bash or other shell environments.
Recommendations
  • Add Bash/shell script examples alongside PowerShell for token retrieval and identity management, especially in sections where PowerShell scripts are shown.
  • Explicitly mention Linux support and provide guidance for Linux users, including any differences in environment variables or tooling.
  • Where PowerShell is referenced, clarify that Azure CLI commands and REST API calls are cross-platform and provide equivalent Bash examples.
  • Consider reordering tabs or examples so that cross-platform tools (Azure CLI, REST API) are presented before platform-specific tools (PowerShell).
  • Add a note or section about using managed identities from Linux-based development environments, including common patterns and troubleshooting tips.
GitHub Create Pull Request
App Service Integrate your app with an Azure virtual network ...main/articles/app-service/overview-vnet-integration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ windows_heavy_example ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily by providing detailed Windows Containers-specific limits and sample calculations, while omitting equivalent details for Linux containers. Windows-specific features (e.g., Windows Server Active Directory domain join, NetBIOS) are mentioned as unsupported, but there is no comparable discussion for Linux-specific features. The troubleshooting and command-line examples use Azure CLI, which is cross-platform, but the only deep-dive example is for Windows Containers. Linux is only referenced briefly in the context of continuous deployment network dependencies, with no parity in container scaling or subnet sizing guidance.
Recommendations
  • Add a dedicated section for Linux Containers, including subnet sizing, scaling, and networking limits, similar to the Windows Containers section.
  • Provide Linux-specific examples and calculations for App Service plan instance IP requirements.
  • Discuss any Linux-specific unsupported features or limitations to match the Windows-focused list.
  • Ensure that examples and guidance are presented for both platforms, or clarify when guidance applies equally to both.
  • Include troubleshooting steps and environment variable usage examples for Linux-based apps (e.g., how to access WEBSITE_PRIVATE_IP in Linux environments).
GitHub Create Pull Request
App Service Quickstart: Run a Custom Container on App Service ...in/articles/app-service/quickstart-custom-container.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-related pivots (Visual Studio, Azure Portal, PowerShell, CLI) before their Linux equivalents, and by providing dedicated PowerShell and Windows CLI sections. Linux examples are present but are fewer and less prominently positioned, with no Linux-specific CLI or shell examples shown in the main pivot list.
Recommendations
  • Ensure Linux pivots (e.g., Bash/CLI, VS Code) are listed before or alongside Windows pivots to avoid ordering bias.
  • Add Linux-specific CLI or shell examples (e.g., Bash, Azure CLI for Linux) to match the PowerShell and Windows CLI coverage.
  • Provide parity in tooling examples, such as including Linux-native tools and workflows where Windows tools (like Visual Studio and PowerShell) are mentioned.
  • Review and balance the depth of instructions and examples for both platforms to ensure equal clarity and completeness.
GitHub Create Pull Request
App Service Quickstart: Deploy Managed Instance on Azure App Service (Preview) ...in/articles/app-service/quickstart-managed-instance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. The only configuration (install) script provided is a PowerShell script (Install.ps1) that installs fonts specifically into the C:\Windows\Fonts directory and modifies Windows registry keys. All runtime and deployment examples use ASP.NET V4.8, a Windows-only framework. There are no Linux-based examples, nor any mention of Linux-compatible configuration scripts (e.g., Bash, shell scripts), Linux runtimes, or Linux file paths. The documentation assumes a Windows environment for both app deployment and configuration, and does not address Linux parity.
Recommendations
  • Provide equivalent Linux configuration (install) script examples, such as Bash scripts for font installation in Linux containers.
  • Include instructions and examples for deploying Linux-based runtimes (e.g., Node.js, Python, .NET Core) on Managed Instance.
  • Clarify whether Managed Instance supports Linux plans, and if so, document the differences and options.
  • Show how to register fonts or perform similar configuration tasks in Linux environments (e.g., copying fonts to /usr/share/fonts and running fc-cache).
  • Add notes or sections highlighting limitations or differences between Windows and Linux plans for Managed Instance.
  • Ensure that examples and screenshots do not exclusively reference Windows file paths or features.
GitHub Create Pull Request
App Service Create an App by Using a Terraform Template ...n/articles/app-service/provision-resource-terraform.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page displays mild Windows bias in several areas. In the prerequisites, Windows and PowerShell configuration options are listed before Linux equivalents, and there is a strong emphasis on using PowerShell and Windows tools. The Visual Studio Code extension is mentioned without reference to Linux-specific editors or CLI workflows. While both Linux and Windows Terraform templates are provided, the overall structure and ordering favor Windows users, and there is limited discussion of Linux-specific tooling or workflows beyond the template itself.
Recommendations
  • List Linux/Bash configuration options before Windows/PowerShell options in the prerequisites section.
  • Include examples or references for popular Linux editors (e.g., Vim, Nano) and CLI workflows, not just Visual Studio Code.
  • Add explicit instructions for running Terraform commands on Linux, including any OS-specific considerations (e.g., permissions, package installation).
  • Ensure parity in troubleshooting and cleanup instructions for both Linux and Windows environments.
  • Consider adding a section on using Terraform in native Linux environments outside of Azure Cloud Shell.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools and patterns (such as Web Deploy/MSDeploy, IIS, and Windows file paths) are mentioned more frequently and often before their Linux equivalents. Many environment variables and examples reference Windows paths (e.g., D:\home), Windows-specific behaviors, or tools, while Linux alternatives are sometimes only mentioned as exceptions or in later sections. Some settings and explanations are tailored to Windows scenarios (e.g., machineKey, IIS, w3wp.exe) without equivalent Linux details or examples. In some cases, Linux-specific configuration is referenced only briefly or as an afterthought, and there are missing Linux examples for certain deployment and logging scenarios.
Recommendations
  • Ensure Linux and Windows examples are provided side-by-side for all environment variables, especially where file paths, deployment methods, or logging are involved.
  • When referencing tools (e.g., Web Deploy/MSDeploy, IIS), mention Linux alternatives (such as Oryx, Apache, Nginx) with equal prominence and detail.
  • Avoid using Windows paths (e.g., D:\home) as the default example; instead, show both Windows and Linux paths (e.g., D:\home and /home) together.
  • For settings that are Windows-specific (e.g., machineKey, IIS, w3wp.exe), provide Linux equivalents or explicitly state when no equivalent exists.
  • Add Linux-focused troubleshooting and configuration sections where only Windows guidance is currently present.
  • Review all tables and examples to ensure Linux scenarios are not omitted or relegated to footnotes.
GitHub Create Pull Request
App Service Routine Maintenance, Restarts, and Downtime ...n/articles/app-service/routine-maintenance-downtime.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by consistently presenting Windows-specific features, tools, and examples before their Linux equivalents. Windows mechanisms (such as IIS Application Initialization Module and .NET Core stdout logging) are described in detail, while Linux alternatives are mentioned briefly or as afterthoughts. Several features are explained with Windows-centric terminology and links, with Linux options either missing, less detailed, or referenced only in passing. There is a lack of parity in example depth and guidance for Linux users.
Recommendations
  • Provide equally detailed explanations and examples for Linux-specific mechanisms, such as expanding on WEBSITE_WARMUP_PATH usage and configuration.
  • Include Linux-first or at least parallel examples for features like application initialization, logging, and troubleshooting.
  • Reference Linux-native tools and patterns (e.g., Nginx/Apache warm-up, stdout/stderr logging, systemd service management) where appropriate.
  • Ensure that documentation sections do not default to Windows terminology or tools, and offer Linux alternatives with equal prominence.
  • Add step-by-step guides or links for configuring and troubleshooting Linux App Service environments, matching the depth given to Windows.
  • Review and update all feature descriptions to clarify platform-specific behaviors and limitations for both Windows and Linux users.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses Microsoft Graph as the app| Azure ...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides installation instructions using both the .NET Core CLI and the Visual Studio Package Manager Console. However, the Package Manager Console instructions (PowerShell-based) are presented after the CLI, and there is no explicit mention of Linux-specific development environments or tools. Visual Studio and its console are Windows-centric, and there are no examples or guidance for Linux IDEs (such as VS Code on Linux) or package management workflows specific to Linux. The documentation does not mention Linux prerequisites, nor does it provide parity for Linux users beyond the generic dotnet CLI commands.
Recommendations
  • Add explicit instructions for Linux users, such as using VS Code or JetBrains Rider, and clarify that the dotnet CLI commands work cross-platform.
  • Remove or de-emphasize Package Manager Console instructions, or provide equivalent instructions for Linux environments (e.g., terminal-based workflows).
  • Include a note about platform compatibility for the .NET CLI and clarify that Visual Studio is Windows-only, while VS Code is cross-platform.
  • Provide troubleshooting steps or prerequisites for Linux environments, such as installing .NET SDK on Ubuntu or other distributions.
  • Consider adding screenshots or examples of the workflow on Linux to ensure parity and inclusivity.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses storage by using managed identities | Azure ...cles/app-service/scenario-secure-app-access-storage.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting installation instructions for the NuGet packages using Visual Studio's Package Manager Console (PowerShell) and referencing Visual Studio tooling before mentioning the .NET Core command-line interface. There are no explicit Linux-specific instructions or examples, and the use of PowerShell and Visual Studio tools may not be applicable or familiar to Linux users.
Recommendations
  • Provide explicit Linux instructions, such as using the .NET CLI in a bash shell and clarifying that Visual Studio steps are optional.
  • Reorder installation instructions to present cross-platform (dotnet CLI) commands first, followed by Windows-specific tooling.
  • Add notes or sections for Linux/macOS users, including guidance for common editors (VS Code, JetBrains Rider) and terminal usage.
  • Avoid assuming Visual Studio or PowerShell availability; mention alternatives for package management and project setup on Linux.
GitHub Create Pull Request
App Service Fix HTTP 502 and HTTP 503 Errors ...articles/app-service/troubleshoot-http-502-http-503.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by highlighting PowerShell as the primary CLI tool for app management and referencing Windows-specific tools like ProcDump. The debug console examples mention PowerShell and DOS commands, but do not reference Bash or Linux shell commands. There are no explicit Linux or Bash examples, nor are Linux troubleshooting tools or patterns mentioned.
Recommendations
  • Include equivalent Linux/Bash command examples in the Kudu debug console section, such as using Bash commands for diagnostics.
  • Mention Linux-native troubleshooting tools (e.g., gcore, strace, lsof) alongside ProcDump for memory dumps and diagnostics.
  • Provide Azure CLI examples for app management and troubleshooting, as Azure CLI is cross-platform and preferred by many Linux users.
  • Explicitly state that Kudu supports both PowerShell and Bash consoles, and show how to access and use the Bash console.
  • Ensure that references to management tools (like PowerShell) are paired with cross-platform alternatives (Azure CLI, Bash scripts) and that examples are provided for both Windows and Linux users.
GitHub Create Pull Request
App Service Tutorial: Connect a web app to SQL Database on behalf of the user ...utorial-connect-app-access-sql-database-as-user-dotnet.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. While most configuration and deployment steps use Azure CLI (which is cross-platform), key database management and user provisioning steps reference Windows-centric tools like SQL Server Management Studio (SSMS) and sqlcmd, without mentioning Linux alternatives. Additionally, publishing instructions prioritize Visual Studio (Windows) before mentioning Git Bash, and local debugging guidance focuses on Visual Studio remote debugging. There are no explicit Linux or cross-platform alternatives for these steps, and no mention of Linux-native SQL tools (e.g., Azure Data Studio, sqlcmd on Linux, or ODBC tools).
Recommendations
  • Include instructions for connecting to Azure SQL Database using Linux-native tools such as Azure Data Studio, sqlcmd on Linux, or other cross-platform SQL clients.
  • When describing publishing workflows, mention cross-platform IDEs (e.g., VS Code) and CLI-based deployment methods before or alongside Visual Studio.
  • For local debugging, provide guidance for Linux/macOS environments, such as using VS Code's remote debugging, or other cross-platform debugging tools.
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary setup steps for non-Windows environments.
  • When referencing database management tools, list cross-platform options first or alongside Windows tools, and provide links to their documentation.
GitHub Create Pull Request
App Service Enable Diagnostic Logging ...n/articles/app-service/troubleshoot-diagnostic-logs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a Windows-first bias: logging features and instructions for Windows apps are described in greater detail and appear before Linux equivalents. Several logging types (web server logging, detailed error messages, failed request tracing) are exclusive to Windows, with no Linux alternatives or explanations. Examples and tooling references (e.g., Log Parser, W3C log format) are Windows-centric. Linux instructions are less detailed and sometimes missing, especially for advanced diagnostics.
Recommendations
  • Provide equivalent Linux examples and instructions for all logging types, or explicitly state when features are unavailable on Linux.
  • Include Linux-specific tools and patterns for accessing and analyzing logs (e.g., using grep, tail, jq, or Docker log commands).
  • Clarify differences in logging capabilities between Windows and Linux, and offer workarounds or alternatives for Linux users.
  • Ensure parity in documentation structure: present Linux and Windows instructions side-by-side where possible, rather than Windows-first.
  • Expand code examples to include Linux-friendly languages and frameworks, and show how to configure logging for those environments.
GitHub Create Pull Request
App Service Troubleshoot Performance Degradation ...es/app-service/troubleshoot-performance-degradation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific tools and patterns, such as PowerShell, IIS diagnostics, and SysInternals Procdump, are mentioned exclusively or before any Linux equivalents. Diagnostic instructions and examples focus on Windows technologies (e.g., .NET Profiler for Windows, web.config for auto-heal), and there are no Linux-specific troubleshooting examples or references to Linux-native tools (such as Bash, Linux process dump tools, or Linux logging paths). The Kudu console is described as supporting PowerShell and DOS commands, with no mention of Bash or Linux shell support. Overall, Linux users may find it difficult to apply the guidance directly to their environments.
Recommendations
  • Add Linux-specific troubleshooting examples, such as using Bash in Kudu, Linux process dump tools (e.g., gcore, lsof), and Linux logging paths.
  • Include instructions for enabling diagnostics and collecting logs on Linux-based App Service plans, referencing Linux equivalents to IIS logs and .NET Profiler.
  • Mention Linux-native configuration files (e.g., appsettings.json, environment variables) for auto-heal or similar features, not just web.config.
  • Provide parity in restart and management examples, e.g., using Azure CLI or Bash scripts, not only Azure PowerShell.
  • Clarify which features and tools are available on Linux App Service plans, and note any differences or limitations.
GitHub Create Pull Request
App Service Tutorial: Access Azure databases with managed identity ...les/app-service/tutorial-connect-msi-azure-database.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a moderate Windows bias, especially in the 'Set up your dev environment' section. Visual Studio for Windows is presented first and in more detail, while Visual Studio for Mac is described as lacking integration and requiring a workaround. Windows-specific tools (Visual Studio, Azure PowerShell) are mentioned before their Linux/macOS equivalents. Azure PowerShell and Visual Studio Windows receive more prominent placement and explanation than cross-platform or Linux-native tools. There are no explicit Linux examples or mentions of Linux-specific development environments (e.g., JetBrains Rider, VS Code on Linux, Bash shell), and the guidance for Linux users is limited to using Azure CLI.
Recommendations
  • Add explicit examples and instructions for Linux development environments, such as VS Code on Linux, JetBrains Rider, or command-line workflows using Bash.
  • Present cross-platform tools (Azure CLI, VS Code) before Windows-specific tools (Visual Studio, Azure PowerShell) to avoid 'windows_first' bias.
  • Include instructions for signing in and configuring Microsoft Entra authentication on Linux and macOS, not just Windows.
  • Clarify that Azure CLI and VS Code are fully supported on Linux and macOS, and provide links to installation guides for those platforms.
  • Where Visual Studio for Windows is mentioned, also mention equivalent steps for Linux/macOS environments, or note any limitations.
  • Consider adding troubleshooting or FAQ entries specifically for Linux/macOS users.
GitHub Create Pull Request
App Service Tutorial: Build and Run a Custom Image in Azure App Service ...main/articles/app-service/tutorial-custom-container.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways. The Windows container tutorial is presented first, with detailed step-by-step instructions using Windows-specific tools (Visual Studio, Windows Explorer, PowerShell scripts) and patterns. The Linux container tutorial, while present and thorough, is positioned after the Windows section and does not receive the same level of integration with IDE tooling or OS-specific features. Windows tools and workflows (Visual Studio, Windows font installation, PowerShell) are mentioned exclusively in the Windows section, with no Linux equivalents or cross-platform alternatives suggested. There are missing Linux examples for scenarios like installing fonts or using IDEs for container orchestration, and the Windows section does not reference Linux alternatives or parity.
Recommendations
  • Present Windows and Linux instructions in parallel or with equal prominence, rather than Windows-first.
  • Where Windows-specific tools (Visual Studio, PowerShell) are used, provide Linux equivalents (e.g., VS Code, Bash scripts) or note cross-platform alternatives.
  • For OS-specific operations (like installing fonts), include Linux examples (e.g., using fc-cache, copying fonts to /usr/share/fonts) and discuss how to adapt the sample for Linux containers.
  • Avoid exclusive use of Windows terminology (e.g., 'Windows Explorer') and provide cross-platform instructions (e.g., 'File Manager' or CLI alternatives).
  • Highlight cross-platform container orchestration tools (e.g., Docker Compose, VS Code Remote Containers) and provide examples for both Windows and Linux.
  • Ensure parity in troubleshooting tips (e.g., line ending issues are discussed for Linux, but similar issues for Windows should be mentioned if relevant).
  • Consider adding a summary table comparing Windows and Linux workflows for common tasks (building, deploying, debugging, logging, SSH access).
GitHub Create Pull Request
App Service Securely connect .NET apps to Azure SQL Database using Managed Identity ...icles/app-service/tutorial-connect-msi-sql-database.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/Visual Studio workflows, using PowerShell and Windows-specific tools for key steps (such as SQLCMD in PowerShell), and omitting explicit Linux or cross-platform alternatives for several operations. Linux development environments and tools are not given equal prominence or example coverage, especially for database administration and local development setup.
Recommendations
  • Provide explicit Linux/macOS equivalents for all command-line steps, especially for SQL Database administration (e.g., using sqlcmd in Bash, Azure Data CLI, or cross-platform tools).
  • Add examples and instructions for setting up and debugging .NET apps with managed identity on Linux/macOS, including using VS Code and the .NET CLI.
  • Ensure that cross-platform tools (like Azure CLI and VS Code) are introduced before or alongside Windows-specific tools (Visual Studio, PowerShell).
  • Include notes or sections on using Docker or WSL for cross-platform development and testing.
  • When referencing PowerShell or Windows tools, always provide the corresponding Bash or shell commands for parity.
  • Highlight any differences or additional steps required for Linux/macOS users, especially around authentication and environment setup.
GitHub Create Pull Request
App Service Build a scheduled WebJob using your preferred language ...ocs/blob/main/articles/app-service/tutorial-webjobs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ windowscode_tabs ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a moderate Windows bias, especially in the .NET section. Windows build and packaging instructions are presented before Linux equivalents, and the use of Windows-specific runtime identifiers (win-x64) and file extensions (.exe) is prominent. The reference to 'windowscode' tabs in links and supported file types further centers Windows as the default. Linux instructions are present but often secondary, and some advanced scenarios (like PowerShell or Windows container specifics) are referenced without Linux parity. Other language pivots (Python, Node, Java, PHP) focus on Linux, but the .NET pivot is Windows-centric.
Recommendations
  • Present Linux and Windows instructions side-by-side or in parallel, rather than listing Windows first.
  • Use neutral language and avoid defaulting to Windows-specific terms (e.g., 'windowscode' tabs, .exe) in cross-platform contexts.
  • Ensure all advanced scenarios (such as deployment, troubleshooting, and supported file types) have Linux equivalents and are equally documented.
  • Clarify when instructions apply to both platforms, and highlight any platform-specific differences explicitly.
  • Provide Linux container and shell examples wherever Windows/PowerShell examples are given.
  • Review links and references to ensure they do not default to Windows-specific tabs or content.
GitHub Create Pull Request
App Service Tutorial for event-driven background processing with the WebJobs SDK ...b/main/articles/app-service/webjobs-sdk-get-started.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio 2022 and PowerShell-based workflows. All setup, package installation, and deployment instructions assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. Package installation is demonstrated exclusively with PowerShell commands in the Package Manager Console, and there are no examples for .NET CLI or other Linux-friendly tools. The use of Windows-centric UI instructions (menus, dialogs) and screenshots further reinforces this bias. There is no guidance for Linux or macOS users, nor any mention of alternative editors or command-line workflows.
Recommendations
  • Add equivalent instructions for Linux and macOS users, including setup steps using the .NET CLI (e.g., 'dotnet new', 'dotnet add package') instead of or alongside Visual Studio and PowerShell.
  • Provide examples for installing NuGet packages using the .NET CLI: 'dotnet add package <package-name> --version <version>' and clarify how to edit configuration files in non-Windows environments.
  • Include guidance for using cross-platform editors such as VS Code, and clarify which steps are specific to Visual Studio versus general .NET development.
  • Add screenshots or textual instructions for Azure portal interactions that are platform-agnostic.
  • Explicitly state platform requirements and offer parity for Linux/macOS users wherever possible, including testing and deployment steps.
  • Mention any limitations or differences when running WebJobs SDK projects on Linux or macOS, and provide troubleshooting tips for those platforms.
GitHub Create Pull Request
App Testing Manage roles in Azure Load Testing ...ticles/app-testing/load-testing/how-to-assign-roles.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing PowerShell examples for command-line role management, without mentioning or providing examples for Azure CLI or Bash (common on Linux/macOS). The only command-line tool referenced is Azure PowerShell, which is primarily used on Windows. There are no Linux-specific instructions, and the order of presentation puts PowerShell before any mention of cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure CLI and Bash can be used for role management, and provide links to relevant documentation.
  • Balance the presentation order by introducing Azure CLI and PowerShell together, or by leading with the cross-platform Azure CLI.
  • Include troubleshooting steps and examples that apply to Linux/macOS environments, not just Windows/PowerShell.
  • Clarify that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the default cross-platform tool.
GitHub Create Pull Request
App Service Develop and deploy WebJobs using Visual Studio .../main/articles/app-service/webjobs-dotnet-deploy-vs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), using Windows-specific UI terms (Solution Explorer, dialog boxes), and omitting any mention of Linux development environments, CLI workflows, or cross-platform tooling. All examples and instructions assume a Windows/Visual Studio workflow, with no parity for Linux or cross-platform scenarios.
Recommendations
  • Add instructions for developing and deploying WebJobs using cross-platform tools such as Visual Studio Code, Azure CLI, or GitHub Actions.
  • Include Linux-specific examples, such as using the Azure CLI or zip deployment from a Linux shell.
  • Clarify which steps are Windows/Visual Studio-specific and provide alternative steps for Linux/macOS users.
  • Reference cross-platform .NET Core workflows and highlight any differences in deployment from non-Windows environments.
  • Mention and link to documentation for deploying WebJobs from Linux or macOS, and provide parity in feature coverage.
GitHub Create Pull Request
App Service Use the Azure WebJobs SDK ...s/blob/main/articles/app-service/webjobs-sdk-how-to.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways: file paths and examples use Windows-style paths (e.g., 'c:\data\import'), references to Windows-specific .NET APIs and classes (such as ServicePointManager and WinHttpHandler), and no explicit mention of Linux equivalents or cross-platform considerations for local development, configuration, or file system bindings. There are no Linux/macOS-specific examples, and Windows-centric tooling (Visual Studio) is referenced without alternatives. This may make it harder for Linux users to follow or adapt the guidance.
Recommendations
  • Provide Linux/macOS-specific examples alongside Windows ones, especially for file paths and environment variable configuration.
  • Mention cross-platform .NET Core compatibility explicitly and clarify any platform-specific limitations or differences.
  • Include references to cross-platform development tools (e.g., VS Code, CLI) in addition to Visual Studio.
  • Use environment variable and file path examples that are platform-agnostic or show both Windows and Linux formats.
  • Clarify whether APIs like ServicePointManager and WinHttpHandler have different behaviors or equivalents on Linux/macOS.
  • Add notes or sections on running and deploying WebJobs SDK projects on Linux-based environments, including Azure App Service for Linux.
GitHub Create Pull Request
App Testing Configure customer-managed keys for encryption ...load-testing/how-to-configure-customer-managed-keys.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI and portal instructions, but PowerShell is often presented before Azure CLI. The use of PowerShell and references to PowerShell modules (Az.KeyVault) are inherently Windows-centric, as PowerShell is most commonly used on Windows. Screenshots and step-by-step instructions are focused on the Azure portal, which is platform-agnostic but often associated with Windows workflows. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The documentation does not address Linux users directly or provide parity for Linux-native command-line environments beyond Azure CLI.
Recommendations
  • Add explicit bash shell examples for key operations, especially for users who prefer native Linux tools.
  • Clarify that Azure CLI commands work cross-platform and provide any necessary setup instructions for Linux environments.
  • Reorder code tabs so that Azure CLI appears before PowerShell, or alternate the order to avoid implicit prioritization.
  • Mention that PowerShell Core is available on Linux and macOS, if PowerShell examples are retained, to reduce the perception of Windows exclusivity.
  • Include notes or links for Linux users regarding authentication, environment setup, and common troubleshooting scenarios.
  • Where screenshots are used, consider including examples from Linux desktop environments or terminal outputs.
GitHub Create Pull Request
App Testing Include file ...-testing/includes/include-deploy-sample-application.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell for deployment instructions and examples. All command-line steps assume a Windows environment, with only a brief mention that PowerShell can be installed on Linux/macOS, but no native Bash or Linux shell alternatives are provided. The deployment script is a PowerShell script, and there are no instructions for Linux users who may prefer Bash or shell scripts. Windows tools and patterns are referenced first and exclusively.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, especially for deployment steps.
  • If the deployment script is only available in PowerShell, offer guidance on how to run it in Linux/macOS environments, or provide a cross-platform alternative.
  • Mention Linux-native tools and commands (e.g., using Bash, sh, or zsh) alongside PowerShell instructions.
  • Ensure that references to region codes and other Azure CLI commands are shown in both PowerShell and Bash syntax.
  • Consider restructuring the documentation so that instructions for Windows and Linux/macOS are presented in parallel, or clearly indicate platform-specific steps.
GitHub Create Pull Request
App Testing Tutorial: Identify performance issues with load testing ...-testing/tutorial-identify-bottlenecks-azure-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell commands and tools (e.g., 'PowerShell commands to deploy the sample application'), listing Windows-centric tools (Visual Studio Code, PowerShell) in the prerequisites, and not providing explicit Linux/macOS equivalents or examples. The deployment instructions mention using PowerShell and command windows, which are primarily associated with Windows, without clarifying or providing alternatives for Linux/macOS users. There are no screenshots or CLI examples shown in a Linux terminal, and no mention of Bash or shell scripting. The documentation assumes familiarity with Windows workflows and tools, and does not address platform-specific differences or provide parity for Linux users.
Recommendations
  • Provide explicit Linux/macOS instructions alongside Windows/PowerShell examples, including Bash equivalents for all CLI commands.
  • Clarify when PowerShell is required and offer alternatives (e.g., Bash, zsh) for non-Windows users.
  • Include screenshots of commands being run in Linux/macOS terminals as well as Windows command prompts.
  • List platform-agnostic tools first in prerequisites (e.g., Azure CLI, Git), and mention platform-specific installation guides for both Windows and Linux/macOS.
  • Avoid using 'command window' or 'PowerShell' generically; specify 'terminal' and provide examples for multiple platforms.
  • Add notes or tips for Linux/macOS users where workflows or commands differ.
GitHub Create Pull Request
App Testing Quickstart: Run Playwright tests at scale ...aywright-workspaces/quickstart-run-end-to-end-tests.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by consistently referencing Windows-centric tools and workflows, such as Visual Studio Code and PowerShell/.NET examples, and by providing instructions that assume use of the Azure portal (which is most commonly used on Windows). There are no explicit Linux-specific instructions, examples, or screenshots, and CLI commands are presented generically without addressing platform differences (e.g., environment variable setup, shell differences). The documentation also prioritizes Visual Studio Code (a Microsoft product popular on Windows) for test running and debugging, without mentioning alternatives for Linux users.
Recommendations
  • Add explicit Linux shell examples for environment variable setup (e.g., export PLAYWRIGHT_SERVICE_URL=...) and clarify cross-platform differences.
  • Include instructions and screenshots for running Playwright tests from Linux terminals and editors (such as VS Code on Linux, or alternatives like Vim, Emacs, or JetBrains IDEs).
  • Provide parity for .NET examples by including equivalent instructions for Linux (e.g., using Bash instead of PowerShell, installation via apt/yum/pacman if relevant).
  • Mention and link to Linux-specific installation guides for Azure CLI and Playwright.
  • Clarify that all CLI commands work on Linux and Mac, and note any platform-specific caveats.
  • Add a section or callout for Linux users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Application Gateway Troubleshoot backend health issues in Azure Application Gateway ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias through frequent use of PowerShell commands and examples, prioritization of Windows tools and workflows (such as certlm.msc, netstat, and Windows command prompt), and lack of equivalent Linux command examples in several troubleshooting steps. While OpenSSL is mentioned for certificate inspection, most step-by-step instructions and troubleshooting commands are Windows-centric, with Linux alternatives either missing or relegated to brief mentions.
Recommendations
  • Provide Linux command-line equivalents for all PowerShell and Windows command prompt examples (e.g., use curl, nc, ss, ip, and OpenSSL for connectivity and certificate checks).
  • Include Linux-specific instructions for inspecting certificates (e.g., using openssl, certtool, or viewing certificate stores on common Linux distributions).
  • When listing troubleshooting steps, present both Windows and Linux methods side-by-side, or in parallel sections, to ensure parity.
  • Reference cross-platform tools (such as Azure CLI) before or alongside platform-specific tools like PowerShell.
  • Add screenshots or terminal outputs from Linux environments where Windows screenshots are provided.
  • Explicitly mention that all steps can be performed on both Windows and Linux, and clarify any platform-specific differences.
GitHub Create Pull Request
App Testing Quickstart: Perform advanced diagnostics with Playwright Workspaces reporting ...vanced-diagnostic-with-playwright-workspaces-reporting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (web UI), Visual Studio Code, and Azure CLI, without providing any Linux-specific instructions, terminal screenshots, or alternative tools. All example commands and environment setup steps are generic and could apply to Linux, but there are no explicit Linux shell examples, nor is there mention of Linux desktop environments or alternative editors. The tip for opening the trace viewer uses the Windows-centric 'Ctrl' key convention, and there is no mention of Linux-specific keyboard shortcuts or usage patterns.
Recommendations
  • Provide explicit Linux shell command examples and screenshots where relevant (e.g., bash, zsh).
  • Mention Linux desktop environments and alternative editors (such as Vim, Emacs, GNOME Terminal) alongside Visual Studio Code.
  • Clarify that Azure CLI and npm commands work on Linux and provide any necessary Linux-specific installation instructions.
  • Include Linux keyboard shortcut conventions (e.g., 'Ctrl' vs 'Cmd' vs 'Super') in tips and instructions.
  • Add notes or sections for troubleshooting or configuring on Linux systems, especially for environment variables and file paths.
  • Ensure parity in examples by alternating or combining Windows and Linux instructions, rather than defaulting to Windows-centric patterns.
GitHub Create Pull Request
App Testing Quickstart: Continuous end-to-end testing ...t-workspaces/quickstart-automate-end-to-end-testing.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is used as the default scripting language in CI pipeline examples (e.g., AzureCLI@2 with scriptType: 'pscore', PowerShell@2 tasks), and authentication setup instructions reference Azure PowerShell before alternatives like Azure CLI. The use of 'AzPowershell' and PowerShell-based tasks is prevalent in both GitHub Actions and Azure Pipelines examples. There are no explicit Linux shell/bash script examples, and Windows-centric tools/patterns are mentioned or implied before their Linux equivalents. The documentation does not provide parity for Linux-native workflows or shell scripting, which may hinder adoption by Linux-focused teams.
Recommendations
  • Provide equivalent bash/shell script examples alongside PowerShell examples, especially for CI/CD pipeline steps.
  • Reference Azure CLI commands before or alongside Azure PowerShell, and clarify when either can be used.
  • Explicitly mention cross-platform compatibility and provide instructions for both Windows and Linux runners.
  • Avoid using Windows-specific terminology (e.g., AzPowershell) as the default; use more generic or platform-neutral language.
  • Add examples for Linux/Mac environments, such as bash scripts for authentication and test execution.
  • Clarify that Playwright and its Azure integrations work on Linux runners and provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. There are no examples or links for equivalent Linux-friendly tools such as Azure CLI, nor are Linux-specific patterns or commands mentioned. This prioritizes Windows tooling and may hinder Linux users from finding relevant guidance.
Recommendations
  • Add equivalent Azure CLI instructions and tutorials for creating autoscaling, zone redundant application gateways.
  • Reference both PowerShell and CLI options in 'Next steps', ensuring parity for Linux and macOS users.
  • Where examples are given, provide both PowerShell and CLI syntax side-by-side.
  • Explicitly mention cross-platform support and link to documentation for Linux/macOS environments.
GitHub Create Pull Request
Application Gateway Backend health ...lication-gateway/application-gateway-backend-health.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing a PowerShell example before the Azure CLI example, and by omitting any Linux-specific commands or troubleshooting tools. The use of PowerShell as a primary example and lack of explicit mention of Linux shell usage or Linux troubleshooting approaches suggests a preference for Windows environments.
Recommendations
  • Provide Bash or Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Explicitly mention that Azure CLI commands work cross-platform and show usage in a Linux terminal.
  • Include troubleshooting steps or tool recommendations relevant to Linux environments (e.g., curl, openssl for certificate checks).
  • Balance the order of examples so that Windows and Linux approaches are presented equally, or clarify platform applicability.
  • Add notes or links for Linux administrators on how to perform backend health checks and certificate troubleshooting using native Linux tools.
GitHub Create Pull Request
Application Gateway Externally managed scheduled autoscaling for Application Gateway v2 ...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively provides PowerShell examples and instructions for implementing scheduled autoscaling with Azure Automation, without mentioning or demonstrating Linux-friendly alternatives such as Azure CLI, Bash, or Python runbooks. The use of PowerShell and references to 'runbooks' implicitly favor Windows environments and tooling, potentially making it less accessible for Linux users or those preferring cross-platform solutions.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash scripts for runbooks to demonstrate Linux compatibility.
  • Explicitly mention that Azure Automation supports Python and Bash runbooks, and provide sample code for those.
  • Reorder or supplement instructions to present both Windows/PowerShell and Linux/Azure CLI approaches side by side.
  • Clarify that PowerShell is not required and that cross-platform alternatives are available for all steps.
  • Include troubleshooting and alerting links relevant to Linux-based runbooks, not just PowerShell.
GitHub Create Pull Request
Application Gateway Common key vault errors in Application Gateway ...gateway/application-gateway-key-vault-common-errors.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for certificate management and update operations, with no equivalent examples for Azure CLI or Bash. Troubleshooting steps and UI navigation are described primarily in terms of the Azure Portal, which is platform-agnostic but often used on Windows. There is no mention of Linux-specific tools, nor are Linux/Bash/CLI examples provided alongside PowerShell commands.
Recommendations
  • Add Azure CLI (az) command examples for all certificate management and troubleshooting steps, especially where PowerShell is currently used.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide Bash/CLI equivalents.
  • Where UI navigation is described, clarify that the Azure Portal is accessible from any OS and avoid implying a Windows-only workflow.
  • Include links to cross-platform documentation and note any differences in command syntax or tool availability between Windows and Linux.
GitHub Create Pull Request
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a bias toward Windows and PowerShell by exclusively providing PowerShell cmdlet examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) and referencing Azure PowerShell as the primary automation/configuration tool. There are no CLI (az), Bash, or Linux-native examples or instructions. The 'devx-track-azurepowershell' custom metadata and the 'Next steps' section also prioritize PowerShell over cross-platform alternatives, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, especially for probe configuration and matching criteria.
  • Include Bash script snippets or Linux shell commands where appropriate to demonstrate cross-platform usage.
  • Mention cross-platform tools (Azure CLI, REST API, Terraform) alongside PowerShell in all instructional sections and 'Next steps'.
  • Adjust metadata and page structure to highlight platform neutrality (e.g., 'devx-track-azurecli' or both).
  • Ensure that all configuration steps and automation patterns are shown for both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for enabling diagnostic logging, referencing Windows-centric tools (Excel, Power BI, Visual Studio, C#), and omitting equivalent Linux/CLI/Bash instructions. Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives, and there are no examples using Azure CLI, Bash, or Linux-native workflows for log management.
Recommendations
  • Add equivalent Azure CLI and Bash examples for enabling diagnostic logging, alongside PowerShell.
  • Include instructions for viewing and analyzing logs using Linux-native tools (e.g., jq, awk, grep) and open-source visualization platforms (e.g., Grafana).
  • Reference cross-platform editors and tools (e.g., VS Code, LibreOffice Calc) in addition to Windows-specific ones like Excel and Visual Studio.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order or grouped by OS, rather than Windows-first.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to relevant cross-platform documentation.
GitHub Create Pull Request
Application Gateway Use with Internal Load Balancer - Azure Application Gateway ...les/application-gateway/application-gateway-ilb-arm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively uses Windows PowerShell (Az module) for all examples and instructions, with no mention of Azure CLI, Bash, or Linux-native tools. The setup and management steps are presented only with PowerShell cmdlets, and references to switching PowerShell modes and using Windows PowerShell are made before any alternative is discussed (none are provided). This creates a strong Windows-centric bias and excludes Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) commands for each step, with Bash syntax examples.
  • Include notes or sections for Linux/macOS users, clarifying how to perform the same operations from those platforms.
  • Reference Azure Cloud Shell, which supports both PowerShell and Bash, as a cross-platform option.
  • Avoid language such as 'switch PowerShell mode' or 'Using Windows PowerShell' unless alternatives are also presented.
  • Ensure that links and references include documentation for both PowerShell and CLI approaches.
GitHub Create Pull Request
Application Gateway TLS policy overview for Azure Application Gateway ...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily through its references to PowerShell for configuration and details retrieval, with no mention of Linux-specific tools or examples (such as Bash, Azure CLI on Linux, or OpenSSL). PowerShell is listed first and most prominently as the method for viewing cipher suite ordering and for configuring TLS policies, and the 'Next steps' section links only to a PowerShell-based configuration guide. There are no Linux, Bash, or cross-platform CLI examples provided, nor is there mention of how to perform these tasks on Linux systems.
Recommendations
  • Add Azure CLI examples for configuring and viewing TLS policies, ensuring they work on both Windows and Linux.
  • Provide Bash script examples for Linux users where applicable.
  • Include references and links to Linux-friendly tools (e.g., OpenSSL, curl) for testing TLS connections and cipher suites.
  • Ensure that documentation for configuration and management tasks is platform-neutral, or explicitly provides both Windows (PowerShell) and Linux (CLI/Bash) instructions.
  • Update 'Next steps' to include links to cross-platform guides, not just PowerShell.
GitHub Create Pull Request
Application Gateway Certificates required to allow backend servers ...ion-gateway/certificates-for-backend-authentication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exclusively provides certificate export instructions using Windows Certificate Manager and PowerShell, with screenshots and step-by-step guidance tailored to Windows users. There are no examples or guidance for performing equivalent operations on Linux or macOS, nor are cross-platform tools (such as OpenSSL) mentioned. The 'Next steps' section also references PowerShell specifically for further configuration.
Recommendations
  • Add equivalent certificate export instructions for Linux and macOS using OpenSSL or other native tools.
  • Provide command-line examples for exporting certificates in Base-64 encoded X.509 (.CER) format using OpenSSL.
  • Include screenshots or terminal output for Linux/macOS workflows.
  • Mention cross-platform tools and clarify that the process is not limited to Windows.
  • Update 'Next steps' to reference both PowerShell and CLI/Bash alternatives for configuring Application Gateway.
GitHub Create Pull Request
Application Gateway WebSocket support in Azure Application Gateway ...s/application-gateway/application-gateway-websocket.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily by referencing Azure PowerShell and linking to a 'quick-create-powershell.md' page as the next step, without mentioning or providing equivalent Linux or cross-platform CLI examples. There is no mention of Azure CLI, Bash, or Linux-specific tooling, nor are there examples or guidance for users on non-Windows platforms. The configuration snippets are generic ARM template JSON, which is platform-neutral, but the operational guidance and next steps are Windows-centric.
Recommendations
  • Include Azure CLI (az) examples alongside or before PowerShell examples for creating and configuring Application Gateway listeners and backend pools.
  • Update the 'Next steps' section to reference both PowerShell and Azure CLI quick-create guides, or provide a unified guide with both sets of instructions.
  • Explicitly mention that configuration can be performed on Linux, macOS, or Windows, and provide links to cross-platform tooling.
  • Add Bash or shell script examples where appropriate, especially for backend server configuration or health probe testing.
  • Ensure parity in documentation by reviewing all operational instructions for platform neutrality and including Linux/macOS alternatives wherever Windows/PowerShell is referenced.
GitHub Create Pull Request
Application Gateway Azure Application Gateway infrastructure configuration ...es/application-gateway/configuration-infrastructure.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily through its use of Azure PowerShell cmdlets for operational examples (such as restarting the Application Gateway), without providing equivalent Azure CLI or Linux shell commands. References to tooling and operational steps are Windows-centric, and there are no explicit Linux or cross-platform examples or instructions. This may disadvantage users who prefer or require Linux-based workflows.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands for all operational tasks, especially for actions like restarting the Application Gateway.
  • Explicitly mention that both PowerShell and Azure CLI are supported, and link to cross-platform installation guides for Azure CLI.
  • Where possible, include bash/Linux shell command snippets for common tasks, or clarify that instructions apply equally to Linux and macOS environments.
  • Review all sections for implicit assumptions of Windows environments and add clarifications or alternatives for Linux users.
  • Add a note or section on cross-platform management, highlighting parity between Windows and Linux tooling for Azure operations.
GitHub Create Pull Request
Application Gateway Configure an internal load balancer (ILB) endpoint ...configure-application-gateway-with-private-frontend-ip.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server as the VM image in examples, providing only PowerShell-based instructions for backend setup (IIS installation), and omitting Linux-based alternatives or CLI examples. Windows tools and patterns (IIS, PowerShell) are mentioned and used without reference to Linux equivalents, and Windows is presented as the default/only option for backend servers.
Recommendations
  • Include Linux-based examples, such as using Ubuntu or CentOS as VM images.
  • Provide instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs using Bash/Azure CLI.
  • Offer both PowerShell and Bash/Azure CLI commands for VM extension configuration.
  • Present Windows and Linux options side-by-side or in parallel sections to ensure parity.
  • Explicitly mention that backend pools can use Linux VMs and provide guidance for their setup.
GitHub Create Pull Request
Application Gateway Create Azure Application Gateway custom error pages ...blob/main/articles/application-gateway/custom-error.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively provides Azure PowerShell examples for configuring custom error pages in Application Gateway, with no mention of Azure CLI, Bash, or Linux-native tooling. The configuration section is labeled 'Azure PowerShell configuration' and links only to PowerShell cmdlet references. There are no Linux or cross-platform command-line instructions, and PowerShell is presented as the sole automation method, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, demonstrating how to set custom error pages using az network application-gateway commands.
  • Include Bash script snippets for Linux users, showing how to automate configuration via Azure CLI.
  • Explicitly mention that both PowerShell and CLI can be used, and provide links to CLI documentation.
  • Ensure screenshots and UI instructions do not assume a Windows environment.
  • Review references and links to ensure parity between PowerShell and CLI documentation.
GitHub Create Pull Request
Application Gateway Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal ...es/application-gateway/create-multiple-sites-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits a clear Windows bias. Virtual machine creation is demonstrated exclusively with Windows Server, and all backend configuration and testing instructions (IIS installation, hosts file editing, DNS commands) use Windows-specific tools and paths. PowerShell is the only scripting environment referenced for VM extension management. There are no Linux VM examples, nor are Linux equivalents (such as Apache/Nginx setup, /etc/hosts editing, or Bash commands) provided or mentioned.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu), including steps for installing a web server such as Apache or Nginx.
  • Include Linux-specific commands for editing /etc/hosts and managing DNS cache (e.g., 'sudo nano /etc/hosts', 'sudo systemd-resolve --flush-caches').
  • Offer Bash/Azure CLI examples alongside PowerShell for VM extension management and other automation tasks.
  • Clarify that Application Gateway supports both Windows and Linux backends, and show how to configure each.
  • Add screenshots or code snippets demonstrating Linux workflows where appropriate.
GitHub Create Pull Request
Application Gateway Tutorial: Create an application gateway with URL path-based routing rules using Azure portal ...rticles/application-gateway/create-url-route-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. It exclusively uses Windows Server virtual machines as backend examples, provides only PowerShell commands for configuration (specifically for installing IIS), and focuses on IIS (a Windows web server) for testing. There are no Linux VM creation steps, no Linux web server installation instructions (e.g., Apache or Nginx), and no Bash or Azure CLI examples for Linux users. Windows tools and patterns are mentioned first and exclusively throughout the tutorial.
Recommendations
  • Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
  • Include steps to install a Linux web server (such as Apache or Nginx) on the Linux VMs, with corresponding commands.
  • Provide Azure CLI or Bash examples for installing web servers and configuring VM extensions on Linux.
  • Mention Linux as a supported backend OS in the prerequisites and throughout the tutorial.
  • Show screenshots and test results for both Windows (IIS) and Linux (Apache/Nginx) backend pools.
  • Ensure that references to tools and commands are platform-neutral or presented in both Windows and Linux variants.
GitHub Create Pull Request
Application Gateway Diagnostic logs for Application Gateway for Containers ...cles/application-gateway/for-containers/diagnostics.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides detailed instructions for enabling diagnostic logging via the Azure portal and PowerShell, both of which are Windows-centric tools. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or ARM templates. The PowerShell example is the only command-line method shown, and it is presented before any mention of Linux alternatives (which are absent). This creates a bias toward Windows users and may hinder Linux users from easily following the documentation.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash script samples for common logging tasks.
  • Mention and provide examples for ARM template or Bicep deployments for diagnostic settings.
  • Explicitly state that the instructions apply to both Windows and Linux, and clarify tool availability.
  • Reorder examples so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside PowerShell.
GitHub Create Pull Request
Application Gateway What is Application Gateway for Containers? ...rticles/application-gateway/for-containers/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows evidence of Windows bias primarily in the 'Deployment strategies' section, where Windows-centric tools (Azure portal, CLI, PowerShell, Terraform) are listed for resource management. PowerShell is mentioned explicitly, and no Linux-specific tools or examples (such as Bash, Azure CLI on Linux, or kubectl commands) are provided. The order of tools also places PowerShell before Terraform, which may reinforce a Windows-first perspective. There are no explicit Linux or cross-platform command examples, nor is there guidance for Linux users.
Recommendations
  • Include Linux-specific and cross-platform examples, such as Azure CLI commands run from Bash or shell scripts.
  • Clarify that Azure CLI and Terraform are cross-platform and can be used on Linux, macOS, and Windows.
  • Provide example workflows for both Windows (PowerShell) and Linux (Bash/shell), especially for resource provisioning and management.
  • Avoid listing PowerShell before cross-platform tools unless contextually relevant; consider grouping tools by platform or indicating their cross-platform nature.
  • Add a note or section highlighting parity and best practices for Linux users managing Application Gateway for Containers.
GitHub Create Pull Request
Application Gateway Troubleshoot session affinity issues ...oubleshoot-application-gateway-session-affinity-issues.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is the only CLI example given for checking settings, and Fiddler (a Windows-only tool) is exclusively used for traffic analysis, with installation instructions referencing Windows-specific actions (e.g., 'Run as administrator'). No Linux equivalents (such as Azure CLI, tcpdump, curl, or Wireshark) are mentioned, nor are Linux troubleshooting workflows or tools provided.
Recommendations
  • Provide Azure CLI examples for checking Application Gateway settings, alongside PowerShell.
  • Include Linux-compatible web debugging tools (e.g., Wireshark, mitmproxy, curl) and show how to use them for session affinity troubleshooting.
  • Add installation and usage instructions for these tools on Linux and macOS.
  • Ensure screenshots and step-by-step guides are platform-agnostic or include both Windows and Linux workflows.
  • Explicitly mention that Fiddler is Windows-only and suggest alternatives for other operating systems.
GitHub Create Pull Request
Application Gateway HTTP response codes - Azure Application Gateway ...in/articles/application-gateway/http-response-codes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing NTLM authentication (a Windows-specific protocol) and linking to Windows documentation first when discussing backend authentication issues. IIS (a Windows web server) is mentioned and explained in detail before Nginx (a popular Linux web server), with configuration guidance and links provided for IIS but less detail for Nginx. There are no examples or troubleshooting steps using Linux tools or environments, and no mention of Linux-specific authentication mechanisms or troubleshooting patterns.
Recommendations
  • Include Linux-specific authentication scenarios (e.g., Kerberos, LDAP) and troubleshooting steps alongside NTLM.
  • Provide equivalent configuration and troubleshooting details for popular Linux web servers (e.g., Apache, Nginx) before or alongside IIS.
  • Add examples and links for Linux tools and commands (e.g., curl, journalctl, systemd logs) for troubleshooting.
  • Ensure that references to backend server configuration (timeouts, authentication) are presented in a cross-platform manner, not Windows-first.
  • Balance documentation by providing parity in detail and guidance for both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Application Gateway high traffic volume support ...n/articles/application-gateway/high-traffic-support.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a mild Windows bias, primarily through references to PowerShell for configuration tasks (e.g., WAF custom rules, TLS policy configuration) and the lack of equivalent Linux/CLI examples. No explicit Linux tools or shell commands are provided, and PowerShell is mentioned as the method for certain advanced configurations. There are no examples or instructions for Bash, Azure CLI, or other cross-platform tools, which may disadvantage Linux users.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all tasks currently described with PowerShell, especially for configuring WAF custom rules and TLS policies.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) before or alongside PowerShell, making it clear that these tasks can be performed on Linux, macOS, and Windows.
  • Add links to documentation pages that describe how to perform the same configuration steps using Azure CLI or ARM templates.
  • Review all configuration and automation instructions to ensure Linux parity and avoid implying PowerShell is the only or preferred method.
GitHub Create Pull Request
Application Gateway Create an ingress controller by using an existing Application Gateway deployment ...ication-gateway/ingress-controller-install-existing.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Several command examples use PowerShell scripting and variables (e.g., $resourceGroup, $identityName), which are specific to Windows environments and not directly compatible with Linux/macOS shells. PowerShell examples are provided before or instead of Bash equivalents in key identity and role assignment steps. The backup section references PowerShell scripts as part of the exported templates. While Azure CLI and Bash commands are present, the use of PowerShell syntax and variables may hinder Linux parity and accessibility.
Recommendations
  • Provide all command examples in both Bash (sh) and PowerShell, or default to Bash for cross-platform compatibility.
  • Replace PowerShell variable syntax ($var) with Bash equivalents (var=value) and use Bash command substitution where appropriate.
  • Explicitly mention Linux/macOS compatibility for all CLI commands and scripts.
  • Ensure that any referenced scripts (e.g., in exported templates) include Bash versions alongside PowerShell.
  • Review and update all code blocks to use Bash unless a Windows-specific scenario is being described.
  • Add a note clarifying that PowerShell commands are for Windows users and provide Bash alternatives for Linux/macOS users.
GitHub Create Pull Request
Application Gateway Configure Application Gateway with a frontend public IPv6 address using the Azure portal ...application-gateway/ipv6-application-gateway-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates Windows bias by exclusively using Windows Server as the backend VM example and providing only PowerShell commands for backend configuration (IIS installation). There are no Linux VM examples, nor are there instructions for installing a web server on Linux or using Bash/CLI commands. Windows tools and patterns are mentioned exclusively, and Linux alternatives are absent.
Recommendations
  • Add Linux VM examples alongside Windows, such as Ubuntu or CentOS, for backend pool configuration.
  • Provide instructions for installing a web server (e.g., Apache or Nginx) on a Linux VM, including relevant Bash/CLI commands.
  • Include Azure CLI and/or Bash script examples for backend configuration, not just PowerShell.
  • Mention that both Windows and Linux VMs are supported as backend targets, and link to relevant documentation for each.
  • Ensure screenshots and walkthroughs demonstrate parity between Windows and Linux scenarios.
GitHub Create Pull Request
Application Gateway Hosting multiple sites on Azure Application Gateway ...articles/application-gateway/multiple-site-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently mentioning Azure PowerShell before Azure CLI in both instructions and links, and by providing PowerShell-specific flags and examples. The 'Next steps' section lists PowerShell before CLI, and the wildcard host names section gives PowerShell syntax first. There are no Linux-specific tools or shell examples (e.g., Bash), and the CLI instructions are generic rather than tailored for Linux environments. The documentation assumes familiarity with PowerShell, a Windows-centric tool, and does not provide parity for Linux users beyond the CLI.
Recommendations
  • Alternate the order of PowerShell and CLI instructions, or list CLI first to balance representation.
  • Provide explicit Bash shell examples for CLI commands, including Linux-specific nuances (such as quoting, environment variables, etc.).
  • Include a section or note for Linux users, highlighting any differences or considerations when using Azure CLI on Linux.
  • Reference cross-platform tools (e.g., Terraform, ARM templates) earlier and more prominently to avoid Windows tool bias.
  • Ensure that all examples and walkthroughs are available for both PowerShell and CLI, and consider adding screenshots or terminal outputs from Linux environments.
GitHub Create Pull Request
Application Gateway Export trusted client CA certificate chain for client authentication ...ateway/mutual-authentication-certificate-management.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily Windows-centric: all certificate export steps rely on Windows GUI tools (Certificate Manager, Certificate Export Wizard) and PowerShell is mentioned as the way to open certificate management. Linux alternatives (such as using OpenSSL or command-line tools) are not provided for exporting certificates or viewing certificate chains. Only in the final concatenation step is a Linux command shown, and even there, the Windows command is listed first. There are no screenshots or step-by-step instructions for Linux environments.
Recommendations
  • Provide equivalent Linux instructions for exporting certificates, e.g., using OpenSSL to extract public and CA certificates.
  • Include Linux command-line examples for viewing certificate details and exporting certificate chains.
  • Add screenshots or terminal output examples for Linux workflows.
  • Mention Linux tools (such as openssl, certtool) alongside Windows tools, and avoid listing Windows steps first by default.
  • Clarify that the process can be performed on both Windows and Linux, and provide parity in guidance for both platforms.
GitHub Create Pull Request
Application Gateway Deploy an Azure Application Gateway with an IPv6 frontend ...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates bias towards Windows environments by exclusively using IIS (a Windows web server) for backend validation, referencing Azure PowerShell for resource cleanup, and omitting Linux-based alternatives or examples. There are no instructions or examples for deploying or validating with Linux VMs (e.g., using Apache or Nginx), nor are Linux command-line tools (such as Azure CLI or Bash) used for resource management.
Recommendations
  • Include examples for deploying Linux VMs in the backend pool, such as Ubuntu with Apache or Nginx, alongside or instead of IIS.
  • Provide validation steps using Linux-based web servers (e.g., curl to test Apache/Nginx response) in addition to IIS.
  • Offer resource cleanup instructions using Azure CLI (az group delete) and Bash, not just Azure PowerShell.
  • Clarify that both Windows and Linux VMs are supported and provide parity in documentation examples.
  • Add notes or links to relevant Linux documentation for users who prefer non-Windows environments.
GitHub Create Pull Request
Application Gateway TLS termination with Azure Key Vault certificates ...b/main/articles/application-gateway/key-vault-certs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for key configuration steps, referencing PowerShell before Azure CLI or ARM templates, and omitting explicit Linux shell (bash) or cross-platform CLI instructions. The use of PowerShell-centric tooling and terminology may disadvantage Linux users or those preferring bash/CLI workflows.
Recommendations
  • Provide equivalent Azure CLI (bash) examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
  • Explicitly mention cross-platform compatibility and clarify which steps can be performed using CLI, ARM templates, or Bicep, not just PowerShell.
  • Reorder examples so that CLI/bash instructions are presented before or alongside PowerShell, ensuring Linux parity.
  • Add troubleshooting and automation guidance for Linux environments, including scripting with Azure CLI.
  • Include notes or links to platform-agnostic documentation for certificate management and deployment.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and references before CLI equivalents, and by omitting any Linux-specific certificate management or command-line examples (e.g., OpenSSL). The 'Next steps' section directs users to a PowerShell-focused guide, reinforcing the Windows-centric approach. There is no mention of Linux tools or workflows for certificate extraction, management, or validation, and the CLI example is minimal compared to the PowerShell section.
Recommendations
  • Add Linux-specific examples for certificate extraction and management, such as using OpenSSL commands to extract and prepare certificate chains.
  • Provide parity in example depth for Azure CLI and PowerShell, ensuring CLI instructions are as comprehensive as PowerShell ones.
  • Include references to Linux tools and workflows (e.g., bash scripts, OpenSSL, keytool) for certificate handling and validation.
  • In 'Next steps', link to both PowerShell and Azure CLI guides, and consider adding a Linux-focused walkthrough.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users throughout the documentation.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell scripts and commands for migration and preview registration, with no mention of Linux shell equivalents or cross-platform CLI usage. The 'Next steps' section links to a PowerShell-based tutorial, and the migration guidance centers on a PowerShell script from the PowerShell Gallery. There is no coverage of Bash, Azure CLI, or Linux-native tooling, nor are Linux-specific examples or instructions provided.
Recommendations
  • Provide equivalent Azure CLI (bash/shell) examples for all PowerShell commands, especially for migration and preview registration/unregistration.
  • Include links to tutorials for creating and managing Application Gateway using Azure CLI on Linux/macOS.
  • Explicitly mention cross-platform support and clarify which instructions are OS-agnostic.
  • Where PowerShell scripts are referenced, note how Linux users can run them (e.g., via Azure Cloud Shell) or provide alternative scripts in Bash.
  • Ensure that Linux and macOS users are considered in all step-by-step guides and migration instructions.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway Private Link ...articles/application-gateway/private-link-configure.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and cmdlet references, which are native to Windows environments. The PowerShell tab and examples precede the Azure CLI section, and the CLI examples are less detailed. There is no mention of Linux-specific tools, shell environments, or cross-platform scripting considerations. The documentation assumes familiarity with Windows-centric tools and patterns, which may disadvantage Linux users.
Recommendations
  • Provide Bash shell examples alongside Azure CLI commands, including environment setup and scripting best practices for Linux users.
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples, covering all steps and edge cases.
  • Mention and link to Linux-specific documentation or troubleshooting guides where relevant.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and provide guidance for installing and using CLI on Linux.
  • Consider reordering sections so that CLI examples appear before or alongside PowerShell, to avoid implicit prioritization of Windows tools.
  • Include notes or tips for Linux users, such as handling environment variables, file paths, and permissions.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using the portal ...in/articles/application-gateway/quick-create-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server virtual machines as backend targets and providing only Windows-specific instructions (such as installing IIS via PowerShell). There are no Linux VM examples, nor instructions for installing a Linux web server (e.g., Apache or Nginx). The only VM creation walkthrough uses Windows Server, and the only backend setup uses IIS and PowerShell. The testing and verification steps are also Windows-centric. While Azure CLI is mentioned as an alternative, all concrete examples and screenshots are Windows-focused.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux-specific commands for installing a web server (such as Apache or Nginx) for testing.
  • Include examples using Bash/SSH in Azure Cloud Shell, not just PowerShell.
  • Show how to add Linux VMs to the backend pool and verify connectivity.
  • Ensure screenshots and walkthroughs represent both Windows and Linux scenarios.
  • Explicitly mention that Application Gateway supports both Windows and Linux backends, and link to relevant documentation.
GitHub Create Pull Request
Application Gateway HTTP to HTTPS redirection in portal - Azure Application Gateway ...s/application-gateway/redirect-http-to-https-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All command-line examples use PowerShell, and instructions for certificate creation, IIS installation, and VM scale set configuration are tailored exclusively for Windows environments. The VM scale set defaults to Windows Server, and there are no equivalent Linux instructions or examples provided. Windows tools and patterns (e.g., New-SelfSignedCertificate, Export-PfxCertificate, IIS installation via PowerShell) are mentioned without Linux alternatives.
Recommendations
  • Provide equivalent Linux examples for certificate creation (e.g., using OpenSSL) and exporting certificates.
  • Include instructions for deploying a Linux-based VM scale set (e.g., Ubuntu) and configuring a web server such as Apache or Nginx.
  • Offer Bash/Azure CLI command alternatives alongside PowerShell commands.
  • Clarify that both Windows and Linux backend pools are supported, and link to relevant Linux documentation.
  • Demonstrate how to install and configure a web server on Linux VMs using Custom Script Extension or cloud-init.
GitHub Create Pull Request
Application Gateway Renew an Azure Application Gateway certificate ...ain/articles/application-gateway/renew-certificates.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, which is more cross-platform. The PowerShell example is detailed and uses Windows-centric patterns (e.g., ConvertTo-SecureString), while the CLI example is less emphasized. There are no Linux-specific instructions, nor are Linux command-line tools (like OpenSSL) mentioned for certificate handling. The portal instructions also implicitly assume a Windows workflow (PFX format, GUI navigation) without discussing Linux alternatives.
Recommendations
  • Provide Linux-specific examples, such as using OpenSSL to generate or convert certificates.
  • Present Azure CLI instructions before or alongside PowerShell, highlighting its cross-platform nature.
  • Mention certificate formats commonly used on Linux (e.g., PEM) and how to convert them to PFX if needed.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide command-line steps for Linux users.
  • Add troubleshooting tips for Linux environments, such as file permissions or path conventions.
GitHub Create Pull Request
Application Gateway Generate self-signed certificate with a custom root CA ...ticles/application-gateway/self-signed-certificates.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits mild Windows bias. Windows and Windows-specific tools (IIS, PowerShell) are mentioned before or more prominently than their Linux equivalents. The Azure PowerShell example is provided in detail, while Azure CLI is only briefly mentioned as an alternative. IIS instructions are listed before Apache and NGINX, and Windows file paths are used in PowerShell examples. There are no Linux-specific automation examples for uploading certificates to Application Gateway.
Recommendations
  • Provide Azure CLI examples alongside or before Azure PowerShell, especially for certificate upload and configuration.
  • Include Linux file path examples in addition to Windows paths in code samples.
  • Offer automation instructions for Linux environments, such as Bash scripts for certificate upload.
  • Balance the order of web server configuration instructions (e.g., alternate between IIS, Apache, and NGINX or group by OS).
  • Explicitly mention Linux equivalents for steps involving Windows tools (e.g., how to add a root certificate to Linux trusted store).
GitHub Create Pull Request
Application Gateway Enabling end to end TLS on Azure Application Gateway ...blob/main/articles/application-gateway/ssl-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific certificate formats (PFX), linking to Windows API documentation (PFXImportCertStore), and providing configuration instructions and next steps primarily via PowerShell. There are no Linux or cross-platform CLI examples, and Windows tools/patterns are mentioned exclusively or before any Linux equivalents. The guidance assumes familiarity with Windows-centric tooling and omits Linux-native certificate management and configuration approaches.
Recommendations
  • Provide equivalent instructions and examples for Linux users, such as using Azure CLI, Bash scripts, or ARM templates for configuration.
  • Reference cross-platform certificate formats and tools (e.g., PEM, OpenSSL) alongside PFX and Windows APIs.
  • Include links to Linux certificate management documentation and tools (e.g., OpenSSL, certbot).
  • Add parity in troubleshooting and configuration guides for both Windows and Linux environments.
  • Ensure that next steps and quickstarts offer both PowerShell and Azure CLI/Bash alternatives.
GitHub Create Pull Request
Automation Convert configurations to composite resources for Azure Automation State Configuration ...articles/automation/automation-dsc-create-composite.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows PowerShell and Windows-centric tools and patterns. All examples and instructions are PowerShell-based, with no mention of Linux equivalents or cross-platform DSC authoring. References to configuration management, module creation, and automation are exclusively tied to Windows PowerShell and related repositories, with Linux support only briefly mentioned in passing (e.g., onboarding physical/virtual Linux machines) and no concrete examples or guidance provided.
Recommendations
  • Add explicit examples and instructions for authoring and converting configurations on Linux systems, using cross-platform PowerShell (pwsh) where appropriate.
  • Clarify which steps and tools are compatible with Linux, and provide alternatives or notes for Linux users.
  • Include Linux-specific scenarios (e.g., Apache web server, iptables firewall) alongside Windows scenarios.
  • Reference and link to documentation for DSC on Linux, including supported resources and configuration patterns.
  • Ensure that onboarding and usage instructions for both Windows and Linux are presented with parity, ideally side-by-side.
GitHub Create Pull Request
Automation Remediate noncompliant Azure Automation State Configuration servers ...b/main/articles/automation/automation-dsc-remediate.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by presenting Windows remediation steps first, providing detailed PowerShell examples and references, and focusing on Windows tools (PowerShell, Chocolatey) with direct code samples. In contrast, Linux remediation is described in more abstract terms, lacks direct script/code examples, and refers to external documentation for details. The Windows workflow is more streamlined and better supported, while Linux instructions are less clear and actionable.
Recommendations
  • Provide direct Linux command/script examples for remediation, similar to the PowerShell example for Windows.
  • Include step-by-step instructions for Linux drift correction, not just references to external documentation.
  • Present Windows and Linux remediation options in parallel sections, giving equal prominence and detail.
  • Reference Linux-native tools and workflows (e.g., shell scripts, Ansible, native DSC commands) where appropriate.
  • Avoid using Windows tools (e.g., Chocolatey) as the sole example for continuous deployment pipelines; include Linux alternatives.
GitHub Create Pull Request
Automation Compile DSC configurations in Azure Automation State Configuration ...lob/main/articles/automation/automation-dsc-compile.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples use Windows PowerShell, and all tooling references are for Windows-based tools (PowerShell cmdlets, WindowsFeature resource, etc.). There are no examples or guidance for compiling DSC configurations on Linux, nor are Linux tools or workflows mentioned. The structure and language consistently prioritize Windows and PowerShell, with no parity for Linux users.
Recommendations
  • Add explicit guidance and examples for compiling DSC configurations on Linux, using native Linux tools or cross-platform PowerShell Core.
  • Include Linux-specific resources and workflows, such as using OpenSSH, Linux file paths, and Linux DSC resources.
  • Clarify any limitations or differences for Linux users, especially in light of the referenced 'automation-dsc-linux-retirement-announcement'.
  • Where PowerShell is referenced, specify whether PowerShell Core (cross-platform) is supported, and provide examples for both Windows and Linux environments.
  • Mention alternative configuration management tools or patterns for Linux if DSC support is deprecated or limited.
GitHub Create Pull Request
Application Gateway Tutorial: Protect your application gateway with Azure DDoS Network Protection ...n-gateway/tutorial-protect-application-gateway-ddos.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server virtual machines as backend examples, providing only PowerShell commands for IIS installation, and omitting any Linux VM or Linux web server setup instructions. Windows tools and patterns (IIS, PowerShell) are mentioned and used without Linux equivalents, and Windows is presented as the default/first choice for backend servers.
Recommendations
  • Include parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu) alongside Windows examples.
  • Provide Linux-specific commands (such as Bash/SSH and apt-get for installing Apache or Nginx) for web server setup and verification.
  • Offer Azure CLI or Bash script examples in addition to PowerShell for VM extension management and configuration.
  • Explicitly mention that Application Gateway supports both Windows and Linux backends, and illustrate with examples.
  • Balance screenshots and walkthroughs to show both Windows and Linux VM creation and configuration in the Azure portal.
GitHub Create Pull Request
Artifact Signing Sign a CI policy by using Artifact Signing ...ain/articles/artifact-signing/how-to-sign-ci-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All examples use PowerShell, with explicit instructions to install Azure PowerShell for Windows. File paths and commands use Windows conventions (e.g., C:\temp), and there are no Linux or cross-platform CLI examples. The prerequisites and workflow assume a Windows environment, and related links focus exclusively on Windows Defender Application Control.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS, using PowerShell Core or Azure CLI where possible.
  • Include Linux-style file paths and clarify cross-platform compatibility of the Az.TrustedSigning module.
  • Add a section on installing and using Azure PowerShell and Az.TrustedSigning on Linux/macOS.
  • Mention and link to Linux-specific documentation or use-cases for CI policy signing, if supported.
  • Clarify whether the signing process is supported on non-Windows platforms, and if not, explicitly state this limitation.
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page is heavily focused on Windows and PowerShell tooling, with all examples, instructions, and referenced modules using PowerShell and Windows-centric patterns. There are no Bash, CLI, or Linux-native examples, and Windows tools and terminology (such as PSCredential, Windows PowerShell, and PowerShell-specific cmdlets) are used exclusively and introduced first. No Linux or cross-platform alternatives are mentioned.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for Linux users.
  • Mention cross-platform authentication approaches, such as using service principals or managed identities via CLI.
  • Clarify which steps and modules are available on Linux/macOS and which are Windows-only.
  • Reference Linux-compatible credential management patterns (e.g., environment variables, Azure CLI credential store).
  • Provide links to Azure CLI documentation and examples alongside PowerShell references.
  • Explicitly state platform requirements and limitations for each method.
GitHub Create Pull Request
Automation Move your Azure Automation account to another subscription ...s/blob/main/articles/automation/how-to/move-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides command-line examples exclusively using Azure PowerShell cmdlets (e.g., Remove-AzResource, Remove-AzActionGroup), which are most commonly used in Windows environments. There are no equivalent Azure CLI or Bash examples, which are preferred on Linux and macOS. The documentation also references PowerShell-specific tooling and patterns, without mentioning or prioritizing cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, using az resource and az monitor action-group commands.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance for Linux/macOS users.
  • Where screenshots or instructions reference the Azure portal, clarify that the portal is cross-platform.
  • Consider including Bash script examples for resource management tasks.
  • Review and update troubleshooting and verification steps to ensure parity for users on Linux and macOS.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias by exclusively providing PowerShell examples and cmdlets, referencing Windows-centric tools (e.g., PowerShell, Add-AzureCertificate), and omitting Linux-native approaches or CLI examples. The certificate management workflow is described almost entirely in terms of PowerShell and Windows cryptography providers, with no mention of Linux shell commands, OpenSSL, or cross-platform alternatives. Python examples are included, but only in the context of Azure Automation runbooks, not for general certificate management. There are no Linux-specific instructions or parity for users who may be managing certificates from Linux environments.
Recommendations
  • Add Azure CLI examples for certificate management tasks, such as uploading, retrieving, and deleting certificates.
  • Include instructions and examples for managing certificates using Linux shell commands (e.g., OpenSSL for certificate creation and manipulation).
  • Reference cross-platform tools and patterns, such as Azure CLI and REST API, before or alongside PowerShell cmdlets.
  • Clarify that PowerShell is available on Linux and macOS, but also provide native Linux command alternatives where appropriate.
  • Document any platform-specific requirements or limitations, such as cryptographic provider compatibility, for both Windows and Linux.
  • Provide troubleshooting steps for Linux users, especially for certificate file formats and permissions.
GitHub Create Pull Request
Automation Quickstart - Create an Azure Automation account using the portal .../quickstarts/create-azure-automation-account-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses exclusively on using the Azure portal UI to create an Automation account, with no mention of command-line alternatives (such as Azure CLI or Bash). The only 'Next steps' tutorial explicitly references PowerShell, which is primarily a Windows-centric tool, and does not provide parity for Linux users (e.g., Bash, Azure CLI, or Python SDK). There are no examples or instructions tailored for Linux environments, nor are Linux tools or patterns mentioned.
Recommendations
  • Include alternative instructions for creating an Automation account using Azure CLI and Bash, which are cross-platform and widely used on Linux.
  • Add 'Next steps' links to tutorials for creating runbooks using Azure CLI, Bash, or Python SDK, not just PowerShell.
  • Explicitly mention that PowerShell is available cross-platform, but also provide Linux-native examples to ensure parity.
  • Where screenshots or UI instructions are given, consider adding CLI equivalents for users who prefer or require command-line automation.
GitHub Create Pull Request
Automation Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation ...icles/automation/troubleshoot/hybrid-runbook-worker.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a Windows bias in several ways: troubleshooting steps and examples are frequently presented for Windows first, with detailed PowerShell commands and references to Windows-specific tools (event logs, registry keys, config files in C:\Program Files, etc.). Linux troubleshooting is covered in a separate, shorter section, with fewer concrete examples and less detail. Some scenarios (e.g., updating Az modules, Set-AzStorageBlobContent issues, proxy configuration) provide only Windows/PowerShell solutions or mention Windows tools/configurations without Linux equivalents. In some cases, Linux steps are missing or less explicit, and Windows-centric terminology (e.g., 'Orchestrator.Sandbox.exe', 'Microsoft-SMA event log') is used throughout.
Recommendations
  • Ensure that every troubleshooting scenario includes both Windows and Linux steps/examples where applicable.
  • Provide Linux equivalents for all PowerShell commands (e.g., Bash scripts, systemctl/service commands, log file locations).
  • Mention Linux tools and patterns (e.g., systemd, journalctl, /var/log paths) alongside Windows tools, not just in a separate section.
  • Avoid presenting Windows solutions first by default; alternate or parallelize Windows and Linux instructions.
  • Expand Linux troubleshooting details to match the depth and specificity of Windows guidance, including error messages, config file paths, and command-line examples.
  • Where Windows-specific configuration files are referenced (e.g., Orchestrator.Sandbox.exe.config), clarify if there is a Linux equivalent or explicitly state if not applicable.
GitHub Create Pull Request
Automation Migrate from a Run As account to Managed identities ...automation/migrate-run-as-accounts-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell for all code examples and automation scripts, referencing only Windows-centric tools and patterns (e.g., PowerShell cmdlets, AzureRM/Az modules), and omitting any examples or guidance for Linux-based automation environments (such as Python, Bash, or CLI usage). The documentation also assumes the use of PowerShell as the default automation language and does not mention or prioritize cross-platform alternatives.
Recommendations
  • Include equivalent examples using Azure CLI, Python SDK, or Bash scripts to demonstrate managed identity authentication and resource management, ensuring Linux parity.
  • Explicitly mention that Azure Automation supports Python runbooks and provide migration guidance and code samples for Python-based automation.
  • Add troubleshooting and migration notes for Linux Hybrid Runbook Workers, including how managed identities are used in non-Windows environments.
  • Reference cross-platform tools and modules (e.g., Azure CLI, REST API) alongside PowerShell, and avoid assuming PowerShell as the default or only option.
  • Reorder sections or provide parallel guidance so that Windows and Linux approaches are presented equally, rather than Windows/PowerShell first.
GitHub Create Pull Request
Automation Azure Quickstart - Configure a VM with Desired State Configuration ...n/articles/automation/quickstarts/dsc-configuration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by focusing on PowerShell-based Desired State Configuration (DSC), referencing Windows-centric tools (such as Chocolatey), and providing examples and instructions primarily in PowerShell. Although the example configures a LAMP stack (Linux), the workflow, tooling, and references are all Windows/PowerShell-centric, and there is no mention of Linux-native configuration tools or workflows. The retirement notice for Linux DSC is prominent, and no alternatives or parity guidance for Linux users are provided.
Recommendations
  • Provide equivalent Linux-native configuration management examples (e.g., using Ansible, Chef, or native Azure Policy Guest Configuration for Linux).
  • Include instructions and examples for configuring Linux VMs using non-PowerShell tools.
  • Mention and link to Linux-specific documentation and alternatives where DSC for Linux is deprecated.
  • Avoid referencing Windows tools (like Chocolatey) as the next step for Linux scenarios, or provide Linux package management alternatives.
  • Clarify the limitations and retirement of Linux DSC, and guide users to supported Linux configuration management options.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation State Configuration issues ...automation/troubleshoot/desired-state-configuration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias. Most troubleshooting steps, examples, and tools are presented using PowerShell and Windows-centric terminology. Windows-specific cmdlets, tools (such as xDscDiagnostics), and portal navigation are described in detail, while Linux equivalents are rarely mentioned or are relegated to brief notes. Linux troubleshooting is only covered in a single scenario, and there are no Linux shell command examples or references to Linux DSC logs or tools. Windows solutions are consistently presented first or exclusively.
Recommendations
  • Add Linux-specific troubleshooting steps and examples for each scenario, including shell commands and log locations.
  • Provide parity in tool references, e.g., mention Linux DSC diagnostics tools or methods alongside xDscDiagnostics.
  • Include Linux portal navigation and extension management instructions where relevant.
  • Ensure that Linux onboarding, error messages, and solutions are described with the same level of detail as Windows.
  • Where PowerShell cmdlets are referenced, add equivalent Linux commands or clarify their applicability to Linux nodes.
  • Review and update all scenarios to explicitly address both Windows and Linux environments, especially as the service approaches end-of-life for Linux support.
GitHub Create Pull Request
Artifact Signing Device Guard Signing Service migration to Artifact Signing ...gning/how-to-device-guard-signing-service-migration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased toward Windows environments. All examples, commands, and tool references are Windows-specific (e.g., PowerShell cmdlets, Windows file paths, Event Viewer, SignTool, mountvol.exe). There are no Linux equivalents or cross-platform instructions, and the migration/deployment steps assume a Windows OS. Artifact Signing is described only in the context of Windows Defender Application Control and related Windows security features.
Recommendations
  • Add equivalent Linux migration instructions if Artifact Signing supports Linux workloads or CI policies.
  • Provide examples using Linux command-line tools (e.g., bash, openssl) for policy conversion, signing, and verification.
  • Clarify whether Artifact Signing is Windows-only, or explicitly state platform limitations.
  • If Linux support exists, include instructions for locating, deploying, and validating CI policies on Linux systems.
  • Reference Linux documentation or tools where applicable (e.g., for signing, certificate management, or policy deployment).
  • Consider adding cross-platform comparison tables for commands and tools.
GitHub Create Pull Request
Artifact Signing Set up signing integrations to use Artifact Signing ...ticles/artifact-signing/how-to-signing-integrations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. The primary integration described in detail is SignTool, which is exclusive to Windows. All setup instructions, prerequisites, and examples are Windows-centric, including use of MSI installers, Windows Package Manager (winget), and PowerShell commands. There are no Linux or cross-platform equivalents provided for SignTool or the installation process. Other integrations (GitHub Actions, Azure DevOps, SDK) are only briefly mentioned, with no parity in example depth or platform-specific guidance for Linux users.
Recommendations
  • Provide equivalent Linux/macOS signing tool integration examples (e.g., using OpenSSL, GPG, or cross-platform .NET tools).
  • Include installation instructions for Artifact Signing Client Tools on Linux (using .tar.gz, .deb, .rpm, or manual extraction).
  • Offer shell (bash/zsh) command examples alongside PowerShell for download and setup.
  • Clarify which integrations are cross-platform and provide explicit Linux/macOS setup steps for each.
  • List Linux prerequisites and supported distributions where applicable.
  • Ensure that non-Windows users can follow the documentation without needing to adapt Windows-specific instructions.
GitHub Create Pull Request
Automanage Azure Automanage for Azure Arc-enabled servers ...e-docs/blob/main/articles/automanage/automanage-arc.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation lists Windows operating systems first in the supported OS section and highlights Windows-specific tools such as Microsoft Antimalware, which is only available for Windows Server. There are no Linux-specific examples or tools mentioned, and no guidance is provided for Linux anti-malware or security solutions. The configuration and onboarding instructions are generic and do not include Linux-specific steps or considerations.
Recommendations
  • List supported operating systems in alphabetical order or alternate the order to avoid implicit prioritization of Windows.
  • Include Linux-specific security and anti-malware recommendations or mention third-party solutions commonly used on Linux.
  • Provide examples or guidance for enabling Automanage on Linux systems, including any differences in configuration or troubleshooting steps.
  • Ensure that service descriptions clarify platform-specific limitations and offer alternatives for Linux where Windows-only features exist.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use dynamic configuration in a .NET app ...figuration/enable-dynamic-configuration-dotnet-core.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several areas: Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents, and screenshots and refresh instructions reference Windows-specific tools (Command Prompt, PowerShell). While Linux/macOS commands are included, Windows tools and patterns are prioritized and referenced more frequently.
Recommendations
  • Present platform instructions in parallel or start with a neutral, cross-platform approach (e.g., bash first, or all platforms side-by-side).
  • Include screenshots or references for Linux/macOS terminals, not just Windows Command Prompt/PowerShell.
  • Use generic terms like 'terminal window' instead of 'Command Prompt or PowerShell window' when referring to where users interact with the app.
  • Ensure all examples and instructions are equally detailed for Linux/macOS users, not just Windows users.
  • Explicitly mention that all steps work on Linux/macOS and provide troubleshooting notes for non-Windows platforms if needed.
GitHub Create Pull Request
Automanage SMB over QUIC with Azure Automanage machine best practices ...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively describes enabling SMB over QUIC with Azure Automanage for Windows Server 2022 Datacenter: Azure Edition VMs. All examples, prerequisites, and instructions are Windows-centric, with no mention of Linux support, Linux-compatible tools, or cross-platform considerations. References and links point only to Windows Server documentation.
Recommendations
  • Explicitly state whether SMB over QUIC and Automanage best practices are supported on Linux VMs. If not supported, clarify this early in the documentation.
  • If Linux support exists or is planned, provide equivalent instructions and examples for Linux VMs, including any required packages, configuration steps, and portal settings.
  • Include references to Linux documentation or tools where applicable, and ensure parity in guidance for certificate management and compliance monitoring.
  • If feature is Windows-only, consider a section explaining why, and suggest alternative secure file sharing solutions for Linux environments.
GitHub Create Pull Request
Automanage Move an Azure Automanage configuration profile across regions ...s/automanage/move-automanaged-configuration-profile.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. There are no equivalent examples for Linux users (e.g., using Bash, curl, or Azure CLI), nor is there mention of cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux administrators from following the guide easily.
Recommendations
  • Add equivalent Linux/Bash examples using curl or Azure CLI for all PowerShell instructions.
  • Explicitly mention that the API calls can be performed from any platform, not just Windows.
  • Provide guidance for Linux and macOS users, including environment setup and authentication steps.
  • Consider reordering examples to present cross-platform (e.g., REST API, Azure CLI) instructions before platform-specific ones like PowerShell.
GitHub Create Pull Request
Azure App Configuration Monitor Azure App Configuration ...s/azure-app-configuration/monitor-app-configuration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways. Windows tools and terminology (such as Windows PowerShell) are mentioned first or exclusively in several places. For example, when describing how to use the Azure CLI, the documentation suggests opening 'Windows PowerShell' as the example console, even though Azure CLI is cross-platform. The PowerShell section is present and detailed, but there is no equivalent section for Bash or Linux shell scripting. The instructions and examples for command-line usage reference Windows environments before Linux or macOS, and do not provide parity for Linux users.
Recommendations
  • When referencing the Azure CLI, suggest opening a 'terminal' or 'command prompt' generically, and provide examples for Bash or Linux/macOS terminals alongside Windows PowerShell.
  • Add a dedicated section for Bash/Linux shell scripting, including examples for common tasks such as authentication and diagnostic setting creation.
  • Avoid using 'Windows PowerShell' as the default example for cross-platform tools; use 'PowerShell' or 'terminal' and clarify platform compatibility.
  • Ensure that screenshots and instructions are platform-neutral or provide alternatives for Linux/macOS users.
  • Explicitly mention that all CLI commands work on Linux/macOS and provide troubleshooting tips for those platforms if needed.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with Aspire .../articles/azure-app-configuration/quickstart-aspire.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Docker Desktop (a Windows/macOS tool) as the default container runtime, omitting Linux alternatives. There are no explicit Linux-specific instructions or examples, and the setup steps and screenshots implicitly target Windows environments. The documentation does not mention Linux-native container runtimes (e.g., Podman), nor does it provide guidance for Linux users on installing prerequisites or running the emulator.
Recommendations
  • Mention and provide instructions for installing and using Linux-native container runtimes such as Podman or Docker Engine.
  • Include explicit Linux setup steps and screenshots where relevant, or clarify that the instructions apply equally to Linux.
  • When referencing Docker Desktop, add a note about alternatives for Linux users, such as Docker Engine or Podman.
  • Ensure that CLI commands and file paths are compatible with both Windows and Linux environments, and clarify any differences.
  • Add troubleshooting tips for common Linux-specific issues (e.g., permissions, networking).
GitHub Create Pull Request
Azure App Configuration Quickstart to learn how to use Azure App Configuration .../azure-app-configuration/quickstart-java-spring-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: Windows command-line instructions (setx, PowerShell) are presented before Linux/macOS equivalents, and Windows-specific tools and patterns (setx, PowerShell) are mentioned explicitly. The Linux/macOS example for setting environment variables is given last and lacks detail compared to the Windows instructions. The build/run/test steps use generic commands but are shown in Windows command prompt syntax. There is no explicit Linux shell or terminal example, and no mention of Linux-specific considerations.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in parallel, rather than listing Windows first.
  • Use generic shell syntax (e.g., $ export VAR=...) for environment variables, and provide both Windows and Linux/macOS examples with equal prominence.
  • Avoid using Windows-specific tools (e.g., setx) without offering Linux/macOS equivalents (e.g., export, or instructions for persistent environment variables).
  • Clarify that build/run commands (mvn) are cross-platform, and show examples in both Windows CMD/PowerShell and Linux/macOS terminal.
  • Add notes or sections for Linux/macOS users, including troubleshooting or environment setup tips specific to those platforms.
GitHub Create Pull Request
Azure Cache For Redis Reboot, Flush, and Schedule Updates Azure Cache for Redis ...articles/azure-cache-for-redis/cache-administration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a bias toward Windows and PowerShell by exclusively providing PowerShell cmdlets and references for management tasks such as rebooting and scheduling updates. There are no examples or instructions for equivalent operations using Linux tools, Bash, or Azure CLI, and PowerShell is mentioned before any cross-platform alternatives. This focus may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples for all management tasks (reboot, flush, schedule updates), as CLI is cross-platform.
  • Include Bash or shell script examples where appropriate, especially for Linux users.
  • Explicitly mention that PowerShell is available cross-platform, but also provide instructions for native Linux environments.
  • Reorder sections to present cross-platform tools (Azure CLI) before or alongside PowerShell.
  • Add links to documentation for Linux/macOS management of Azure Cache for Redis.
GitHub Create Pull Request
Azure Cache For Redis Remove TLS 1.0 and 1.1 from use with Azure Cache for Redis ...ticles/azure-cache-for-redis/cache-remove-tls-10-11.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts and examples for checking and configuring TLS settings on Azure Cache for Redis. There are no equivalent Linux shell (bash) or cross-platform CLI examples for these tasks. The instructions and tooling referenced (PowerShell, Az.RedisCache module) are Windows-centric and appear before any mention of Azure CLI, which is only briefly referenced and not exemplified. No Linux or macOS-specific guidance is provided for verifying TLS versions or configuring the cache.
Recommendations
  • Provide bash or shell script examples for checking TLS versions from Linux/macOS environments.
  • Include Azure CLI commands for both checking and configuring Minimum TLS Version, with clear instructions for Linux/macOS users.
  • Add notes or sections explicitly addressing how to perform these tasks on non-Windows platforms.
  • Ensure that cross-platform tools (like Azure CLI) are presented before or alongside Windows-specific tools.
  • Reference Linux-native tools (such as openssl or nmap) for TLS version detection and provide sample commands.
GitHub Create Pull Request
Automanage Tutorial - python ...ticles/automanage/tutorial-create-assignment-python.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for creating Windows virtual machines and referencing Windows-centric tools (PowerShell). There are no Linux VM creation examples, nor any mention of Linux-specific patterns or considerations. The Azure CLI installation link defaults to Windows instructions, and PowerShell is presented as an equal alternative to Azure CLI, which is more cross-platform. No Linux shell or VM examples are given.
Recommendations
  • Add examples for creating Linux virtual machines using both Azure CLI and PowerShell (e.g., using --image UbuntuLTS).
  • Include Linux shell (bash) instructions and clarify cross-platform usage for Azure CLI.
  • Provide parity in documentation for Linux environments, such as mentioning SSH key authentication and Linux-specific VM configuration.
  • Update installation instructions for Azure CLI to reference cross-platform guides, not just Windows.
  • Balance the use of PowerShell and CLI by clarifying platform compatibility and suggesting CLI for Linux/macOS users.
GitHub Create Pull Request
Automanage Create a custom profile in Azure Automanage for VMs ...articles/automanage/virtual-machines-custom-profile.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation displays a Windows bias by referencing Windows-specific features (such as Windows Admin Center and audit modes for Windows machines only) without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or instructions tailored for Linux VMs, and Windows tools are referenced exclusively. The documentation assumes a Windows-centric use case, omitting Linux-specific configuration or parity.
Recommendations
  • Add explicit guidance and examples for Linux VMs, including any differences in supported services and settings.
  • Clarify which features are Windows-only and provide Linux alternatives or note limitations for Linux users.
  • Include Linux-specific tools or configuration instructions where relevant (e.g., mention Linux security baselines, antimalware options, or monitoring agents).
  • Ensure that examples and feature lists are presented in a cross-platform manner, not prioritizing Windows features or tools.
  • Add a section or table comparing feature support between Windows and Linux VMs in Azure Automanage.
GitHub Create Pull Request
Automation Using a user-assigned managed identity for an Azure Automation account ...main/articles/automation/add-user-assigned-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. PowerShell is used almost exclusively for all command-line examples, including REST API calls, ARM template deployments, and role assignments. There are no Bash, Azure CLI, or Linux shell examples provided. Even when discussing REST API or HTTP endpoints, the examples use PowerShell rather than cross-platform tools like curl or Azure CLI. Windows tools and patterns (e.g., PowerShell cmdlets, Windows-style file paths) are mentioned first and often exclusively, with Linux equivalents missing.
Recommendations
  • Add Azure CLI examples for all operations (e.g., assigning managed identities, role assignments, ARM template deployments).
  • Provide Bash or shell script examples for REST API calls, using curl or wget, to demonstrate Linux compatibility.
  • Include Linux file path conventions and clarify that examples work on both Windows and Linux, or provide OS-specific notes.
  • Reorder sections so that cross-platform or OS-neutral methods (e.g., Azure portal, REST API, Azure CLI) are presented before or alongside PowerShell.
  • Explicitly mention Linux support for Automation accounts and managed identities, and link to Linux-specific documentation if available.
GitHub Create Pull Request
Azure Cache For Redis Managed identity for storage accounts ...ticles/azure-cache-for-redis/cache-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. While it mentions both Azure CLI and Azure PowerShell, the PowerShell example is given equal prominence to the CLI, and both are presented after the Azure Portal instructions. There are no explicit Linux-specific instructions or examples, and the PowerShell example is not marked as Windows-only, which may imply parity where there is none. The screenshots and instructions are all based on the Azure Portal, which is cross-platform, but there is no mention of Linux shell scripting or alternative tools. There is also no mention of Bash or Linux-specific command-line nuances, and the CLI example does not clarify its cross-platform nature.
Recommendations
  • Clearly indicate which tools are cross-platform (e.g., Azure CLI) and which are Windows-specific (e.g., Azure PowerShell).
  • Provide explicit Bash/Linux shell examples where appropriate, especially for scripting scenarios.
  • If PowerShell is shown, also show equivalent Bash or shell commands for Linux users.
  • Add notes or callouts for any platform-specific limitations or differences.
  • Ensure that CLI examples are tested and shown in a way that is copy-paste friendly for both Windows and Linux shells (e.g., avoid backslashes for line continuation unless appropriate).
GitHub Create Pull Request
Azure Change Tracking Inventory Azure Change Tracking and Inventory Support Matrix ...-inventory/change-tracking-inventory-support-matrix.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by frequently listing Windows examples, tools, and concepts before their Linux equivalents. Windows-specific terminology (e.g., registry, services, file paths) is prevalent, and examples such as alert queries and configuration instructions often prioritize Windows scenarios. Powershell is used for both Windows and Linux extension installation, which may not be optimal for Linux users. Some configuration options (like data collection frequency) are only available for Windows resources, and alerting examples focus on Windows paths and registry keys, with fewer Linux-centric scenarios.
Recommendations
  • Ensure Linux examples and terminology are presented alongside or before Windows equivalents, especially in tables and code samples.
  • Provide Linux-native command examples (e.g., bash, shell scripts) for extension installation and configuration, rather than using Powershell for Linux.
  • Expand alerting and query examples to include common Linux scenarios, such as tracking changes to /etc/passwd, /etc/ssh/sshd_config, or systemd service states.
  • Clarify any feature parity gaps (such as configurable data collection frequency) and provide roadmaps or workarounds for Linux users.
  • Balance the documentation by alternating the order of Windows and Linux references in lists, tables, and examples.
  • Add explicit guidance for Linux-specific troubleshooting, limitations, and best practices.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using an ARM template ...cles/azure-compute-fleet/quickstart-create-rest-api.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: feature registration is shown only with PowerShell and Azure portal, with no Azure CLI or Linux shell example; the ARM template exclusively provisions Windows VMs (WindowsServer image, osType: Windows) with no mention of Linux alternatives; and Windows-centric tools (PowerShell) are referenced before cross-platform options. There are no Linux or Bash examples for registration, deployment, or VM configuration.
Recommendations
  • Add Azure CLI and Bash examples for resource provider registration alongside PowerShell.
  • Include ARM template snippets or guidance for deploying Linux-based fleets (e.g., Ubuntu, CentOS images, osType: Linux).
  • Ensure that cross-platform tools (Azure CLI) are presented before or alongside Windows-specific tools.
  • Provide explicit instructions or links for Linux users on how to perform prerequisite steps and clean-up operations.
  • Clarify that the ARM template can be adapted for Linux VMs and show how to do so.
GitHub Create Pull Request
Azure Functions Guide for running C# Azure Functions in an isolated worker process ...icles/azure-functions/dotnet-isolated-process-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Visual Studio, PowerShell) are mentioned before or more prominently than their Linux equivalents. Many CLI examples and configuration instructions default to Windows terminology and commands, with Linux alternatives often relegated to tabs or secondary notes. Some deployment and debugging instructions are Windows-centric, and PowerShell is listed as a primary automation option. Linux-specific guidance is present but less visible, and Linux examples are sometimes missing or less detailed.
Recommendations
  • Ensure all CLI and configuration examples are provided for both Windows and Linux, with equal prominence.
  • Present Linux tools (e.g., bash, Azure CLI) alongside or before Windows tools (e.g., PowerShell), not as secondary options.
  • Add explicit Linux shell examples for all Azure CLI and deployment commands, including file paths and environment variable conventions.
  • Include Linux-specific troubleshooting and debugging guidance where Windows instructions are given.
  • Avoid listing Windows tools (Visual Studio, PowerShell) first in getting started and deployment sections; alternate or parallelize the order.
  • Where tabs are used for code/configuration, ensure Linux is always an option and not omitted.
  • Review all references to Windows-only features and clarify Linux alternatives or limitations.
GitHub Create Pull Request
Automanage Repair a broken Azure Automanage Account .../main/articles/automanage/repair-automanage-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by mentioning PowerShell as a primary method for ARM deployments alongside Azure CLI, listing PowerShell before Linux-friendly alternatives, and referencing Windows-centric tooling (PowerShell modules) without providing equivalent Linux shell examples. While Azure CLI is cross-platform, the explicit inclusion and prioritization of PowerShell and lack of Linux shell (bash) or scripting examples indicate a preference for Windows workflows.
Recommendations
  • Add explicit bash shell examples for ARM deployments, showing how to use Azure CLI in a Linux environment.
  • When listing command-line options, alternate or randomize the order of PowerShell and CLI, or group them as 'cross-platform' and 'Windows-specific'.
  • Include notes clarifying that Azure CLI commands work on Linux, macOS, and Windows, and provide sample bash scripts for common tasks.
  • If PowerShell is mentioned, also mention bash or other Linux-native shells for parity.
  • Avoid referencing Windows-specific modules (e.g., New-AzDeployment) without Linux equivalents or alternatives.
GitHub Create Pull Request
Automation Authenticate Azure Automation runbooks with Amazon Web Services ...n/articles/automation/automation-config-aws-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing AWS credential management via the AWS PowerShell user guide and omitting Linux-specific instructions or examples. There are no mentions of Linux tools or CLI workflows, and the only external credential reference is to PowerShell. The documentation assumes Azure portal usage and does not provide parity for Linux users or alternative command-line methods.
Recommendations
  • Include instructions and examples for authenticating AWS from Linux environments, such as using the AWS CLI.
  • Reference AWS CLI documentation alongside PowerShell guides for credential management.
  • Provide examples of creating and storing credentials using Linux shell commands or scripts.
  • Clarify that the process is platform-agnostic where possible, or explicitly note differences for Windows and Linux users.
  • Add links to relevant Linux documentation and tools (e.g., AWS CLI credential configuration).
GitHub Create Pull Request
Automation Manage connections in Azure Automation ...lob/main/articles/automation/automation-connections.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a strong bias toward Windows and PowerShell environments. All command-line examples for creating and managing connections use PowerShell cmdlets, with no equivalent CLI or Bash/Linux shell examples. The documentation refers to 'Windows PowerShell' explicitly and does not mention cross-platform alternatives like Azure CLI or REST API for Linux/macOS users. The internal cmdlets and graphical runbook sections also assume a Windows-centric workflow. While Python examples are provided, they are specific to Azure Automation runbooks and do not address general Linux shell usage.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlet operations (e.g., creating, retrieving, and deleting connections).
  • Include Bash/Linux shell examples where applicable, especially for connection management tasks.
  • When introducing tools or workflows, mention cross-platform options (e.g., Azure CLI, REST API) alongside or before Windows/PowerShell tools.
  • Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' and clarify when examples are cross-platform.
  • Provide explicit guidance for Linux/macOS users on how to perform the same tasks, including any platform-specific prerequisites or differences.
  • Ensure that all code tabs or sections (PowerShell, CLI, Python) are equally represented and easy to find.
GitHub Create Pull Request
Automation Create a standalone Azure Automation account ...les/automation/automation-create-standalone-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by primarily featuring PowerShell examples and references, mentioning Azure PowerShell as the only CLI for key rotation, and listing PowerShell runbooks and cmdlet references before alternatives. There are no examples using Azure CLI, Bash, or Linux-native tools, and Linux-centric workflows are not discussed. The documentation assumes familiarity with Windows tooling and patterns, and does not provide parity for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell cmdlet examples, especially for key rotation and account management.
  • Include Bash shell examples and instructions for Linux/macOS users where applicable.
  • Present cross-platform options side-by-side, or alternate the order so Linux tools are not always listed after Windows/PowerShell.
  • Reference both PowerShell and Python runbooks equally in tutorials and next steps, and add Bash or other language runbook examples if supported.
  • Explicitly mention platform neutrality of the Azure portal and clarify that all steps can be performed from any OS.
  • Provide links to Linux-specific documentation or troubleshooting guides for Azure Automation.
GitHub Create Pull Request
Azure Functions App settings reference for Azure Functions ...ain/articles/azure-functions/functions-app-settings.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Several settings and examples are Windows-specific or prioritize Windows terminology and tools. Windows-only settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are called out, and some examples use Windows path syntax (e.g., %HOME%\typescript). PowerShell-specific configuration is documented in detail, while equivalent Linux shell or cross-platform alternatives are not. In some cases, Windows behaviors are explained before Linux equivalents, and PowerShell is mentioned as a primary automation tool, with Azure CLI listed second. Linux-specific settings (e.g., linuxFxVersion) are present but not always given parity in examples or explanations. Some settings (e.g., WEBSITE_TIME_ZONE) do provide both Windows and Linux examples, but this is not consistent throughout.
Recommendations
  • Ensure all examples and settings provide both Windows and Linux equivalents, especially for environment variables, file paths, and tooling.
  • Where PowerShell is mentioned for automation, also provide Bash/Azure CLI examples and reference cross-platform scripting.
  • For settings that are OS-specific, clearly label them and provide guidance for both Windows and Linux users.
  • Review sample values for path-related settings to use Linux syntax (e.g., /home/typescript) alongside Windows syntax.
  • Expand documentation for Linux-specific tools and patterns, such as bash scripting, Linux file system paths, and Linux container deployment.
  • Where deprecated or legacy Windows settings are discussed, ensure Linux alternatives are equally highlighted.
GitHub Create Pull Request
Automation Create modular runbooks in Azure Automation .../main/articles/automation/automation-child-runbooks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All examples use PowerShell syntax and cmdlets (e.g., Start-AzAutomationRunbook, Disable-AzContextAutosave), with no mention of Linux shell scripting, Python runbooks, or cross-platform alternatives. Windows/PowerShell terminology and modules are introduced first and exclusively, and there is no guidance for users working in Linux environments or with non-PowerShell runbook types.
Recommendations
  • Add equivalent examples using Python runbooks, which are supported in Azure Automation and commonly used on Linux.
  • Include notes or sections on how to create and call modular runbooks using Bash or other Linux shell scripts, if supported.
  • Mention cross-platform considerations, such as authentication and context management, for Linux and non-Windows environments.
  • Clarify which features and cmdlets are Windows/PowerShell-specific and provide Linux alternatives or limitations where applicable.
  • Reorder or balance the presentation so that Windows/PowerShell and Linux/Python approaches are given equal prominence.
GitHub Create Pull Request
Automation Use an alert to trigger an Azure Automation runbook ...utomation/automation-create-alert-triggered-runbook.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All code samples and runbook examples use PowerShell exclusively, with no mention or examples of Python or other cross-platform scripting languages supported by Azure Automation. Prerequisites and links reference Windows-centric resources (e.g., creating Windows VMs, installing PowerShell modules), and the runbook creation workflow defaults to PowerShell. There are no Linux-specific instructions, nor are Bash or Python alternatives provided. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux users or their workflows.
Recommendations
  • Provide equivalent examples using Python runbooks, which are supported in Azure Automation and widely used on Linux.
  • Include instructions and links for creating and managing Linux VMs, not just Windows VMs.
  • Add guidance for installing and using Az CLI (cross-platform) in addition to PowerShell, especially for assigning permissions and managing resources.
  • Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.), and show how to select and use them.
  • Offer Bash/CLI examples for steps that currently only show PowerShell, such as role assignment and VM management.
  • Clarify any platform-specific limitations or considerations (e.g., differences in managed identity usage between Windows and Linux VMs).
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell. All migration scripts and runbook examples are provided exclusively in PowerShell and PowerShell Workflow, with no mention of Bash, Python, or other Linux-native scripting options. The instructions and tabs for Hybrid Runbook Worker installation and migration reference Windows first and do not provide Linux-specific steps or examples. There is no guidance for Linux users on how to perform equivalent disaster recovery tasks using Linux tools or scripting languages.
Recommendations
  • Provide equivalent migration scripts and runbook examples using Bash, Python, or other Linux-native tools.
  • Add Linux-specific tabs and instructions for Hybrid Runbook Worker installation, deletion, and migration.
  • Ensure that both Windows and Linux procedures are presented in parallel, with equal prominence and detail.
  • Include references to Linux command-line tools and automation patterns where appropriate.
  • Clarify any platform-specific limitations or requirements for disaster recovery steps.
GitHub Create Pull Request
Automation Set up Azure Automation continuous deployment with Chocolatey ...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page is heavily biased towards Windows environments. All examples, tooling, and step-by-step instructions focus exclusively on Windows, PowerShell, and Windows-specific package managers (Chocolatey). Linux is only mentioned in passing, with no practical examples, instructions, or equivalent tooling provided. The use of PowerShell DSC and Windows Management Framework further reinforces the Windows-centric approach, and there are no references to Linux configuration management tools or package managers beyond a brief mention of apt-get.
Recommendations
  • Provide equivalent Linux examples using native tools (e.g., Azure Automation DSC for Linux, or alternatives such as Ansible, Chef, or Puppet).
  • Include step-by-step instructions for setting up continuous deployment on Linux VMs, using Linux package managers (apt, yum, etc.) and configuration management.
  • Offer sample configuration scripts for Linux (e.g., Bash, Python, or cross-platform PowerShell Core) in addition to Windows PowerShell.
  • Mention and link to Linux-compatible VM extensions and Azure Automation modules.
  • Clarify in the introduction whether the guide is Windows-only, or update it to be cross-platform where possible.
  • Add a section comparing Windows and Linux approaches, highlighting any differences and providing guidance for both.
GitHub Create Pull Request
Automation Configure data at scale for Azure Automation State Configuration ...cles/automation/automation-dsc-config-data-at-scale.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily focused on Windows and PowerShell, with all examples and instructions referencing Windows PowerShell DSC and related cmdlets. There is no mention of Linux equivalents, nor are there examples or guidance for configuring data at scale for Linux environments. The prerequisites and next steps are all Windows/PowerShell-centric, and Linux is only referenced in a link, not in the main content or examples.
Recommendations
  • Add explicit examples and instructions for configuring data at scale using Linux DSC agents, including relevant commands and file formats.
  • Mention and describe Linux-compatible tools (such as Open Management Infrastructure (OMI) and cross-platform DSC) where appropriate.
  • Provide parity in documentation structure, ensuring that Linux onboarding, configuration, and management steps are presented alongside Windows steps.
  • Update prerequisites and applicability to include Linux platforms where supported.
  • Include links to Linux-specific documentation and community resources.
GitHub Create Pull Request
Automation Configure data based on STIG for Azure Automation State Configuration ...tomation/automation-dsc-configuration-based-on-stig.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily focused on Windows and PowerShell, referencing Windows PowerShell 5.1 explicitly and providing examples and tooling (PowerSTIG, DSC) that are primarily Windows-centric. There is no mention of Linux equivalents or examples, and the guidance assumes familiarity with Windows tools and patterns. Although there is a brief mention of onboarding Linux machines, no Linux-specific configuration or tooling is discussed.
Recommendations
  • Include examples and instructions for configuring Linux servers using Azure Automation State Configuration.
  • Reference cross-platform DSC implementations (such as PowerShell Core or native Linux DSC support) where applicable.
  • Provide parity in documentation by listing Linux tools, patterns, and community projects that address STIG compliance.
  • Clarify which features and tools are Windows-only and which are available on Linux, and provide links to Linux-specific resources.
GitHub Create Pull Request
Automation Integrate Azure Automation State Configuration with Azure Monitor Logs ...main/articles/automation/automation-dsc-diagnostics.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All code examples and setup instructions use PowerShell and Az PowerShell modules, which are native to Windows environments. There are no Bash, CLI, or Linux-native instructions or examples. The prerequisites and troubleshooting steps reference PowerShell modules and tools exclusively, and the only example of continuous deployment uses Chocolatey, a Windows package manager. There is no mention of Linux equivalents or cross-platform alternatives, and Linux support is only referenced in the context of retirement announcements.
Recommendations
  • Provide equivalent instructions and code examples using Azure CLI and Bash, which are cross-platform and commonly used on Linux.
  • Include steps for installing and configuring required modules on Linux systems, or clarify platform limitations.
  • Reference Linux-compatible tools (e.g., Ansible, shell scripts) where appropriate, or explain how Linux users can achieve similar outcomes.
  • Add explicit notes about platform support and limitations, especially in light of Linux retirement announcements, and offer migration guidance for Linux users.
  • Ensure that examples and tooling references are presented in a platform-neutral way, or offer parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
Automation Get started with Azure Automation State Configuration .../articles/automation/automation-dsc-getting-started.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature), with no Linux equivalents or cross-platform examples. The prerequisites and instructions focus on creating Windows VMs, and references are primarily to Windows PowerShell DSC documentation. Linux support is only mentioned in passing, and there are no Linux-specific configuration samples, resources, or onboarding steps. The documentation also references Windows-specific tools and patterns before any mention of Linux, and does not provide parity in guidance for Linux users.
Recommendations
  • Add Linux DSC configuration examples, such as using nxFile or nxPackage resources, alongside Windows examples.
  • Include instructions for onboarding Linux VMs to Azure Automation State Configuration, with screenshots and step-by-step guidance.
  • Reference Linux DSC documentation and resources in the prerequisites and next steps sections.
  • Clarify the current support status for Linux (given the retirement announcement), and provide migration or alternative guidance for Linux users.
  • Ensure that cross-platform tools and patterns are presented equally, and avoid presenting Windows-specific tools or examples first.
  • Where PowerShell is referenced, note cross-platform alternatives (e.g., PowerShell Core, or native Linux configuration tools if applicable).
GitHub Create Pull Request
Azure Functions host.json reference for Azure Functions 2.x ...b/main/articles/azure-functions/functions-host-json.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for Azure Functions host.json is generally cross-platform, but there are several instances of Windows bias. The managedDependency feature is described as PowerShell-only, with references to Windows-centric dependency management. The snapshotConfiguration section refers to environment variables like LOCALAPPDATA, APPDATA, and TEMP, which are Windows-specific, and the default temp folder path uses the Windows-style %TEMP% variable. Additionally, references to Kudu performance counters and the use of Windows-style environment variable conventions appear before any Linux equivalents. While Linux is mentioned (e.g., console log color suppression), examples and explanations tend to default to Windows tools and patterns.
Recommendations
  • Provide equivalent Linux/macOS environment variable references and default paths (e.g., $HOME/tmp, /tmp) alongside Windows examples in snapshotConfiguration and tempFolder settings.
  • Clarify managedDependency support for non-PowerShell languages and platforms, or explicitly state Linux/Unix alternatives if available.
  • Mention Kudu alternatives or clarify its availability on Linux-based hosting plans.
  • Ensure examples and explanations use cross-platform conventions (e.g., both %TEMP% and $TMPDIR), and avoid Windows-first ordering.
  • Add more explicit Linux/macOS usage notes, especially for file paths, environment variables, and dependency management.
GitHub Create Pull Request
Automation Create configurations from existing servers for Azure Automation State Configuration ...ticles/automation/automation-dsc-config-from-server.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and references centered around Windows PowerShell DSC and related tools. There is no mention of Linux equivalents, and Linux onboarding is only referenced as a link, not described or exemplified. The documentation assumes familiarity with Windows tooling and does not provide guidance for Linux users.
Recommendations
  • Include explicit examples for Linux systems, such as how to extract configurations from Linux servers using cross-platform DSC tools.
  • Mention and describe Linux-compatible DSC resources and modules, if available.
  • Provide step-by-step instructions for onboarding Linux servers, not just a link.
  • Clarify which features or tools are Windows-only and suggest alternatives for Linux where possible.
  • Add references to community or Microsoft-supported DSC solutions for Linux, such as those using PowerShell Core or native Linux configuration management tools.
GitHub Create Pull Request
Automation Work with Azure Desired State Configuration extension version history ...rticles/automation/automation-dsc-extension-history.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page is heavily focused on Windows environments, with all version history, OS support, and examples referencing only Windows Server and Windows Client editions. PowerShell and Windows Management Framework are mentioned exclusively as the tooling for DSC, with no mention of Linux equivalents or support. There are no examples, instructions, or references for Linux DSC extension usage, and the only nod to Linux is an end-of-life announcement, further reinforcing the Windows-centric bias.
Recommendations
  • Add historical context and details about Linux support, including which extension versions supported Linux and when support was retired.
  • Include explicit Linux OS support information (where applicable) in version tables, or clearly state when Linux support was removed.
  • Provide examples or references for Linux DSC extension usage, including configuration and troubleshooting steps for Linux VMs (if still relevant for older versions).
  • Mention Linux equivalents to PowerShell DSC, such as OMI or cross-platform DSC implementations, and link to their documentation.
  • Balance references to Windows Management Framework and PowerShell with information about Linux management tools or frameworks, where applicable.
  • If Linux support is fully retired, add a prominent section summarizing the history and rationale, and direct users to alternative solutions for Linux configuration management.
GitHub Create Pull Request
Automation Enable Azure Automation State Configuration .../main/articles/automation/automation-dsc-onboarding.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a strong Windows and PowerShell bias. Most examples and workflows are described using PowerShell cmdlets and Windows tooling, with Linux instructions often appearing after Windows ones or being less detailed. Key onboarding and configuration steps are presented primarily with PowerShell scripts, and Linux-specific workflows are less prominent, sometimes requiring the use of Windows tools to manage Linux nodes. There are also sections where Linux examples are missing or less comprehensive compared to their Windows counterparts.
Recommendations
  • Provide Linux-first or Linux-parity examples for all major workflows, including onboarding, configuration, and troubleshooting.
  • Include native Linux shell (bash) or Python examples for generating and applying metaconfigurations, rather than requiring PowerShell or Windows-based tools for Linux nodes.
  • Ensure that Linux tools and scripts (e.g., Register.py, SetDscLocalConfigurationManager.py) are documented with the same level of detail and step-by-step guidance as PowerShell cmdlets.
  • Clearly separate Windows and Linux instructions, and avoid requiring a Windows machine or PowerShell to manage Linux nodes.
  • Add troubleshooting and status-checking sections specifically for Linux, not just referencing the Windows DSC extension.
  • Where possible, mention Linux tools and workflows before or alongside Windows ones, rather than always after.
GitHub Create Pull Request
Automation Azure Automation State Configuration overview ...ob/main/articles/automation/automation-dsc-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing heavily on PowerShell DSC, providing more detailed information and examples for Windows (including specific OS versions, tools like WinRM, and proxy configuration via metaconfiguration scripts), and mentioning Windows requirements and features before Linux equivalents. Linux support is referenced but lacks detail, examples, and parity in tooling explanations. The documentation also references Windows-centric tools (e.g., WinRM, WMF 5.1) and does not provide Linux-specific configuration examples or troubleshooting guidance.
Recommendations
  • Provide Linux-specific examples for onboarding, configuration, and troubleshooting, similar to the detail given for Windows.
  • Include explicit lists of supported Linux distributions and versions, not just a link to external documentation.
  • Add Linux equivalents for Windows tools (e.g., explain how DSC for Linux is installed/configured, alternatives to WinRM, and proxy configuration with environment variables).
  • Ensure that Linux instructions and examples are presented alongside Windows, not only as afterthoughts or external links.
  • Add Linux-focused continuous deployment pipeline examples (e.g., using apt/yum instead of Chocolatey).
  • Expand the PowerShell cmdlet reference to include cross-platform usage or note Linux-specific considerations.
GitHub Create Pull Request
Azure Functions Use Python and TensorFlow for machine learning in Azure ...ure-functions/functions-machine-learning-tensorflow.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides command examples for Bash (Linux/macOS), PowerShell, and Cmd, but frequently lists Windows-specific tools and patterns first or equally, such as using 'py' instead of 'python', referencing Windows registry edits for long paths, and providing PowerShell/Cmd examples alongside Bash. The troubleshooting section focuses on Windows-specific errors and solutions, with less detail for Linux/macOS issues. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. The Azure Functions Core Tools and Python virtual environment instructions are generally cross-platform, but Windows-specific commands and troubleshooting are given prominence.
Recommendations
  • Ensure Linux/macOS examples are presented first or equally, not after Windows/PowerShell/Cmd examples.
  • Expand troubleshooting sections to include common Linux/macOS errors and solutions, not just Windows-specific issues like long path registry edits.
  • When referencing commands, clarify platform-specific differences and avoid assuming Windows tools (e.g., 'py' command) are available on all platforms.
  • Include alternative editors or tools that are popular on Linux/macOS, or clarify cross-platform compatibility.
  • Explicitly mention any platform-specific limitations or requirements for Azure Functions Core Tools and Python environments.
  • Where possible, provide parity in depth and detail for both Windows and Linux/macOS instructions and troubleshooting.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-based deployment methods (such as Visual Studio and FTPS) are mentioned first and more frequently, with Linux-specific methods often described as exceptions or limitations. Several deployment technologies are marked as 'Windows-only' or default to Windows, while Linux equivalents are less emphasized or require additional configuration. Examples and tool references (Visual Studio, FTPS, Local Git) are predominantly Windows-centric, and Linux deployment scenarios are often described in terms of their constraints or as alternatives rather than primary options.
Recommendations
  • Provide Linux-specific deployment examples and workflows alongside Windows ones, ensuring parity in detail and clarity.
  • When listing deployment methods, avoid listing Windows tools (Visual Studio, FTPS, Local Git) first; instead, present cross-platform tools (Azure CLI, Core Tools) before platform-specific ones.
  • Explicitly mention Linux equivalents for all deployment technologies, including any required configuration steps, and provide sample commands or scripts for Linux environments.
  • Clarify which deployment methods are cross-platform and which are platform-specific, and ensure that Linux options are not described only in terms of limitations.
  • Include references to Linux-native tools and environments (e.g., Bash, Linux file system paths) in examples and instructions.
  • Balance the use of screenshots and walkthroughs between Windows and Linux environments, or use generic/neutral representations where possible.
GitHub Create Pull Request
Azure Functions Create a function in Azure from the command line ...es/azure-functions/how-to-create-function-azure-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. In several places, Windows-specific tools and patterns (such as PowerShell and Cmd) are presented alongside Bash, but Windows shells are listed first. The Java section provides examples for Bash, PowerShell, and Cmd, but Bash is not consistently prioritized. There is mention of setting JAVA_HOME, which is relevant for both platforms, but the example paths and instructions are not platform-neutral. The documentation refers to 'terminal or command prompt' generically, but does not provide explicit Linux-specific instructions or troubleshooting. There are no explicit examples of Linux-specific tools (e.g., shell scripts, environment variable export patterns), and the use of 'console' as a code block type is ambiguous. The inclusion of jq and Azure CLI is platform-neutral, but the overall pattern leans toward Windows-first presentation.
Recommendations
  • Ensure Bash (Linux/macOS) examples are listed before or alongside Windows (PowerShell/Cmd) examples, especially in multi-tab sections.
  • Explicitly mention Linux/macOS terminals and provide troubleshooting or setup notes for those platforms.
  • When referencing environment variables (e.g., JAVA_HOME), provide both Windows (set) and Linux/macOS (export) syntax.
  • Use platform-neutral terminology (e.g., 'terminal' instead of 'command prompt') and clarify any platform-specific steps.
  • Add explicit Linux/macOS shell script examples where appropriate, and clarify any differences in file paths or permissions.
  • Review included snippets (INCLUDE blocks) to ensure they do not assume Windows tooling or patterns.
GitHub Create Pull Request
Azure Functions Migrate apps from Azure Functions version 1.x to 4.x ...rticles/azure-functions/migrate-version-1-version-4.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily through its use of PowerShell scripts for key migration steps, such as identifying function apps to migrate. These examples are presented without equivalent Bash, Azure CLI, or Linux-native alternatives. The documentation references Windows-centric tools (PowerShell, Visual Studio) and patterns (Cloud Shell with PowerShell), and does not provide Linux-first or cross-platform instructions for these steps. This may hinder Linux users or those who prefer Bash/Azure CLI workflows.
Recommendations
  • Provide equivalent Bash and Azure CLI examples for identifying function apps to migrate, alongside PowerShell.
  • Explicitly mention cross-platform alternatives for all command-line instructions, including how to perform steps on Linux/macOS.
  • Include references to Linux-native tools and workflows (e.g., VS Code, Azure CLI) where Visual Studio or PowerShell are mentioned.
  • Ensure that all code snippets and instructions are platform-agnostic or have clear alternatives for non-Windows environments.
  • Add a section or callout clarifying platform compatibility for all tools and scripts, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Azure Functions Azure Functions language stack support policy ...in/articles/azure-functions/language-support-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias. It lists Azure PowerShell as a primary method for checking runtime versions alongside Azure CLI and portal, and includes a dedicated resource section for PowerShell as a supported language. There is no explicit mention of Linux-specific tools (e.g., Bash, shell scripts), and the ordering of runtime inspection methods puts PowerShell on equal footing with CLI and portal, which may be interpreted as Windows-centric. No Linux-specific examples or tools are provided.
Recommendations
  • Add explicit examples and instructions for Linux users, such as using Bash or shell scripting to interact with Azure Functions.
  • Clarify cross-platform parity by mentioning that Azure CLI is available on both Windows and Linux, and provide Linux-specific usage notes where relevant.
  • Include references to Linux-native tools or environments (e.g., bash, zsh, or other shells) in sections discussing runtime inspection and configuration.
  • Ensure that PowerShell is not presented as the default or primary method unless justified by user base data; otherwise, present CLI and portal first, with PowerShell as an alternative.
  • Consider adding a section or FAQ entry addressing cross-platform support and best practices for both Windows and Linux users.
GitHub Create Pull Request
Azure Functions Build a custom remote MCP server using Azure Functions ...s/azure-functions/scenario-custom-remote-mcp-server.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates mild Windows bias, primarily in the deployment and configuration steps. Windows-specific tools and patterns (such as PowerShell scripts and references to Windows command line) are presented alongside, but often before, Linux/macOS equivalents. The documentation also references PowerShell and Windows-specific installation instructions in the prerequisites, and the Windows tab for deployment scripts uses PowerShell, which may be less familiar to Linux users. However, Linux/macOS instructions are present and reasonably complete, and most examples are cross-platform.
Recommendations
  • Ensure Linux/macOS instructions are always presented first or equally alongside Windows instructions, rather than after.
  • Where possible, use shell-agnostic commands (e.g., bash scripts) as the primary example, with PowerShell as an alternative.
  • Avoid referencing Windows-specific installation instructions or tools unless absolutely necessary; provide parity for Linux (e.g., installation steps for PowerShell on Linux if referenced).
  • Explicitly state cross-platform compatibility for all tools and commands, and clarify any platform-specific differences.
  • Consider including troubleshooting notes for common Linux/macOS issues (e.g., environment variable handling, shell differences).
GitHub Create Pull Request
Automation Edit textual runbooks in Azure Automation ...articles/automation/automation-edit-textual-runbook.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily focused on PowerShell and Windows workflows. All code examples use Windows PowerShell, with explicit references to Windows file paths (e.g., c:\runbooks). There are no examples or guidance for using Linux or cross-platform tools, such as PowerShell Core on Linux/macOS, nor are there instructions for using Bash, Azure CLI, or other non-Windows environments. Windows terminology and tools are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Add examples for editing and managing runbooks using PowerShell Core on Linux/macOS, including appropriate file paths and environment notes.
  • Include instructions and sample commands for using Azure CLI to export/import runbooks, if supported.
  • Clarify that PowerShell is cross-platform and provide guidance for non-Windows users, including any prerequisites or differences.
  • Avoid using Windows-specific file paths in examples; use generic or platform-agnostic paths, or provide both Windows and Linux/macOS variants.
  • Explicitly mention support and limitations for Linux/macOS environments in Azure Automation documentation.
GitHub Create Pull Request
Automation Author graphical runbooks in Azure Automation ...les/automation/automation-graphical-authoring-intro.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page is heavily focused on Windows PowerShell and PowerShell Workflow, with all examples, terminology, and tooling referencing Windows-centric technologies. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The graphical runbook authoring is described exclusively in terms of PowerShell cmdlets and expressions, and references to Windows tools (e.g., System Center Orchestrator, Service Management Automation) are present. No Linux or cross-platform examples, patterns, or considerations are provided.
Recommendations
  • Explicitly state the platform compatibility of graphical runbooks (e.g., clarify if only Windows-based Automation workers are supported, or if Linux workers are available).
  • Add examples or guidance for Linux users, such as how to author runbooks using Bash or Python if supported, or clarify limitations.
  • Reference cross-platform scripting options (e.g., PowerShell Core, Bash, Python) and provide parity in examples where possible.
  • Mention Linux equivalents to Windows tools (e.g., alternatives to System Center Orchestrator) or clarify if none exist.
  • Provide a section on considerations for Linux-based automation accounts, including supported modules, authentication, and limitations.
  • Update terminology to be more inclusive (e.g., 'PowerShell' instead of 'Windows PowerShell' where PowerShell Core is supported).
GitHub Create Pull Request
Automation Azure Automation Hybrid Runbook Worker Overview ...rticles/automation/automation-hybrid-runbook-worker.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as a primary onboarding and management channel, with no equivalent Linux shell examples (e.g., Bash). Windows terminology and tools (such as 'System account', 'PowerShell Workflow', and 'Run As account') are referenced more frequently and in greater detail than their Linux counterparts. Linux is mentioned, but examples, operational details, and troubleshooting guidance are not provided at parity with Windows. The documentation also lists Windows before Linux in several places and does not provide Linux-specific usage patterns or authentication guidance.
Recommendations
  • Add Linux-specific examples for onboarding, management, and troubleshooting, including Bash/CLI commands.
  • Provide parity in operational details for Linux, such as describing the 'nxautomation' account and its permissions, and how to configure authentication for Linux Hybrid Runbook Workers.
  • Include Linux shell (Bash) equivalents for PowerShell cmdlets and workflows.
  • Ensure that references to operating systems are balanced, listing Windows and Linux together or alternating order.
  • Expand documentation on Linux-specific troubleshooting and best practices for Hybrid Runbook Worker deployment and management.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows and PowerShell tools/cmdlets are mentioned and linked more frequently and earlier than Linux equivalents. Backup and export instructions rely on Windows PowerShell cmdlets, with no Linux CLI or scripting alternatives provided. In the data retention section, only Windows PowerShell cmdlets are referenced for resource management. The TLS upgrade section gives a Windows registry link before the Linux OpenSSL guidance, and Linux instructions are less detailed and less integrated. There is a lack of parity in examples and tooling for Linux users.
Recommendations
  • Provide equivalent Linux CLI (e.g., Azure CLI, Bash) examples and commands alongside PowerShell instructions for all resource management and backup operations.
  • Include links to Linux-specific documentation and tools (such as az CLI commands) wherever Windows/PowerShell cmdlets are referenced.
  • Ensure Linux guidance is presented with equal prominence and detail as Windows guidance, including step-by-step instructions for common tasks.
  • Add explicit Linux examples for exporting runbooks, DSC configurations, and other assets, using cross-platform tools or scripts.
  • Review tables and lists to ensure Linux is not treated as an afterthought or secondary platform.
GitHub Create Pull Request
Automation Azure Automation network configuration details ...rticles/automation/automation-network-configuration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific DSC resources (such as WaitFor resources with a Windows path), linking only to Windows PowerShell documentation, and omitting explicit Linux equivalents or examples. There are no mentions of Linux DSC resources, nor are there examples or guidance tailored for Linux environments, despite Azure Automation supporting both Windows and Linux nodes.
Recommendations
  • Include references and links to Linux DSC resources and documentation, such as those for Linux-based Desired State Configuration.
  • Provide examples or notes on network configuration for Linux nodes, including any differences in resource usage or communication patterns.
  • Ensure parity in documentation by listing both Windows and Linux resource paths and examples when discussing DSC resources.
  • Add clarification on whether the listed network requirements apply identically to Linux nodes, or highlight any platform-specific considerations.
GitHub Create Pull Request
Automation Migrate from Orchestrator to Azure Automation (Beta) ...ticles/automation/automation-orchestrator-migration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows-centric technologies, specifically PowerShell and Windows file paths. All examples and tooling references are for Windows environments, with no mention of Linux or cross-platform alternatives. The migration process assumes familiarity with Windows tools and patterns, and does not provide guidance or parity for Linux users.
Recommendations
  • Provide equivalent examples using Azure Automation Python runbooks or Bash scripts where possible.
  • Clarify whether the migration toolkit and Runbook Converter can be used on Linux/macOS, or provide alternatives for non-Windows platforms.
  • Include instructions for Linux users on how to prepare and import runbooks, including file path conventions and environment setup.
  • Mention Azure Automation's support for non-Windows runbook types and how Linux users can leverage these.
  • Add notes or sections explicitly addressing cross-platform considerations and limitations.
GitHub Create Pull Request
Automation Manage role permissions and security in Azure Automation ...les/automation/automation-role-based-access-control.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell usage. All command-line examples for configuring Azure RBAC and managing role assignments use Azure PowerShell cmdlets, with no mention of Azure CLI or Bash alternatives. The only script-based instructions are PowerShell, and references to 'tabs=windows' in linked content further reinforce the Windows-first approach. There are no Linux-specific instructions, nor are cross-platform tools (such as Azure CLI) presented as alternatives or in parity with PowerShell. This may hinder Linux users or those who prefer Bash/CLI workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, including role assignment, removal, and listing.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI, and provide Bash examples.
  • Where scripts are provided, offer both PowerShell and Bash/CLI versions, and clarify platform compatibility.
  • Review linked content (such as extension-based Hybrid Runbook Worker install) to ensure Linux instructions are present and not relegated to secondary tabs.
  • In introductory sections, list Azure CLI and REST API options before or alongside PowerShell, to avoid Windows-first impression.
  • Include notes or sections for Linux administrators, highlighting any platform-specific considerations or best practices.
GitHub Create Pull Request
Automation Azure Automation Runbook Types ...b/main/articles/automation/automation-runbook-types.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exhibits a Windows bias by prioritizing PowerShell (a Windows-centric technology) throughout, referencing Windows-specific tools, file paths, and patterns (e.g., C:\modules, .ps1 scripts) without Linux equivalents. Examples and troubleshooting steps almost exclusively use PowerShell and Windows paths, with little to no demonstration of Linux-specific scenarios, especially for PowerShell and graphical runbooks. Python runbooks mention Linux only briefly and do not provide Linux-specific examples or troubleshooting. The documentation often discusses Windows support and limitations before Linux, and Linux support is sometimes described as an exception or afterthought.
Recommendations
  • Provide Linux-specific examples for PowerShell runbooks, including file paths, module management, and troubleshooting steps relevant to Linux Hybrid Runbook Workers.
  • Include explicit guidance and examples for authoring and running runbooks on Linux Hybrid Runbook Workers, especially for PowerShell and Python.
  • Balance the order of presentation so that Linux support and limitations are described alongside Windows, not after or as exceptions.
  • Add troubleshooting sections and sample scripts for common Linux issues (e.g., permissions, file system differences, environment variables) in runbooks.
  • Where Windows-specific tools or patterns are mentioned (e.g., C:\modules, .ps1), provide Linux equivalents (e.g., /opt/modules, .sh or .ps1 usage on Linux) or clarify cross-platform compatibility.
  • Clarify which features are available or limited on Linux Hybrid Runbook Workers for each runbook type, and provide parity where possible.
GitHub Create Pull Request
Automation Runbook authoring using VS Code in Azure Automation ...in/articles/automation/automation-runbook-authoring.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by listing Windows operating systems and PowerShell versions first, focusing heavily on PowerShell (especially Windows PowerShell 5.1), and providing directory path examples only in Windows format (e.g., C:\abc). There are no Linux/macOS-specific examples or instructions, and the use of Windows-centric terminology and tools is prevalent throughout the page.
Recommendations
  • Provide Linux/macOS path examples alongside Windows ones (e.g., /home/user/abc).
  • When listing supported operating systems, alternate or randomize the order, or explicitly state that all are equally supported.
  • Include Linux/macOS-specific instructions or notes where relevant, such as how to install required modules or set directory paths.
  • Balance PowerShell and Python coverage, and clarify any OS-specific limitations or differences.
  • Avoid using only Windows-centric terminology (like 'C:\abc'); use cross-platform language or dual examples.
GitHub Create Pull Request
Automation Use Azure Automation runbooks and modules in PowerShell Gallery ...main/articles/automation/automation-runbook-gallery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All examples and workflows center around PowerShell, PowerShell Gallery, and Windows-centric tools. There is minimal mention of Python runbooks, and no Linux-specific examples, tools, or workflows are provided. Windows terminology and patterns (e.g., PowerShell cmdlets, Windows Azure VM) are used exclusively or before any Linux alternatives. The only nod to Linux is in a suggested tag for contributed runbooks, but no practical guidance or examples are given for Linux users.
Recommendations
  • Add explicit Linux-focused examples, such as importing and running Python runbooks for Linux VMs.
  • Include guidance for managing runbooks and modules on Linux Azure VMs, including file copy scenarios and automation tasks.
  • Provide parity in tooling by referencing Bash, CLI, or other Linux-native tools alongside PowerShell.
  • Ensure that documentation sections do not assume PowerShell as the default and offer alternative workflows for Linux users.
  • Highlight any limitations or differences when using Azure Automation with Linux environments.
  • Add links to Linux-specific tutorials and documentation where relevant.
GitHub Create Pull Request
Automation Handle errors in Azure Automation graphical runbooks ...omation/automation-runbook-graphical-error-handling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing PowerShell, Windows cmdlets, and Windows-centric error handling patterns. All examples, terminology, and recommended practices are framed around PowerShell and Windows tools, with no mention of Linux, Bash, or cross-platform alternatives. There are no examples or guidance for users running graphical runbooks in Linux environments or using non-PowerShell scripting languages.
Recommendations
  • Include examples using Bash or Python activities for error handling in graphical runbooks, especially for Linux-based automation scenarios.
  • Reference Linux equivalents for cmdlets and error handling patterns, such as using shell exit codes, try/catch in Bash, or error handling in Python.
  • Explicitly state platform compatibility for graphical runbooks and clarify whether Linux Hybrid Workers are supported.
  • Provide parallel documentation sections or examples for Linux users, including how to handle errors in non-Windows environments.
  • Avoid using Windows-centric terminology (e.g., PowerShell errors, cmdlets) as the default; instead, present cross-platform approaches side-by-side.
GitHub Create Pull Request
Automation What's New in Azure Automation .../azure-docs/blob/main/articles/automation/whats-new.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page for Azure Automation updates demonstrates a Windows bias through its heavy focus on PowerShell runbooks, frequent mention of Windows-specific modules and tools (such as AzureRM and Az PowerShell modules), and prioritization of PowerShell and Windows-related features in announcements. While Linux is occasionally referenced (e.g., support for Linux Hybrid Runbook Workers), examples and tooling are almost always PowerShell-centric, and Windows terminology is used first or exclusively in several places. There is a lack of parity in showcasing Linux-specific automation scenarios, tools, or shell examples (e.g., Bash), and the documentation does not provide equivalent Linux-first or cross-platform examples.
Recommendations
  • Include Linux shell (Bash, sh) and cross-platform CLI examples alongside PowerShell in runbook and automation scenarios.
  • Highlight Linux-specific automation use cases and tools, such as native Bash scripts, Ansible, or Python runbooks for Linux environments.
  • Ensure announcements and feature descriptions mention Linux and Windows equivalently, avoiding Windows-first ordering or terminology.
  • Provide migration and troubleshooting guidance for both Windows and Linux users, not just PowerShell/AzureRM/Az module transitions.
  • Add explicit documentation sections or examples for Linux Hybrid Runbook Workers, including installation, configuration, and scripting.
  • Where Visual Studio Code extensions or other tooling are referenced, clarify cross-platform support and provide Linux usage instructions.
GitHub Create Pull Request
Automation Runbook execution in Azure Automation ...in/articles/automation/automation-runbook-execution.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exhibits a strong Windows and PowerShell bias. All code examples are in PowerShell, and references to runbook types and modules focus exclusively on PowerShell and Windows-specific tools (e.g., WinSCP.exe, IIS administration, .NET Framework). There is little to no mention of Linux equivalents, Bash, or Python runbooks, and Windows patterns (such as using C:\temp, UAC, and .exe files) are referenced without Linux alternatives. The documentation does not provide parity for Linux users or those using non-Windows scripting environments.
Recommendations
  • Add examples for Python runbooks and Bash scripts where applicable, especially in sections about error handling, temporary storage, and exception management.
  • Include Linux-specific guidance for Hybrid Runbook Workers, such as how to manage elevation, temporary storage (e.g., /tmp), and third-party software installation on Linux hosts.
  • Mention Linux equivalents for Windows tools (e.g., alternatives to WinSCP.exe, IIS administration, .NET Framework) and clarify module compatibility for Linux environments.
  • Provide explicit documentation on how Azure Automation supports Linux runbooks, including limitations, supported modules, and best practices.
  • Balance references to PowerShell with information about Python and other supported languages, and link to relevant tutorials for Linux users.
GitHub Create Pull Request
Automation Configure runbook output and message streams ...s/automation/automation-runbook-output-and-messages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows/PowerShell bias. All examples, code snippets, and tooling references are exclusively for Windows PowerShell, with no mention of Linux-native tools, Bash, or cross-platform scripting alternatives. Windows PowerShell cmdlets and patterns are presented as the default and only option for runbook output and message stream handling. There is no guidance for users running Azure Automation runbooks from Linux environments or using non-PowerShell languages (except a brief note about Python output language support).
Recommendations
  • Add equivalent examples and instructions for Bash, Python, and other supported languages in Azure Automation, especially for output and message stream handling.
  • Explicitly mention cross-platform compatibility for Azure Automation runbooks, clarifying which features and cmdlets are available on Linux and macOS agents.
  • Provide guidance on retrieving runbook output and messages using Azure CLI, REST API, or SDKs, which are platform-agnostic.
  • Include references to Linux shell scripting patterns for error and output handling, such as using stdout/stderr, exit codes, and logging.
  • Clarify any limitations or differences in stream handling between Windows PowerShell and PowerShell Core (pwsh) on Linux/macOS.
  • Where PowerShell is referenced, specify whether instructions apply to Windows PowerShell, PowerShell Core, or both, and note any differences.
GitHub Create Pull Request
Automation Deploy an Amazon Web Services VM with an Azure Automation runbook ...icles/automation/automation-scenario-aws-deployment.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exclusively uses PowerShell and Windows-centric tooling for all examples and instructions, including module installation, scripting, and credential management. There are no references to Linux-native tools, Bash, or cross-platform alternatives. All steps assume familiarity with PowerShell and Windows environments, and there is no guidance for users who may prefer or require Linux-based automation approaches.
Recommendations
  • Provide equivalent examples using AWS CLI and Bash scripts for Linux users.
  • Include instructions for installing and using AWS CLI or SDKs in Azure Automation, highlighting cross-platform compatibility.
  • Mention how to author and run Python or Bash runbooks in Azure Automation for AWS VM provisioning.
  • Add notes or sections clarifying platform requirements and offering parity for Linux/macOS users.
  • Ensure that credential management examples include both PowerShell and Linux CLI methods.
GitHub Create Pull Request
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell examples for command-line operations and configuration steps, with no equivalent examples for Bash, Azure CLI, or other Linux-native tools. PowerShell is consistently presented as the primary or sole scripting interface, and Windows-centric tools and patterns (such as PowerShell cmdlets) are referenced throughout. REST API examples are included, but there is a lack of parity for Linux users who may prefer Bash or Azure CLI workflows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, including assigning managed identities, configuring Key Vault access policies, and updating encryption settings.
  • Include Bash script snippets for common tasks, especially those relevant to Linux automation environments.
  • Explicitly mention cross-platform support for Azure Automation and clarify that PowerShell is available on Linux, but users may also use Azure CLI or REST API.
  • Reorder sections or provide parallel examples so that Linux-friendly tools (Azure CLI, Bash) are presented before or alongside PowerShell, rather than after.
  • Reference documentation for Azure CLI and Bash where PowerShell modules are mentioned, to guide Linux users to equivalent resources.
GitHub Create Pull Request
Automation Track updated files with an Azure Automation watcher task ...s/automation/automation-scenario-using-watcher-task.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias. All examples and instructions use PowerShell scripts and Windows-style paths (e.g., D:\examplefiles). The only method shown for creating test files is via PowerShell, with no mention of Linux shell equivalents. Folder paths and commands are Windows-centric, and there is no guidance for Linux-based Hybrid Runbook Workers or Bash scripting. The documentation assumes a Windows environment throughout and does not provide Linux parity.
Recommendations
  • Include equivalent Linux/Bash examples for file creation and manipulation (e.g., using 'touch' or 'mkdir' in Bash).
  • Mention how to configure watcher tasks for folders on Linux-based Hybrid Runbook Workers, including example Linux paths (e.g., /home/examplefiles).
  • Provide sample runbooks or scripts written in Bash or Python, or clarify if only PowerShell is supported.
  • Explicitly state platform requirements and limitations (e.g., if watcher tasks only work on Windows Hybrid Runbook Workers).
  • Add troubleshooting notes or guidance for users running Linux Hybrid Runbook Workers.
  • Where possible, use platform-neutral language and examples, or present Windows and Linux instructions side-by-side.
GitHub Create Pull Request
Automation Azure Automation account authentication overview ...in/articles/automation/automation-security-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell cmdlets as the primary automation method and omitting Linux-specific tools or examples. There is no mention of Bash, shell scripts, or Linux authentication patterns, nor are there examples or guidance for Linux users. The documentation implicitly assumes a Windows-centric environment, particularly in the context of Azure Automation and Hybrid Runbook Worker usage.
Recommendations
  • Include examples using Bash or shell scripts alongside PowerShell examples for runbook authentication and automation tasks.
  • Explicitly mention Linux support for Hybrid Runbook Workers and provide guidance for configuring authentication on Linux-based workers.
  • Reference Linux-native tools (e.g., Azure CLI, OpenSSH) in addition to Windows tools like PowerShell.
  • Add a section or callouts for cross-platform considerations, highlighting any differences or additional steps required for Linux environments.
  • Ensure parity in documentation by providing step-by-step instructions for both Windows and Linux users when creating and authenticating Automation accounts.
GitHub Create Pull Request
Automation Automation services in Azure - overview ...s/blob/main/articles/automation/automation-services.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is repeatedly emphasized as the primary automation scripting language, with frequent references to PowerShell runbooks, modules, and integration. Windows-centric tools and concepts (e.g., registry, Active Directory, SQL Server) are mentioned more often than Linux equivalents. Examples and scenarios tend to focus on Windows environments, with little explicit mention of Linux-specific automation patterns, tools, or shell scripting. Although some services claim Linux support, practical Linux usage examples or references to Linux-native tools (e.g., Bash, systemd, cron) are missing.
Recommendations
  • Provide explicit Linux automation examples, such as Bash or Python runbooks, and reference Linux shell scripting in addition to PowerShell.
  • Mention Linux-native tools and concepts (e.g., systemd, cron, package managers) when discussing configuration and update management.
  • Balance references to Windows-specific technologies (e.g., registry, Active Directory) with Linux equivalents (e.g., /etc files, LDAP, system logs).
  • Include Linux-focused scenarios in tables and user stories, such as automating patching or configuration drift detection on Ubuntu or CentOS servers.
  • Clarify cross-platform capabilities in Azure Automation, Logic Apps, and Functions, and provide links to Linux documentation where relevant.
GitHub Create Pull Request
Automation Migration guidance from Change Tracking and inventory using Log Analytics to Azure Monitoring Agent ...g/guidance-migration-log-analytics-monitoring-agent.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates several Windows biases. PowerShell is the only scripting method provided for bulk migration, with no equivalent Bash or Linux-native script. Windows-specific concepts (e.g., registry, Windows services) are mentioned before Linux equivalents, and the migration script parameters and prerequisites are PowerShell-centric. There are no Linux command-line examples or explicit Linux onboarding steps outside of the generic Azure portal workflow. Windows terminology and tools are referenced more frequently and prominently than Linux ones.
Recommendations
  • Provide Bash or shell script examples for Linux users, especially for bulk migration scenarios.
  • Include Linux-specific onboarding steps and screenshots where applicable, not just generic portal instructions.
  • List Linux data types (e.g., daemons, files) alongside Windows types, and avoid Windows-first ordering.
  • Reference Linux-native tools and commands (e.g., az CLI, systemd) where relevant, not just PowerShell.
  • Ensure all instructions and prerequisites explicitly mention Linux compatibility and provide parity in detail.
GitHub Create Pull Request
Automation Send an email from an Azure Automation runbook ...blob/main/articles/automation/automation-send-email.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses PowerShell for all examples, setup, and automation steps, with no mention of Bash, CLI, or Python alternatives. All code snippets, module requirements, and instructions are tailored for PowerShell and the Azure Az PowerShell module, which are more commonly associated with Windows environments. There are no Linux shell (Bash) or cross-platform scripting examples, and the documentation does not address how to perform these tasks using the Azure CLI or other non-Windows tools. The structure and language assume familiarity with Windows/PowerShell paradigms, contributing to a strong Windows bias.
Recommendations
  • Provide equivalent examples using Azure CLI (az commands) and Bash scripts for all major steps, including Key Vault creation, secret management, and role assignments.
  • Include a section or parallel instructions for creating and running runbooks using Python, which is supported in Azure Automation and is cross-platform.
  • Mention that Azure Automation supports both PowerShell and Python runbooks, and show how to select the runbook type accordingly.
  • Reference Linux/macOS environments explicitly, including any prerequisites or differences in module installation or authentication.
  • Where PowerShell modules are required, note any cross-platform compatibility or provide alternatives for users on Linux/macOS.
  • Ensure that tool and command references do not assume a Windows environment by default, and avoid presenting Windows-specific tools or patterns before their cross-platform equivalents.
GitHub Create Pull Request
Automation Start an Azure Automation Runbook from a Webhook ...s/blob/main/articles/automation/automation-webhooks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias. All code examples and instructions use PowerShell, a Windows-centric tool, and reference Windows file paths (e.g., 'path\names.json'). There are no examples using Bash, curl, or other Linux-native tools. REST API usage is shown only via PowerShell's Invoke-RestMethod. The documentation does not mention or show how to perform these tasks from Linux or macOS environments, nor does it provide parity for non-Windows users.
Recommendations
  • Add equivalent examples using Bash and curl for creating, invoking, and deleting webhooks.
  • Show how to use Azure CLI (az) for all operations, as it is cross-platform.
  • Include Linux/macOS file path conventions in examples (e.g., '/home/user/names.json').
  • Demonstrate REST API calls using curl or httpie, not just PowerShell.
  • Clarify that PowerShell Core is available cross-platform, but provide examples for both Windows PowerShell and PowerShell Core on Linux/macOS.
  • Explicitly mention platform compatibility and provide troubleshooting tips for Linux/macOS users.
GitHub Create Pull Request
Automation Compose DSC configurations ...omation/compose-configurationwithcompositeresources.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented towards Windows and PowerShell. All examples and terminology (e.g., 'PSExecutionPolicy', '[PSCredential]', PowerShell cmdlets) are Windows-centric, with no Linux equivalents or examples provided. The mention of Chocolatey (a Windows package manager) further reinforces the Windows bias. Additionally, the inclusion of a Linux retirement announcement suggests diminishing support for Linux, but no alternative guidance is offered for Linux users.
Recommendations
  • Provide equivalent Linux examples for composing DSC configurations, including references to Linux-specific resources and parameters.
  • Include guidance or links for Linux users on how to achieve similar configuration management, possibly with other tools or Azure features.
  • Mention Linux tools and patterns (such as native shell scripts or Ansible) where appropriate, and avoid assuming PowerShell is the only option.
  • Ensure that examples and screenshots include both Windows and Linux scenarios, or clarify platform limitations explicitly.
  • If Linux support is deprecated, offer migration paths or alternatives for Linux users.
GitHub Create Pull Request
Automation Delete an Azure Automation Run As account ...blob/main/articles/automation/delete-run-as-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page focuses on deleting Azure Automation Run As accounts primarily through PowerShell and the Azure portal, both of which are Windows-centric tools. There are no examples or instructions for Linux users (e.g., using Azure CLI, Bash, or other cross-platform tools). The mention of PowerShell and portal actions comes before any consideration of Linux alternatives, and no Linux-specific guidance is provided.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include Bash script examples for deleting Run As accounts, if applicable.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or other supported tools.
  • Ensure that any references to PowerShell are balanced with references to cross-platform alternatives.
  • Add a section or note for Linux/macOS users to clarify platform compatibility.
GitHub Create Pull Request
Automation Context switching in Azure Automation ...ocs/blob/main/articles/automation/context-switching.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses PowerShell examples and Windows-centric Azure PowerShell cmdlets (Az, AzureRM) for context switching in Azure Automation. There are no references to Linux-native tools, Bash, CLI, or cross-platform scripting approaches. The guidance and code samples assume a Windows/PowerShell environment, which may disadvantage Linux users or those using Azure CLI.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for context management and runbook authentication.
  • Include Bash or Python runbook snippets to demonstrate context switching in non-PowerShell environments.
  • Explicitly mention cross-platform support and clarify which recommendations apply to Linux-based runbooks.
  • Reference Linux tools and patterns (e.g., environment variables, service principals via CLI) alongside PowerShell guidance.
  • Reorder sections or provide parallel guidance so Linux/CLI approaches are presented equally or before Windows/PowerShell methods.
GitHub Create Pull Request
Automation Manage your Azure Automation account ...e-docs/blob/main/articles/automation/delete-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI or bash examples. The use of PowerShell cmdlets is emphasized for automation and solution removal tasks, and there is no mention of Linux shell commands or cross-platform scripting approaches. Additionally, the PowerShell examples are presented before any mention of Azure CLI, and the portal instructions reference Windows-centric UI patterns. This limits accessibility for users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, such as deleting Automation accounts and removing solutions.
  • Include bash shell script examples where applicable to demonstrate cross-platform automation.
  • Explicitly mention that both PowerShell and Azure CLI are supported on Windows, Linux, and macOS, and provide guidance for installing and using these tools on non-Windows platforms.
  • Ensure that references to the Azure portal UI do not assume a Windows environment, and clarify that the portal is accessible from any modern browser on any OS.
  • Consider reordering examples so that Azure CLI and PowerShell are presented together, or alternate which is shown first, to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Automation Disable local authentication in Azure Automation ...in/articles/automation/disable-local-authentication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows-centric tools (e.g., PowerShell cmdlets like Invoke-AzRestMethod and Get-AzAutomationAccount). No Linux shell (bash, curl, az CLI) examples are given, nor are Linux workflows or tools mentioned. The instructions and verification steps are written for PowerShell users, implicitly prioritizing Windows environments and leaving Linux users without direct guidance.
Recommendations
  • Add equivalent examples using Azure CLI (az) and REST API calls via curl for Linux/macOS users.
  • Explicitly mention that the PowerShell examples are for Windows and provide parallel instructions for Linux environments.
  • Include verification steps using az CLI or curl to check the disableLocalAuth property.
  • Reference cross-platform tools and patterns before or alongside Windows-specific ones.
  • Add a note about platform compatibility and recommend tools for both Windows and Linux users.
GitHub Create Pull Request
Automation Using a system-assigned managed identity for an Azure Automation account ...s/automation/enable-managed-identity-for-automation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples for enabling and using managed identity (including REST API, ARM template deployment, role assignment, authentication, and resource access) are provided exclusively in PowerShell, with only one Python example (for runbooks) and no Bash, CLI, or Linux-native scripting alternatives. Windows/PowerShell tools and patterns (e.g., New-Object, Invoke-RestMethod, Windows file paths) are used throughout, and instructions for checking Hybrid Runbook Worker versions list Windows before Linux. There is no mention of Azure CLI, Bash, or Linux shell commands for any of the main workflows.
Recommendations
  • Add Azure CLI and Bash examples for all major workflows (enabling managed identity, assigning roles, authenticating, accessing resources).
  • Include Linux-native instructions and file paths where applicable, especially for REST API and ARM template deployment steps.
  • Present Linux and Windows instructions in parallel, or alternate their order to avoid 'windows_first' bias.
  • Expand Python and other cross-platform runbook examples beyond the single Python snippet.
  • Reference Linux tools and patterns (e.g., curl, jq, az CLI) alongside PowerShell equivalents.
  • Ensure troubleshooting and migration sections include Linux/CLI guidance, not just PowerShell.
GitHub Create Pull Request
Automation Disable system-assigned managed identity for Azure Automation account .../automation/disable-managed-identity-for-automation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides detailed PowerShell-based instructions for disabling a system-assigned managed identity in Azure Automation, including use of Windows-specific tools and cmdlets. No equivalent Linux or cross-platform CLI examples (such as Azure CLI, curl, or bash scripts) are provided, and the PowerShell workflow is presented as the only programmatic option after the REST API section. This creates a bias toward Windows users and leaves Linux users without clear guidance.
Recommendations
  • Add equivalent Azure CLI examples for authentication and REST API invocation, which work on both Windows and Linux.
  • Provide curl or bash script examples for sending PATCH requests to the REST API.
  • Include instructions for obtaining access tokens using cross-platform tools (e.g., Azure CLI's 'az account get-access-token').
  • Explicitly mention that PowerShell examples are Windows-centric and offer alternative steps for Linux/macOS users.
  • Reorder or parallelize example sections so that Windows and Linux methods are presented together, rather than Windows-first.
GitHub Create Pull Request
Automation Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in Azure Automation ...ation/extension-based-hybrid-runbook-worker-install.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates several forms of Windows bias. Windows and PowerShell examples are presented first and in greater detail, with Linux examples often following or being less emphasized. PowerShell is the primary automation tool referenced, even for Linux scenarios, and Windows-specific tools and paths are mentioned more frequently. Infrastructure-as-code examples (Bicep, ARM) and CLI samples focus on Windows VM creation and extension installation, with little to no Linux VM equivalents. Folder permissions and troubleshooting notes are Windows-centric, and Linux-specific requirements or commands are less visible or omitted.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which platform is shown first in code samples and walkthroughs.
  • Provide Linux-native automation examples (e.g., Bash scripts, cloud-init, Ansible) in addition to PowerShell, especially for Linux VM onboarding and extension management.
  • Expand infrastructure-as-code samples (Bicep, ARM templates) to include Linux VM creation and extension installation, not just Windows.
  • Include Linux-specific troubleshooting, permissions, and configuration steps with equal detail to Windows.
  • Reference Linux tools and patterns (e.g., systemd, SELinux, package managers) where relevant, not just Windows tools.
  • Clarify when PowerShell Core is required or optional on Linux, and offer alternatives for users who prefer native Linux scripting.
  • Ensure all folder paths, permissions, and operational notes are provided for both platforms, not just Windows.
GitHub Create Pull Request
Automation Manage runbooks in Azure Automation ...-docs/blob/main/articles/automation/manage-runbooks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for managing runbooks in Azure Automation exhibits a strong Windows bias. All code examples use PowerShell, with cmdlets and patterns specific to Windows environments. File paths are given in Windows format (e.g., C:\Runbooks\...), and there is no mention of Bash, shell scripting, or Linux-native tools. The documentation assumes the use of Windows-centric tools and workflows, and does not provide equivalent guidance or examples for Linux users or those preferring Bash/Python automation. Linux alternatives are not discussed, and PowerShell is presented as the default or only option for scripting and automation.
Recommendations
  • Add equivalent examples using Bash and Azure CLI for all major operations (create, import, publish, schedule, restore runbooks).
  • Include Linux file path examples and clarify cross-platform compatibility for script imports.
  • Explicitly mention and link to documentation for using Python runbooks, including how to author, test, and publish them from Linux environments.
  • Provide guidance on using Azure CLI and REST API for runbook management, with sample commands.
  • Clarify which features and cmdlets are available and supported on Linux, macOS, and Windows.
  • Add a section addressing cross-platform considerations, including differences in authentication, file handling, and environment setup.
GitHub Create Pull Request
Automation Use the Azure Automation graphical runbook SDK (preview) ...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily oriented toward Windows and PowerShell. All examples and SDK usage revolve around PowerShell commands, modules, and workflows, with no mention of Linux-compatible scripting or tools. The graphical runbook SDK is described as managing Windows PowerShell code, and all activity types and value descriptors are PowerShell-centric. There are no Linux/bash examples, nor is there guidance for non-Windows environments.
Recommendations
  • Add examples that demonstrate how to use the SDK with Linux-compatible scripting languages (e.g., Bash, Python) if supported.
  • Clarify whether the graphical runbook SDK and Azure Automation graphical runbooks can be authored or executed on Linux environments, and document any limitations or alternatives.
  • Include references to cross-platform modules or scripting patterns, and provide parity in documentation for Linux users.
  • If PowerShell Core (cross-platform) is supported, explicitly mention this and provide examples for Linux/macOS usage.
  • Document any differences in runbook execution or authoring between Windows and Linux environments.
GitHub Create Pull Request
Automation Use Azure Private Link to securely connect networks to Azure Automation ...in/articles/automation/how-to/private-link-security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell for configuration examples, especially in the section on setting public network access flags. There are no equivalent CLI or Linux shell examples provided. Additionally, the State Configuration scenario highlights PowerShell Desired State Configuration (DSC) as the main configuration management tool, which is Windows-centric, without mention of cross-platform alternatives. While the page acknowledges Linux support in some features (e.g., Update Management), practical examples and tooling guidance are focused on Windows.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside PowerShell scripts for configuration tasks such as setting public network access flags.
  • Include Linux-specific instructions and examples for agent installation, configuration, and management where relevant.
  • Mention and link to cross-platform configuration management options (such as Ansible or Chef) in addition to PowerShell DSC, especially in the State Configuration scenario.
  • Ensure screenshots and UI walkthroughs clarify parity for Linux users (e.g., agent installation, hybrid worker setup).
  • Explicitly state any differences or limitations for Linux environments where applicable, and provide workarounds or alternatives.
GitHub Create Pull Request
Automation Manage Office 365 services using Azure Automation ...ocs/blob/main/articles/automation/manage-office-365.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses Windows PowerShell examples and tools, such as the Microsoft Graph PowerShell module and Send-MailMessage, with explicit notes that PowerShell Core (cross-platform) is not supported. There are no Linux or cross-platform alternatives, and all instructions assume a Windows environment, both in tooling and workflow.
Recommendations
  • Provide equivalent examples using PowerShell Core (pwsh) where possible, or clarify platform limitations.
  • Include guidance for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform scripting alternatives.
  • List platform support for each tool/module, and suggest alternatives for unsupported platforms.
  • Add explicit instructions or links for setting up Azure Automation and Office 365 management from non-Windows environments.
  • Where Windows-specific tools (e.g., Send-MailMessage) are used, suggest cross-platform alternatives (e.g., using SMTP libraries in Python, or other PowerShell modules that work on Linux).
GitHub Create Pull Request
Automation Manage Runtime Environment and Associated Runbooks in Azure Automation ...main/articles/automation/manage-runtime-environment.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing heavily on PowerShell examples, referencing Windows PowerShell modules and patterns, and providing detailed instructions for PowerShell environments and packages. Windows-centric tools (e.g., PowerShell Gallery, Az PowerShell module) are mentioned and used as defaults, while Linux-specific details and examples are minimal or absent. Python (Linux) environments are mentioned but not explored in equivalent depth, and Linux-native tools or workflows are not provided.
Recommendations
  • Provide equal depth and step-by-step examples for Python (Linux) runbooks, including REST API payloads and portal workflows.
  • Include Linux-native package management instructions (e.g., pip, requirements.txt) and clarify how Python packages are managed and uploaded.
  • Add examples of viewing installed Python packages (e.g., using pip list) similar to the PowerShell Get-Module example.
  • Reference Linux-specific documentation for Python modules and packages, and avoid linking only to Windows PowerShell module documentation.
  • Clarify the runtime environment OS (Windows vs. Linux) and provide troubleshooting steps for both platforms.
  • Ensure screenshots and UI instructions are not PowerShell-centric and show parity for Python workflows.
  • Mention and provide examples for Azure CLI usage in Python runbooks, not just PowerShell.
GitHub Create Pull Request
Automation Manage databases in Azure SQL databases using Azure Automation ...articles/automation/manage-sql-server-in-automation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell and Az PowerShell cmdlets for all automation and SQL management examples. There are no references to Linux-native tools, Bash, or cross-platform alternatives. Instructions for installing modules and running commands assume a Windows environment (elevated PowerShell prompt), and there is no mention of how to accomplish these tasks on Linux-based Hybrid Runbook Workers or using Bash/CLI. The documentation also introduces Windows-centric patterns and tools before any Linux equivalents (which are absent).
Recommendations
  • Include equivalent examples using Azure CLI and Bash scripts for connecting and managing Azure SQL databases.
  • Document how to install required modules and run automation tasks on Linux-based Hybrid Runbook Workers.
  • Add notes or sections clarifying cross-platform support and differences, especially for Linux users.
  • Reference Linux tools (e.g., sqlcmd, Azure CLI) alongside PowerShell cmdlets, and provide sample code for both environments.
  • Ensure that instructions for configuring Hybrid Runbook Workers cover both Windows and Linux setup steps.
GitHub Create Pull Request
Automation Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation ...g-agent-based-hybrid-worker-to-extension-based-workers.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias in several areas. Windows examples, tools, and terminology are presented first or exclusively in key sections, especially in the Bicep and ARM template samples, which only provision Windows VMs. PowerShell is heavily featured, with detailed cmdlets and usage, while Linux equivalents are minimal or absent. The extension installation examples and resource definitions focus on Windows-specific handlers (HybridWorkerForWindows), and Linux-specific instructions are either missing or relegated to notes or optional sections. The removal process for agent-based workers is more detailed for Windows (registry manipulation) than for Linux (simple directory removal), and permissions guidance is Windows-centric.
Recommendations
  • Provide parallel Bicep and ARM template examples for Linux VMs, using the correct image references and extension types (HybridWorkerForLinux).
  • Include Linux-specific CLI and PowerShell commands, such as az vm create with Linux images and Set-AzVMExtension/New-AzConnectedMachineExtension using HybridWorkerForLinux.
  • Expand Linux prerequisites and troubleshooting sections to match the depth given to Windows, including permissions, identity, and hardening guidance.
  • Ensure all extension installation examples clearly show both Windows and Linux type values and settings.
  • Balance the order of presentation so that Linux instructions/examples are given equal prominence and detail as Windows.
  • Add more Linux-specific automation and management scenarios, including common distributions and shell scripting examples.
GitHub Create Pull Request
Automation Manage Python 3 packages in Azure Automation ...ocs/blob/main/articles/automation/python-3-packages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation displays a Windows bias in several ways. Windows and PowerShell examples are given exclusively for Python 3.8, with instructions and screenshots referencing Windows environments and tools first or only. Linux instructions are present for Python 3.10, but there is no parity for Linux-based management of Python 3.8 packages. PowerShell cmdlets are provided for package management, but there are no equivalent CLI or bash examples for Linux users. Windows terminology and tooling are referenced before or instead of Linux alternatives.
Recommendations
  • Provide Linux-based examples for Python 3.8 package management, including instructions for generating wheel files and importing packages using Linux tools.
  • Add Azure CLI or bash script equivalents for all PowerShell cmdlet examples, ensuring Linux users have clear guidance.
  • Present Windows and Linux instructions side-by-side or in tabs, rather than prioritizing Windows first.
  • Explicitly mention Linux support and limitations for Hybrid Runbook Workers and package management.
  • Review screenshots and UI references to ensure they are not Windows-specific unless necessary, and provide Linux alternatives where applicable.
GitHub Create Pull Request
Automation Create an Azure Automation account using a Resource Manager template ...ation/quickstart-create-automation-account-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and the Azure portal as primary deployment methods, with PowerShell examples and terminology appearing before Azure CLI equivalents. There is no mention of Linux-specific tools or workflows, and no Linux shell examples are provided. The guidance for resolving template errors and deploying via command line is focused on PowerShell, with Azure CLI only mentioned secondarily and without detailed Linux context.
Recommendations
  • Provide explicit Bash/Linux shell examples for deploying the ARM template using Azure CLI, including command syntax and environment notes.
  • Mention Linux and macOS compatibility for Azure CLI, and clarify that PowerShell is not required for non-Windows users.
  • Reorder instructions to present Azure CLI and Bash examples before or alongside PowerShell, rather than after.
  • Include troubleshooting steps and error messages relevant to Linux environments (e.g., file permissions, shell quoting).
  • Reference Linux-native tools (such as curl, jq) where appropriate for template management and deployment.
  • Add a note or section highlighting cross-platform support and differences, ensuring parity in guidance for Linux users.
GitHub Create Pull Request
Automation Azure Automation overview ...s/azure-docs/blob/main/articles/automation/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Automation demonstrates a Windows bias in several ways. PowerShell is mentioned repeatedly as the primary automation language, especially in the context of Desired State Configuration (DSC), with little to no mention of Linux-native equivalents. Windows-centric tools and scenarios (e.g., Active Directory, SharePoint Server, SQL Server) are listed prominently, while Linux-specific examples or tools are missing or only referenced generically. When discussing runbooks and configuration management, Windows/PowerShell approaches are described first and in more detail, with Linux support only mentioned as a general capability rather than with concrete examples or guidance.
Recommendations
  • Include explicit Linux shell (Bash, sh) runbook examples alongside PowerShell and Python.
  • Discuss Linux-native configuration management tools (e.g., Ansible, Chef, Puppet) and how they integrate with Azure Automation.
  • Provide Linux-specific scenarios (e.g., automating package updates, managing systemd services, configuring iptables) in the 'Common scenarios' section.
  • Clarify how Azure Automation supports Linux DSC (if available) or alternatives, and provide links to relevant documentation.
  • Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows/PowerShell first.
  • Add references to Linux-specific modules or packages available in the Automation account.
  • Highlight any differences or considerations when deploying Hybrid Runbook Worker on Linux vs. Windows.
GitHub Create Pull Request
Automation Quickstart - Enable managed identities for your Automation account using the Azure portal ...cles/automation/quickstarts/enable-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily through its exclusive reference to PowerShell in the 'Next steps' section, suggesting the use of a PowerShell runbook as the default follow-up. There are no examples or guidance for Linux users, such as Bash or Python runbooks, nor are there references to Linux command-line tools or workflows. The instructions are entirely portal-based, which is cross-platform, but the only code-based example is Windows-centric.
Recommendations
  • Include links or examples for creating and using managed identities with Bash or Python runbooks in addition to PowerShell.
  • Add references to Azure CLI or REST API methods for enabling managed identities, which are platform-agnostic.
  • In the 'Next steps' section, provide alternative tutorials for Linux users, such as 'Create Automation Python runbook using managed identity' or 'Create Automation Bash runbook using managed identity'.
  • Ensure that any code snippets or automation examples are available in both PowerShell and Bash/Python where applicable.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, with examples, code snippets, and workflow patterns almost exclusively using PowerShell, PowerShell Workflow, and Windows-specific cmdlets. Windows tools and patterns (such as PowerShell hashtables, .NET types, and Windows PowerShell attributes) are mentioned throughout, with little to no equivalent coverage for Linux or cross-platform scenarios. Python runbooks are briefly mentioned, but lack parity in example depth and practical usage scenarios compared to PowerShell. There are no examples or guidance for using Linux-native tools, shell scripts, or cross-platform automation approaches.
Recommendations
  • Add equivalent examples for Bash/shell runbooks, including parameter passing and invocation from Linux environments.
  • Provide guidance and code samples for starting runbooks using Azure CLI (az), which is cross-platform, alongside PowerShell examples.
  • Include Linux-specific notes and troubleshooting tips for common scenarios, such as file paths, authentication, and environment differences.
  • Expand Python runbook examples to match the depth and practical scenarios shown for PowerShell, including parameter handling, JSON input, and automation patterns.
  • Clarify which features and patterns are Windows-only, and offer alternatives or workarounds for Linux users.
  • Mention and demonstrate usage of cross-platform SDKs (e.g., Azure SDK for Python, Node.js) for starting runbooks and passing parameters.
GitHub Create Pull Request
Automation Manage schedules in Azure Automation ...main/articles/automation/shared-resources/schedules.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and cmdlets for managing Azure Automation schedules. All CLI-based instructions use PowerShell syntax, and there is no mention of Bash, Azure CLI, or Linux-native tools. The use of PowerShell is assumed throughout, and no alternative cross-platform scripting examples are provided. Windows-centric tools and patterns (e.g., PowerShell, .ps1 scripts) are referenced without Linux equivalents, and PowerShell instructions are presented before any mention of ARM templates or portal usage.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets and scenarios, demonstrating how to manage schedules using az automation commands.
  • Include Bash script examples for common scheduling tasks to support Linux users.
  • Explicitly state cross-platform options for automation (e.g., Azure CLI, REST API) and provide usage instructions.
  • Reference Linux-native tools or patterns where relevant, such as cron for local scheduling, and clarify the platform compatibility of each method.
  • Reorganize sections to present cross-platform or platform-neutral methods (e.g., Azure CLI, REST API, ARM templates) before platform-specific tools like PowerShell.
GitHub Create Pull Request
Automation Quickstart: Use Terraform to create an Azure Automation account ...ickstarts/create-azure-automation-account-terraform.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence and is referenced in the 'Next steps' section. The tutorial for further learning is focused on creating a PowerShell runbook, which is a Windows-centric automation pattern. There are no Linux shell (bash) or cross-platform scripting examples, and the documentation references Windows tools (PowerShell) without mentioning Linux alternatives or parity.
Recommendations
  • Add bash/Linux shell examples alongside Azure CLI and PowerShell for verifying results.
  • In the 'Next steps' section, include links to tutorials for creating Python or bash runbooks, not just PowerShell.
  • Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
  • Where PowerShell is referenced, note its availability on Linux and macOS, or provide equivalent bash commands.
  • Ensure that automation patterns and examples are not exclusively focused on Windows tools.
GitHub Create Pull Request
Automation Azure Quickstart - Install Hybrid Worker extension on Azure portal. ...omation/quickstarts/install-hybrid-worker-extension.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. The step-by-step instructions, screenshots, and extension selection all reference 'Windows Hybrid Worker', with no equivalent guidance or visuals for Linux VMs. Prerequisites and installation steps mention only Windows, omitting Linux-specific instructions, extension names, or considerations. The documentation does not provide parity for Linux users, despite mentioning Linux support in the introduction.
Recommendations
  • Add explicit instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
  • Include the Linux-specific extension name and any differences in configuration or prerequisites for Linux VMs.
  • Present Windows and Linux examples side-by-side or in parallel sections to ensure equal visibility and usability.
  • Clarify any platform-specific limitations or requirements in the prerequisites section.
  • Ensure that all referenced links and next steps provide clear Linux guidance where applicable.
GitHub Create Pull Request
Automation Remove user-assigned managed identity for Azure Automation account ...n/articles/automation/remove-user-assigned-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell examples for command-line and scripting operations, referencing Windows-centric tools and cmdlets (e.g., Set-AzAutomationAccount, Invoke-RestMethod), and omitting equivalent Linux-friendly instructions (such as Azure CLI or curl). Steps for REST API usage are shown exclusively with PowerShell, and verification steps also rely on PowerShell. No Bash, Azure CLI, or cross-platform shell examples are provided.
Recommendations
  • Add equivalent Azure CLI examples for all operations shown with PowerShell, including authentication, resource modification, and verification.
  • Provide REST API invocation examples using curl or httpie, which are standard on Linux and macOS.
  • Include Bash script snippets alongside PowerShell, especially for variable assignment and file manipulation.
  • Clarify that PowerShell examples can be run on Linux/macOS with PowerShell Core, or explicitly note platform requirements.
  • Reorder sections or provide parallel examples so that Linux-friendly methods (Azure CLI, Bash, curl) are presented alongside or before Windows/PowerShell methods.
  • Reference cross-platform tools and patterns where possible, reducing reliance on Windows-only cmdlets.
GitHub Create Pull Request
Automation Runtime Environment in Azure Automation ...in/articles/automation/runtime-environment-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell as the primary scripting language, referencing multiple PowerShell versions, and focusing on Windows-centric tools and patterns. Azure CLI is only discussed in the context of PowerShell 7.4, with no mention of Bash or Linux shell usage. Package management examples and system-generated environments are centered around PowerShell and Python, with PowerShell always listed first. There are no Linux-specific examples, nor is there guidance for users who prefer Bash or other Linux-native tools.
Recommendations
  • Include examples and guidance for using Bash scripts and Linux shell environments in Azure Automation.
  • Discuss Azure CLI usage in the context of Bash or Linux environments, not just PowerShell.
  • List scripting languages and runtime environments in a neutral order (e.g., alphabetical) rather than always putting PowerShell first.
  • Provide parity in package management instructions for both PowerShell (PSGallery) and Python (PyPI), and mention Linux-native package sources where relevant.
  • Add links to Linux shell scripting documentation alongside PowerShell references.
  • Clarify support for Linux-based runbooks and environments, including any limitations or best practices.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. It focuses almost exclusively on PowerShell cmdlets and Windows-centric tools for credential management in Azure Automation. All code examples outside of Python are PowerShell-based, and there are no Bash, CLI, or Linux-native examples. The creation and management of credentials are described using Windows PowerShell and related modules, with no mention of Linux shell equivalents or cross-platform Azure CLI usage. The documentation assumes familiarity with Windows/PowerShell patterns and tools, and does not provide parity for Linux users.
Recommendations
  • Add Azure CLI examples for credential management, including creation, retrieval, and deletion of credentials.
  • Include Bash or shell script examples where applicable, especially for runbook scenarios.
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users.
  • List Linux-compatible tools and modules alongside PowerShell cmdlets, and clarify any platform limitations.
  • Reorder sections or provide parallel instructions so that Windows and Linux approaches are presented equally.
GitHub Create Pull Request
Automation Manage modules in Azure Automation ...b/main/articles/automation/shared-resources/modules.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily focused on PowerShell modules and Windows-centric workflows. Examples, tools, and instructions are almost exclusively PowerShell-based, with explicit references to Windows PowerShell features (such as Import-Module, using module statement, and Windows-specific cmdlets). Internal cmdlets and modules are noted as unavailable on Linux Hybrid Runbook Workers, but no Linux alternatives or parity guidance is provided. Python modules are mentioned briefly, but without examples or integration guidance. There are no Linux shell (bash, CLI) examples, and the overall structure assumes a Windows-first approach.
Recommendations
  • Provide equivalent Linux/Unix examples for module management, such as using Azure CLI or bash scripts.
  • Clarify which features and modules are supported on Linux Hybrid Runbook Workers, and offer alternatives or workarounds where functionality is missing.
  • Include guidance and examples for managing Python modules and runbooks on Linux, with parity to PowerShell workflows.
  • Add explicit notes or tables comparing Windows and Linux support for each module and cmdlet.
  • Where internal cmdlets are unavailable on Linux, suggest alternative approaches for Linux users.
  • Balance the documentation by introducing Linux-first or cross-platform sections, and ensure that instructions do not assume Windows as the default environment.
GitHub Create Pull Request
Automation Manage variables in Azure Automation ...main/articles/automation/shared-resources/variables.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. PowerShell is presented as the primary scripting interface, with cmdlets and examples focused exclusively on Windows PowerShell and Az modules. Windows terminology (e.g., 'Windows Hybrid Runbook Worker') is used throughout, and there are no Bash, CLI, or Linux-native examples or references. The documentation does not mention or provide parity for Linux shell scripting, nor does it discuss how to manage variables from Linux environments or with cross-platform tools. Python examples are included, but only in the context of Azure Automation runbooks, not general Linux usage.
Recommendations
  • Add Azure CLI examples for variable management, showing equivalent operations to PowerShell cmdlets.
  • Include Bash shell scripting examples for accessing and managing variables, especially for Linux Hybrid Runbook Workers.
  • Clarify cross-platform compatibility of cmdlets and tools, and explicitly mention Linux support where applicable.
  • Reorder sections so that platform-neutral or cross-platform approaches (e.g., Azure CLI, REST API) are presented before Windows-specific tools.
  • Add notes or guidance for Linux users, including any prerequisites or differences in workflow.
  • Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' or specify when instructions are platform-specific.
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exhibits a strong Windows and PowerShell bias. All command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. The only scripting language supported for source control integration is PowerShell 5.1, and all automation and configuration steps are shown using PowerShell cmdlets. There are no Linux or cross-platform examples, and the documentation assumes the user is operating in a Windows/PowerShell environment.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for all PowerShell commands, especially for role assignment and source control configuration.
  • Explicitly state platform support and limitations (e.g., clarify if Linux-based runbooks or Python runbooks can be synchronized).
  • Include guidance for users working on Linux or macOS, such as using Azure CLI or REST API for automation tasks.
  • Mention cross-platform tools and editors (e.g., VS Code on Linux/macOS) in sections about encoding and editing runbooks.
  • If PowerShell is required, clarify that PowerShell Core (pwsh) is available cross-platform and provide examples for non-Windows environments.
GitHub Create Pull Request
Automation Start a runbook in Azure Automation ...e-docs/blob/main/articles/automation/start-runbooks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows PowerShell cmdlets as the primary command-line method for starting runbooks. There are no examples or mentions of Linux-native tools, Bash, Azure CLI, or cross-platform scripting approaches. The documentation assumes the use of PowerShell and Windows-centric workflows, omitting guidance for Linux users or those using non-PowerShell environments.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Include Bash scripting samples for starting runbooks via the Azure Automation API.
  • Explicitly mention that PowerShell Core is available on Linux/macOS and clarify compatibility.
  • Provide guidance or links for Linux users on installing and using Azure Automation tools.
  • Reorder sections to present cross-platform or platform-neutral methods (such as Azure CLI or REST API) before Windows-specific tools.
  • Highlight platform differences and considerations for both Windows and Linux users.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation runbook issues ...blob/main/articles/automation/troubleshoot/runbooks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily focused on PowerShell-based troubleshooting and examples, with nearly all code samples, cmdlet references, and troubleshooting steps using PowerShell or Windows-centric tools (e.g., PowerShell ISE, Windows Management Instrumentation). There is little to no mention of Linux-specific tools, shell environments, or cross-platform scripting approaches, and Linux alternatives are not provided or referenced. Python is mentioned only briefly, and no Linux shell (bash) examples or troubleshooting patterns are given.
Recommendations
  • Provide equivalent troubleshooting steps and examples for Linux environments, including bash or Python scripts where applicable.
  • Include guidance for users running Azure Automation runbooks from Linux machines, such as using Azure CLI, bash, or Python.
  • Reference cross-platform tools (e.g., VS Code, Azure CLI) and clarify when steps are OS-agnostic.
  • Add explicit notes or sections for Linux users, highlighting differences in module installation, authentication, and error handling.
  • Ensure that troubleshooting steps do not assume the use of PowerShell or Windows-only tools, or provide alternatives for Linux users.
  • Where PowerShell is required, mention PowerShell Core (pwsh) and its cross-platform capabilities, and provide examples for Linux/macOS.
GitHub Create Pull Request
Automation Configure machines to a desired state in Azure Automation ...automation/tutorial-configure-servers-desired-state.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All examples use Windows-centric DSC resources (e.g., WindowsFeature IIS), and all command-line instructions are given in PowerShell. Prerequisites and links focus on Windows VMs and Windows PowerShell DSC, with no Linux configuration examples or equivalent Linux tooling mentioned. The retirement announcement for Linux DSC is included, but there is no guidance or parity for Linux users.
Recommendations
  • Add explicit Linux onboarding/configuration examples, using Linux DSC resources (if still supported) or alternatives.
  • Include Bash/CLI examples where possible, or clarify cross-platform support and alternatives for Linux users.
  • Mention Linux VM creation and configuration in prerequisites and link to relevant documentation.
  • If Linux DSC is deprecated, provide migration guidance or alternatives for Linux configuration management (e.g., Ansible, Chef, native Azure solutions).
  • Balance references to Windows tools (PowerShell, WindowsFeature) with Linux equivalents or alternatives.
GitHub Create Pull Request
Automation Remove DSC and node from Automation State Configuration ...configuration/remove-node-and-configuration-package.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell-based instructions and cmdlets, mentioning Windows tools and patterns first, and providing more detailed steps for Windows nodes. Linux instructions are present but less detailed, sometimes only referencing file deletion or external resources, and Linux command examples are limited to package removal rather than configuration management.
Recommendations
  • Provide equivalent Linux command-line examples for unregistering nodes and deleting configurations, such as using shell scripts or CLI commands.
  • Include Linux-specific tooling or automation steps (e.g., omicli, systemctl for OMI/DSC services) alongside PowerShell examples.
  • Ensure that Linux instructions are as detailed as Windows instructions, with step-by-step guidance and screenshots where appropriate.
  • Present Windows and Linux instructions in parallel or in clearly separated sections to avoid implicit prioritization.
  • Reference Linux documentation and resources directly within the main content, not only as external links.
GitHub Create Pull Request
Automation Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation .../troubleshoot/extension-based-hybrid-runbook-worker.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. In many troubleshooting steps and scenarios, Windows instructions, tools, and PowerShell examples are presented first or in greater detail than their Linux equivalents. Windows-specific tools (such as PowerShell scripts, registry edits, and references to Windows services and event logs) are frequently mentioned, sometimes without parallel Linux guidance. Some scenarios (e.g., registry and folder permissions, event log troubleshooting) are Windows-only, and Linux troubleshooting is less detailed or omitted in those cases.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and prominence.
  • Where Windows-specific tools (e.g., PowerShell scripts, registry edits) are referenced, provide Linux equivalents (e.g., bash scripts, config file locations, systemd service management) or note their absence.
  • Include Linux-specific troubleshooting for scenarios currently covered only for Windows (e.g., permissions, log analysis, service management).
  • Add Linux examples for event log analysis, resource monitoring, and authentication troubleshooting.
  • Ensure that Linux troubleshooting steps are as detailed and actionable as Windows steps.
  • Where possible, use OS-agnostic terminology and structure to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation managed identity issues ...n/articles/automation/troubleshoot/managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exhibits a strong Windows bias. All troubleshooting examples and code snippets use PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM, Invoke-RestMethod), which are native to Windows and not available by default on Linux. There are no Bash, Azure CLI, or Python examples, nor any mention of Linux-specific troubleshooting patterns or tools. The documentation implicitly assumes the user is running runbooks or troubleshooting from a Windows environment, and does not address Linux automation scenarios or provide parity for Linux users.
Recommendations
  • Add equivalent troubleshooting steps and code examples using Azure CLI (az), Bash scripts, or Python SDK to support Linux users.
  • Explicitly mention how to perform managed identity troubleshooting from Linux environments, including any differences in authentication or error messages.
  • Where PowerShell cmdlets are referenced, provide side-by-side examples for Azure CLI and/or REST API calls.
  • Clarify which steps or commands are platform-specific and offer alternatives for Linux/macOS users.
  • Include notes or links to installing PowerShell Core on Linux if PowerShell is required, or recommend native Linux tools where possible.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation shared resource issues ...n/articles/automation/troubleshoot/shared-resources.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page is heavily focused on PowerShell-based troubleshooting and examples, which are primarily relevant to Windows environments. All code samples and cmdlet references use PowerShell syntax and Windows-centric tools (e.g., Remove-AzAutomationModule, Update-AzureModule.ps1). There are no equivalent examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. Windows-specific DLL errors are discussed without mention of Linux error patterns or troubleshooting steps.
Recommendations
  • Provide equivalent troubleshooting steps and examples using Azure CLI and Bash scripts for Linux users.
  • Include cross-platform guidance for module management, such as using REST API or Azure CLI commands.
  • Mention Linux-specific error messages or scenarios where applicable, and how to resolve them.
  • Clarify which steps or tools are Windows-only and offer alternatives for Linux/macOS environments.
  • Add notes or sections explicitly addressing Linux automation environments and their unique considerations.
GitHub Create Pull Request
Avere Vfxt Disaster recovery guidance for Avere vFXT for Azure ...ocs/blob/main/articles/avere-vfxt/disaster-recovery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Azure-based copy tools with a focus on Windows-centric options (AzCopy, Azure PowerShell, Azure Data Factory) and omitting Linux-native equivalents or examples. The mention of Azure PowerShell, a Windows-first tool, precedes any reference to cross-platform or Linux-friendly alternatives. There are no explicit Linux command-line examples or mentions of tools like Azure CLI, rsync, or other Linux-native utilities for data copying or management.
Recommendations
  • Add explicit examples using Azure CLI for copying data between Blob containers, as Azure CLI is cross-platform and widely used on Linux.
  • Mention and provide sample commands for Linux-native tools such as rsync or rclone, where appropriate, for copying data.
  • Reorder tool recommendations to list cross-platform options (e.g., Azure CLI, AzCopy) before Windows-specific ones (e.g., Azure PowerShell).
  • Clarify that AzCopy and Azure CLI are available on Linux and macOS, and provide installation instructions or links for those platforms.
  • Include sample workflows or commands for Linux environments when describing backup and restore procedures.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration dynamic configuration in an ASP.NET web application (.NET Framework) | Microsoft Docs ...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ visual_studio_only ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The tutorial is strongly oriented toward Windows development, focusing exclusively on ASP.NET (.NET Framework) and Visual Studio, both of which are Windows-only. All project creation and build/run instructions assume Visual Studio, with no mention of Linux-compatible alternatives (e.g., Mono, .NET Core, VS Code). While environment variable setup includes bash commands for macOS/Linux, all code samples and workflow steps are tailored for Windows users, and Windows command-line tools (cmd, PowerShell) are listed before Linux equivalents.
Recommendations
  • Add instructions for setting up and running the application on Linux (e.g., using Mono or .NET Core where possible).
  • Include alternative IDEs such as Visual Studio Code or JetBrains Rider, and provide steps for project creation and management on those platforms.
  • Present Linux/macOS commands before or alongside Windows commands, not after.
  • Clarify platform limitations (e.g., .NET Framework is Windows-only) and link to cross-platform alternatives (e.g., ASP.NET Core tutorials).
  • Provide guidance for building and running the application using command-line tools (dotnet CLI, msbuild) on Linux/macOS.
  • Where possible, offer parity in troubleshooting, resource cleanup, and next steps for non-Windows environments.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use Dynamic Configuration Using Push Refresh in a .NET App ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core-push-refresh.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Windows Command Prompt and PowerShell instructions before Linux/macOS equivalents. Screenshots and examples use Windows Command Prompt, and Windows-specific tools (setx, PowerShell) are highlighted. Although Linux/macOS instructions are present, they are secondary and less visually emphasized. No Linux-specific tools or screenshots are provided.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than always after.
  • Include screenshots of the app running in Linux/macOS terminals to balance visual representation.
  • Highlight cross-platform command-line usage (e.g., bash, sh) and avoid Windows-centric tools like setx where possible.
  • Explicitly mention that all steps are supported equally on Linux/macOS, and provide troubleshooting tips for those platforms.
  • Ensure parity in example code and environment variable setup, possibly using .env files or platform-neutral approaches.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use dynamic configuration in a .NET background service ...enable-dynamic-configuration-dotnet-background-service.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes explicit Windows tool usage (cmd, PowerShell) with detailed steps. While Linux/macOS commands are present, Windows instructions are consistently listed first, and there is more detail about Windows-specific behaviors (such as needing to restart the command prompt after setx). There is also a slight emphasis on Windows tools and patterns, such as referencing Visual Studio (though the .NET CLI is recommended for cross-platform use).
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabs or in the same order to avoid prioritizing Windows.
  • Provide equal detail for Linux/macOS instructions (e.g., mention if a shell restart is needed after export, as is done for Windows setx).
  • Where possible, use cross-platform commands or highlight the .NET CLI as the primary tool, minimizing references to Windows-specific tools or patterns.
  • Consider starting with Linux/macOS examples or alternating the order in which platforms are presented.
  • Explicitly state that all steps are cross-platform unless there are genuine platform-specific differences.
GitHub Create Pull Request
Azure App Configuration Integrate Azure App Configuration using a continuous integration and delivery pipeline ...es/azure-app-configuration/integrate-ci-cd-pipeline.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows command prompt and PowerShell instructions before macOS and Linux equivalents, and by referencing Windows-specific tools and patterns (e.g., Visual Studio Code as 'available on Windows, macOS, and Linux' but with a subtle Windows-first tone). The example project is based on ASP.NET Core, which is cross-platform, but the build instructions and environment variable setup are presented in a way that prioritizes Windows users. There is also a reliance on MSBuild and .csproj scripting, which are more familiar to Windows developers.
Recommendations
  • Present Linux and macOS instructions before or alongside Windows instructions, rather than after.
  • Include bash/zsh examples for scripting and environment variable setup, and highlight cross-platform compatibility.
  • Mention cross-platform editors and tools (e.g., VS Code, JetBrains Rider) equally, without a Windows-first tone.
  • Clarify that MSBuild and .csproj scripting can be used on Linux and macOS with .NET Core SDK.
  • Add explicit notes or sections for CI/CD pipelines commonly used on Linux (e.g., GitHub Actions, Jenkins) in addition to Azure DevOps.
  • Ensure all code snippets and commands are tested and presented for all supported platforms.
GitHub Create Pull Request
Azure App Configuration Use variant feature flags in a Python application ...pp-configuration/howto-variant-feature-flags-python.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways: Windows setup instructions and links are given first in the prerequisites, virtual environment activation is shown only with the Windows path, and environment variable setup provides detailed Windows Command Prompt and PowerShell instructions before mentioning the Linux/macOS alternative. There are no Linux-specific examples for virtual environment activation or other common Linux workflows, and no parity in tool recommendations or troubleshooting for non-Windows platforms.
Recommendations
  • Provide Linux/macOS instructions alongside Windows instructions, not after them, and ensure equal detail.
  • Include the Linux/macOS command for activating a Python virtual environment (e.g., `source venv/bin/activate`).
  • Link to Python installation documentation for Linux/macOS, not just Windows.
  • When listing environment variable setup, present all platforms together or alternate the order to avoid Windows-first bias.
  • Add troubleshooting notes or tips for common Linux/macOS issues (e.g., permissions, package managers).
  • Review all code snippets and instructions to ensure they are platform-agnostic or provide alternatives for each major OS.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with Azure Functions | Microsoft Docs ...app-configuration/quickstart-azure-functions-csharp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ visual_studio_only ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and workflows. Visual Studio is the only development environment mentioned, and instructions for creating and running the function app are centered on Visual Studio. Environment variable setup lists Windows command prompt and PowerShell before Linux/macOS, and screenshots and debugging steps are Visual Studio-specific. There is no mention of cross-platform editors (e.g., VS Code) or Linux-native development workflows, nor are there CLI-based alternatives for creating and running the function app.
Recommendations
  • Add instructions for creating and running Azure Functions apps using cross-platform tools such as Visual Studio Code and Azure Functions Core Tools CLI.
  • Provide Linux/macOS examples and workflows alongside Windows instructions, including screenshots and step-by-step guides.
  • List environment variable setup commands for Linux/macOS before or alongside Windows commands to avoid ordering bias.
  • Include references to platform-agnostic development environments and clarify that Azure Functions development is supported on Linux/macOS.
  • Offer guidance for users who do not use Visual Studio, such as how to debug and run locally using CLI tools.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with .NET Framework ...icles/azure-app-configuration/quickstart-dotnet-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and workflows. Visual Studio (Windows-only) is the sole IDE mentioned, and all project creation steps assume its use. Environment variable instructions list Windows Command Prompt and PowerShell before Linux/macOS, and use setx (Windows-specific) as the primary example. There are no Linux-specific development environment instructions, nor any mention of cross-platform .NET development tools (e.g., VS Code, JetBrains Rider, or CLI-only workflows). The configuration file examples and build/run instructions are tailored to Windows conventions, with no guidance for Linux users on compiling or running .NET Framework apps.
Recommendations
  • Include instructions for creating and running the app using cross-platform tools such as Visual Studio Code or JetBrains Rider, and .NET CLI where possible.
  • Provide Linux/macOS-specific steps for project setup, environment variable management, and running the application, including terminal commands and any required dependencies.
  • List Linux/macOS commands before or alongside Windows commands to avoid implicit prioritization.
  • Clarify that .NET Framework is Windows-only, and suggest .NET Core/.NET 6+ for cross-platform scenarios, with links to equivalent quickstarts.
  • Add troubleshooting notes for Linux/macOS users, especially regarding environment variables and compatibility.
GitHub Create Pull Request
Azure App Configuration Quickstart for Adding Feature Flags to .NET/.NET Framework Apps ...re-app-configuration/quickstart-feature-flag-dotnet.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing environment variable setup instructions for Windows tools (Command Prompt and PowerShell), referencing Visual Studio as the only IDE, and showing screenshots from Windows Command Prompt. There are no examples or instructions for Linux or macOS users (e.g., Bash, zsh, VS Code, or cross-platform .NET CLI usage). This may hinder Linux developers from following the quickstart without additional research.
Recommendations
  • Add equivalent Linux/macOS instructions for setting environment variables (e.g., export Endpoint="..." in Bash/zsh).
  • Include cross-platform IDE options such as Visual Studio Code and .NET CLI commands for project creation and running.
  • Provide screenshots or terminal output examples from Linux/macOS environments.
  • Explicitly mention that the quickstart applies to non-Windows platforms and provide guidance for those users.
  • Where PowerShell is referenced, also provide Bash/zsh equivalents.
  • Consider a 'platform tabs' approach for steps that differ between Windows, Linux, and macOS.
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to Azure Functions | Microsoft Docs ...tion/quickstart-feature-flag-azure-functions-csharp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ visual_studio_only ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and workflows. Visual Studio is listed as the only required IDE, with no mention of cross-platform alternatives like VS Code. Environment variable instructions are given first for Windows Command Prompt and PowerShell, with Linux/macOS examples listed last. The local testing workflow is tightly coupled to Visual Studio, which is primarily a Windows tool, and there are no instructions for running or debugging the function app on Linux (e.g., via Azure Functions Core Tools CLI or VS Code).
Recommendations
  • Add instructions for using VS Code or other cross-platform editors to create and debug Azure Functions apps.
  • Provide parity in environment variable setup instructions, listing Linux/macOS commands before or alongside Windows commands.
  • Include steps for running and debugging the function locally using Azure Functions Core Tools CLI on Linux/macOS.
  • Clarify that Visual Studio is optional and provide alternative workflows for non-Windows users.
  • Ensure screenshots and examples reflect cross-platform usage, not just Visual Studio on Windows.
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to Python with Azure App Configuration ...re-app-configuration/quickstart-feature-flag-python.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific instructions (Windows command prompt and PowerShell) are presented before macOS and Linux equivalents, with more detailed guidance and validation steps for Windows users. The prerequisite section links to Windows Python setup documentation first, and Windows environment variable tools (setx, PowerShell) are described in greater detail than their Unix counterparts. Linux and macOS instructions are present but appear after Windows and are less emphasized.
Recommendations
  • Present OS instructions in parallel tabs or in a neutral order (e.g., alphabetical: Linux, macOS, Windows) rather than Windows-first.
  • Provide equal detail and validation steps for Linux/macOS as for Windows, including how to check environment variable persistence.
  • Include links to Linux and macOS Python setup documentation in the prerequisites section alongside the Windows link.
  • Avoid using Windows-specific tools (e.g., setx) without mentioning Unix equivalents (e.g., export in .bashrc/.zshrc for persistence).
  • Ensure screenshots and examples do not implicitly favor Windows environments.
  • Explicitly state cross-platform compatibility and highlight any OS-specific caveats.
GitHub Create Pull Request
Azure App Configuration Create an Azure App Configuration store by using Azure Resource Manager template (ARM template) ...azure-app-configuration/quickstart-resource-manager.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides deployment instructions using PowerShell cmdlets only, which are primarily associated with Windows environments. There are no examples or guidance for deploying the ARM template using Azure CLI, Bash, or other cross-platform tools. The PowerShell example is given as the sole command-line option, and no Linux/macOS-specific instructions or parity are present.
Recommendations
  • Add equivalent Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Clearly mention that both PowerShell and Azure CLI can be used, and provide links to relevant Azure CLI documentation.
  • Consider including Bash script snippets or instructions for users on Linux/macOS.
  • Ensure that references to command-line tools do not assume a Windows environment by default.
GitHub Create Pull Request
Azure App Configuration Azure App Configuration REST API - Microsoft Entra authorization ...e-app-configuration/rest-api-authorization-azure-ad.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation mentions Azure CLI, PowerShell, and the Azure portal as tools for managing role assignments, listing PowerShell before Linux-native alternatives and referencing the portal (which is platform-agnostic but often associated with Windows environments). There are no explicit Linux or bash examples, nor is there mention of Linux-specific tools or patterns. The lack of Linux command-line examples and the ordering of tools suggest a Windows-first and PowerShell-heavy bias.
Recommendations
  • Provide explicit bash/Linux shell examples for managing role assignments using Azure CLI.
  • List Azure CLI (cross-platform) before PowerShell when mentioning command-line tools.
  • Include references or links to Linux-specific documentation or usage patterns.
  • Clarify that Azure CLI is available and supported on Linux, macOS, and Windows.
  • Add examples showing role assignment management from a Linux environment.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app | Microsoft Docs ...-configuration/use-key-vault-references-spring-boot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-specific instructions and tools (such as setx and PowerShell) are presented before their Linux/macOS equivalents. The environment variable setup section gives Windows Command Prompt and PowerShell examples first, with Linux/macOS instructions following. The use of Windows-centric tools and patterns (setx, PowerShell) is emphasized, while Linux alternatives are less detailed. Screenshots and portal instructions are platform-neutral, but command-line and environment setup favor Windows.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
  • Provide more detailed Linux/macOS instructions, including shell-specific notes (e.g., bash, zsh) and persistence of environment variables.
  • Avoid using Windows-specific tools (like setx) without mentioning cross-platform alternatives (e.g., editing ~/.bashrc or ~/.profile for Linux/macOS).
  • Where possible, use platform-neutral commands and highlight cross-platform editors and tools.
  • Consider adding a table or section summarizing environment variable setup for all major platforms.
GitHub Create Pull Request
Azure Cache For Redis How to configure Azure Cache for Redis ...main/articles/azure-cache-for-redis/cache-configure.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily by referencing PowerShell as the example for configuring the 'databases' setting during cache creation, without providing equivalent Linux (bash/Azure CLI) examples. PowerShell is mentioned first and exclusively in the relevant configuration section, and there is no parity for Linux users in terms of step-by-step instructions or code samples. Additionally, the 'Export template' section references PowerShell for deployment, again without Linux alternatives.
Recommendations
  • Provide Azure CLI (bash) examples alongside PowerShell for all configuration tasks, especially for cache creation and setting 'databases'.
  • Ensure that both Windows and Linux tools are mentioned together, or Linux tools are mentioned first in sections relevant to cross-platform users.
  • Add explicit instructions and code samples for Linux users (using Azure CLI) wherever PowerShell is referenced.
  • Review all sections for tool parity and update references to avoid assuming a Windows environment.
  • Include notes or links to platform-specific guides for both Windows and Linux users.
GitHub Create Pull Request
Azure Cache For Redis Configure active geo-replication for Enterprise Azure Cache for Redis instances ...cache-for-redis/cache-how-to-active-geo-replication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring active geo-replication, but the PowerShell examples are given equal prominence and detail as the CLI examples. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The use of PowerShell, which is traditionally associated with Windows, may imply a Windows-centric approach. Additionally, there are no explicit Linux tool references or guidance for Linux users, and the CLI examples do not clarify cross-platform compatibility.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
  • Add notes or sections for Linux/macOS users, including any environment-specific considerations (e.g., authentication, path formats, installation steps).
  • If PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash scripts for Linux users.
  • Ensure screenshots and UI references do not assume Windows-only environments (e.g., avoid showing only Windows-style paths or UI elements).
  • Where possible, include troubleshooting or tips for Linux users, such as common permission issues or differences in shell behavior.
GitHub Create Pull Request
Azure Cache For Redis Best practices for scaling ...es/azure-cache-for-redis/cache-best-practices-scale.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by mentioning PowerShell cmdlets as a primary method for programmatic scaling, listing PowerShell before Azure CLI and REST API, and not providing explicit Linux or Bash examples. There is no mention of Linux-specific tools or shell commands, and PowerShell is referenced multiple times without parity for Linux users.
Recommendations
  • Provide explicit Bash/Azure CLI examples for scaling operations alongside PowerShell examples.
  • List cross-platform tools (Azure CLI, REST API) before platform-specific ones like PowerShell.
  • Clarify that Azure CLI and REST API are fully supported on Linux and macOS, and provide links or examples for those environments.
  • Avoid implying PowerShell is the default or preferred method; present all options equally.
  • Add a section or note highlighting Linux/macOS usage patterns for scaling Azure Cache for Redis.
GitHub Create Pull Request
Azure Cache For Redis Data persistence ...re-cache-for-redis/cache-how-to-premium-persistence.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and examples for configuring Redis persistence, with PowerShell mentioned before Azure CLI in both prerequisites and setup sections. There are no Linux-specific examples, nor are Linux-native tools or shell scripts referenced. The CLI instructions are present, but the overall pattern and language favor Windows and PowerShell environments, and there is no mention of Linux-specific considerations or parity.
Recommendations
  • Add explicit Linux shell script examples for common persistence operations (e.g., using Bash with az CLI).
  • Include instructions for installing and using Azure CLI on Linux, and clarify that all CLI commands work cross-platform.
  • Reorder sections to present Azure CLI before PowerShell to avoid implicit prioritization of Windows tools.
  • Mention Linux-native environments (e.g., Ubuntu, CentOS) in prerequisites and examples.
  • Provide troubleshooting tips or notes for Linux users, such as file permissions or environment variables that may differ from Windows.
  • Clarify that Azure CLI and portal instructions are platform-agnostic, and highlight any differences if they exist.
GitHub Create Pull Request
Azure Cache For Redis Configure a virtual network - Premium-tier Azure Cache for Redis instance ...les/azure-cache-for-redis/cache-how-to-premium-vnet.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias in its example for verifying cache connectivity, where only the Windows-specific 'tcping.exe' tool is mentioned and demonstrated. No Linux equivalent (such as 'tcping' for Linux, 'nc', or 'telnet') is provided, nor is there any mention of how to perform the same operation on Linux or macOS systems. The documentation also refers to a sample client application without specifying cross-platform instructions, and generally omits Linux-specific tools or patterns.
Recommendations
  • Provide Linux and macOS equivalents for all command-line examples, such as using 'tcping', 'nc', or 'telnet' for port checks.
  • Explicitly mention cross-platform tools and usage patterns, ensuring parity in instructions for both Windows and Linux environments.
  • Include sample commands and troubleshooting steps for Linux shells (bash/zsh) alongside Windows/PowerShell examples.
  • When referencing downloadable tools, link to both Windows and Linux versions, or suggest installation via package managers (e.g., 'apt', 'yum', 'brew').
  • Clarify that client applications and connectivity tests can be performed from any supported OS, and provide guidance for each.
GitHub Create Pull Request
Azure Cache For Redis Migrate to Azure Cache for Redis ...rticles/azure-cache-for-redis/cache-migration-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (AzCopy, PowerShell cmdlets) for critical migration steps without providing equivalent Linux or cross-platform alternatives. Examples and tool mentions prioritize Windows environments, and there are no explicit Linux command-line or Bash examples for key operations such as uploading RDB files or automating import/export. This may hinder Linux users or those working in non-Windows environments.
Recommendations
  • For every mention of AzCopy, include equivalent Linux command-line instructions (e.g., using AzCopy on Linux, Azure CLI, or other cross-platform tools).
  • When referencing PowerShell cmdlets (Import-AzRedisCache, Export-AzRedisCache), provide Azure CLI equivalents or REST API examples for Linux/macOS users.
  • Explicitly state that AzCopy and Azure CLI are cross-platform, and provide installation/use instructions for Linux.
  • Add Bash or shell script examples for common migration tasks, such as uploading RDB files to Azure Storage and triggering imports.
  • Ensure that all migration steps are described in a platform-neutral way, or provide parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
Azure Cache For Redis What is Azure Cache for Redis? .../main/articles/azure-cache-for-redis/cache-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing ASP.NET and the Redis Output Cache Provider (Windows/.NET technologies) as the primary example for content caching, without mentioning equivalent Linux or cross-platform frameworks. The related content section lists .NET Framework and .NET Core guides before Node.js, Java, and Python, suggesting a Windows-first approach. There are no explicit Linux-specific examples, tools, or patterns mentioned, nor is there guidance for Linux-based deployment or integration.
Recommendations
  • Include examples for popular Linux-based web frameworks (e.g., Django, Flask, Express.js) in the content caching section.
  • Mention cross-platform or Linux-specific Redis integration patterns and tools alongside Windows/.NET examples.
  • Reorder or balance the related content section to give equal prominence to Linux-friendly languages and frameworks.
  • Add guidance or links for deploying and using Azure Cache for Redis from Linux environments, including CLI usage and integration with Linux-based applications.
GitHub Create Pull Request
Azure Cache For Redis Use redis-cli ...s/azure-cache-for-redis/cache-how-to-redis-cli-tool.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows is mentioned frequently, including instructions to use WSL and Windows Terminal, and references to Azure PowerShell are given equal prominence to Azure CLI. The guidance for Windows users is detailed, while Linux instructions are straightforward. The retrieval of cache keys lists Azure CLI and PowerShell together, but PowerShell is a Windows-centric tool. There is no explicit omission of Linux examples, but Windows-specific tools and patterns are highlighted.
Recommendations
  • Present Linux and macOS instructions before Windows, or in parallel, to avoid 'windows_first' ordering.
  • Emphasize native Linux usage rather than suggesting WSL as the primary method for Windows users.
  • Provide more parity in tooling examples, such as focusing on Azure CLI (cross-platform) before PowerShell (Windows-centric).
  • Clarify that redis-cli is natively available on Linux and macOS, and that Windows users can use WSL as an alternative, but not as the only recommended method.
  • Ensure that all examples and troubleshooting steps are shown for both Linux and Windows environments, where applicable.
GitHub Create Pull Request
Azure Cache For Redis Azure Cache for Redis with Azure Private Link ...n/articles/azure-cache-for-redis/cache-private-link.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. All step-by-step instructions for resource creation and management are based on the Azure portal UI, which is most commonly used on Windows. The scripting examples are provided first in Azure PowerShell, a Windows-centric tool, and only subsequently in Azure CLI, which is cross-platform. There are no explicit Linux shell or Bash examples, nor any mention of Linux-specific tools or workflows. The documentation does not address Linux users directly or provide parity in command-line instructions (e.g., Bash, shell scripts, or Linux desktop screenshots).
Recommendations
  • Provide Bash or shell script examples for key operations (e.g., using curl for REST API calls, or using Azure CLI in Bash).
  • Add explicit notes or sections for Linux users, including any platform-specific considerations (such as DNS resolution, firewall configuration, or package installation).
  • Include screenshots or instructions that are platform-neutral or show both Windows and Linux environments.
  • List Azure CLI examples before PowerShell, or present them side-by-side to emphasize cross-platform parity.
  • Reference Linux tools (e.g., nslookup, dig, curl) in troubleshooting and verification steps, not just generic commands.
  • Clarify that Azure CLI is available on Windows, Linux, and macOS, and provide installation links for all platforms.
GitHub Create Pull Request
Azure Cache For Redis Troubleshoot connectivity ...ure-cache-for-redis/cache-troubleshoot-connectivity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias in the 'Test connectivity' section by recommending the use of PSPING in Azure PowerShell to test connectivity, without providing a Linux equivalent or mentioning Linux tools. Windows tooling is presented first and exclusively, while Linux users are left without guidance for similar troubleshooting steps. Although Linux is referenced elsewhere (e.g., TCP settings), actionable troubleshooting examples and commands are Windows-centric.
Recommendations
  • Provide Linux equivalents for connectivity testing, such as using 'nc' (netcat), 'telnet', or 'redis-cli' with appropriate flags.
  • Present both Windows and Linux troubleshooting commands side-by-side, or at least mention Linux tools before or alongside Windows tools.
  • Explicitly state which commands are platform-specific and offer alternatives for each major OS.
  • Expand the 'Test connectivity' section to include example commands for Linux/macOS users, e.g., 'nc <cachename> <port>' or 'telnet <cachename> <port>'.
  • Review other troubleshooting steps to ensure Linux parity in actionable guidance.
GitHub Create Pull Request
Azure Cache For Redis Redis version 4 retirement ...ticles/azure-cache-for-redis/cache-retired-features.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation mentions PowerShell as a method to trigger the Redis upgrade process, but does not provide equivalent Linux-specific examples (e.g., Bash, shell scripting) or mention Linux tools explicitly. The order of tools listed (REST API, Azure CLI, PowerShell) is neutral, but the lack of Linux command-line examples and the explicit mention of PowerShell suggest a Windows bias. There are no examples or instructions for Linux users, and the documentation does not reference Linux-specific workflows or tools.
Recommendations
  • Add explicit Bash or shell command examples for Linux users alongside PowerShell examples.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
  • Mention Linux tools and workflows where relevant, such as using curl for REST API calls.
  • Ensure that instructions and screenshots are inclusive of both Windows and Linux environments.
GitHub Create Pull Request
Azure Cache For Redis Migrate from VNet injection caches to Private Link caches ...articles/azure-cache-for-redis/cache-vnet-migration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page exhibits mild Windows bias. PowerShell cmdlets are mentioned as primary methods for exporting and importing RDB files, with no equivalent Linux CLI or Azure CLI examples provided. AzCopy is referenced for file transfer, which, while cross-platform, is often associated with Windows usage. The order of examples and tooling references tends to prioritize Windows-centric approaches, with no explicit mention of Linux workflows or commands.
Recommendations
  • Add Azure CLI examples for exporting and importing Redis cache data, alongside PowerShell.
  • Explicitly mention and provide Linux shell command equivalents (e.g., using curl, scp, or Azure CLI) for file operations.
  • Clarify that AzCopy is cross-platform and provide usage examples for both Windows and Linux.
  • Ensure that migration instructions do not assume a Windows environment; include steps for Linux users (e.g., bash scripting, Linux VM setup).
  • Balance references to PowerShell with Bash/Azure CLI examples throughout the documentation.
GitHub Create Pull Request
Azure Change Tracking Inventory Azure Change Tracking Extension Version Details and Known Issues ...change-tracking-inventory/extension-version-details.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page shows a Windows bias in several ways: Windows-specific features (e.g., registry, environment variables, Knowledge Base IDs) are highlighted, with Linux equivalents either missing or less detailed. Windows issues and workarounds (such as using KQL functions for Base64 decoding) are described, but Linux-specific troubleshooting is sparse. Windows recommendations (such as upgrading AMA versions) are given, while Linux guidance is less frequent or absent. Some extension updates only mention Windows improvements, with 'None' for Linux.
Recommendations
  • Provide Linux-specific examples and troubleshooting steps where Windows ones are given (e.g., environment variables, file path handling, Base64 decoding).
  • Highlight Linux features and improvements with equal detail as Windows, including guidance for Linux-specific extension upgrades and known issues.
  • Add parity for Linux tools and patterns (e.g., mention Linux equivalents to Windows registry, environment variables, and Knowledge Base IDs).
  • Ensure that recommendations and workarounds are provided for both platforms, not just Windows.
  • When listing OS-specific notes, avoid 'None' for Linux unless truly not applicable, and strive to provide meaningful Linux content.
GitHub Create Pull Request
Azure Change Tracking Inventory Azure Change Tracking and Inventory Overview by Using Azure Monitor Agent ...change-tracking-inventory/overview-monitoring-agent.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed examples and tables exclusively for Windows registry keys, mentioning Windows services and tools (e.g., registry, Internet Explorer, explorer.exe) without Linux equivalents, and omitting Linux-specific configuration or monitoring examples (such as Linux daemons, config files, or package managers). While the overview mentions Linux compatibility, practical examples and guidance are focused on Windows.
Recommendations
  • Add equivalent Linux examples, such as monitoring changes to important Linux configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config) and Linux daemons (systemd services).
  • Include tables or lists of commonly tracked Linux files, directories, and services, similar to the Windows registry key table.
  • Provide step-by-step instructions or screenshots for enabling and configuring Change Tracking and Inventory on Linux systems, not just Windows.
  • Mention Linux-specific tools and patterns (e.g., systemd, cron, package managers like apt/yum) where relevant.
  • Ensure parity in troubleshooting and advanced configuration sections for both Windows and Linux environments.
GitHub Create Pull Request
Azure Change Tracking Inventory Enable Change Tracking and Inventory at Scale for Azure VMs by Using Azure Policy ...ng-inventory/enable-change-tracking-at-scale-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias. Windows-specific features (Registry, Files, Software) are listed before Linux equivalents, and screenshots and examples focus on generic VM selection without showing Linux-specific configuration or file types. The policy names and extension configuration steps mention Windows before Linux, and there are no explicit Linux command-line or configuration examples. Windows tools and patterns (such as Registry and Software tracking) are highlighted, while Linux equivalents (such as package inventory or config file tracking) are not described in detail.
Recommendations
  • Provide explicit Linux examples, such as tracking package inventory or configuration files, and show relevant screenshots.
  • Include Linux-specific terminology and tools (e.g., apt, yum, config files) alongside Windows Registry and Software.
  • Alternate the order of Windows and Linux mentions to avoid Windows-first bias.
  • Add command-line examples for Linux (bash, shell scripts) where appropriate, not just portal-based instructions.
  • Clarify Linux support for each feature, especially where Windows-only features (like Registry tracking) are mentioned.
GitHub Create Pull Request
Azure Change Tracking Inventory Quickstart: Enable Azure Change Tracking and Inventory for Single and Multiple Machines from the Portal ...nges-collect-inventory-azure-change-tracking-inventory.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows VMs and Windows-specific features (such as Windows Registry and Windows Software) before Linux equivalents. The prerequisites link only to Windows VM creation, omitting Linux VM setup. Throughout the portal instructions, examples and screenshots focus on generic VM selection without clarifying Linux-specific steps or differences. Only in the CLI section are Linux and Windows commands presented side-by-side, but the overall flow and feature emphasis are Windows-centric.
Recommendations
  • Add explicit links and instructions for creating Linux VMs in the prerequisites section, alongside Windows VM setup.
  • Ensure examples and screenshots throughout the portal instructions clarify any Linux-specific steps, UI differences, or considerations.
  • Balance feature descriptions to highlight Linux capabilities (e.g., Linux file tracking) equally with Windows features (e.g., registry tracking).
  • Where Windows-specific terminology is used (e.g., Registry, Software), provide parallel Linux concepts (e.g., configuration files, installed packages) and examples.
  • Review the order of presentation so that Linux is not consistently mentioned after Windows, but rather in parallel or alternating order.
GitHub Create Pull Request
Azure Compute Fleet Create an Azure Compute Fleet using Azure portal ...ticles/azure-compute-fleet/quickstart-create-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. The password requirements link references Windows documentation first, and password complexity rules are described in detail, while SSH key guidance for Linux is brief and refers to a separate page. There are no concrete Linux-specific examples or screenshots, and Windows terminology (e.g., password complexity) is foregrounded over Linux SSH key usage. Linux images are mentioned, but the workflow and examples are not equally detailed for Linux users.
Recommendations
  • Provide equal detail for Linux workflows, including step-by-step SSH key generation and usage directly in the page.
  • Reference both Windows and Linux documentation for password and SSH requirements, not just Windows.
  • Include screenshots or examples showing both Windows and Linux image selection and administrator account setup.
  • Clarify parity in supported features and options for both OS types throughout the guide.
  • Avoid linking only to Windows documentation for generic requirements; link to OS-agnostic or Linux-specific resources as appropriate.
GitHub Create Pull Request
Azure Change Tracking Inventory Tutorial: Change a Workspace and Configure Data Collection Rules ...torial-change-workspace-configure-data-collection-rule.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ windows_registry_heavy
Summary
The documentation provides parity between Windows and Linux in the file tracking sections, with separate tabs and tables for each. However, Windows concepts (such as Windows Registry and Windows environment variables) are given dedicated sections and examples, while Linux equivalents (such as tracking configuration files or directories) are not discussed in as much detail. Windows-specific tools and patterns (e.g., registry, environment variables like %winDir%) are mentioned, but Linux-specific tools or patterns (such as environment variables, symlinks, or common config file locations) are missing. The order of presentation often places Windows first, and the registry section is Windows-only with no Linux equivalent discussed.
Recommendations
  • Add Linux-specific examples for environment variables (e.g., $HOME, $PATH) in the Linux file tracking section.
  • Discuss Linux equivalents to Windows Registry, such as tracking changes in configuration files under /etc or using dconf/gsettings for desktop environments.
  • Ensure Linux tabs/examples are presented with equal prominence and detail as Windows, including screenshots if possible.
  • Where Windows-specific concepts are discussed (e.g., registry), add a note or section about how similar use cases are handled on Linux.
  • Consider alternating the order of Windows and Linux examples or presenting them side-by-side for better parity.
GitHub Create Pull Request
Azure Fluid Relay Customer-managed keys for Azure Fluid Relay encryption ...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided and referenced before Azure CLI, and prerequisite links and instructions (e.g., managed identity tutorial) point to Windows-centric resources. Azure PowerShell (a Windows-first tool) is given equal or greater prominence than Azure CLI, and there are no explicit Linux shell or scripting examples. The documentation does not mention Linux-specific patterns, nor does it clarify cross-platform compatibility for CLI or REST instructions.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Ensure prerequisite tutorials and links include Linux and cross-platform instructions (e.g., managed identity setup for Linux VMs).
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and highlight any platform-specific considerations.
  • Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add notes or sections on using REST API and CLI from Linux environments, including authentication and environment setup.
  • Review all referenced tutorials and ensure Linux parity in their content.
GitHub Create Pull Request
Azure Functions Bring dependencies and third-party libraries to Azure Functions ...icles/azure-functions/bring-dependency-to-functions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias in several ways: Java examples use Windows-style paths and reference ffmpeg.exe, with no mention of Linux equivalents or cross-platform considerations. The Java section instructs users to use a Windows-specific executable and path format, and does not provide Linux alternatives or guidance. PowerShell is mentioned as an upload option for Azure Files, but Linux-native tools (e.g., scp, rsync) are not referenced. The Python section does mention chmod for Linux, but overall, Windows tools and patterns are presented first or exclusively, especially in Java examples.
Recommendations
  • Provide Linux-specific examples for Java, including use of ffmpeg (not ffmpeg.exe) and Linux-style paths.
  • Explicitly mention cross-platform considerations in all code samples, such as path separators and executable file extensions.
  • Include Linux-native upload tools (e.g., scp, rsync, sftp) as alternatives to PowerShell for uploading files to Azure Files.
  • Add notes or code samples showing how to set executable permissions on Linux for Java (e.g., using chmod in deployment scripts).
  • Ensure that documentation sections do not assume Windows as the default environment, and present Linux options equally or first where appropriate.
GitHub Create Pull Request
Azure Functions Configure monitoring for Azure Functions .../main/articles/azure-functions/configure-monitoring.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates moderate Windows bias. Command-line examples for overriding monitoring configuration are provided for both Azure CLI and PowerShell, but PowerShell is featured as a primary scripting option, which is Windows-specific. There is no mention of Linux shell equivalents (e.g., Bash), and PowerShell is presented before any Linux alternatives. Additionally, references to Visual Studio and Windows-centric tooling appear without equal emphasis on Linux-native tools or workflows. While Azure CLI is cross-platform, the lack of explicit Bash or Linux shell examples and the prioritization of PowerShell and Visual Studio contribute to a Windows-first orientation.
Recommendations
  • Add Bash shell examples alongside PowerShell for all command-line instructions, especially for overriding app settings.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample Bash syntax (e.g., export, az commands) where appropriate.
  • Include references to Linux-native editors (e.g., VS Code on Linux, vim, nano) and workflows in sections discussing Visual Studio or Windows-centric tools.
  • Ensure that instructions for managing app settings in the Azure portal clarify any Linux-specific caveats (such as the note about periods in app settings on Linux plans), and provide alternative Linux-friendly approaches.
  • Where PowerShell is used, clarify its availability on Linux and macOS, or offer alternative shell scripting examples.
GitHub Create Pull Request
Azure Functions Build a scalable web API using Azure Functions ...functions/create-first-function-azure-developer-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides examples and instructions for multiple programming languages and platforms, but there is a noticeable Windows bias in several areas. Windows-specific command shells (Cmd, PowerShell) are given dedicated sections, sometimes before Linux equivalents. PowerShell is treated as a first-class language option, and Windows command patterns (e.g., .venv\scripts\activate, for /f loops) are included. Linux instructions are present, but Windows tools and patterns are often mentioned first or with more detail.
Recommendations
  • Ensure Linux/macOS instructions are presented before or alongside Windows instructions, especially in tabbed command sections.
  • Provide parity in shell examples: include bash/zsh instructions for all relevant commands, not just Python virtual environments.
  • Avoid Windows-centric terminology like 'command prompt' as the default; use 'terminal' or clarify both.
  • For PowerShell, clarify cross-platform usage and provide equivalent bash/zsh scripts where possible.
  • Review all code and command examples to ensure Linux users are not required to infer or adapt Windows-specific instructions.
  • Explicitly mention platform compatibility for tools like Azure Developer CLI and Azure Functions Core Tools, and link to platform-specific installation guides.
GitHub Create Pull Request
Azure Functions How to disable functions in Azure Functions ...blob/main/articles/azure-functions/disable-function.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation presents Windows-centric tools and workflows (Azure PowerShell, portal UI) before or alongside cross-platform options (Azure CLI), with PowerShell examples given equal prominence to CLI. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The only explicit Linux consideration is a limitation note, not a parity feature or example.
Recommendations
  • Add explicit Bash or shell examples for Linux users, especially for Azure CLI commands.
  • Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Reorder examples to present Azure CLI before PowerShell, or group them by platform.
  • Include notes or examples for managing app settings using Linux-native tools or scripts.
  • Address Linux-specific workflows, such as using environment variables or configuration files in Linux deployments.
  • Expand the 'Considerations' section to include best practices and caveats for Linux environments, not just limitations.
GitHub Create Pull Request
Azure Functions Bindings for Durable Functions - Azure .../azure-functions/durable/durable-functions-bindings.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides extensive PowerShell examples and references to Windows-specific tools and configuration patterns (such as function.json and run.ps1), especially in the PowerShell sections. These examples and configuration instructions are tailored to Windows environments and do not mention Linux alternatives or cross-platform considerations. The documentation also introduces PowerShell before Python in some places and does not clarify platform differences, which may implicitly prioritize Windows usage.
Recommendations
  • Add explicit notes about PowerShell support on Linux and provide bash or shell script equivalents where possible.
  • Clarify that function.json and run.ps1 patterns are not exclusive to Windows and describe how to use them on Linux/macOS.
  • Include cross-platform CLI examples (e.g., Azure CLI, bash) alongside PowerShell for orchestration and activity triggers.
  • Ensure that examples and configuration instructions do not assume a Windows environment and mention any platform-specific limitations.
  • Where PowerShell is used, add links or references to Linux-compatible shells and scripting approaches for Azure Functions.
GitHub Create Pull Request
Azure Functions Durable Functions best practices and diagnostic tools ...s/durable/durable-functions-best-practice-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-centric tools and patterns, such as PowerShell and Visual Studio, more prominently than Linux alternatives. Examples include listing PowerShell as a primary language for concurrency tuning, referencing Visual Studio and Visual Studio Code for Roslyn Analyzer usage, and mentioning Application Insights (which is often used in Windows-centric environments) without highlighting Linux-friendly diagnostic alternatives. There are no explicit Linux examples or mentions of Linux-specific tools, and Windows tools are often listed before or instead of Linux equivalents.
Recommendations
  • Provide explicit Linux examples for diagnostic and development workflows, such as using Bash or Linux-native editors (e.g., Vim, Emacs) for code analysis.
  • Mention cross-platform alternatives to PowerShell, such as Bash scripts, when discussing performance and concurrency settings.
  • Reference Linux-compatible monitoring and logging tools (e.g., Azure CLI, Kusto queries from Linux terminals) alongside Application Insights.
  • Clarify that Visual Studio Code is cross-platform and suggest Linux installation instructions or alternatives for Roslyn Analyzer usage.
  • Add links or notes about using Durable Functions on Linux-based Azure Function hosts, including any platform-specific considerations.
GitHub Create Pull Request
Azure Functions Configure Durable Functions app with managed identity ...urable/durable-functions-configure-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and workflows (such as Visual Studio, Visual Studio Code, and Azure CLI) exclusively or first, without mentioning Linux equivalents or providing Linux-specific instructions. The local development section assumes use of Microsoft developer tools and does not address Linux authentication contexts or alternative editors. There are no explicit Linux examples or instructions for configuring Durable Functions with managed identity on Linux environments.
Recommendations
  • Include explicit instructions and examples for Linux environments, such as authentication via Linux shell, use of open-source editors (e.g., VS Code on Linux, Vim), and Linux-specific Azure CLI usage.
  • Mention Linux developer credential sources (e.g., Azure CLI on Linux, environment variables, service principals) alongside Windows/Visual Studio contexts.
  • Provide screenshots and walkthroughs using Linux terminals and file systems where appropriate.
  • Clarify that Azurite and Durable Functions are cross-platform, and provide setup instructions for Linux and macOS.
  • Add a note or section on differences or considerations when developing and deploying from Linux systems.
GitHub Create Pull Request
Azure Functions Durable Functions publishing to Azure Event Grid ...unctions/durable/durable-functions-event-publishing.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows evidence of Windows bias primarily through references to Windows-specific tools (such as the Storage Emulator), and by mentioning Windows-centric options (PowerShell, Storage Emulator) before or instead of Linux equivalents. There are no explicit Linux or cross-platform alternatives provided for the Storage Emulator, and PowerShell is referenced as an alternative to Azure CLI without any mention of Bash or Linux shell scripting. The instructions for local development and debugging assume the use of the Storage Emulator, which is only available on Windows, and do not mention Azurite's cross-platform capabilities or provide Linux setup instructions.
Recommendations
  • Replace references to the Storage Emulator with Azurite, and provide explicit instructions for installing and running Azurite on Linux and macOS.
  • When mentioning PowerShell, also mention Bash or other Linux-native scripting options, and provide equivalent examples if relevant.
  • Ensure all CLI examples are explicitly cross-platform (e.g., Azure CLI), and clarify that they work on Linux, macOS, and Windows.
  • Add a section or callout for Linux/macOS users, including any differences in setup, especially for local development and storage emulation.
  • Review screenshots and UI instructions to ensure they are not Windows-specific, or provide alternatives for Linux/macOS users where applicable.
GitHub Create Pull Request
Azure Functions Orchestration versioning in Durable Functions - Azure .../durable/durable-functions-orchestration-versioning.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides language-specific examples, including PowerShell, which is primarily a Windows-centric technology. PowerShell examples are given equal prominence alongside Linux-friendly languages (Python, JavaScript), and PowerShell-specific SDKs and patterns are mentioned throughout. There are no explicit Linux shell (bash, sh) examples or references to Linux-native tools or deployment patterns. The documentation assumes PowerShell as the default shell for scripting, which may disadvantage Linux users who commonly use bash/zsh. Additionally, Windows/PowerShell terminology and tooling are referenced before or instead of Linux equivalents (e.g., no bash example for orchestration triggers or activity calls).
Recommendations
  • Add bash or shell script examples for orchestration triggers and activity calls, especially in sections where PowerShell is demonstrated.
  • Include references to Linux-native tools and deployment patterns (e.g., Azure CLI usage from bash, Linux service management).
  • Clarify that PowerShell examples are primarily for Windows users and provide equivalent Linux shell examples for parity.
  • Where SDKs or tooling are Windows-specific (e.g., PowerShell SDK), mention Linux alternatives or note platform limitations.
  • Consider reordering examples so that Linux-friendly languages (Python, JavaScript) are presented before PowerShell, or alternate the order to avoid implicit prioritization.
GitHub Create Pull Request
Azure Functions How to run Durable Functions as WebJobs - Azure ...ure-functions/durable/durable-functions-webjobs-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. It consistently presents Windows-centric development patterns, such as using Visual Studio (Windows-only) and the Windows Classic Desktop project template as the primary workflow. All code/package installation examples use PowerShell commands, with no mention of Linux equivalents (e.g., bash, dotnet CLI, or cross-platform editors). The Azurite storage emulator is referenced without clarifying cross-platform usage, and there are no instructions for running or deploying WebJobs from Linux or macOS environments. Linux tools, editors, and workflows are either omitted or mentioned only as alternatives, with caveats.
Recommendations
  • Provide equivalent instructions for Linux/macOS environments, including using Visual Studio Code and the dotnet CLI for project creation and package management.
  • Include bash or shell commands for installing NuGet packages, alongside PowerShell examples.
  • Clarify that Azurite is cross-platform and provide installation/running instructions for Linux/macOS.
  • Offer guidance for running and deploying WebJobs from Linux/macOS, including any platform-specific considerations.
  • Present cross-platform workflows first or in parallel, rather than defaulting to Windows/Visual Studio.
  • Explicitly mention any limitations or differences when using Linux/macOS, and provide workarounds or alternatives.
GitHub Create Pull Request
Azure Functions Sub-orchestrations for Durable Functions - Azure ...ctions/durable/durable-functions-sub-orchestrations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page includes a prominent PowerShell-specific note and full PowerShell code examples alongside other languages. PowerShell is a Windows-centric tool, and its inclusion (with a dedicated SDK note and example) may signal a Windows bias. The note about PowerShell SDK appears before any mention of Linux or cross-platform equivalents, and there is no mention of Bash, Linux shell, or cross-platform scripting alternatives. There is no explicit Linux example or reference to Linux-specific tooling or patterns.
Recommendations
  • Add a note clarifying PowerShell support on Linux and macOS, or mention cross-platform alternatives where relevant.
  • Include Bash or other Linux shell examples if scripting is discussed, or clarify that Durable Functions are cross-platform and provide guidance for Linux users.
  • Balance the introductory notes by mentioning both Windows and Linux environments, especially when discussing SDKs or tooling.
  • If PowerShell is shown, consider also showing Bash or Python CLI equivalents for orchestration management tasks.
  • Explicitly state platform compatibility for all SDKs and tools referenced, and link to documentation for Linux/macOS usage where available.
GitHub Create Pull Request
Azure Functions Versioning in Durable Functions - Azure ...zure-functions/durable/durable-functions-versioning.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing code examples in C#, PowerShell, and Java, with PowerShell being a Windows-centric shell language. There are no examples for Linux-native shells (such as Bash), nor are Linux-specific tools or deployment patterns mentioned. Windows/PowerShell examples are presented alongside C# and Java, but Linux alternatives are absent, and deployment guidance references Azure App Service deployment slots (which are more familiar to Windows users) without mentioning Linux-specific deployment workflows or CLI tools.
Recommendations
  • Add Bash or other Linux shell examples for orchestration logic, especially for users running Durable Functions on Linux.
  • Include references to Linux-native tools and deployment patterns, such as Azure CLI commands for deployment and queue management.
  • Explicitly mention Linux support and parity in deployment slot guidance, including any differences or considerations for Linux-based Azure Functions.
  • Provide links or sections on managing Durable Functions storage and queues using Linux tools (e.g., Azure CLI, azcopy) in addition to Windows-centric approaches.
  • Ensure that examples and instructions are platform-neutral or provide parallel guidance for both Windows and Linux environments.
GitHub Create Pull Request
Azure Functions Choosing an orchestration framework ...rable-task-scheduler/choose-orchestration-framework.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias. PowerShell is listed as a first-class language for Durable Functions quickstarts, with a dedicated link, while Linux-specific shells (e.g., Bash) are not mentioned. The quickstart and sample tables list PowerShell alongside .NET, Python, JavaScript/TypeScript, and Java, but do not provide parity for Linux-native scripting languages or tools. There is also a tendency to mention Windows-centric technologies (PowerShell, MSSQL) before Linux alternatives, and no explicit mention of Linux development environments or shell usage.
Recommendations
  • Add Linux/Bash shell examples and quickstarts alongside PowerShell for Durable Functions.
  • Explicitly mention Linux development environments and workflows (e.g., VS Code on Linux, Bash terminal usage).
  • Include parity for Linux-native tools and scripting languages in quickstart/sample tables.
  • Avoid listing Windows-centric technologies (PowerShell, MSSQL) before Linux alternatives; present them in parallel or with equal prominence.
  • Clarify that Durable Functions and SDKs are cross-platform and provide guidance for Linux users.
GitHub Create Pull Request
Azure Functions Quickstart: Create a Java Durable Functions app ...in/articles/azure-functions/durable/quickstart-java.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates some Windows bias. In the manual setup section, the default runtime OS in the Maven plugin configuration is set to 'windows', with no mention of Linux alternatives. In the Maven command section, examples for Bash, PowerShell, and Cmd are provided, but PowerShell and Cmd (Windows shells) are listed after Bash, which is positive, but their inclusion may reinforce Windows-centric workflows. Visual Studio Code instructions are cross-platform, but there is no explicit mention of Linux-specific considerations or parity in deployment/runtime configuration. The use of Azure Functions Core Tools is cross-platform, but the documentation does not clarify Linux support or provide Linux-specific troubleshooting or configuration notes.
Recommendations
  • Explicitly mention Linux support in all relevant sections, especially in runtime configuration (e.g., show how to set <os>linux</os> in the Maven plugin).
  • Provide Linux-specific examples or troubleshooting notes where appropriate, such as file paths, permissions, or shell commands.
  • Balance shell examples by including zsh or other common Linux shells, and clarify that Bash commands work on Linux/macOS.
  • In the Maven plugin configuration, show both Windows and Linux runtime options, or default to a neutral value.
  • Add a note about Azure Functions Core Tools being cross-platform and provide installation instructions for Linux.
  • Ensure that any references to tools or workflows (e.g., Visual Studio Code) clarify their cross-platform nature and provide links to Linux/macOS setup guides.
GitHub Create Pull Request
Azure Functions Quickstart: Create an app with Durable Task SDKs and Durable Task Scheduler ...ask-scheduler/quickstart-portable-durable-task-sdks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation exhibits some Windows bias, particularly in the Python quickstart where Windows-specific commands and instructions are presented before their Linux equivalents. The presence of a 'powershell' pivot (even though its content is not shown here) suggests a focus on Windows tooling. In the Python section, Windows activation commands are listed first, and Linux instructions are secondary. There are no explicit Linux-specific tools or troubleshooting tips, and the documentation does not provide parity in example outputs or screenshots for Linux environments. However, the main commands for running the emulator and applications are cross-platform (bash/Docker), and Java/C# instructions are generally platform-neutral.
Recommendations
  • Present Linux and Windows instructions with equal prominence, or default to platform-neutral commands where possible.
  • In tabbed code blocks, do not always list Windows first; alternate or use platform detection.
  • Include Linux-specific troubleshooting tips (e.g., Docker permissions, executable flags) alongside Windows tips.
  • Add example outputs and screenshots from Linux terminals/environments to match those shown for Windows.
  • If a PowerShell pivot is present, ensure there is a corresponding Bash or shell script example for Linux/Mac users.
  • Explicitly state that all commands are cross-platform where applicable, and clarify any platform-specific differences.
GitHub Create Pull Request
Azure Functions Quickstart: Create a Durable Functions app that uses the MSSQL storage provider ...n/articles/azure-functions/durable/quickstart-mssql.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several forms of Windows bias. The database setup section provides only PowerShell commands for Docker-based SQL Server setup, which are more familiar to Windows users and may be less accessible to Linux users. References to SQL Server Express specifically mention 'your local Windows computer' before mentioning Docker as an alternative, and no explicit Linux shell (bash) examples are provided for key steps. The troubleshooting section refers to Docker Desktop, a tool primarily used on Windows and macOS, with no mention of Linux-native Docker workflows. Overall, Linux users may find it harder to follow the quickstart due to the lack of parity in examples and tool references.
Recommendations
  • Provide equivalent bash shell commands for Docker-based SQL Server setup and validation, alongside PowerShell examples.
  • Mention Linux as a first-class platform for local development, including references to Linux-native Docker workflows and tools.
  • Include instructions for installing and running SQL Server Express or Docker on Linux, not just on 'your local Windows computer'.
  • Add troubleshooting steps relevant to Linux environments, such as using 'docker exec' and file system navigation from the Linux terminal.
  • Ensure that all command-line examples (e.g., azurite, func host start) are shown in both Windows (PowerShell) and Linux (bash) formats where differences exist.
GitHub Create Pull Request
Azure Functions Quickstart: Configure a storage provider by using Netherite ...ticles/azure-functions/durable/quickstart-netherite.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools (such as the legacy Azure Storage Emulator), provides instructions and notes for Windows users before Linux, and omits explicit Linux command-line examples or Linux-specific instructions. The use of Azure Storage Explorer (a cross-platform tool, but often associated with Windows) is highlighted, and there is a lack of parity in showing Linux alternatives or clarifying cross-platform steps. The section on ensuring 64-bit architecture is labeled 'Windows only', but does not provide equivalent Linux validation steps.
Recommendations
  • Add explicit Linux command-line examples where applicable, such as using Bash or Linux-native tools for configuration and deployment.
  • Clarify that Azurite is cross-platform and provide installation instructions for Linux and macOS, not just Windows.
  • When mentioning Azure Storage Explorer, note its availability on Linux and macOS, and provide download links for all platforms.
  • In sections labeled 'Windows only', provide guidance for Linux users on how to validate architecture or clarify that no action is needed.
  • Avoid referencing legacy Windows-only tools (like Azure Storage Emulator) without also mentioning their cross-platform replacements.
  • Ensure that all steps and screenshots are representative of both Windows and Linux environments, or provide alternatives where UI differs.
GitHub Create Pull Request
Azure Functions Build a serverless workflow using Durable Functions - Azure Functions ...unctions/durable/scenario-build-serverless-workflow.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides command examples for multiple platforms, but Windows-specific instructions (Cmd, PowerShell) are consistently included and sometimes presented before Linux/macOS equivalents. There are multiple tabs for Windows command shells (Cmd, PowerShell, bash), and Windows tools/patterns (such as 'py' for Python, Windows path separators, and PowerShell variable assignment) are explicitly shown. Linux/macOS instructions are present but sometimes less detailed, and Windows command patterns are given equal or greater prominence.
Recommendations
  • Ensure Linux/macOS examples are always presented first or in parallel with Windows examples, especially in tabbed sections.
  • Where possible, provide cross-platform commands using POSIX-compliant syntax and avoid Windows-specific tools or patterns unless necessary.
  • Clarify which commands apply to which platforms, and avoid assuming Windows as the default environment.
  • For Python virtual environment activation, prefer showing the most common Linux/macOS pattern first, and ensure Windows instructions use both bash and Cmd/PowerShell accurately.
  • Consider adding explicit notes about differences in file paths, shell syntax, and environment activation between platforms.
  • Audit all command examples to ensure Linux parity and that no steps are omitted for Linux/macOS users.
GitHub Create Pull Request
Azure Functions Quickstart: Create a Python Durable Functions app ...es/azure-functions/durable/quickstart-python-vscode.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates some Windows bias, primarily by listing Windows-specific instructions and tools before or more prominently than Linux equivalents. For example, the virtual environment activation instructions list Windows (Powershell) after Linux/macOS, but the command uses Powershell syntax and the path casing ('.venv\scripts\activate') is Windows-specific. The documentation also assumes Visual Studio Code as the main editor, which is cross-platform but more commonly associated with Windows workflows. Additionally, the use of Azurite and Azure Functions Core Tools is described in a way that may be more familiar to Windows users, and there is no mention of potential Linux-specific issues or alternatives. However, Linux instructions are present, and the documentation does not completely omit Linux/macOS users.
Recommendations
  • Ensure that all command-line instructions are clearly separated and equally emphasized for Windows, Linux, and macOS, including both bash and Powershell/CMD where relevant.
  • When referencing tools like Azurite or Azure Functions Core Tools, note any OS-specific installation or usage steps, and provide links or notes for Linux package managers (e.g., apt, yum, Homebrew).
  • Avoid using Windows path casing (e.g., '.venv\scripts\activate') without also showing the Linux/macOS equivalent ('.venv/bin/activate').
  • Consider including screenshots from Linux/macOS environments as well as Windows.
  • Explicitly mention any known Linux/macOS caveats or troubleshooting steps, and provide parity in example commands and environment setup.
  • If Visual Studio Code is required, clarify that it is cross-platform and provide download links for all supported OSes.
GitHub Create Pull Request
Azure Functions Tutorial: Add Azure OpenAI text completions to your functions in Visual Studio Code ...zure-functions/functions-add-openai-text-completion.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of Visual Studio Code and Azurite emulator instructions that assume a Windows environment. Steps such as starting Azurite and running the function app use commands and patterns typical for Windows users (e.g., using F1 and F5 keys, referencing Core Tools in debug mode), without mentioning or providing examples for Linux or macOS equivalents. There are no Linux-specific instructions for installing prerequisites, running Azurite, or using alternative editors/terminals. The documentation also references Windows-centric tools and workflows before any cross-platform alternatives.
Recommendations
  • Add explicit instructions for Linux and macOS users, including terminal commands for starting Azurite and running/debugging Azure Functions.
  • Include installation steps for prerequisites (such as .NET Core CLI, Azurite) on Linux and macOS, not just Windows.
  • Mention cross-platform alternatives to Visual Studio Code where appropriate, or clarify that VS Code is available on all platforms.
  • Provide keyboard shortcut alternatives for F1 and F5 for Linux/macOS users, or describe how to perform these actions via command line.
  • Ensure that any references to file paths, environment variables, and configuration steps are platform-agnostic or include platform-specific notes.
GitHub Create Pull Request
Azure Functions Create and Manage Function Apps in a Flex Consumption Plan ...in/articles/azure-functions/flex-consumption-how-to.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It consistently references Windows-centric tools (Visual Studio Code, Azure CLI, PowerShell), and in several places, features or capabilities are described as unavailable in Visual Studio Code (which is cross-platform but often associated with Windows workflows). There are no explicit Linux-specific examples, nor are Linux command-line patterns (e.g., bash scripting, Linux file system conventions) provided. Powershell is listed as a supported runtime, but there are no equivalent Linux shell (bash/zsh) examples. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users in terms of deployment, configuration, or troubleshooting workflows.
Recommendations
  • Add explicit Linux shell (bash/zsh) examples for deployment, scripting, and resource management alongside Azure CLI and Powershell examples.
  • Clarify cross-platform support for Visual Studio Code, and provide instructions for Linux-specific installation and usage.
  • Include troubleshooting steps and tips for common Linux environments (e.g., Ubuntu, CentOS) when using Azure CLI and deploying function apps.
  • Where Powershell is referenced as a runtime or scripting tool, provide equivalent bash or other Linux shell examples, or clarify if such support is unavailable.
  • Review all tool references (e.g., Visual Studio Code, Azure CLI) to ensure installation and usage instructions are not Windows-centric, and add Linux-specific notes where appropriate.
  • Explicitly mention supported operating systems for all tools and runtimes, and provide links to Linux documentation where available.
GitHub Create Pull Request
Azure Functions Work with access keys in Azure Functions .../main/articles/azure-functions/function-keys-how-to.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing access keys, but PowerShell scripts are given equal prominence and detail as CLI commands. PowerShell is a Windows-centric tool, and there are no explicit Linux shell (bash) or cross-platform scripting examples beyond the CLI. Additionally, the CLI commands are described as running in Azure Cloud Shell (Bash), but it is noted that they must be modified to run in a Windows terminal, implying a Windows-first perspective. There are no explicit Linux-native examples or instructions for running commands in a typical Linux environment.
Recommendations
  • Add explicit bash shell examples for Linux users, especially for REST API calls (e.g., using curl or httpie).
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide instructions for running them in local terminals on each OS.
  • Reduce reliance on PowerShell for scripting examples, or provide equivalent bash scripts for Linux/macOS users.
  • When mentioning modifications for Windows terminals, also include notes for Linux/macOS environments to ensure parity.
  • Consider adding a cross-platform scripting section showing both PowerShell and bash approaches side-by-side.
GitHub Create Pull Request
Azure Functions RedisPubSubTrigger for Azure Functions ...ctions/functions-bindings-cache-trigger-redispubsub.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides code samples for multiple languages, including C#, Java, JavaScript, Python, and PowerShell. However, there is a noticeable bias towards Windows and Windows-centric tooling: PowerShell is included as a first-class language example, and connection string examples use the '.redis.cache.windows.net' domain, which is associated with Azure's Windows-centric Redis offering. There are no explicit Linux shell (e.g., Bash) examples, and PowerShell is presented alongside other cross-platform languages, despite being primarily a Windows shell. Additionally, the documentation does not mention Linux-specific patterns or tools, nor does it provide guidance for Linux users (e.g., using Bash, environment variable configuration in Linux, or Linux-specific troubleshooting).
Recommendations
  • Add Bash shell examples for Linux users alongside PowerShell, especially for environment variable configuration and function invocation.
  • Clarify that PowerShell examples are cross-platform only if using PowerShell Core, and provide equivalent Bash commands for Linux environments.
  • Include notes or sections on how to configure Redis connection strings and environment variables on Linux-based Azure Functions hosts.
  • Ensure that references to Redis endpoints and connection strings are not Windows-centric (e.g., mention that '.redis.cache.windows.net' applies to Azure, not to self-hosted or Linux Redis instances).
  • Explicitly state Linux compatibility and provide troubleshooting steps or caveats for Linux users where relevant.
GitHub Create Pull Request
Azure Functions Azure Functions SignalR Service bindings .../azure-functions/functions-bindings-signalr-service.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its structure and example choices. The installation instructions and extension management are described with a focus on NuGet packages and .NET-centric workflows, which are most familiar to Windows users. The mention of PowerShell as a supported language is explicit, but there are no Linux-specific instructions, examples, or references to Linux-native tools or shell environments. The guidance for environment variable naming and configuration does not clarify platform differences, and there is no mention of Linux development patterns or troubleshooting.
Recommendations
  • Add explicit Linux examples for extension installation and configuration, such as using the Azure Functions Core Tools CLI on Linux.
  • Include Bash or shell script equivalents alongside PowerShell instructions where relevant.
  • Clarify environment variable naming conventions for Linux shells (e.g., using ':' vs '__' in environment variables).
  • Reference Linux-native tools and workflows (such as VS Code on Linux, Azure CLI usage, or package managers like apt/yum for prerequisites).
  • Provide troubleshooting tips or notes for common Linux development scenarios (e.g., file permissions, case sensitivity, local.settings.json handling).
GitHub Create Pull Request
Azure Functions Azure Functions Web PubSub input binding ...azure-functions/functions-bindings-web-pubsub-input.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides code samples for C#, JavaScript, and Python, but omits complete examples for PowerShell and Java, stating that samples are pending or not supported. There is no explicit mention of Windows-specific tools or patterns, but the lack of PowerShell samples (which is often associated with Windows) and the absence of Linux-specific instructions or shell examples (e.g., Bash) indicate a bias toward Windows environments. The documentation does not provide parity for Linux users, especially in scripting or automation contexts.
Recommendations
  • Add complete PowerShell examples, ensuring they work on both Windows PowerShell and PowerShell Core on Linux.
  • Provide equivalent Bash or shell script examples for Linux users, especially for automation and deployment scenarios.
  • Include notes or instructions for configuring and running Azure Functions on Linux environments, such as using Azure CLI or Bash.
  • Ensure that any references to environment variables, file paths, or system tools are cross-platform or provide both Windows and Linux variants.
  • Explicitly mention support for Linux and cross-platform development in introductory sections.
GitHub Create Pull Request
Azure Functions Integration and automation platform options in Azure ...ctions/functions-compare-logic-apps-ms-flow-webjobs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (PowerShell, Visual Studio), mentioning them before Linux alternatives, and omitting explicit Linux or cross-platform examples for management and development. While some cross-platform capabilities are implied (e.g., Azure CLI, support for Bash scripts), the documentation does not provide Linux-specific instructions, examples, or highlight Linux development environments, leading to a perception that Windows is the primary or preferred platform.
Recommendations
  • Add explicit Linux-based examples for management and development tasks, such as using Bash scripts, Azure CLI on Linux, and Linux-native editors (e.g., VS Code on Linux).
  • Include instructions or references for deploying and managing Azure Functions, Logic Apps, and WebJobs from Linux environments.
  • Mention Linux-compatible tools (e.g., VS Code, Azure CLI) before or alongside Windows tools (e.g., PowerShell, Visual Studio) to ensure parity.
  • Provide sample workflows or code snippets that demonstrate automation and integration using Linux shell scripts.
  • Clarify cross-platform support in relevant sections, especially where Windows tools are listed, to avoid implying Windows exclusivity.
GitHub Create Pull Request
Azure Functions Azure Functions custom handlers .../articles/azure-functions/functions-custom-handlers.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-style executable naming ('handler.exe') is used throughout configuration and examples, with Linux/macOS equivalents only briefly mentioned in parentheses and never shown in detail. All configuration and deployment examples use Windows conventions first or exclusively, and there are no explicit Linux shell or deployment examples. The documentation does not provide parity for Linux users in terms of example commands, file naming, or deployment instructions.
Recommendations
  • Provide explicit Linux/macOS examples alongside Windows ones, including file naming (e.g., 'handler' vs 'handler.exe') and configuration.
  • Show example host.json configurations for both Windows and Linux/macOS, making it clear how to specify the executable path for each platform.
  • Include Linux/macOS deployment instructions and shell commands (e.g., using bash, chmod, etc.) in addition to Windows commands.
  • Clarify platform-specific requirements for custom handler binaries, such as file permissions and executable formats.
  • Ensure that example code and file system diagrams use platform-neutral naming or show both variants.
  • Mention cross-platform testing strategies and tools, not just those common on Windows.
GitHub Create Pull Request
Azure Functions Azure Functions Core Tools reference ...cles/azure-functions/functions-core-tools-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Functions Core Tools exhibits a moderate Windows bias. It references Windows-specific tools and patterns, such as 'func.exe', PowerShell managed dependencies, and the Microsoft Azure Storage Emulator (Windows-only). Windows terminology and tooling are mentioned before Linux equivalents, and some features (like log streaming) are noted as unsupported for Linux in certain plans. There are no explicit Linux shell examples, and installation or usage patterns for Linux are not described or linked directly. The documentation assumes familiarity with Windows-centric workflows and omits Linux-specific guidance or parity in several areas.
Recommendations
  • Include explicit Linux and macOS examples for all commands, especially where file paths, environment variables, or shell usage may differ.
  • Reference Linux equivalents for tools such as the Azure Storage Emulator (e.g., Azurite), and provide guidance for Linux users.
  • Avoid using Windows-specific terminology (e.g., '.exe' suffix) in the main description; clarify cross-platform availability.
  • Where features are not supported on Linux, provide alternative workflows or workarounds for Linux users.
  • Add installation and troubleshooting sections for Linux and macOS, with links to relevant documentation.
  • Ensure that PowerShell-specific options and behaviors are clearly marked as such, and provide parity for Bash or other shells where possible.
GitHub Create Pull Request
Azure Functions Create your function app resources using Azure Resource Manager templates ...ns/functions-create-first-function-resource-manager.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ARM templates, but the PowerShell examples are prominent and detailed for all programming languages, reinforcing a Windows-centric approach. PowerShell is a Windows-native tool, and its inclusion as a primary method (alongside CLI) may signal a bias toward Windows users. There are no explicit Bash or Linux shell examples, nor is there mention of Linux-specific tooling or patterns. The use of Cloud Shell mitigates some bias, as it supports both Bash and PowerShell, but the documentation does not demonstrate Bash usage or clarify cross-platform equivalence.
Recommendations
  • Add Bash shell examples for all programming languages, using Azure CLI commands, to demonstrate Linux parity.
  • Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows, and clarify that PowerShell is optional.
  • Reorder or balance the presentation so that Bash/Azure CLI examples appear before or alongside PowerShell examples, rather than after.
  • Include notes about cross-platform compatibility and recommend tools available on Linux (e.g., Bash, zsh) for deploying ARM templates.
  • Avoid implying PowerShell is the default or preferred method, especially for non-Windows users.
GitHub Create Pull Request
Azure Functions Develop Azure Functions using Visual Studio .../main/articles/azure-functions/functions-develop-vs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation is heavily focused on Windows development using Visual Studio, with all instructions, screenshots, and workflows tailored to the Windows environment. There are no examples or guidance for Linux or macOS users, and all tooling references (Visual Studio, PowerShell, Package Manager Console, remote debugging) are Windows-centric. Linux alternatives, such as VS Code, CLI workflows, or cross-platform debugging, are not mentioned or are relegated to secondary references. The use of PowerShell for package installation further reinforces the Windows bias.
Recommendations
  • Add equivalent instructions and examples for developing Azure Functions using VS Code or other cross-platform editors.
  • Include CLI-based workflows for project creation, binding addition, and publishing, using Azure Functions Core Tools and .NET CLI.
  • Provide Linux/macOS-specific guidance for local development, debugging, and remote debugging, including screenshots and step-by-step instructions.
  • Replace or supplement PowerShell commands with .NET CLI or Bash equivalents for package management.
  • Clarify which steps are Windows-specific and offer alternatives for non-Windows environments.
  • Highlight cross-platform capabilities of Azure Functions and ensure parity in documentation coverage.
GitHub Create Pull Request
Azure Functions Develop legacy C# class library functions using Azure Functions ...cles/azure-functions/functions-dotnet-class-library.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows tools and patterns are mentioned first or exclusively (e.g., Visual Studio, Windows MSI installer, Windows paths), PowerShell and Windows command examples are provided, and Linux equivalents (such as bash, Linux file paths, or Linux-specific instructions) are missing or relegated to secondary status. There is a lack of parity in examples and instructions for Linux/macOS users, particularly around local development, tool installation, and deployment.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, such as installation of Azure Functions Core Tools (e.g., apt, brew, or manual install).
  • Include bash/zsh command examples alongside PowerShell and cmd examples.
  • Mention cross-platform editors (e.g., VS Code) before or alongside Windows-only tools (e.g., Visual Studio), and clarify which instructions apply to which OS.
  • Use platform-neutral file paths and environment variable references, or show both Windows and Linux/macOS formats.
  • Explicitly state when a tool or feature is Windows-only, and offer alternatives for Linux/macOS users.
  • Add troubleshooting and configuration guidance for Linux/macOS environments, especially for local development and deployment.
GitHub Create Pull Request
Azure Functions Configure function app settings in Azure Functions ...ns/functions-how-to-use-azure-function-app-settings.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a notable Windows bias. Windows-specific tools (PowerShell, Kudu, App Service Editor) are referenced and exemplified throughout, often before or instead of Linux alternatives. Many features and migration steps are described as Windows-only, with Linux support either missing, deprecated, or explicitly excluded. Examples for PowerShell are provided, but Linux shell or bash equivalents are not. Several portal features and in-portal editors are available only for Windows, and Linux users are frequently directed to local development or told that features are unavailable.
Recommendations
  • Provide Linux shell (bash) equivalents for all PowerShell examples, especially for common tasks like managing app settings and FTPS credentials.
  • Clearly indicate feature parity and limitations for Linux, and update documentation as Linux support evolves.
  • Where features are Windows-only, suggest Linux alternatives or workarounds, such as using Azure CLI, REST API, or local development tools.
  • Include explicit Linux-focused sections or tabs for procedures, especially for plan migration, extension installation, and portal features.
  • Highlight any upcoming changes to Linux support (such as planned retirement of Linux Consumption plan) at the top of the page.
  • Ensure screenshots and step-by-step instructions are available for both Windows and Linux environments where applicable.
GitHub Create Pull Request
Azure Functions Develop and run Azure Functions locally ...in/articles/azure-functions/functions-develop-local.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page shows mild Windows bias, primarily by listing Windows-centric tools (Visual Studio, PowerShell) before cross-platform or Linux-native alternatives. Visual Studio is featured as the primary environment for C# development, and PowerShell is highlighted as an HTTP test tool before Linux-native tools like curl. While Visual Studio Code and command-line/terminal options are mentioned as cross-platform, Windows tools and patterns are often listed first or given more detailed descriptions. There are no explicit Linux-only examples, and Linux-specific workflows are not described in detail.
Recommendations
  • Ensure Linux and macOS environments are mentioned with equal prominence and detail as Windows, especially in introductory tables and environment lists.
  • Provide explicit Linux/macOS examples for common workflows, such as using bash/zsh in terminal instructions, or referencing Linux package managers for installing Azure Functions Core Tools.
  • List cross-platform tools (e.g., curl, Bruno) before Windows-specific tools (e.g., PowerShell, Visual Studio) in tool recommendations.
  • Add links or sections for Linux-specific troubleshooting, setup, and best practices.
  • Clarify that Visual Studio is Windows-only and suggest Linux/macOS alternatives (e.g., JetBrains Rider for .NET, or VS Code with .NET extensions).
  • Include screenshots or walkthroughs for Linux/macOS environments where possible.
GitHub Create Pull Request
Azure Functions Tutorial: Trigger Azure Functions on blob containers using an event subscription ...s/azure-functions/functions-event-grid-blob-trigger.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using Visual Studio Code and its extensions for all development, deployment, and Azure management tasks. All instructions rely on VS Code's command palette and GUI-based workflows, with no mention of Linux-native tools, CLI alternatives, or platform-specific differences. There are no examples using Bash, Azure CLI, or Linux file system conventions, and the use of Azurite and other extensions is described only in the context of VS Code, which is more commonly used on Windows. The documentation does not provide parity for Linux users who may prefer CLI or non-GUI workflows.
Recommendations
  • Add equivalent instructions using Azure CLI and Bash for all major steps, such as creating storage accounts, blob containers, function apps, and event subscriptions.
  • Include examples for running and debugging Azure Functions locally using Azure Functions Core Tools from the command line, not just via VS Code.
  • Document how to install and use Azurite directly from npm or Docker on Linux, outside of VS Code.
  • Provide guidance for editing configuration files (e.g., local.settings.json, host.json) using standard text editors and command-line tools.
  • Mention platform-specific considerations, such as file paths, environment variables, and authentication methods for Linux and macOS.
  • Ensure that all screenshots and step-by-step instructions have CLI equivalents, and link to official Azure CLI documentation where appropriate.
GitHub Create Pull Request
Azure Functions Continuously update function app code using Azure Pipelines ...icles/azure-functions/functions-how-to-azure-devops.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. Windows-based examples and agent images ('windows-latest') are presented first or exclusively for .NET (C#) and PowerShell, while Linux alternatives are either secondary or only mentioned for specific languages (e.g., Python, Java, JavaScript). PowerShell is included as a primary language tab, but there is no equivalent for Bash or other Linux-native scripting languages. The default deployment type is Windows, and Linux deployment requires explicit configuration. Some features (like deployment slots) are described with Windows examples first, and Linux limitations are highlighted. There is a lack of parity in scripting examples, and Linux-specific build/deploy patterns are not as thoroughly covered.
Recommendations
  • Provide Linux-based build and deployment examples for all supported languages, including .NET (C#) and PowerShell, not just Python, Java, and JavaScript.
  • Include Bash or other Linux-native scripting tabs alongside PowerShell to balance scripting language coverage.
  • Present Linux and Windows examples side-by-side or in parallel, rather than defaulting to Windows-first ordering.
  • Clarify feature parity and limitations for both Windows and Linux up front, and offer workarounds or alternatives where Linux support lags.
  • Ensure that all agent image choices ('windows-latest', 'ubuntu-latest') are explained and justified for each language, and encourage Linux usage where appropriate.
  • Highlight Linux deployment as a first-class option, not as a secondary or advanced configuration.
GitHub Create Pull Request
Azure Functions Use GitHub Actions to make code updates in Azure Functions ...les/azure-functions/functions-how-to-github-actions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation generally presents Windows options before Linux, both in tab order and in explanatory text (e.g., 'Choose either Windows or Linux' with Windows listed first). PowerShell is included as a language with both Windows and Linux tabs, but Python is explicitly unsupported on Windows, indicating a Windows-centric approach. Examples and templates for Windows are consistently presented before Linux equivalents. There is frequent mention of Windows-specific runners (e.g., 'windows-latest') and deployment methods, and Windows deployment details are often given before Linux. The documentation references Windows tools and patterns (such as PowerShell and Windows runners) more prominently than Linux equivalents.
Recommendations
  • Alternate the order of Windows and Linux examples/tabs so that Linux is not always second.
  • Provide equal prominence to Linux runners and deployment methods in explanatory text and tables.
  • Where possible, use neutral language (e.g., 'Choose your operating system: Linux or Windows') rather than listing Windows first.
  • Ensure that all language stacks have Linux examples where supported, and highlight Linux support for languages like Python.
  • Add explicit references to Linux tools and shell usage (e.g., Bash) where relevant, not just PowerShell.
  • Review all workflow templates and ensure Linux options are equally visible and accessible.
  • Clarify any limitations or differences for Linux users early in the documentation, rather than as footnotes.
GitHub Create Pull Request
Azure Functions Connect a function app to Azure SQL with managed identity and SQL bindings ...ctions-identity-access-azure-sql-with-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and workflows, such as PowerShell and Azure Portal, and by omitting explicit Linux or cross-platform alternatives. Examples for enabling managed identity and database access are described for Azure Portal, PowerShell, and Azure CLI, but PowerShell is mentioned before CLI, and no Linux-specific instructions (e.g., Bash scripting, Linux-native SQL clients) are provided. The SQLCMD example is generic but assumes Cloud Shell, which is cross-platform, yet does not mention Linux desktop tools or workflows. There are no explicit Linux or macOS examples, nor are open-source alternatives to Windows tools discussed.
Recommendations
  • Add explicit Linux/macOS instructions and examples, such as using Bash scripts or Linux-native SQL clients (e.g., mssql-cli, sqlcmd on Linux).
  • Present Azure CLI examples before PowerShell, or in parallel, to emphasize cross-platform parity.
  • Include screenshots or walkthroughs for Linux environments (e.g., Ubuntu terminal, macOS Terminal) alongside Azure Portal and PowerShell.
  • Mention and link to installation guides for required tools on Linux/macOS (e.g., sqlcmd, Azure CLI).
  • Avoid referencing Windows-specific tools or workflows without providing their Linux/macOS equivalents.
GitHub Create Pull Request
Azure Functions Monitor executions in Azure Functions .../main/articles/azure-functions/functions-monitoring.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows features and tools, such as Performance Counters and built-in log streaming, which are either unsupported or limited on Linux. Linux limitations are mentioned only as caveats, and there are no Linux-specific examples or guidance. Windows-centric features are described first or exclusively, and Linux users are left with less detailed instructions or alternatives.
Recommendations
  • Provide Linux-specific examples and guidance for monitoring and logging, including alternative tools or patterns where Windows features are unavailable.
  • Clearly document parity gaps and offer workarounds or best practices for Linux users, such as using Live Metrics Stream or exporting logs to external systems.
  • Reorder sections to present cross-platform solutions first, or explicitly indicate which features are Windows-only and suggest Linux alternatives.
  • Include troubleshooting and configuration steps for Linux environments, especially where features like Performance Counters or built-in log streaming are unsupported.
  • Add links to Linux-focused documentation or community resources for monitoring Azure Functions on Linux.
GitHub Create Pull Request
Azure Functions Azure Functions legacy C# script developer reference ...articles/azure-functions/functions-reference-csharp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive or prioritized mention of Windows-centric tools and workflows. Core Tools usage is described without platform-specific instructions, but references to Visual Studio and Visual Studio Code (both Windows-first IDEs) are frequent and appear before alternatives. There are no explicit Linux or macOS-specific examples, nor is there guidance for common Linux workflows (e.g., bash, zsh, or Linux package management). Windows-specific assembly references (e.g., Microsoft.WindowsAzure.Storage) and file path examples use backslashes, which are Windows conventions. No Linux shell commands, package installation steps, or troubleshooting notes for Linux environments are provided.
Recommendations
  • Add explicit Linux/macOS instructions and examples alongside Windows/Visual Studio workflows, including bash/zsh command lines and VS Code on Linux.
  • Include Linux-specific troubleshooting notes, such as permissions, file system case sensitivity, and common issues with Core Tools on Linux.
  • Use platform-agnostic file path examples (forward slashes or environment variables) or provide both Windows and Linux path formats.
  • Mention Linux package managers (apt, yum, brew) for installing prerequisites like .NET SDK and Azure Functions Core Tools.
  • Clarify that Core Tools and Azure Functions development are cross-platform, and highlight any platform-specific limitations or considerations.
  • Provide parity in code snippets and instructions for Linux users, such as using environment variables, file uploads, and directory structures.
  • Ensure all references to Windows-specific assemblies or APIs are accompanied by notes on their cross-platform compatibility or alternatives.
GitHub Create Pull Request
Azure Functions Automate function app resource deployment to Azure ...es/azure-functions/functions-infrastructure-as-code.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_examples_prominent ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates several types of Windows bias. Windows examples and terminology are frequently presented before Linux equivalents, especially in code samples and hosting plan definitions. PowerShell is used as the primary scripting language for deployment automation, with less emphasis on Bash or cross-platform CLI. Windows-specific tools and settings (such as WEBSITE_NODE_DEFAULT_VERSION) are highlighted, and some sections (e.g., deployment slots, remote builds, validation) provide more detail for Windows scenarios. Although Linux examples are present, they are often secondary, and some advanced Linux deployment scenarios (such as Bash scripting for deployment) are missing.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is shown first in code samples and explanations.
  • Include Bash or cross-platform Azure CLI scripts for deployment automation, not just PowerShell.
  • Ensure all advanced deployment scenarios (e.g., slot swaps, remote builds, validation) have Linux-specific instructions and examples.
  • Highlight Linux-specific settings and considerations equally with Windows, especially in application configuration tables.
  • Where Windows tools or terminology are mentioned, provide Linux equivalents (e.g., VS Code extensions, deployment commands).
  • Add links to Linux-focused sample repositories and templates.
  • Review all sections for parity in detail and troubleshooting guidance for both platforms.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several Windows-centric biases. Hybrid Connections are explicitly supported only for Windows-based function apps, with Linux support called out as missing. Example automation commands are provided for Azure PowerShell and Azure CLI, but PowerShell is highlighted, and there is no mention of Bash or Linux-specific scripting. Subnet sizing recommendations are given for both Windows and Linux, but Windows is listed first and with larger minimums, suggesting a default focus on Windows. No Linux-specific troubleshooting or operational guidance is provided, and Windows features/tools (such as Hybrid Connections) are described in detail without Linux alternatives.
Recommendations
  • Clearly indicate Linux support or limitations for all features, not just Hybrid Connections.
  • Provide Linux/Bash equivalents for all PowerShell examples, especially for automation and configuration.
  • Present Windows and Linux guidance in parallel, or alternate which is listed first to avoid implicit prioritization.
  • Offer troubleshooting steps and tooling guidance that are relevant for Linux-based function apps.
  • Where features are Windows-only, suggest Linux alternatives or workarounds, or explain the roadmap for Linux parity.
  • Include explicit examples for Linux environments in quickstart and tutorial sections.
  • Review all screenshots and UI instructions to ensure they are applicable to both Windows and Linux hosting scenarios.
GitHub Create Pull Request
Azure Functions Azure Functions Premium plan ...ain/articles/azure-functions/functions-premium-plan.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits several Windows-centric biases. Examples and instructions are frequently provided for Azure PowerShell (a Windows-focused tool) alongside Azure CLI, but there are no Linux-specific shell examples (e.g., Bash scripts, Linux-native tools). In migration scenarios, only Windows is supported, with Linux explicitly excluded. The ordering of examples and region scale-out tables consistently lists Windows before Linux, reinforcing a Windows-first perspective. There is also a lack of parity in migration support and troubleshooting guidance for Linux users.
Recommendations
  • Add Linux-specific examples and instructions, such as Bash shell commands or references to Linux-native tools where appropriate.
  • Ensure that CLI examples are clearly marked as cross-platform and provide any necessary Linux-specific notes (e.g., environment variable syntax differences, file paths).
  • Where PowerShell is used, clarify its availability on Linux and provide installation instructions or alternatives for Linux users.
  • In migration and troubleshooting sections, explicitly address Linux scenarios and provide guidance or workarounds if features are not supported.
  • Reorder tables and example lists to alternate or balance Windows and Linux, rather than always listing Windows first.
  • Where features are not available on Linux, provide context and timelines for parity, or suggest alternative approaches for Linux users.
GitHub Create Pull Request
Azure Functions Guidance for developing Azure Functions ...b/main/articles/azure-functions/functions-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools such as Visual Studio and PowerShell are mentioned prominently and often before cross-platform or Linux-native alternatives. Visual Studio is listed first in C# quickstarts and development tools, and PowerShell is included as a primary language pivot. There is little explicit mention of Linux-specific workflows, editors, or shell environments (e.g., Bash), and no Linux-first examples or tool recommendations are provided. The documentation assumes that Visual Studio and Visual Studio Code are the main local development environments, which may not reflect the preferences of Linux users.
Recommendations
  • Include Linux-specific development tool examples, such as using Bash, Vim, or Emacs for local development.
  • Provide explicit instructions and examples for Linux environments, such as using the Azure CLI in Bash or Zsh, and clarify cross-platform compatibility for all tools.
  • List cross-platform or Linux-native tools (e.g., Azure CLI, VS Code) before Windows-only tools (e.g., Visual Studio) in quickstart and development tool sections.
  • Add guidance for setting up local development environments on Linux, including package installation commands and troubleshooting tips.
  • Ensure parity in language pivots by offering Linux shell examples alongside PowerShell examples where relevant.
GitHub Create Pull Request
Azure Functions Develop Azure Functions locally using Core Tools ...b/main/articles/azure-functions/functions-run-local.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation generally aims for cross-platform parity, but there are subtle signs of Windows bias. Windows command-line examples are provided alongside Bash, and references to 'command prompt' and 'func.exe' (the Windows executable) appear throughout. Azure PowerShell is mentioned as a primary tool for publishing, and PowerShell is given equal prominence as a language, which may not reflect typical Linux workflows. The documentation sometimes lists Windows tools or patterns before Linux equivalents, and references to Windows-specific behaviors (such as MSI installation and func.exe) are present.
Recommendations
  • When showing command-line examples, always present Bash (Linux/macOS) examples first, or provide both Bash and Windows CMD/PowerShell examples side by side.
  • Avoid referring to the Functions host as 'func.exe'—use 'func' or 'the Functions host' to be platform-neutral.
  • When mentioning prerequisites or tools (e.g., Azure CLI, Azure PowerShell), clarify which are cross-platform and which are Windows-specific, and ensure Linux-first or parity in instructions.
  • Where PowerShell is referenced as a language, clarify its cross-platform availability and provide Bash alternatives where appropriate.
  • Review installation and upgrade instructions to ensure Linux package managers (apt, yum, brew, npm) are given equal or greater prominence compared to Windows installers.
  • Audit all references to Windows-specific behaviors or terminology and provide Linux/macOS equivalents where relevant.
GitHub Create Pull Request
Azure Functions Azure Functions Scale and Hosting .../blob/main/articles/azure-functions/functions-scale.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways. Windows is frequently mentioned first in tables and plan descriptions, and Windows-specific features (such as PowerShell modules and the full .NET Framework) are highlighted as primary use cases for the Consumption plan. There is a lack of Linux-specific examples or tooling references, and Linux support is often described in terms of limitations or retirement (e.g., Linux Consumption plan being retired), rather than as a first-class option. Windows deployment and features are described in more detail, while Linux options are sometimes referenced only in passing or with caveats.
Recommendations
  • Present Linux and Windows options in parallel, rather than listing Windows first or as the default.
  • Include Linux-specific examples, tools, and scenarios (e.g., Bash, Linux-native deployment workflows, Python on Linux).
  • Avoid framing Linux support primarily in terms of limitations or retirement; highlight Linux strengths and supported scenarios.
  • Where Windows-specific features (such as PowerShell modules) are mentioned, also provide equivalent Linux-native alternatives or note cross-platform options.
  • Ensure parity in technical detail and guidance for both Linux and Windows hosting plans, including container support and networking features.
GitHub Create Pull Request
Azure Functions Target-based scaling in Azure Functions ...cles/azure-functions/functions-target-based-scaling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is largely cross-platform and focuses on configuration via JSON and code samples for multiple languages. However, there are subtle signs of Windows bias: (1) PowerShell is grouped with JavaScript/TypeScript in examples, suggesting parity but giving PowerShell more visibility than Bash or Linux shell scripting; (2) a comment in the Java Kafka example specifically calls out enabling a line for Windows, with no equivalent Linux guidance; (3) there is no mention of Linux-specific tools, shell environments, or deployment patterns, and Windows/PowerShell are referenced before Linux alternatives in the limited cases where OS-specific configuration is discussed.
Recommendations
  • Add explicit Linux/Bash shell scripting examples or references where PowerShell is mentioned, to ensure parity.
  • Where OS-specific configuration is referenced (e.g., sslCaLocation for Kafka), provide both Windows and Linux instructions.
  • Avoid grouping PowerShell with JavaScript/TypeScript unless there is a clear cross-platform rationale; consider grouping Bash with PowerShell for parity.
  • Include notes or links for Linux-specific deployment or configuration patterns where relevant.
  • Review all examples and notes to ensure that Windows tools or patterns are not mentioned before Linux equivalents unless there is a technical reason.
GitHub Create Pull Request
Azure Functions Create and deploy function code to Azure using Visual Studio Code ...cles/azure-functions/how-to-create-function-vs-code.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation shows mild Windows bias. Windows-specific tools and instructions are referenced, such as PowerShell and Windows terminal settings. In several places, Windows instructions are given before Linux/macOS equivalents (e.g., compiling Go/Rust for Linux from Windows, troubleshooting shell settings). PowerShell is included as a first-class language, and its prerequisites link only to Windows installation instructions. Some troubleshooting steps reference Windows-specific issues (e.g., default terminal shell not set to WSL Bash). However, most examples and instructions are cross-platform, and Linux/macOS are mentioned where relevant.
Recommendations
  • For PowerShell prerequisites, provide installation instructions for Linux/macOS alongside Windows.
  • In troubleshooting, clarify solutions for Linux/macOS users (e.g., shell settings, emulator usage).
  • When listing platform-specific build steps (e.g., Go/Rust), present Linux/macOS instructions before or alongside Windows, not after.
  • Ensure all tool links (e.g., Azure Functions Core Tools, PowerShell) point to cross-platform documentation.
  • Explicitly mention Linux/macOS compatibility in all relevant sections, especially for language runtimes and extensions.
GitHub Create Pull Request
Azure Functions Deploy a PyTorch model as an Azure Functions application ...n/articles/azure-functions/machine-learning-pytorch.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides command examples for Bash (Linux/macOS), PowerShell, and Cmd, but Windows-specific tools and patterns (such as 'py' launcher, registry edits, and long path issues) are mentioned first or exclusively. Troubleshooting tips and editor recommendations are Windows-centric, and some Linux-specific issues (such as permissions or package installation) are only briefly mentioned. The documentation assumes familiarity with Windows environments and tools, with Linux/macOS guidance often secondary.
Recommendations
  • Ensure Linux/macOS examples are presented with equal prominence and detail as Windows examples.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, package installation failures, virtual environment activation quirks).
  • Provide editor recommendations for Linux/macOS (e.g., alternatives to Visual Studio Code, such as Vim or Sublime Text).
  • Offer guidance for resolving long path issues on Linux/macOS (e.g., using different filesystems or symlink strategies), not just Windows registry edits.
  • Use 'python' consistently in examples, with notes about 'py' launcher availability on Windows, rather than defaulting to Windows-first patterns.
  • Add explicit instructions for activating/deactivating virtual environments on Linux/macOS, including shell-specific notes (bash, zsh, etc.).
GitHub Create Pull Request
Azure Functions Migrate C# app from in-process to isolated worker model ...es/azure-functions/migrate-dotnet-to-isolated-model.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell scripts for identifying function apps to migrate, without offering Bash, Azure CLI, or Linux-native alternatives. Windows-centric tools and workflows (PowerShell, Visual Studio) are mentioned as primary options, with no parity for Linux or cross-platform tools. There are no examples or guidance for users working on Linux or macOS environments, and Windows tools are referenced before any mention of alternatives.
Recommendations
  • Provide equivalent Azure CLI (az) or Bash scripts for identifying function apps, alongside PowerShell examples.
  • Explicitly mention cross-platform tooling such as Azure Functions Core Tools and VS Code, and provide instructions for Linux/macOS environments.
  • Include deployment and configuration steps using CLI commands and scripts that work natively on Linux/macOS.
  • Reference Linux and macOS development environments in migration steps, and clarify any differences or requirements.
  • Ensure all automation and CI/CD guidance is platform-neutral, or provide examples for both Windows and Linux pipelines.
GitHub Create Pull Request
Azure Functions Migrate apps from Azure Functions version 3.x to 4.x ...rticles/azure-functions/migrate-version-3-version-4.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell scripts for identifying function apps to migrate, referencing Azure PowerShell multiple times, and omitting equivalent Linux/bash/CLI examples. The initial migration steps and tooling recommendations (such as Visual Studio and .NET Upgrade Assistant) are Windows-centric, with no mention of Linux-native alternatives or parity in scripting. Linux-specific considerations (such as shell commands or CLI usage) are missing or deferred, and Windows tools are mentioned first or exclusively.
Recommendations
  • Provide Azure CLI/bash examples alongside PowerShell scripts for identifying and managing function apps, ensuring Linux users have clear instructions.
  • Mention Linux-compatible IDEs and tools (such as VS Code, JetBrains Rider, or CLI-based workflows) in migration steps, not just Visual Studio.
  • Explicitly state cross-platform compatibility for tools like .NET Upgrade Assistant, and provide installation/usage instructions for Linux.
  • Add a section or callouts for Linux-specific migration considerations, such as file permissions, environment variables, and runtime differences.
  • Ensure that scripting and automation steps are presented in a platform-neutral way, or offer both Windows and Linux alternatives side-by-side.
GitHub Create Pull Request
Azure Functions Migrate Consumption plan apps to Flex Consumption in Azure Functions ...unctions/migration/migrate-plan-consumption-to-flex.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed, step-by-step instructions for migrating Azure Functions from the Consumption plan to the Flex Consumption plan, with clear separation between Windows and Linux workflows. However, there is a noticeable Windows bias: Windows examples and tools (such as Azure CLI commands, Kusto queries, and portal steps) are often presented first or in greater detail, and some migration steps (especially for Windows) require more manual effort and use Windows-centric tools. The Linux migration process is streamlined via the 'az functionapp flex-migration' CLI command, but the documentation does not always provide Linux equivalents for all Windows manual steps, and some advanced configuration or troubleshooting guidance is Windows-focused. In addition, references to PowerShell and Windows-specific deployment/storage patterns are more prevalent, and some examples (such as file share access and storage account details) are tailored to Windows.
Recommendations
  • Ensure all manual migration steps and troubleshooting guidance for Windows have equivalent, detailed Linux instructions (not just relying on the automated CLI command).
  • Present Linux and Windows instructions in parallel, or alternate which platform is shown first, to avoid the perception of Windows primacy.
  • Include Linux-specific troubleshooting, advanced configuration, and recovery steps, especially for scenarios where the automated CLI migration may not be sufficient.
  • Reduce reliance on Windows-centric tools and patterns (such as file shares, PowerShell, and Windows-specific storage account settings) in examples, or provide Linux alternatives.
  • Explicitly call out any limitations or differences for Linux users, and provide workarounds or guidance where parity is not yet possible.
  • Expand Linux coverage in sections such as performance benchmarking, monitoring, and post-migration validation to match the depth of Windows guidance.
GitHub Create Pull Request
Azure Functions Respond to blob storage events using Azure Functions ...ticles/azure-functions/scenario-blob-storage-events.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates some Windows bias, primarily through the use of Visual Studio Code as the main development environment, frequent references to the command palette (<kbd>F1</kbd>), and inclusion of PowerShell as a supported language. While Linux/macOS instructions are present for Python virtual environments, Windows-specific instructions (Windows Bash, Windows Cmd) are listed separately and prominently. The use of Azurite and Azure Functions Core Tools is cross-platform, but troubleshooting tips and some commands (e.g., 'func.exe host process', 'default terminal for Visual Studio Code isn't set to WSL Bash') are Windows-centric. PowerShell is treated as a first-class language, and Windows terminal patterns are referenced before or alongside Linux equivalents.
Recommendations
  • Ensure Linux/macOS instructions are given equal prominence and clarity as Windows instructions throughout the documentation, not just in language-specific sections.
  • Add troubleshooting notes for Linux/macOS environments (e.g., permissions, common issues with Azurite or Core Tools on Linux).
  • Where possible, use OS-neutral terminology (e.g., 'terminal' instead of 'command prompt') and avoid referencing Windows-specific processes unless necessary.
  • Provide examples or screenshots for Linux/macOS workflows, especially for Visual Studio Code usage and Azurite integration.
  • Clarify that all tools (Azurite, Azure Functions Core Tools, azd) are cross-platform and provide installation links or instructions for Linux/macOS users.
  • Consider including Bash or shell script examples for automation, not just PowerShell.
GitHub Create Pull Request
Azure Functions Troubleshoot Python function apps in Azure Functions ...n/articles/azure-functions/recover-python-functions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several forms of Windows bias. In command examples and troubleshooting steps, Windows (and PowerShell) instructions are often presented before or more prominently than Linux equivalents. Some sections provide only Windows-specific commands or tools (e.g., PowerShell, 'py' launcher), with Linux/Unix alternatives mentioned second or less thoroughly. There are also references to Windows-only packages (e.g., pywin32) and patterns (pip freeze from Windows), but Linux-specific troubleshooting and best practices are less emphasized.
Recommendations
  • Present Linux and Windows instructions side-by-side, or default to Linux-first examples since Azure Functions Python runs on Linux.
  • Ensure all command examples (e.g., checking Python bitness, deleting directories) include both Linux (bash) and Windows (PowerShell/CMD) variants with equal prominence.
  • Highlight Linux deployment patterns and troubleshooting steps, especially since the runtime is Linux-based.
  • Explicitly warn users developing on Windows about cross-platform issues and provide Linux-oriented solutions.
  • Include more Linux tool recommendations (e.g., bash, native package managers) and avoid assuming use of Windows-specific tools (e.g., py launcher, PowerShell).
  • Where packages are Windows-only, suggest Linux alternatives or clarify limitations for Linux deployments.
GitHub Create Pull Request
Azure Functions Respond to database changes in Azure SQL Database using Azure Functions ...ure-functions/scenario-database-changes-azure-sqldb.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively using Visual Studio Code and its extensions (such as the SQL Server (mssql) extension and Azure Functions Core Tools) for all instructions and examples. There are no references to Linux-native tools (e.g., sqlcmd, Azure Data Studio, or command-line alternatives), nor are there any examples or instructions for using the CLI outside of Visual Studio Code. The workflow assumes the use of GUI-based tools and patterns common to Windows, such as right-clicking in explorers, and does not mention Linux-specific considerations or alternatives.
Recommendations
  • Provide equivalent instructions for Linux users, including how to use azd, Azure Functions Core Tools, and SQL database access from the terminal.
  • Include examples using command-line tools such as sqlcmd or Azure Data Studio for database access and manipulation.
  • Mention installation and usage steps for Azure Functions Core Tools and azd on Linux, including any required dependencies.
  • Add notes or sections that clarify cross-platform compatibility and highlight any differences in workflow or available features between Windows and Linux.
  • Offer alternative workflows that do not require Visual Studio Code or its extensions, especially for users who prefer or require terminal-based development.
GitHub Create Pull Request
Azure Functions Respond to database changes in Azure Cosmos DB using Azure Functions ...-functions/scenario-database-changes-azure-cosmosdb.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific instructions (e.g., PowerShell commands, references to Windows terminal, and troubleshooting for Windows/WSL) are presented alongside, or sometimes before, Linux/macOS equivalents. The use of PowerShell for permission setting is highlighted, and troubleshooting tips focus on Windows environments (e.g., avoiding WSL Bash). There is limited coverage of Linux/macOS workflows, with some examples and troubleshooting steps missing or less detailed for non-Windows platforms.
Recommendations
  • Ensure Linux/macOS instructions are presented with equal prominence and detail as Windows instructions, including troubleshooting tips.
  • Provide Bash or shell script equivalents for all PowerShell commands, and clarify when each should be used.
  • Include explicit examples and troubleshooting steps for Linux/macOS users, such as common permission issues, terminal settings, and environment setup.
  • Avoid Windows-centric language (e.g., referencing 'func.exe' host process) and use platform-neutral terminology where possible.
  • Review and expand documentation for missing or placeholder sections for Linux/macOS and non-Windows languages/tools.
GitHub Create Pull Request
Azure Functions How to target Azure Functions runtime versions ...b/main/articles/azure-functions/set-runtime-version.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell examples are presented alongside Azure CLI and portal methods, but Windows-specific tools and patterns (such as PowerShell cmdlets and Visual Studio behaviors) are described in detail, often before or with more context than their Linux equivalents. Linux-specific instructions are present but sometimes less detailed, and certain operations (like pinning via portal or PowerShell) are explicitly unavailable for Linux, with CLI as the only option. The documentation also references Windows-centric developer workflows (e.g., Visual Studio publish dialogs) without Linux IDE equivalents.
Recommendations
  • Ensure Linux instructions are as detailed and prominent as Windows instructions, including troubleshooting and workflow notes.
  • Where Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned, provide equivalent Linux developer workflows (e.g., VS Code, CLI scripting).
  • Clarify limitations for Linux (e.g., portal/PowerShell unavailability) and suggest alternative approaches or workarounds.
  • Consider presenting CLI examples before platform-specific tools to promote cross-platform parity.
  • Add explicit Linux troubleshooting and migration guidance, matching the depth provided for Windows.
GitHub Create Pull Request
Azure Government Azure Government virtual machine extensions ...azure-government/documentation-government-extension.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands to list VM extensions in Azure Government, without offering equivalent Azure CLI or Bash examples for Linux users. The primary example uses Windows tooling (PowerShell), and the 'Next steps' section lists Windows extension deployment before Linux, further reinforcing the bias.
Recommendations
  • Add Azure CLI and/or Bash examples for listing VM extensions, ensuring Linux users have clear guidance.
  • Present both Windows (PowerShell) and Linux (CLI/Bash) instructions side-by-side or in parallel sections.
  • Alternate or randomize the order of Windows and Linux links in 'Next steps' to avoid consistently prioritizing Windows.
  • Explicitly mention cross-platform options for connecting to Azure Government and managing VM extensions.
GitHub Create Pull Request
Azure Functions Storage considerations for Azure Functions ...ain/articles/azure-functions/storage-considerations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a moderate Windows bias. Windows hosting scenarios and settings are frequently mentioned before Linux equivalents, and PowerShell examples and features are highlighted (such as managed dependencies in PowerShell and specific settings for Windows plans). Linux-specific guidance is less prominent, and in some cases, Linux examples or parity are missing or relegated to later sections. Windows tools and patterns (such as Visual Studio and PowerShell) are referenced more often and earlier than Linux alternatives.
Recommendations
  • Ensure Linux hosting scenarios and settings are described alongside Windows, not after or as exceptions.
  • Provide Linux-specific examples and CLI commands wherever PowerShell or Windows tools are referenced.
  • Highlight Linux deployment and troubleshooting workflows with parity to Windows (e.g., mention Linux Consumption plan status and alternatives up front).
  • Include cross-platform development tools (such as VS Code, CLI, and scripting) in examples, not just Visual Studio or PowerShell.
  • Clarify which features/settings are Windows-only and suggest Linux equivalents or workarounds.
  • Balance the order of presentation so Linux is not always secondary to Windows.
GitHub Create Pull Request
Azure Government Compare Azure Government and global Azure ...re-government/compare-azure-government-global-azure.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is mentioned and exemplified more frequently than Linux-native alternatives, and Windows-centric tools and patterns (such as Visual Studio and PowerShell modules) are referenced without equivalent Linux or cross-platform guidance. In several cases, examples and instructions are provided for PowerShell first or exclusively, while Linux/Unix alternatives (such as Bash scripting or native CLI usage) are either mentioned secondarily or omitted. There are missing Linux-specific examples for tasks like endpoint discovery and extension deployment, and Windows tools (Visual Studio, PowerShell) are referenced without cross-platform alternatives.
Recommendations
  • Provide Linux/Bash examples alongside PowerShell for all CLI operations, especially for endpoint discovery and extension deployment.
  • Reference cross-platform tools (such as VS Code, Azure CLI) before or alongside Windows-centric tools like Visual Studio.
  • Ensure that instructions for SDK endpoint modifications, firewall exceptions, and other configuration steps include Linux-specific guidance (e.g., modifying config files, using environment variables in Bash).
  • Add explicit notes or sections for Linux/macOS users where workflows or commands differ from Windows.
  • Review and update links to documentation so that they point to cross-platform or Linux-specific resources when available.
  • Avoid assuming PowerShell as the default scripting environment; clarify when commands are platform-specific and offer alternatives.
GitHub Create Pull Request
Azure Government Deploy an app in Azure Government with Azure Pipelines ...icles/azure-government/connect-with-azure-pipelines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exhibits a strong Windows bias, primarily by providing only PowerShell scripts and instructions for service principal creation, referencing Windows-specific tools (PowerShell, Set-ExecutionPolicy), and omitting equivalent Linux/bash examples. The prerequisites and step-by-step guidance assume a Windows environment, with no mention of cross-platform alternatives or parity for Linux/macOS users.
Recommendations
  • Provide equivalent bash/CLI examples for service principal creation, using Azure CLI (az) commands, which work on Linux, macOS, and Windows.
  • Include instructions for running scripts on Linux/macOS, such as using chmod to set execution permissions and running scripts with bash.
  • Mention cross-platform compatibility of Azure Pipelines agents and tools, and clarify which steps are OS-agnostic.
  • Reorder or balance examples so that Linux/bash alternatives are presented alongside or before Windows/PowerShell instructions.
  • Add notes or sections for Linux/macOS users, including troubleshooting and environment setup guidance.
GitHub Create Pull Request
Azure Government Azure Government Identity ...e-government/documentation-government-plan-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric technologies (Active Directory, NTLM/Kerberos, ADFS), providing guidance and links only for Windows Server tools, and omitting Linux equivalents or cross-platform identity management solutions. Examples and deployment scenarios focus on Windows infrastructure, with no mention of Linux authentication protocols, tools, or integration patterns.
Recommendations
  • Include examples and guidance for integrating Azure Government identity with Linux-based systems, such as using LDAP, SSSD, or Kerberos on Linux.
  • Reference cross-platform identity management tools and protocols (e.g., Samba, FreeIPA, OpenLDAP) where appropriate.
  • Provide parity in documentation by offering Linux-specific deployment scenarios for hybrid identity, including how to synchronize Linux-based directories with Microsoft Entra ID.
  • Mention and link to documentation for configuring identity federation and authentication for Linux workloads in Azure Government.
  • When discussing legacy authentication, clarify how Linux applications can participate or alternatives for Linux environments.
GitHub Create Pull Request
Azure Functions Update Language Versions in Azure Functions ...n/articles/azure-functions/update-language-versions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation frequently presents Windows-specific instructions and examples before Linux equivalents, especially in sections about updating stack configurations and using the Azure CLI. Windows tools and patterns (such as .NET SDK, Visual Studio Code, and PowerShell) are referenced prominently. In some cases, Linux instructions are less detailed or deferred, and Python on Windows is explicitly unsupported. There is a consistent pattern of presenting Windows steps first, which may make Linux users feel secondary.
Recommendations
  • Present Windows and Linux instructions in parallel, or alternate which platform is shown first in each section.
  • Ensure that all examples and step-by-step guides are equally detailed for both Windows and Linux.
  • Add more Linux-specific troubleshooting and toolchain guidance, such as common Linux IDEs and package managers.
  • Explicitly acknowledge Linux parity in introductory sections, reassuring users that all platforms are supported.
  • Where a feature is unsupported on a platform (e.g., Python on Windows), provide clear alternatives or migration paths.
  • Include Linux shell (bash/zsh) command examples alongside PowerShell where relevant.
  • Review and update any references to Windows-only tools to include Linux equivalents (e.g., .NET SDK installation on Linux, VS Code extensions for Linux).
GitHub Create Pull Request
Azure Government Azure guidance for secure isolation ...es/azure-government/azure-secure-isolation-guidance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas: Windows technologies (Hyper-V, BitLocker, Windows Firewall) are discussed in greater detail and often before their Linux equivalents; Windows-specific tools and patterns (PowerShell, RDP) are mentioned more frequently and sometimes as the default; examples and instructions for Linux (e.g., disk encryption, VM provisioning) are present but less detailed or appear after Windows instructions; and some sections lack Linux-specific examples or guidance, especially for advanced features and security controls.
Recommendations
  • Ensure Linux examples and instructions are provided alongside Windows examples, with equal detail and prominence.
  • When describing Azure features or security controls, mention Linux-compatible tools and technologies (e.g., SSH, iptables, SELinux, DM-Crypt) before or alongside Windows equivalents.
  • Avoid defaulting to Windows terminology (e.g., 'Windows Firewall', 'PowerShell') when cross-platform alternatives exist; use generic or platform-neutral terms where possible.
  • Provide explicit Linux command-line examples (e.g., Azure CLI, bash scripts) in addition to PowerShell, especially in sections about VM provisioning, disk encryption, and network configuration.
  • Clarify parity and limitations between Windows and Linux for all features, especially in security, encryption, and management tooling.
  • Review and update references to third-party tools and documentation to include Linux-focused solutions and best practices.
GitHub Create Pull Request
Azure Government Azure AI services on Azure Government ...vernment/documentation-government-cognitiveservices.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All setup and provisioning instructions use Azure PowerShell commands, with no mention of Azure CLI or Bash alternatives. The quickstart links and examples prioritize Windows and Visual Studio, and do not provide Linux or cross-platform instructions. There is no guidance for Linux users or references to Linux tools, making it difficult for non-Windows developers to follow the documentation.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all provisioning and account management steps.
  • Include instructions for connecting to Azure Government using Azure CLI on Linux/macOS.
  • Ensure quickstart links include tabs or pivots for Linux and cross-platform environments (e.g., Bash, Python, REST API).
  • Mention Linux-compatible tools and workflows alongside PowerShell and Windows-specific instructions.
  • Review all screenshots and UI references to ensure they are not exclusively Windows-centric.
GitHub Create Pull Request
Azure Government Azure Government developer guide ...government/documentation-government-developer-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before Linux equivalents, and by providing explicit links for connecting with PowerShell and Visual Studio, which are primarily Windows tools. Although a CLI example is included, it is listed after PowerShell, and there is no explicit mention of Linux-specific tools or workflows (e.g., Bash, VS Code on Linux, Linux package managers). The quickstart section prioritizes Windows tools and patterns, and does not provide parity for Linux users.
Recommendations
  • Add explicit Linux quickstart examples, such as connecting with Bash or using Azure CLI on Linux.
  • Include guidance for using cross-platform editors like VS Code, with instructions for Linux and macOS.
  • Ensure that CLI examples are listed before or alongside PowerShell examples to avoid implying Windows-first workflows.
  • Mention Linux package managers and installation steps for Azure CLI and SDKs on Linux.
  • Provide parity in troubleshooting and configuration guidance for Linux environments.
GitHub Create Pull Request
Azure Government Azure Government Marketplace images ...e-government/documentation-government-image-gallery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for listing images, referencing Windows VM creation steps before Linux, and omitting Linux-specific command-line examples (e.g., Azure CLI or Bash). There is no mention of Linux tools or workflows for obtaining image lists, and the step-by-step instructions prioritize Windows resources.
Recommendations
  • Add equivalent Azure CLI and Bash examples for listing VM images, suitable for Linux and cross-platform users.
  • Present both Windows and Linux VM creation links together or alternate their order to avoid implicit prioritization.
  • Explicitly mention that PowerShell is available on Linux and macOS, or clarify cross-platform options.
  • Include references to Linux-specific tools or workflows where relevant, such as using Bash scripts or cloud-init for image management.
GitHub Create Pull Request
Azure Government Azure Government Security ...e-government/documentation-government-plan-security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas. Windows and Windows Server are mentioned explicitly and before Linux alternatives (e.g., SMB 3.0 for encryption), and Windows-specific tools and protocols are referenced without equivalent Linux guidance. Powershell is highlighted in blog post examples, while Linux-specific examples are less prominent or only referenced in passing. There is a lack of parity in providing Linux-focused examples, tools, and operational patterns.
Recommendations
  • Include Linux-specific examples and guidance alongside Windows examples, especially for encryption, file sharing, and monitoring.
  • Mention Linux tools and protocols (e.g., NFS, SSH, LUKS, OpenSSL) when discussing data encryption, file shares, and secure connectivity.
  • Provide parity in blog post references, ensuring Linux attack detection and mitigation are covered as thoroughly as Windows/Powershell scenarios.
  • Explicitly state cross-platform support for Azure features and clarify any differences in implementation or best practices for Linux environments.
  • Add sample code snippets or configuration steps for Linux systems where Windows/Powershell examples are given.
GitHub Create Pull Request
Azure Health Insights How to use Azure AI Health Insights containers .../main/articles/azure-health-insights/use-containers.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific requirements (such as Docker needing to support Linux containers on Windows) are mentioned before Linux equivalents. There is a reference to using PowerShell and Azure CLI scripts for automation, but no Linux shell script examples are provided. The use of backslash as a line continuation character is noted, but no explicit Linux (bash) alternatives are shown. No Linux-specific troubleshooting or command-line examples are given, and the documentation does not provide parity for Linux automation or scripting.
Recommendations
  • Add explicit Linux shell script examples for automating resource deployment and container configuration, alongside PowerShell and Azure CLI.
  • When discussing line continuation characters, provide both Windows (backslash) and Linux (backslash or backtick) examples, or clarify with explicit examples for each OS.
  • Mention Linux prerequisites and installation steps with equal prominence to Windows, including troubleshooting steps specific to Linux environments.
  • Provide parity in automation examples: if PowerShell is mentioned, also include bash or shell script equivalents.
  • Ensure that references to host operating systems (Windows, Linux, macOS) are balanced and that examples are provided for all major platforms.
GitHub Create Pull Request
Azure Netapp Files Create a capacity pool for Azure NetApp Files ...etapp-files/azure-netapp-files-set-up-capacity-pool.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by explicitly mentioning PowerShell and its module update instructions, while omitting equivalent instructions for Linux shells (e.g., Bash) or Azure CLI on Linux. PowerShell is referenced before any Linux alternatives, and there are no examples or guidance for Linux users, such as Bash commands or Linux-specific update instructions.
Recommendations
  • Add explicit instructions for updating and using the Azure CLI on Linux, including Bash examples.
  • Provide parity in command-line examples by including both PowerShell and Bash/Azure CLI commands where relevant.
  • Mention Linux and macOS environments alongside Windows when discussing prerequisites and tools.
  • Ensure that references to PowerShell are balanced with references to Bash/Azure CLI, and do not appear first unless contextually appropriate.
  • Include troubleshooting or setup notes for Linux users, such as package installation or environment setup.
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files SDKs and CLI tools ...icles/azure-netapp-files/azure-netapp-files-sdk-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation lists both Azure CLI and PowerShell as supported command-line tools, but PowerShell is given equal prominence despite being primarily a Windows tool. There are no explicit Linux-specific tools or examples, and no mention of Bash or shell scripting, which are common on Linux. The CLI section does not clarify cross-platform compatibility or provide Linux-oriented usage patterns.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide examples of its use on Linux (e.g., Bash shell commands).
  • Add a note clarifying PowerShell Core is available on Linux, if relevant, and provide Linux-specific installation or usage instructions.
  • Include Linux/Bash script examples for common operations alongside PowerShell examples.
  • Mention other Linux-native tools or patterns if available (e.g., REST API usage via curl).
  • Reorder CLI tool presentation to list Azure CLI first, emphasizing its cross-platform nature.
GitHub Create Pull Request
Azure Government Azure Government Overview ...s/azure-government/documentation-government-welcome.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. In the 'Get started' section, Windows-centric tools (PowerShell, SQL Server Management Studio) are listed alongside cross-platform options (Azure CLI, portal), but Windows tools are mentioned explicitly and before Linux equivalents. PowerShell and SSMS are Windows-specific, and there is no mention of Linux-native tools (e.g., Bash, Azure Data Studio) or explicit Linux examples. The ordering and tool selection suggest a preference for Windows environments.
Recommendations
  • Include explicit Linux examples and instructions, especially for connecting and managing Azure Government resources.
  • Mention and link to Linux-native tools (e.g., Bash shell usage with Azure CLI, Azure Data Studio for database management).
  • Balance the ordering of guides so that cross-platform or Linux options (Azure CLI, portal) are listed before or alongside Windows-specific tools.
  • Add notes clarifying platform compatibility for each tool, and provide parity in guidance for both Windows and Linux users.
GitHub Create Pull Request
Azure Maps Authentication with Microsoft Azure Maps .../main/articles/azure-maps/azure-maps-authentication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in the section about programmatically retrieving the Azure Maps Client ID. PowerShell is presented first and in detail, while the Azure CLI is mentioned second. There are no examples using Bash, Linux shell scripting, or other cross-platform tools. The only explicit tooling examples are Windows-centric (PowerShell, Azure CLI), and no Linux-specific or platform-neutral alternatives are provided.
Recommendations
  • Provide Bash/Linux shell examples for retrieving the Client ID, e.g., using Azure CLI in Bash.
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform.
  • Add notes clarifying that Azure CLI works on Windows, Linux, and macOS.
  • Include platform-neutral code snippets where possible, such as REST API calls using curl.
  • Avoid presenting Windows-specific tools (PowerShell) as the primary or only method.
  • Review other sections for implicit Windows assumptions and add Linux/macOS equivalents where needed.
GitHub Create Pull Request
Azure Netapp Files Configure AD DS LDAP over TLS for Azure NetApp Files ...articles/azure-netapp-files/configure-ldap-over-tls.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server tools and workflows (Certification Authority, MMC snap-in) for certificate generation and export. No Linux or cross-platform alternatives are provided for these steps, and all screenshots and instructions are Windows-centric. There is no mention of how to perform equivalent tasks on Linux systems, nor are Linux tools or commands referenced.
Recommendations
  • Add instructions for generating and exporting root CA certificates using Linux tools such as OpenSSL.
  • Include Linux-specific examples and screenshots for certificate management.
  • Reference cross-platform certificate management options where possible, such as using OpenSSL or certtool.
  • Clarify that the process is not limited to Windows environments and provide parity for Linux administrators.
  • Reorder or supplement instructions so that Linux and Windows approaches are presented with equal prominence.
GitHub Create Pull Request
Azure Netapp Files Understand default and individual user and group quotas for Azure NetApp Files volumes ...s/default-individual-user-group-quotas-introduction.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation presents Windows client instructions and screenshots before Linux equivalents, and references Windows-specific concepts (such as SIDs and Windows Explorer) more prominently. Linux instructions are present but less detailed, and there is no mention of Linux group quota reporting tools or troubleshooting beyond the quota(1) command and error message. The 'Next steps' section also links to a Windows-specific topic.
Recommendations
  • Present Linux and Windows client instructions in parallel or alternate order to avoid implicit prioritization.
  • Provide more detailed Linux examples, including screenshots of quota reporting in common desktop environments or terminal output.
  • Reference Linux-specific concepts (such as GID, common quota management tools, and troubleshooting steps) with equal prominence to Windows equivalents.
  • Include links to Linux documentation or man pages in the 'Next steps' section, similar to the Windows SID documentation link.
  • Clarify any protocol-specific limitations (e.g., group quotas not supported on SMB) in both Windows and Linux contexts, and suggest workarounds or alternatives for Linux users where possible.
GitHub Create Pull Request
Azure Netapp Files Manage Azure NetApp Files storage with cool access ...main/articles/azure-netapp-files/manage-cool-access.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by primarily providing Azure PowerShell examples for feature registration, referencing right-click actions and GUI screenshots typical of Windows environments, and omitting explicit Linux shell (bash) or cross-platform CLI instructions in key procedural steps. Azure CLI is mentioned as an alternative, but no concrete CLI or bash examples are shown. The workflow descriptions and screenshots focus on Windows-style interfaces and patterns, with no Linux-specific guidance or parity.
Recommendations
  • Provide explicit Azure CLI (bash) command examples alongside PowerShell for all registration and management steps, including full syntax and sample output.
  • Include instructions and screenshots for managing cool access using the Azure Portal on Linux or macOS, if applicable, or clarify that the steps are platform-agnostic.
  • Avoid referencing right-click actions or Windows-specific UI patterns without noting how the equivalent action is performed on other platforms.
  • Add a section or callouts for Linux administrators, describing how to perform all tasks using Linux-native tools and shell environments.
  • Ensure that all code blocks are labeled with the platform or shell they target, and offer alternatives for both Windows and Linux users.
GitHub Create Pull Request
Azure Large Instances Onboarding requirements for Azure Large Instances ...icles/azure-large-instances/onboarding-requirements.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for onboarding and configuration tasks, with no equivalent Linux CLI (e.g., Bash/Azure CLI) examples. Windows tools and patterns (PowerShell cmdlets) are mentioned and used throughout the setup instructions, while Linux alternatives are absent or referenced only generically. The only explicit Linux mention is in the context of setting up a Red Hat Satellite server, but no Linux-based onboarding or configuration instructions are provided.
Recommendations
  • Provide equivalent Azure CLI (az) or Bash examples for all PowerShell cmdlet instructions, especially for onboarding, resource management, and ExpressRoute configuration.
  • Explicitly mention Linux-compatible tools and workflows where relevant, such as using Azure CLI on Linux/macOS for resource provisioning and management.
  • Structure example sections to present both Windows (PowerShell) and Linux (CLI/Bash) approaches side-by-side, or clearly indicate which instructions apply to which platform.
  • Include references to Linux documentation and troubleshooting resources for Azure Large Instances.
  • Clarify prerequisites for both Windows and Linux users, including installation steps for Azure CLI and authentication methods.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the JavaScript REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively using PowerShell commands for project setup, package installation, and script execution. There are no Linux or macOS shell (bash/sh/zsh) equivalents provided, and Windows/PowerShell commands are presented as the default or only option. This may hinder Linux and macOS users from following the instructions seamlessly.
Recommendations
  • Provide equivalent bash/sh/zsh commands alongside PowerShell examples for all project setup, npm installation, and script execution steps.
  • Explicitly mention cross-platform compatibility and clarify that commands can be run in any terminal (Windows, Linux, macOS) with appropriate syntax.
  • Add a section or callout for Linux/macOS users, highlighting any differences in environment setup, file paths, or command usage.
  • Where possible, use generic commands (e.g., 'npm install ...', 'node search.js') in documentation examples, or show both PowerShell and bash variants side by side.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Python REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively using PowerShell commands for project setup and environment variable configuration, without providing equivalent Linux/macOS shell examples (e.g., Bash). All command-line instructions (mkdir, cd, file creation, pip install, setting environment variables) are shown in PowerShell syntax, and there is no mention of Linux tools or patterns. This may hinder Linux/macOS users from following the guide seamlessly.
Recommendations
  • Provide Bash (Linux/macOS) equivalents for all PowerShell commands, including project creation (mkdir, cd, touch demo.py), package installation (pip install), and environment variable setting (export VAR=value).
  • Add a note clarifying that both Windows and Linux/macOS are supported, and show both sets of commands side-by-side or in tabs.
  • Avoid using only PowerShell syntax in documentation targeting cross-platform Python developers.
  • Mention common Linux/macOS tools (e.g., nano, vi for editing files) where appropriate.
  • Review all code snippets and command-line instructions for OS-specific assumptions, ensuring Linux parity.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the C# REST SDK ...ain/articles/azure-maps/how-to-dev-guide-csharp-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell for all command-line examples, including project creation, package installation, and environment variable setup. There are no equivalent examples for Linux or macOS users, such as Bash or sh commands. The documentation assumes a Windows environment throughout, which may hinder accessibility for developers on other platforms.
Recommendations
  • Provide equivalent Bash/sh examples alongside PowerShell for all command-line instructions, including project creation, package installation, and environment variable setup.
  • Explicitly state cross-platform compatibility for .NET and Azure Maps SDK, and clarify that instructions apply to Windows, Linux, and macOS.
  • Add notes or sections for Linux/macOS users, highlighting any differences in environment variable syntax or shell usage.
  • Consider using generic .NET CLI commands (without shell-specific syntax) where possible, or present both PowerShell and Bash side-by-side.
  • Review screenshots and references to ensure they do not assume a Windows-only environment.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Java REST SDK (preview) .../main/articles/azure-maps/how-to-dev-guide-java-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a significant Windows bias. All shell and command-line examples use PowerShell syntax, including project creation, file creation, environment variable setting, and program execution. There are no equivalent Linux/macOS shell (bash/sh) examples, and Windows-specific tools and patterns (e.g., New-Item, $Env:) are used exclusively and presented first. This may hinder Linux/macOS users from following the guide without additional research or translation.
Recommendations
  • Provide equivalent bash/sh examples for all PowerShell commands, including Maven project creation, file creation (e.g., touch demo.java), environment variable setting (e.g., export SUBSCRIPTION_KEY=...), and program execution (e.g., java demo.java).
  • When presenting command-line instructions, show both Windows (PowerShell/CMD) and Linux/macOS (bash/sh) variants side-by-side or in tabs.
  • Avoid using Windows-specific tools (e.g., New-Item) without alternatives; use cross-platform commands where possible.
  • Explicitly mention cross-platform compatibility and provide guidance for users on Linux/macOS.
  • Review and update all code snippets and instructions to ensure Linux parity and accessibility.
GitHub Create Pull Request
Azure Maps How to secure an Azure Maps application with a SAS token ...blob/main/articles/azure-maps/how-to-secure-sas-app.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting all command-line examples in PowerShell syntax, explicitly stating that Azure CLI runs in a PowerShell instance, and using Windows-style variable assignment and command substitution (e.g., $var = $(...)). There are no Linux shell (bash/zsh) equivalents provided, nor any mention of how to adapt the examples for Linux or macOS environments. The documentation assumes a Windows/PowerShell context throughout, which may hinder accessibility for Linux users.
Recommendations
  • Provide equivalent bash/zsh examples for all command-line steps, using Linux-style variable assignment and command substitution (e.g., var=$(...) instead of $var = $(...)).
  • Clarify that Azure CLI is cross-platform and can be run in any shell, not just PowerShell.
  • Add notes or sections explicitly addressing Linux/macOS usage, including any differences in file paths, environment setup, or command syntax.
  • Avoid language that implies PowerShell is the default or only environment (e.g., 'runs in a PowerShell instance'); instead, use neutral phrasing such as 'in your terminal'.
  • Where scripts are provided, offer both PowerShell and bash versions, or use syntax compatible with both where possible.
GitHub Create Pull Request
Azure Netapp Files What changing to volume hard quota means for your Azure NetApp Files service ...les/azure-netapp-files/volume-hard-quota-guidelines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias in several areas. In the VM-level monitoring section, Windows examples and screenshots are presented before Linux equivalents, and more detail is given to Windows tools (Explorer, dir command) than Linux (only df is mentioned). In the CLI/PowerShell section, PowerShell screenshots and references are prominent, while Linux shell examples are absent. The documentation also refers to Windows-specific patterns (Explorer, context menus) and provides more visual aids for Windows workflows.
Recommendations
  • Present Linux and Windows examples in parallel or alternate their order to avoid Windows-first bias.
  • Expand Linux coverage in CLI sections by including bash shell examples (e.g., using Azure CLI from bash, not just PowerShell).
  • Add screenshots and step-by-step instructions for Linux workflows, such as using the Azure CLI in a Linux terminal.
  • Mention Linux tools (e.g., lsblk, mount, df) with equal detail as Windows tools.
  • Ensure parity in visual aids: provide Linux screenshots for capacity reporting and management tasks.
  • Clarify that Azure CLI is cross-platform and provide explicit instructions for both Windows and Linux environments.
GitHub Create Pull Request
Azure Relay Integrate Azure Relay with Azure Private Link Service ...blob/main/articles/azure-relay/private-link-service.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based examples and instructions, such as using Azure PowerShell and referencing the creation of a Windows virtual machine for validation. There are no Linux CLI (az CLI), Bash, or Linux VM examples, and Windows tools and patterns are mentioned exclusively or before any Linux equivalents.
Recommendations
  • Add equivalent az CLI (cross-platform) examples for creating private endpoints and managing Azure Relay resources.
  • Include instructions and screenshots for creating and validating with a Linux virtual machine, not just Windows.
  • Provide Bash shell commands for DNS validation, alongside Windows command prompt examples.
  • Mention Linux tools and patterns (e.g., using /etc/hosts, dig, or nslookup on Linux) where appropriate.
  • Ensure parity in step-by-step instructions for both Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager Add module settings in the Bicep config file ...s/azure-resource-manager/bicep/bicep-config-modules.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Azure CLI as the primary credential sources, listing 'AzurePowerShell' immediately after 'AzureCLI' in credential precedence, and omitting explicit Linux or cross-platform command examples. No Linux-specific tools or authentication patterns are mentioned, and the documentation does not clarify parity or differences for Linux users.
Recommendations
  • Explicitly mention that Azure CLI and Azure PowerShell are available on both Windows and Linux, and clarify any platform-specific differences.
  • Provide Linux-specific examples or notes, such as authentication via environment variables or managed identities, especially for scenarios where Azure PowerShell is not available or commonly used.
  • Include guidance for using Bicep in Linux environments, such as installation instructions, credential management, and troubleshooting tips.
  • List credential types in a neutral order (e.g., alphabetically) to avoid implying Windows-first workflows.
  • Reference cross-platform editors and tools (e.g., VS Code) with installation and usage notes for Linux.
GitHub Create Pull Request
Azure Maps How to use the Azure Maps map control npm package ...lob/main/articles/azure-maps/how-to-use-npm-package.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently uses PowerShell syntax (e.g., 'npm install' and 'npm run build' shown as PowerShell code blocks) for all command-line examples, which may suggest a Windows-centric approach. There are no explicit Linux or macOS terminal examples, nor any mention of platform-specific differences or considerations. The documentation does not reference Windows-specific tools, but the command-line instructions implicitly favor Windows by using PowerShell formatting and not acknowledging other shells.
Recommendations
  • Provide command-line examples in a neutral shell format (e.g., generic bash or sh), or show both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) examples side-by-side.
  • Use 'shell' or 'bash' code block formatting for npm commands, as these are cross-platform and most users on Linux/macOS expect bash syntax.
  • Add a note clarifying that npm commands work on all major platforms and mention any platform-specific considerations (e.g., file paths, permissions).
  • Avoid using PowerShell-specific formatting unless demonstrating a PowerShell-specific feature.
  • Explicitly mention Linux/macOS compatibility in the prerequisites or installation sections.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Bicep ...zure-resource-manager/bicep/deployment-script-bicep.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell examples and references are presented alongside Azure CLI, but PowerShell is given equal or sometimes greater prominence, and Windows-centric tools and patterns (such as PowerShell scripting and ARMClient usage via PowerShell) are frequently referenced. The deployment and management instructions for Bicep scripts often default to PowerShell, with CLI alternatives provided but not always prioritized. There is little explicit mention of Linux-specific scripting environments or shell usage outside of Azure CLI, and no examples using Bash or other native Linux tools for deployment or management. The documentation does not provide parity for Linux users in terms of deployment workflow examples, troubleshooting, or environment setup.
Recommendations
  • Provide Linux-native deployment and management examples, such as Bash scripts using az CLI for resource group and deployment management.
  • Ensure that CLI (az) examples are presented before or at least equally with PowerShell examples, especially in quickstart and workflow sections.
  • Explicitly mention and demonstrate how to use Linux shell environments for script development, deployment, and troubleshooting.
  • Include instructions for setting up and using Bicep and deployment scripts on Linux, including package installation, environment configuration, and common Linux patterns.
  • Avoid assuming PowerShell as the default scripting environment; clarify when examples are Windows-specific and provide Linux equivalents.
  • Highlight cross-platform compatibility and note any limitations or differences in behavior between Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager Develop a deployment script in Bicep ...re-resource-manager/bicep/deployment-script-develop.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references are consistently presented alongside Azure CLI (Bash) examples, but Windows-centric tools and patterns (such as PowerShell, Connect-AzAccount, CommandLineToArgvW, and Start-Sleep) are mentioned explicitly and sometimes before their Linux equivalents. Windows/PowerShell concepts (like $ErrorActionPreference, Start-Sleep, and Connect-AzAccount) are explained in detail, while Linux/Bash error handling and scripting patterns receive less attention. The documentation references Windows APIs (CommandLineToArgvW) for argument parsing, which may be unfamiliar or irrelevant to Linux users. However, most examples do provide both CLI (Bash) and PowerShell variants, and the underlying deployment scripts run in Ubuntu containers, which helps mitigate bias.
Recommendations
  • Ensure that CLI (Bash) examples and explanations are presented before or alongside PowerShell examples, not after.
  • Provide equivalent Linux/Bash scripting patterns and troubleshooting tips (e.g., explain 'set -e', error trapping, and debugging in Bash as thoroughly as PowerShell's $ErrorActionPreference).
  • Avoid referencing Windows-specific APIs (e.g., CommandLineToArgvW) without also explaining the Linux/Bash equivalent or clarifying cross-platform behavior.
  • When discussing sleep/troubleshooting, mention Bash alternatives (e.g., 'sleep 60') alongside PowerShell's Start-Sleep.
  • Expand explanations of Bash/CLI tools and patterns (e.g., jq usage, output handling, error management) to match the detail given to PowerShell.
  • Review sample links and ensure parity in complexity and coverage between CLI and PowerShell samples.
  • Explicitly state that deployment scripts run in Ubuntu containers and clarify any platform-specific behaviors or limitations.
GitHub Create Pull Request
Azure Resource Manager Bicep What-If: Preview Changes Before Deployment ...rticles/azure-resource-manager/bicep/deploy-what-if.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently presenting PowerShell examples alongside Azure CLI, often giving PowerShell equal or greater prominence. There is no mention of Linux-specific shell environments (e.g., Bash, zsh), nor are there any explicit Linux terminal examples or instructions. The installation and usage instructions for Azure CLI are generic, but all scripting examples are either Azure CLI (which is cross-platform) or PowerShell (which is Windows-centric, though available on Linux, but not the default). No Linux-native tools or shell patterns are shown, and PowerShell examples are provided for every operation, sometimes with more detail than CLI. There are no Bash or Linux shell script equivalents, and no guidance for Linux users on environment setup or command usage nuances.
Recommendations
  • Add explicit Bash examples for all Azure CLI commands, using standard Linux shell syntax (e.g., export, $(...), etc.), and clarify that Azure CLI commands work natively in Bash/zsh/fish on Linux and macOS.
  • Include notes or sections on installing Azure CLI and running Bicep deployments on Linux and macOS, including package manager instructions (apt, yum, brew).
  • Clarify that PowerShell is available cross-platform, but is not the default shell on Linux/macOS, and provide guidance for users who prefer Bash.
  • Where PowerShell is mentioned, add parallel Bash scripting examples for programmatic evaluation (e.g., using jq to parse JSON output from Azure CLI).
  • Ensure that all examples and instructions are presented in a way that does not assume a Windows environment, and avoid giving PowerShell precedence over CLI or Bash.
GitHub Create Pull Request
Azure Netapp Files Back up using Azure Application Consistent Snapshot tool for Azure NetApp Files | Microsoft Docs ...articles/azure-netapp-files/azacsnap-cmd-ref-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias in several ways. The section on flushing file buffers provides detailed, step-by-step instructions for running azacsnap.exe with administrator privileges on Windows, including using CMD, PowerShell, and Task Scheduler, while the Linux equivalent is briefly mentioned as using the 'sync' command with no further guidance or examples. Windows-specific tools and patterns (elevated CMD, PowerShell, Task Scheduler) are described in depth, and Windows instructions are presented first and more prominently than Linux instructions.
Recommendations
  • Provide equally detailed instructions for Linux, including example commands for flushing I/O buffers, running azacsnap with sudo, and automating with cron or systemd.
  • Present Linux and Windows instructions in parallel, or start with Linux examples if the tool is cross-platform.
  • Include troubleshooting tips and privilege escalation methods for Linux, similar to the Windows section.
  • Add explicit Linux example commands for common operations, such as viewing logs, automating backups, and managing permissions.
  • Ensure that all features and options described for Windows are also covered for Linux, or note any platform-specific limitations.
GitHub Create Pull Request
Azure Netapp Files Configure the database for Azure Application Consistent Snapshot tool for Azure NetApp Files ...cles/azure-netapp-files/azacsnap-configure-database.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways. The Microsoft SQL Server section exclusively uses Windows-style commands (e.g., .\azacsnap.exe) and references Windows tools and patterns, such as running commands from the Windows shell and using .exe files. There are no Linux equivalents or examples for SQL Server, and the instructions for configuring and testing AzAcSnap with SQL Server are only provided for Windows environments. In contrast, the SAP HANA, Oracle, and IBM Db2 sections provide detailed Linux shell commands and procedures, but the SQL Server section lacks parity for Linux users.
Recommendations
  • Add Linux-specific instructions and examples for configuring AzAcSnap with Microsoft SQL Server, including shell commands and usage patterns for SQL Server on Linux.
  • Provide parity in testing and configuration commands for SQL Server on Linux (e.g., using ./azacsnap instead of .\azacsnap.exe, and referencing Linux paths and environments).
  • Explicitly mention any differences or requirements for SQL Server on Linux, such as package installation, user permissions, and environment setup.
  • Ensure that all database sections (SAP HANA, Oracle, Db2, SQL Server) offer both Windows and Linux examples where applicable, and avoid presenting Windows instructions first or exclusively.
GitHub Create Pull Request
Azure Resource Manager Linter rule - no location expressions outside of parameter default values ...anager/bicep/linter-rule-no-loc-expr-outside-params.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page provides deployment guidance and examples exclusively using Azure PowerShell commands, which are primarily associated with Windows environments. There is no mention of cross-platform or Linux-native tools such as Azure CLI, nor are Linux shell examples provided. Windows/PowerShell tools are discussed in detail, with no parity for Linux or macOS users.
Recommendations
  • Include equivalent Azure CLI examples for deployment scenarios, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Mention that Azure PowerShell is available on Linux and macOS, but clarify cross-platform alternatives.
  • Provide bash or shell script examples where appropriate.
  • Ensure that references to deployment commands do not assume a Windows-first audience by listing CLI and PowerShell options together or in parallel sections.
  • Add notes or links for Linux/macOS users on how to perform the same actions using their preferred tools.
GitHub Create Pull Request
Azure Netapp Files Install the Azure Application Consistent Snapshot tool for Azure NetApp Files ...n/articles/azure-netapp-files/azacsnap-installation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Linux and Windows instructions, but Windows examples and terminology (such as GUI, %PATH%, and Windows-specific commands) are often presented first or with more detail. Windows tools and patterns (e.g., 'where', 'copy', GUI steps) are mentioned explicitly, while Linux equivalents are less emphasized or missing. Some steps, such as user creation and environment variable setup, are more thoroughly described for Windows, and Linux instructions sometimes refer to external documents for critical setup steps.
Recommendations
  • Ensure Linux and Windows instructions are presented in parallel, with equal detail and prominence.
  • Provide Linux shell command equivalents for all Windows command examples (e.g., 'where' vs. 'which' or 'find').
  • Avoid Windows-first ordering; alternate or present both platforms together.
  • Expand Linux examples to include GUI alternatives if Windows GUI steps are described, or clarify if only CLI is supported.
  • Include explicit Linux instructions for all steps currently referencing external documents.
  • Use neutral language and avoid assuming Windows as the default platform.
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files for Azure Government ...b/main/articles/azure-netapp-files/azure-government.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and listing PowerShell access as a primary method for connecting to Azure Government. The PowerShell section is more extensive than the Azure CLI section, and Windows-specific tools (PowerShell, Microsoft Graph PowerShell, Microsoft Entra PowerShell) are highlighted. There are no Linux-specific examples or mentions of Linux-native tools, and the ordering of sections places Windows/PowerShell access before any Linux alternatives.
Recommendations
  • Add explicit Linux examples for connecting to Azure Government, such as using Bash or shell scripts.
  • Include instructions for using Azure CLI on Linux, emphasizing cross-platform compatibility.
  • Mention and provide examples for REST API access using curl or other Linux-native tools.
  • Balance the coverage of PowerShell and CLI by providing equivalent step-by-step instructions for both.
  • Clearly state that Azure CLI and REST API methods work on Linux, macOS, and Windows, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Resource Manager Tutorial - custom actions & resources ...ns/tutorial-create-managed-app-with-custom-provider.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a bias toward Windows environments by providing a detailed PowerShell script for packaging and uploading the managed application artifacts to Azure Storage, while omitting equivalent instructions for Linux/macOS users (e.g., Bash or Azure CLI). The PowerShell example appears before the Azure CLI deployment steps, and there is no mention of cross-platform alternatives for the artifact upload process. The use of Windows-specific tools and scripting patterns (e.g., $RANDOM, backtick line continuation, PowerShell cmdlets) further reinforces the Windows-centric approach.
Recommendations
  • Provide Bash/Azure CLI examples for packaging and uploading the application artifacts to Azure Storage, suitable for Linux/macOS users.
  • Present cross-platform instructions side-by-side or in tabs, ensuring parity and visibility for both Windows and Linux users.
  • Avoid using Windows-specific scripting features (e.g., backtick line continuation) without offering alternatives.
  • Explicitly mention that both PowerShell and Bash/CLI can be used, and link to relevant cross-platform documentation.
  • Consider including a table or section summarizing equivalent commands for Windows (PowerShell), Linux (Bash), and macOS.
GitHub Create Pull Request
Azure Netapp Files Create an SMB volume for Azure NetApp Files ...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and screenshots for Windows-based tools and workflows (MMC, Windows SMB client, Windows File Browser), omitting equivalent Linux guidance for managing SMB volumes. All examples for setting permissions and share management are Windows-centric, with no mention of Linux SMB clients (e.g., smbclient, mount.cifs) or Linux-based permission management. Windows terminology and commands are used without Linux alternatives, and the order of presentation prioritizes Windows tools.
Recommendations
  • Add Linux-specific instructions and examples for mounting and managing SMB volumes, such as using smbclient, mount.cifs, or Nautilus.
  • Include screenshots or command-line examples for Linux environments when setting file and share permissions.
  • Explicitly mention Linux support in relevant sections, and provide parity in step-by-step guides for both platforms.
  • Reference Linux documentation and tools alongside Windows ones, rather than only in separate articles.
  • Where Windows commands (e.g., net view) are mentioned, provide the Linux equivalent (e.g., smbclient -L).
  • Clarify any platform-specific limitations or differences in SMB feature support (e.g., encryption, access-based enumeration) for Linux clients.
GitHub Create Pull Request
Azure Netapp Files Quickstart: Set up Azure NetApp Files and NFS volume ...-netapp-files-quickstart-set-up-account-create-volumes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides parallel instructions for Azure Portal, PowerShell, Azure CLI, ARM templates, and Terraform. However, PowerShell is given prominent placement and detailed examples, reflecting a Windows-centric approach. References to PowerShell Cloud Shell and installation instructions for the Azure PowerShell module further reinforce Windows bias. There is no explicit mention of Linux-specific shell environments (e.g., bash), nor are there examples using Linux-native tools or scripting patterns. While Azure CLI is included and is cross-platform, the documentation does not highlight Linux usage or parity, and PowerShell is often listed before CLI, suggesting a Windows-first mindset.
Recommendations
  • Add explicit bash shell examples for Linux users alongside PowerShell, especially for environment setup and scripting.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide guidance for installing CLI on those platforms.
  • Mention Linux-native tools (e.g., curl, jq) where relevant, and provide sample scripts for common Linux automation scenarios.
  • Balance the order of examples so that Azure CLI (cross-platform) is presented before PowerShell, or alternate their order.
  • Reference Linux Cloud Shell usage and provide links to Linux-specific documentation for Azure resource management.
  • Avoid assuming PowerShell as the default scripting environment; acknowledge and support bash/zsh and other shells.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Automation to another region ...manager/management/relocation/relocation-automation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell-based examples and instructions for exporting and importing runbooks, without mentioning or providing equivalent guidance for Linux users (e.g., Azure CLI, Bash, or REST API). The use of PowerShell is presented as the primary or sole method for key operations, and no Linux-specific tools or workflows are referenced.
Recommendations
  • Include Azure CLI and Bash examples for exporting and importing runbooks, alongside PowerShell instructions.
  • Reference cross-platform tools (e.g., REST API, Terraform) for automation tasks, and provide sample commands/scripts.
  • Explicitly mention Linux-compatible workflows and tools in each step where PowerShell is referenced.
  • Add a section or note clarifying that all steps can be performed on Linux, and link to relevant Linux documentation.
  • Ensure parity in screenshots and diagrams by showing both Windows and Linux environments where applicable.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Cosmos DB NoSQL account to another region ...-manager/management/relocation/relocation-cosmos-db.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation frequently lists Windows-centric tools (Azure PowerShell, Azure portal) before cross-platform or Linux-native options (Azure CLI). In several places, PowerShell is mentioned alongside or before CLI, and the Azure portal (which is OS-agnostic but often associated with Windows workflows) is consistently listed first. There are no explicit Linux-only examples or references to Linux-specific workflows, and no command-line examples are provided to illustrate parity.
Recommendations
  • Alternate the order of tool mentions so that Azure CLI is listed before or alongside Azure PowerShell and Azure portal, especially in step-by-step instructions.
  • Explicitly state that Azure CLI is cross-platform and provide CLI examples for each operation, especially for tasks like creating VNets, subnets, and Cosmos DB accounts.
  • Include Linux shell (bash) command examples where possible, not just references to documentation.
  • Add a section or callout highlighting that all operations can be performed from Linux environments using the Azure CLI.
  • Avoid defaulting to PowerShell or portal-first instructions; strive for equal visibility for Linux-friendly tools.
GitHub Create Pull Request
Azure Resource Manager Relocation guidance for Azure Firewall ...e-manager/management/relocation/relocation-firewall.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for command-line operations, with no mention of Azure CLI, Bash, or Linux shell equivalents. The use of PowerShell is pervasive throughout the export, modification, and redeployment steps, and references to Windows-centric tools and patterns (e.g., PowerShell cmdlets, Read-Host prompts) are present. There are no Linux-specific instructions or cross-platform alternatives, and PowerShell is presented before any other automation or scripting option.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all command-line steps, ensuring parity for Linux and macOS users.
  • Explicitly mention that PowerShell examples are suitable for Windows, and provide guidance for users on other platforms.
  • Include cross-platform instructions for exporting, modifying, and deploying ARM templates, such as using Azure CLI or REST API.
  • Avoid using Windows-specific patterns (e.g., Read-Host) in examples, or provide equivalent alternatives for Linux shells.
  • Review related links and ensure they reference cross-platform documentation where available.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of a property ...es/azure-resource-manager/templates/copy-properties.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits Windows bias by referencing Windows-specific VM deployment templates, mentioning Azure PowerShell before Azure CLI, and lacking Linux-focused examples or links. The only example template provided is for deploying Windows VMs, and deployment instructions prioritize PowerShell over CLI or other cross-platform tools.
Recommendations
  • Include example templates for Linux VM deployments alongside Windows examples.
  • Provide links to both Windows and Linux quickstart templates in the 'Example templates' section.
  • Mention Azure CLI and REST API equally or before PowerShell when discussing deployment methods.
  • Add explicit Linux-focused deployment instructions and examples to ensure parity.
  • Review and update links to ensure cross-platform coverage (e.g., link to deploy-CLI.md as well as deploy-powershell.md).
GitHub Create Pull Request
Azure Resource Manager Key Vault secret with template ...zure-resource-manager/templates/key-vault-parameter.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page presents both Azure CLI and PowerShell examples for all command-line operations, but PowerShell is consistently given equal prominence and sometimes appears first in code blocks and references. The page also references Windows-specific scenarios (e.g., installing a certificate from Key Vault on a Windows VM) and includes links and examples that are Windows-centric. There is no explicit mention of Linux-specific patterns, nor are there examples using Linux-native tools or shell scripting. The documentation assumes parity between Azure CLI and PowerShell, but PowerShell is a Windows-first tool, and its heavy inclusion may signal a bias toward Windows environments.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for tasks like secret retrieval and deployment.
  • Include references to Linux VM scenarios (e.g., installing certificates on Linux VMs) alongside Windows VM examples.
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux and macOS, possibly with screenshots or terminal output from those platforms.
  • Avoid referencing Windows-specific tools or scenarios without providing Linux equivalents or alternatives.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell (Windows-centric) in each section.
  • Add a note or section on best practices for Linux users when working with Azure Key Vault and ARM templates.
GitHub Create Pull Request
Azure Resource Manager Templates overview .../articles/azure-resource-manager/templates/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page exhibits moderate Windows bias. PowerShell is mentioned as the primary scripting tool for testing ARM templates (arm-ttk), with no equivalent Bash or Linux-native tool referenced. The authoring tools highlighted are Visual Studio and Visual Studio Code, both of which are strongly associated with Windows (though VS Code is cross-platform, Visual Studio is Windows-only). The CI/CD integration section references Azure DevOps and Visual Studio projects, which are more common in Windows environments. While deployment options include Azure CLI and Bash scripts, PowerShell is often mentioned first or exclusively in some contexts.
Recommendations
  • Include explicit Bash and Azure CLI examples for template testing and deployment, especially where PowerShell is referenced.
  • Mention cross-platform alternatives to Visual Studio for authoring templates, such as VS Code (with emphasis on its Linux support) or other editors.
  • Reference Linux-native CI/CD tools (e.g., GitHub Actions, Jenkins) alongside Azure DevOps and Visual Studio projects.
  • When listing deployment options, alternate the order or explicitly state Linux compatibility for each method.
  • Provide links to Linux-specific documentation or tutorials for ARM template authoring, testing, and deployment.
GitHub Create Pull Request
Azure Resource Manager Convert portal template to template spec ...re-resource-manager/templates/template-spec-convert.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based migration instructions and examples, referencing a PowerShell script as the primary automation method, and omitting any equivalent instructions or examples for Linux or cross-platform environments (such as Bash, Azure CLI, or REST API). The manual portal steps are platform-neutral, but all automation guidance is Windows-centric.
Recommendations
  • Provide equivalent migration instructions using Azure CLI or Bash scripts for Linux/macOS users.
  • Include REST API or ARM template-based migration options for cross-platform automation.
  • Explicitly mention platform compatibility for the PowerShell script and suggest alternatives for non-Windows environments.
  • Ensure that examples and tooling references are presented in a platform-neutral order, or offer both Windows and Linux options side-by-side.
GitHub Create Pull Request
Azure Resource Manager Use template deployment scripts | Microsoft Docs ...nager/templates/template-tutorial-deployment-script.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. PowerShell is the only supported scripting language for deployment scripts in the tutorial, and all inline script examples use PowerShell syntax. References to PowerShell escape characters and output handling are prominent. While Azure CLI examples are provided for some steps, the core deployment script resource only supports PowerShell, with no Bash or Linux shell alternatives. Windows tools and patterns (e.g., Visual Studio Code, PowerShell cmdlets) are mentioned first or exclusively, and there is no guidance for Linux-native scripting or troubleshooting.
Recommendations
  • Add support and examples for Bash scripts in deploymentScripts resources, if supported by the platform.
  • Provide equivalent Bash or shell script examples alongside PowerShell for all steps, especially for deployment script content.
  • Include troubleshooting instructions for Linux environments (e.g., file locations, error handling in Bash).
  • Mention Linux-native editors (e.g., Vim, Nano) and workflows in addition to Visual Studio Code.
  • Clarify platform limitations (e.g., if only PowerShell is supported, explicitly state this and provide guidance for Linux users).
  • Ensure CLI examples are as detailed and prominent as PowerShell examples, and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Azure Resource Manager Template functions - scope ...resource-manager/templates/template-functions-scope.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page focuses on ARM template scope functions and provides JSON-based examples that are platform-neutral. However, in the 'Next steps' section, deployment guidance is linked specifically to Azure PowerShell, a Windows-centric tool, without mention of Linux-friendly alternatives like Azure CLI or Bash scripting. There are no explicit Linux or cross-platform deployment examples, and PowerShell is referenced before any Linux-equivalent tooling.
Recommendations
  • Add links and examples for deploying ARM templates using Azure CLI, which is cross-platform and widely used on Linux.
  • In the 'Next steps' section, provide parity by including guidance for Bash and Azure CLI alongside PowerShell.
  • Where deployment tooling is referenced, avoid listing Windows/PowerShell options first; present CLI and PowerShell together, or in alphabetical order.
  • Explicitly state that the JSON templates and functions are platform-agnostic, and clarify that deployment can be performed from Windows, Linux, or macOS.
  • Consider adding a brief section or table comparing deployment commands across PowerShell, Azure CLI, and Bash to help users choose the best fit for their environment.
GitHub Create Pull Request
Azure Resource Manager Roll back on error to successful deployment .../azure-resource-manager/templates/rollback-on-error.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page presents PowerShell examples before Azure CLI examples, and uses Windows-style paths (e.g., c:\MyTemplates\azuredeploy.json) in PowerShell commands. The PowerShell section is detailed and uses Windows-centric tooling, which may suggest a Windows-first approach. There are no explicit Linux shell examples (e.g., Bash), nor are Linux-specific considerations or file path formats mentioned.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include Linux/Bash shell examples, especially for Azure CLI usage, and use Linux-style file paths (e.g., /home/user/templates/azuredeploy.json) in at least one example.
  • Add a note clarifying that both PowerShell and Azure CLI are cross-platform, and provide links to installation/use on Linux and macOS.
  • Where file paths are shown, provide both Windows and Linux formats, or use environment variables to indicate cross-platform compatibility.
  • Consider including troubleshooting or usage notes relevant to Linux environments (e.g., permissions, shell differences).
GitHub Create Pull Request
Azure Resource Manager Use ARM template test toolkit ...icles/azure-resource-manager/templates/test-toolkit.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is heavily focused on PowerShell as the only supported method for running the ARM template test toolkit, regardless of platform. Windows is presented first in installation instructions, and all examples (including Linux and macOS) require PowerShell rather than native shell commands or tools. There is no mention of Linux-native alternatives, and the toolkit itself is described as a set of PowerShell scripts, which may not be ideal for Linux users who prefer bash or other shell environments.
Recommendations
  • Provide bash or shell script examples for Linux users, or clarify if PowerShell is the only supported method.
  • Consider developing or documenting a cross-platform CLI wrapper or tool that does not require PowerShell.
  • List Linux installation instructions before Windows, or present all platforms together to avoid Windows-first ordering.
  • Explicitly state the lack of Linux-native alternatives if PowerShell is required, and suggest how Linux users can best integrate PowerShell into their workflows.
  • Document any limitations or differences in PowerShell usage on Linux/macOS compared to Windows, including file path conventions and permissions.
GitHub Create Pull Request
Azure Resource Manager Create portal forms for template spec ...anager/templates/template-specs-create-portal-forms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced first and more frequently than Azure CLI, especially for tasks like retrieving tenantId and objectId, and for creating template specs. The instructions for obtaining Azure Active Directory object IDs exclusively mention PowerShell cmdlets (Get-AzSubscription, Get-AzADUser, Get-AzADServicePrincipal) without CLI or cross-platform alternatives. Visual Studio Code is mentioned as an editor, but no Linux-specific tools or workflows are highlighted. There are no explicit Linux examples or shell commands, and the overall flow assumes familiarity with Windows-centric tools.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, especially for retrieving tenantId and objectId (e.g., az account show, az ad user show, az ad sp show).
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Mention cross-platform editors (such as Vim, nano, or gedit) alongside Visual Studio Code.
  • Clarify that all CLI commands work on Linux, macOS, and Windows, and provide shell syntax examples (bash/zsh) where appropriate.
  • Add notes or sections for Linux users, including file management and environment setup tips.
  • Ensure screenshots and instructions do not assume a Windows environment.
GitHub Create Pull Request
Azure Netapp Files Mount NFS volumes for virtual machines ...etapp-files-mount-unmount-volumes-for-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Linux and Windows instructions for mounting NFS volumes, but there is a slight Windows bias in the ordering and detail. The Windows section references Windows-specific tools and commands (e.g., the 'Mount' command), and the Windows mounting example is given in detail, while the Linux mounting section is less explicit about troubleshooting or advanced options. The Windows section also refers to mounting via SMB as a preferred alternative, but does not offer similar parity for Linux. Additionally, the Windows mounting instructions require a Linux step first (chmod), which may be confusing for Windows-only administrators.
Recommendations
  • Provide Linux troubleshooting tips and advanced mount options similar to those given for Windows (e.g., handling connection issues, recommended mount flags).
  • Include explicit Linux command-line examples for mounting NFSv3 and NFSv4.1, and clarify differences in support and behavior.
  • Offer parity in SMB mounting instructions for Linux clients, similar to the Windows dual-protocol guidance.
  • Reorder sections so that Linux and Windows instructions are presented in parallel, or clarify why one must precede the other (e.g., why chmod must be run from Linux before Windows can mount).
  • Reference Linux tools/utilities (e.g., nfs-utils, showmount) where appropriate, and provide links to their documentation.
  • Clarify limitations and best practices for both platforms equally, and avoid implying Windows is the default or preferred platform.
GitHub Create Pull Request
Azure Netapp Files Resize the capacity pool or a volume for Azure NetApp Files ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a mild Windows bias. REST API automation is linked with PowerShell examples, and the REST API section explicitly references 'REST API using PowerShell for Azure NetApp Files' before any mention of Linux or cross-platform scripting. There are no Linux-specific CLI or scripting examples (e.g., bash, curl, or Python), and PowerShell is the only automation tool mentioned for REST API usage. The Azure CLI section is platform-neutral, but the overall automation guidance leans toward Windows/PowerShell tools.
Recommendations
  • Add Linux/bash/curl examples for REST API usage alongside PowerShell examples.
  • Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows and Linux shells.
  • Include references to scripting with Python or other cross-platform languages for REST API automation.
  • Avoid listing PowerShell examples or links before Linux equivalents; present both options together or alternate their order.
  • Clarify that REST API automation can be performed from any OS, not just Windows/PowerShell.
GitHub Create Pull Request
Azure Netapp Files SMB performance best practices for Azure NetApp Files ...ure-netapp-files/azure-netapp-files-smb-performance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All operational examples, commands, and monitoring instructions are Windows-centric, using PowerShell cmdlets (e.g., Get-SmbClientNetworkInterface, set-SmbClientConfiguration), Windows tools (Performance Monitor, netstat, Hyper-V), and references to Windows OS versions. There are no Linux-specific SMB client examples, nor are Linux tools or configuration patterns mentioned. The documentation assumes Windows environments for both configuration and performance monitoring, omitting guidance for Linux users.
Recommendations
  • Add equivalent Linux SMB client configuration and performance tuning instructions (e.g., using smbclient, mount.cifs, or relevant kernel parameters).
  • Include Linux command-line examples for monitoring SMB connections and performance (e.g., using netstat, iostat, atop, or smbstatus).
  • Reference Linux SMB client support for SMB Multichannel, Signing, and Encryption, noting any differences or limitations.
  • Provide guidance on enabling and verifying RSS and accelerated networking in Linux environments.
  • Balance Windows and Linux coverage in all sections, ensuring that Linux administrators can follow best practices and monitor performance effectively.
GitHub Create Pull Request
Azure Netapp Files Configure application volume groups for SAP HANA using REST API ...les/configure-application-volume-group-sap-hana-api.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using Azure CLI and jq (both available on Windows and Linux, but Azure CLI is most commonly used in Windows-centric Azure environments) for all shell examples. There are no PowerShell-specific examples, but the instructions and code samples assume the use of Azure CLI and jq, without mentioning or providing Linux-specific alternatives (such as native bash parsing, curl-only examples, or guidance for Linux users who may not use jq). There is no mention of Linux-specific tools, nor are there examples for Linux-only environments or considerations for Linux users. The documentation also refers to Azure-specific constructs (such as AvSet, PPG, and delegated subnets) that are more familiar to Windows/Azure administrators, and does not provide parity guidance for Linux-centric SAP HANA deployments.
Recommendations
  • Add explicit Linux shell examples using bash and curl without Azure CLI or jq dependencies, or provide alternatives for jq (such as Python or native bash parsing).
  • Clarify that Azure CLI and jq are cross-platform, and provide installation instructions for Linux users.
  • Include notes or examples for Linux-only environments, such as using curl with manual token management, or using other Linux-native tools.
  • Provide guidance for Linux administrators on mapping Azure constructs (AvSet, PPG, delegated subnet) to typical Linux deployment patterns.
  • Ensure that all examples are presented in a way that is platform-neutral, or provide both Windows and Linux variants where relevant.
GitHub Create Pull Request
Azure Netapp Files Configure NFSv4.1 Kerberos encryption for Azure NetApp Files ...es/azure-netapp-files/configure-kerberos-encryption.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias in several areas: it relies on PowerShell commands (Set-ADComputer) for critical configuration steps, references Windows-specific tools (RSAT), and assumes the use of Active Directory Domain Services (AD DS) for Kerberos setup. These instructions are presented before or in place of Linux-native alternatives, despite the target NFS client being Linux. There are no examples or guidance for performing equivalent Kerberos/AD computer account configuration from Linux, nor mention of cross-platform alternatives for managing AD objects.
Recommendations
  • Provide Linux-native alternatives for managing Active Directory computer accounts, such as using 'ldapmodify', 'adcli', or 'realm' commands.
  • Include examples of configuring Kerberos encryption types for AD computer accounts from a Linux host, where possible.
  • Mention and link to cross-platform tools (e.g., Samba's 'net ads', 'ldapmodify') for AD integration and management.
  • Clarify which steps require Windows-only tools and which can be performed from Linux, and provide parity in instructions.
  • Add troubleshooting and verification steps for Linux environments, such as using 'klist', 'ldapsearch', or 'adcli info'.
GitHub Create Pull Request
Azure Netapp Files Create and manage Active Directory connections for Azure NetApp Files ...re-netapp-files/create-active-directory-connections.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell commands as the only example for managing Active Directory user encryption types and for registering Azure NetApp Files features. Windows-specific tools and patterns (e.g., Group Policy, registry keys, AD DS concepts) are referenced exclusively or before any Linux equivalents. There is a lack of Linux-focused examples, such as how to perform equivalent operations using Linux tools (e.g., ldapmodify, kadmin, or samba-tool), and no guidance is given for Linux administrators who may need to interact with AD DS or Kerberos. The documentation assumes familiarity with Windows administration and does not offer parity for Linux environments.
Recommendations
  • Provide Linux command-line examples for managing AD DS/Kerberos settings, such as using ldapmodify, kadmin, or samba-tool, alongside PowerShell examples.
  • Include instructions for configuring Kerberos encryption types and LDAP settings from Linux clients, especially for NFSv4.1 Kerberos volumes.
  • Reference Linux tools and configuration files (e.g., /etc/krb5.conf, /etc/ldap.conf) where appropriate, and explain how to verify or troubleshoot AD DS connectivity from Linux.
  • Add troubleshooting steps and best practices for Linux environments, such as renewing Kerberos tickets, mounting NFS shares, and handling LDAP timeouts.
  • Ensure that all feature registration and management steps are shown with both Azure CLI and PowerShell, and clarify which steps are OS-agnostic.
GitHub Create Pull Request
Azure Netapp Files Enable Active Directory Domain Services (AD DS) LDAP authentication for NFS volumes ...s/azure-netapp-files/configure-ldap-extended-groups.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows/Active Directory environments. It exclusively references Windows-based LDAP servers (Active Directory Domain Services and Microsoft Entra Domain Services), omits support for OpenLDAP or other third-party LDAP servers, and provides configuration guidance and screenshots using Windows tools (MMC snap-in, Multi-valued String Editor, Attribute Editor). Linux-specific examples and tools for managing LDAP attributes are missing, and Linux client configuration is only briefly mentioned and deferred to other documentation.
Recommendations
  • Add explicit Linux/OpenLDAP support or clarify the limitations and provide alternatives for Linux environments.
  • Include Linux-based examples for managing POSIX attributes (e.g., using ldapmodify, LDIF files, or phpldapadmin).
  • Provide parity in screenshots and step-by-step instructions for both Windows and Linux LDAP management tools.
  • Mention Linux tools and patterns (such as nslcd, sssd, or openldap utilities) where relevant, not just Windows MMC.
  • If OpenLDAP is unsupported, offer guidance for hybrid environments or migration strategies for Linux administrators.
GitHub Create Pull Request
Azure Netapp Files Configure network features for an Azure NetApp Files volume ...icles/azure-netapp-files/configure-network-features.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell examples and commands before Linux/Azure CLI equivalents, using Windows-centric tools (PowerShell) for feature registration and management, and referencing Windows-specific patterns (Active Directory, domain controllers) without equal Linux/NFS context. While Azure CLI and REST API options are included, PowerShell is often listed first or with more detail, and Linux-specific usage patterns are not highlighted.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and preferred by many Linux users.
  • Expand Linux/NFS-specific guidance, especially for scenarios involving DNS, domain controllers, or network security, to ensure parity with Windows/Active Directory coverage.
  • Include explicit Linux shell command examples (e.g., bash scripts for Azure CLI) where PowerShell is used.
  • Clarify that all CLI commands work on Linux, macOS, and Windows, and provide troubleshooting tips for Linux environments.
  • Add references to Linux authentication and identity management patterns where only Windows/Active Directory are mentioned.
  • Ensure screenshots and UI references do not assume a Windows environment (e.g., avoid Windows-specific UI elements or terminology).
GitHub Create Pull Request
Azure Netapp Files Convert an NFS volume between NFSv3 and NFSv4.1 with Azure NetApp Files ...in/articles/azure-netapp-files/convert-nfsv3-nfsv41.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias primarily in the feature registration section, where Azure PowerShell commands are presented first and in detail, with only a brief mention of Azure CLI as an alternative. The registration examples and command syntax are Windows/PowerShell-centric, and there is no explicit Linux shell example for registration. However, the main conversion workflow and mount/unmount examples are Linux-focused, using Linux commands and patterns.
Recommendations
  • Provide explicit Azure CLI examples for feature registration, including full command syntax and output, alongside PowerShell examples.
  • Present Azure CLI and PowerShell registration options in parallel, or lead with Azure CLI to better support Linux users.
  • Clarify that both Windows and Linux administrators can use either Azure CLI or PowerShell, and link to installation instructions for both tools.
  • Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific differences.
  • Add a short section on how to perform registration from a native Linux shell, including prerequisites (e.g., installing Azure CLI).
GitHub Create Pull Request
Azure Netapp Files Create volume replication for Azure NetApp Files ...etapp-files/cross-region-replication-create-peering.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting Azure PowerShell commands first and in detail for feature registration and status checking, while only briefly mentioning Azure CLI as an alternative. There are no Linux-specific examples or guidance, and the use of PowerShell is highlighted without equivalent Bash or Linux shell instructions. The overall workflow assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Provide step-by-step Azure CLI examples alongside PowerShell for all command-line operations, including feature registration and status checking.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Include screenshots or instructions for using the Azure CLI in Linux environments where applicable.
  • Ensure that any references to command-line tools do not prioritize Windows tools over cross-platform alternatives.
  • Add a section or note clarifying tool parity and recommending CLI usage for non-Windows users.
GitHub Create Pull Request
Azure Netapp Files Create a dual-protocol volume for Azure NetApp Files ...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several areas. Windows tools and workflows (Active Directory Users and Computers MMC snap-in, Attribute Editor) are described in detail, with step-by-step instructions and screenshots, while equivalent Linux-based LDAP management tools (such as ldapmodify, phpldapadmin, or command-line utilities) are not mentioned. The section on managing POSIX attributes is exclusively focused on Windows environments. Additionally, examples and instructions for configuring or managing LDAP attributes are provided only for Windows, with no Linux alternatives. The order of presentation also favors Windows tools and patterns, with Linux approaches relegated to references or omitted.
Recommendations
  • Add equivalent Linux-based instructions for managing LDAP POSIX attributes, such as using command-line tools (ldapmodify, ldapadd, ldapsearch) or graphical tools (phpldapadmin).
  • Include screenshots and step-by-step guidance for Linux LDAP management workflows.
  • Present both Windows and Linux examples side-by-side, or alternate their order to avoid Windows-first bias.
  • Reference common Linux LDAP server setups (OpenLDAP, 389 Directory Server) and provide guidance for attribute management in those environments.
  • Clarify that both Windows and Linux environments are supported and provide parity in documentation coverage.
GitHub Create Pull Request
Azure Netapp Files Disable showmount in Azure NetApp Files .../main/articles/azure-netapp-files/disable-showmount.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page primarily provides Azure PowerShell commands for managing the showmount feature, with PowerShell examples given first and in detail. While Azure CLI is briefly mentioned, no explicit Linux shell or CLI examples are provided, and no Linux-native tooling or workflows are discussed. The documentation assumes familiarity with Windows-centric tools and patterns, potentially making it less accessible for Linux-focused administrators.
Recommendations
  • Provide explicit Azure CLI command examples using bash syntax for registering, checking, and unregistering the feature.
  • Include instructions or examples for performing these operations from a Linux environment, such as using the Azure CLI in bash.
  • Clarify that both Windows and Linux users can use Azure CLI, and link to relevant Linux installation guides for Azure CLI.
  • Reorder examples so that Azure CLI (cross-platform) instructions appear before or alongside PowerShell examples.
  • Add a note or section addressing Linux administrators, highlighting any differences or considerations for Linux environments.
GitHub Create Pull Request
Azure Netapp Files Understand dual-protocol security style and permission behaviors in Azure NetApp Files ...ure-netapp-files/dual-protocol-permission-behaviors.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows/NTFS concepts before their UNIX/NFS equivalents, providing more detailed explanations for Windows tools and behaviors, and omitting practical Linux/NFS management examples (such as explicit CLI commands for permission management or troubleshooting). Windows terminology and tools (Active Directory, Windows RPC, NTFS ACLs) are described in greater depth and often appear first in lists or tables. Linux/NFS management is mentioned but lacks step-by-step guidance or parity in example depth.
Recommendations
  • Provide equal depth and clarity for Linux/NFS workflows, including explicit CLI examples (e.g., chown, chmod, nfs4_getfacl, nfs4_setfacl) for managing permissions and troubleshooting.
  • Ensure that both Windows and Linux tools are introduced together, or alternate which is presented first in lists and tables.
  • Add practical Linux/NFS scenarios, such as configuring LDAP for UNIX users, managing NFSv4.x ACLs, and mapping UNIX identities, with step-by-step instructions.
  • Clarify limitations and workarounds for Linux/NFS environments as thoroughly as for Windows/SMB, including GUI and CLI management options.
  • Reference Linux documentation and tools (e.g., man pages, open-source utilities) alongside Windows equivalents.
GitHub Create Pull Request
Azure Netapp Files Application resilience FAQs for Azure NetApp Files ...icles/azure-netapp-files/faq-application-resilience.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page shows a moderate Windows bias. SMB/Windows scenarios are described in detail, with specific features (SMB Transparent Failover, Continuous Availability) and supported workloads listed, most of which are Windows-centric (Citrix, FSLogix, MS SQL Server, MSIX app attach). Linux equivalents (e.g., Linux SQL Server) are explicitly excluded. In the Boomi section, recommendations for SMB are tied to Windows VMs, while NFS is tied to Linux VMs, but the SMB/Windows guidance is more prominent. There are no PowerShell examples, but Windows tools and features are mentioned before or instead of Linux alternatives. Some sections lack Linux-specific examples or parity in feature discussion.
Recommendations
  • Add explicit Linux examples for SMB-based workloads, including guidance for Linux SMB clients and their limitations or configuration.
  • Where Windows tools or features (e.g., SMB Continuous Availability, Transparent Failover) are discussed, clarify Linux support status and provide alternative approaches for Linux environments.
  • Avoid excluding Linux workloads (e.g., Linux SQL Server) without explanation; if unsupported, explain why and suggest alternatives.
  • Balance recommendations by listing Linux and Windows options together, rather than prioritizing Windows scenarios.
  • Include example configurations or best practices for Linux-based applications using SMB, if applicable.
  • Ensure that feature support tables or lists include both Windows and Linux workloads, or clearly state platform limitations.
GitHub Create Pull Request
Azure Netapp Files Understand Domain Name Systems in Azure NetApp Files ...icles/azure-netapp-files/domain-name-system-concept.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by consistently referencing Windows/Active Directory DNS as the default or best practice, providing examples and screenshots primarily from Windows environments, and listing Windows tools and patterns before Linux equivalents. Linux/BIND is mentioned only as an alternative, and practical Linux configuration steps or troubleshooting are missing. DNS management and troubleshooting are described with a Windows-centric approach, and command examples favor Windows syntax and context.
Recommendations
  • Include explicit Linux/BIND configuration examples and troubleshooting steps alongside Windows/Active Directory instructions.
  • Provide screenshots and walkthroughs for DNS management using Linux tools (e.g., BIND, systemd-resolved, etc.) in addition to Windows DNS Manager.
  • Present Linux and Windows tools (e.g., dig, nslookup) in parallel, with equal detail and context for both platforms.
  • Avoid language that implies Windows/Active Directory DNS is the only or preferred option; clarify that external DNS servers (such as BIND) are fully supported and provide best practices for their use.
  • Add guidance for secure dynamic DNS updates with Linux/BIND servers, including relevant configuration and authentication mechanisms.
  • Balance references to Microsoft documentation with links to authoritative Linux/BIND resources.
GitHub Create Pull Request
Azure Netapp Files Enable Continuous Availability on existing Azure NetApp Files SMB volumes ...p-files/enable-continuous-availability-existing-SMB.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All operational instructions and verification steps are centered on Windows systems, specifically referencing rebooting Windows servers and using PowerShell commands (get-smbconnection) to verify configuration. There are no examples or guidance for Linux or macOS clients, nor are cross-platform tools or methods mentioned.
Recommendations
  • Add instructions for Linux and macOS clients, including how to verify SMB Continuous Availability from those platforms.
  • Provide equivalent command-line examples for Linux (e.g., using smbclient, mount.cifs, or other relevant tools).
  • Clarify whether rebooting is required for non-Windows clients and provide platform-specific guidance.
  • Mention any differences or limitations in SMB CA support for non-Windows clients.
  • Reorder or parallelize instructions so that Windows and Linux/macOS guidance are presented together, ensuring parity.
GitHub Create Pull Request
Azure Netapp Files NFS FAQs for Azure NetApp Files ...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page displays Windows bias in the section addressing NFS access from Windows clients. It provides PowerShell commands and Windows-specific mount instructions, but does not offer equivalent Linux examples or commands. The Windows client troubleshooting is detailed, while Linux troubleshooting is omitted. In other sections, Linux is referenced (e.g., /etc/fstab), but Windows tools and patterns are given more prominence and detail where examples are present.
Recommendations
  • Provide equivalent Linux troubleshooting steps for NFS client issues, such as folder lookup performance.
  • Include Linux mount command examples alongside Windows examples, especially in sections where mounting is discussed.
  • When giving PowerShell commands for Windows, also provide the corresponding Linux shell commands (e.g., for NFS client configuration).
  • Ensure that for every Windows-specific tool or pattern mentioned, the Linux equivalent is described with equal detail and prominence.
  • Review the order of examples and explanations to avoid presenting Windows first by default; alternate or present both platforms together.
GitHub Create Pull Request
Azure Netapp Files Generate user and group quota reports for Azure NetApp Files volumes ...zure-netapp-files/generate-user-group-quota-reports.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing Azure PowerShell examples for feature registration and status checking, mentioning PowerShell before Azure CLI, and omitting direct Linux shell or CLI examples. The registration steps are shown using PowerShell syntax, which is native to Windows, and only briefly reference Azure CLI as an alternative without examples. There are no Linux-specific instructions or screenshots, and no mention of Linux shell commands or patterns for quota report generation.
Recommendations
  • Provide explicit Azure CLI examples for feature registration and status checking alongside PowerShell, with full command syntax.
  • Include Linux shell usage patterns or instructions for quota report generation, where applicable.
  • Ensure screenshots and UI instructions are platform-neutral or show parity between Windows and Linux environments.
  • Mention cross-platform compatibility for CLI tools and clarify how Linux users can perform the same operations.
  • Consider adding a section for Linux administrators outlining steps using bash or other common Linux tools.
GitHub Create Pull Request
Azure Netapp Files SMB FAQs for Azure NetApp Files ...-docs/blob/main/articles/azure-netapp-files/faq-smb.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. Most examples, troubleshooting steps, and tool references are exclusively for Windows environments (e.g., MMC, Active Directory Users and Computers, Windows Server, Windows updates, DFS Namespace). There is little to no mention of Linux clients, tools, or configuration patterns, and no Linux-specific examples or troubleshooting guidance are provided. The documentation assumes the reader is operating in a Windows-centric ecosystem, omitting parity for Linux SMB clients and management tools.
Recommendations
  • Add examples and troubleshooting steps for accessing Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or Nautilus).
  • Include Linux equivalents for management tasks, such as modifying share permissions or viewing open files (e.g., using setfacl, getfacl, or smbstatus).
  • Reference Linux authentication and integration patterns, such as joining SMB shares to Samba or using Kerberos from Linux.
  • Provide guidance on configuring clock synchronization and network authentication on Linux systems.
  • Mention Linux support for SMB features (e.g., offline files, DFS-N, Alternate Data Streams) and note any limitations or differences.
  • Balance references to Windows tools (MMC, ADUC, PowerShell) with Linux alternatives or note when features are Windows-only.
GitHub Create Pull Request
Azure Netapp Files azure-netapp-files-create-volumes-smb.md ...e-netapp-files/includes/smb-continuous-availability.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias by focusing exclusively on Windows-centric workloads and tools (Citrix, FSLogix, MSIX app attach, SQL Server on Windows), explicitly stating that Linux SQL Server is not supported, and referencing Windows-specific security privileges (SeSecurityPrivilege) and Active Directory. There are no examples, guidance, or mention of Linux equivalents or support for Linux workloads.
Recommendations
  • Clearly state the lack of Linux support in the introduction and provide a roadmap or expected timeline for Linux parity if possible.
  • Include a section for Linux users explaining current limitations and any alternative approaches or workarounds.
  • If/when Linux support is added, provide equivalent examples and instructions for Linux environments (e.g., using Linux SMB clients, Linux-based SQL Server, and relevant security configurations).
  • Reference cross-platform tools and patterns where possible, or clarify when features are Windows-only.
  • Solicit feedback from Linux users to understand their needs and document any common use cases or requests.
GitHub Create Pull Request
Azure Netapp Files Understand Kerberos in Azure NetApp Files ...docs/blob/main/articles/azure-netapp-files/kerberos.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows Active Directory as the only supported KDC, prioritizing Windows terminology and tools (such as Event Viewer, MMC, PowerShell, and setspn), and providing detailed workflows and troubleshooting steps for Windows environments. Linux-specific tools, workflows, and examples are either missing or mentioned only in passing, with little practical guidance for Linux administrators. Windows patterns and troubleshooting steps are described before or instead of Linux equivalents, and there is a lack of parity in example commands and administrative procedures for Linux environments.
Recommendations
  • Add explicit Linux administration examples, such as using kadmin, klist, ktutil, and other standard Linux Kerberos tools for keytab and principal management.
  • Provide Linux-specific troubleshooting steps and error messages, including references to syslog, journalctl, and common Linux Kerberos log locations.
  • Include example workflows for configuring Kerberos realms and principals on Linux clients and servers, not just via Active Directory.
  • Clarify how non-Windows KDCs (such as MIT Kerberos or FreeIPA) can be integrated or why they are unsupported, and offer guidance for Linux environments where AD is not present.
  • Balance references to Windows tools (Event Viewer, MMC, PowerShell, setspn) with Linux equivalents, and ensure that Linux commands are presented alongside Windows commands where relevant.
  • Expand documentation of NFS Kerberos workflows to include Linux client configuration, troubleshooting, and best practices, with step-by-step instructions.
GitHub Create Pull Request
Azure Netapp Files Understand name mapping using LDAP in Azure NetApp Files ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol-name-mapping.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively describing the name mapping process using Windows tools (Active Directory Users and Computers MMC), without mentioning or providing equivalent steps for Linux LDAP management tools. The instructions and screenshots focus on Windows environments first, and there are no examples or guidance for performing similar tasks on Linux LDAP servers or with Linux-native tools.
Recommendations
  • Add instructions and examples for configuring asymmetric name mapping using common Linux LDAP management tools (e.g., ldapmodify, phpldapadmin, or command-line utilities).
  • Include screenshots or walkthroughs for editing LDAP attributes on Linux systems.
  • Present both Windows and Linux approaches side-by-side, or at least mention Linux alternatives when describing Windows-specific steps.
  • Clarify that the process can be performed on non-Windows LDAP servers and provide references or links to relevant Linux documentation.
GitHub Create Pull Request
Azure Netapp Files Understand lightweight directory access protocol (LDAP) basics in Azure NetApp Files ...-netapp-files/lightweight-directory-access-protocol.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing primarily on Microsoft Active Directory as the LDAP server, mentioning Windows-centric tools and patterns (such as nslookup with Windows syntax), and providing examples and configuration details for Windows environments before Linux equivalents. Linux/UNIX alternatives (such as FreeIPA, OpenLDAP, Red Hat Directory Server) are mentioned only in a note and lack detailed examples or parity in instructions. There is a lack of Linux command-line examples and configuration guidance, and the documentation assumes familiarity with Windows tools and terminology.
Recommendations
  • Provide equal coverage and configuration examples for Linux-based LDAP servers (e.g., FreeIPA, OpenLDAP, Red Hat Directory Server) alongside Active Directory.
  • Include Linux command-line examples (e.g., using dig, ldapsearch) for querying LDAP service records and troubleshooting.
  • Present Linux/UNIX tools and patterns before or alongside Windows tools to avoid ordering bias.
  • Expand documentation to cover schema extension and attribute mapping for Linux LDAP servers, not just Active Directory.
  • Ensure that all features and limitations are described for both Windows and Linux LDAP environments, with clear guidance for each.
GitHub Create Pull Request
Azure Netapp Files Understand LDAP schemas in Azure NetApp Files ...files/lightweight-directory-access-protocol-schemas.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. It exclusively references Microsoft Active Directory as the LDAP server, describes schema and attribute management only in terms of Windows tools (ADSI Edit), and provides examples and screenshots solely from a Windows environment. There are no mentions of Linux LDAP servers (such as OpenLDAP), nor any guidance or examples for configuring equivalent schema or attribute indexing in Linux environments. The documentation assumes the reader is using Windows and omits Linux-specific patterns, tools, or best practices.
Recommendations
  • Add sections describing how RFC 2307bis schemas and attribute indexing are managed in popular Linux LDAP servers (e.g., OpenLDAP, 389 Directory Server).
  • Provide Linux-specific examples for schema inspection and modification, such as using ldapmodify, slapd.conf, or LDIF files.
  • Include screenshots or command-line examples from Linux environments to illustrate equivalent configuration steps.
  • Mention Linux tools (e.g., ldapsearch, ldapmodify) and provide parity in instructions for both Windows and Linux administrators.
  • Clarify that Azure NetApp Files supports LDAP servers beyond Active Directory and provide guidance for non-Windows environments.
GitHub Create Pull Request
Azure Netapp Files Manage file access logs in Azure NetApp Files ...articles/azure-netapp-files/manage-file-access-logs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a Windows bias in several ways: instructions for setting SACLs for SMB shares are provided only for Windows administration hosts, with step-by-step GUI instructions specific to Windows. There is no equivalent example or detailed steps for Linux environments, even though dual-protocol volumes with UNIX security style are mentioned. Windows tools and patterns (e.g., right-click, Properties, Security tab) are described in detail, while Linux methods are referenced only via a link, not explained inline. Windows instructions are presented first and more prominently.
Recommendations
  • Provide explicit, step-by-step instructions for setting Audit ACEs and ACLs on Linux, including relevant commands (e.g., setfacl, nfs4_setfacl) and examples.
  • Ensure parity in detail and clarity between Windows and Linux sections, including screenshots or terminal output for Linux where appropriate.
  • Present Windows and Linux instructions side-by-side or in parallel tabs, rather than Windows first and Linux as a reference.
  • Mention Linux tools and patterns (such as command-line utilities) directly in the documentation, not only via external links.
  • Clarify which steps apply to which OS, and avoid assuming the administrator is using Windows unless the protocol or security style requires it.
GitHub Create Pull Request
Azure Netapp Files Manage SMB share ACLs in Azure NetApp Files ...-netapp-files/manage-smb-share-access-control-lists.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively describes Windows-based methods for managing SMB share ACLs in Azure NetApp Files, focusing on Windows Explorer and Microsoft Management Console (MMC). There are no examples or instructions for performing these tasks from Linux or via cross-platform tools, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add instructions or examples for viewing and modifying SMB share ACLs from Linux systems, such as using smbclient, smbcacls, or other Samba utilities.
  • Clarify whether share ACL management is possible from non-Windows platforms, and if not, explicitly state this limitation.
  • If possible, provide PowerShell and CLI examples that can be run on Linux (e.g., via PowerShell Core or Azure CLI).
  • Include a comparison table of management options across platforms (Windows, Linux, macOS) to help users understand platform limitations and capabilities.
  • Mention any REST API or SDK options for managing SMB share ACLs, if available, to support automation and cross-platform scenarios.
GitHub Create Pull Request
Azure Netapp Files Modify an Active Directory Connection for Azure NetApp Files ...re-netapp-files/modify-active-directory-connections.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by focusing exclusively on Active Directory (a Windows-centric technology), referencing Windows tools and concepts (such as 'Active Directory Sites and Services', 'group policy', and 'NTFS permissions'), and omitting any Linux-specific examples or equivalent tooling. The instructions and field descriptions assume a Windows environment and do not provide guidance for Linux administrators or integration with Linux-based directory services (e.g., OpenLDAP).
Recommendations
  • Add examples or guidance for integrating Azure NetApp Files with Linux-based directory services, such as OpenLDAP or FreeIPA, if supported.
  • Include Linux command-line examples for relevant configuration steps, such as modifying LDAP settings or Kerberos configuration.
  • Mention Linux tools and configuration files (e.g., /etc/krb5.conf, /etc/ldap.conf) where applicable, alongside Windows tools.
  • Clarify whether features like AES encryption, LDAP signing, and SMB server prefix changes have specific considerations for Linux clients or servers.
  • Provide parity in troubleshooting steps and references for both Windows and Linux environments.
GitHub Create Pull Request
Azure Netapp Files Ways to monitor Azure NetApp Files ...icles/azure-netapp-files/monitor-azure-netapp-files.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is mentioned explicitly as a method to retrieve Activity log entries, while Linux equivalents (such as Bash or Azure CLI on Linux) are not detailed. In the capacity utilization section, Windows is mentioned before Linux clients, and no specific Linux commands or tools are provided. There is a lack of Linux-specific examples or guidance throughout the page.
Recommendations
  • Provide explicit Linux/Bash/Azure CLI examples alongside PowerShell for retrieving Activity logs.
  • Ensure Linux tools and commands (e.g., df, du, Azure CLI on Linux) are described in capacity monitoring sections.
  • Alternate the order of mentioning Windows and Linux clients to avoid Windows-first bias.
  • Include screenshots or step-by-step instructions for Linux environments where relevant.
  • Reference cross-platform tools and clarify any differences in usage between Windows and Linux.
GitHub Create Pull Request
Azure Netapp Files Understand SMB file permissions in Azure NetApp Files ...-netapp-files/network-attached-file-permissions-smb.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page focuses exclusively on Windows-centric concepts such as NTFS ACLs and references Microsoft documentation. There are no examples or mentions of Linux tools, commands, or approaches for managing SMB file permissions, nor is there guidance for Linux administrators. The terminology and links are Windows-specific, and Linux parity is not addressed.
Recommendations
  • Include examples of managing SMB file permissions from Linux clients, such as using 'smbclient', 'setfacl', or 'getfacl'.
  • Provide guidance on how Linux users can view and modify NTFS ACLs on Azure NetApp Files SMB shares.
  • Reference relevant Linux documentation or tools alongside Microsoft/Windows documentation.
  • Clarify any limitations or differences when accessing SMB volumes from Linux versus Windows.
  • Add a section comparing Windows and Linux approaches to SMB permissions management.
GitHub Create Pull Request
Azure Netapp Files Migrate volumes to Azure NetApp Files ...ob/main/articles/azure-netapp-files/migrate-volumes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples and referencing a PowerShell migration assistant workflow script as the primary automation method. The feature registration steps are shown first using Azure PowerShell, with Azure CLI only mentioned as an alternative. There are no Linux shell (bash) or cross-platform CLI examples for migration workflow automation, and no Linux-specific guidance or parity in scripting. The documentation assumes familiarity with Windows tooling and patterns, potentially making it less accessible to Linux users.
Recommendations
  • Provide equivalent Linux/bash shell examples for feature registration and migration workflow steps using Azure CLI.
  • Include a Linux shell script sample for the migration assistant workflow, similar to the PowerShell script referenced.
  • Present Azure CLI commands before or alongside PowerShell commands to avoid Windows-first ordering.
  • Explicitly mention cross-platform support and clarify that all steps can be performed from Linux/macOS environments.
  • Add troubleshooting and environment setup notes for Linux users (e.g., installing Azure CLI, authentication methods).
GitHub Create Pull Request
Azure Netapp Files Monitor the capacity of an Azure NetApp Files volume ...articles/azure-netapp-files/monitor-volume-capacity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation presents Windows client methods before Linux equivalents, provides more detailed instructions and screenshots for Windows (File Explorer and dir command), and references PowerShell in the REST API section. Windows-specific tools and patterns are mentioned explicitly, while Linux coverage is more limited and less visually supported.
Recommendations
  • Present Windows and Linux client instructions in parallel or alternate the order to avoid Windows-first bias.
  • Include equivalent screenshots and step-by-step instructions for Linux tools (e.g., graphical file managers, terminal commands).
  • Reference Linux automation tools (such as shell scripts or Ansible) alongside PowerShell in REST API usage examples.
  • Expand Linux-specific troubleshooting and usage notes to match the depth provided for Windows.
  • Ensure parity in visual aids and command explanations for both platforms.
GitHub Create Pull Request
Azure Netapp Files Understand NAS file permissions in Azure NetApp Files ...zure-netapp-files/network-attached-file-permissions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates Windows bias by presenting Windows SMB inheritance controls first, including a screenshot of the Windows interface, while Linux/NFS equivalents are described only in text and with less detail. Windows tools and patterns (advanced permission view, GUI screenshot) are highlighted, whereas Linux/NFS methods (umask, setgid, ACL flags) are mentioned briefly and without examples or visuals. No Linux command-line examples or screenshots are provided.
Recommendations
  • Add Linux/NFS command-line examples (e.g., setfacl, chmod, chown) for managing inheritance and permissions.
  • Include screenshots or terminal output demonstrating how to view and set inheritance flags on NFS shares.
  • Present NFS/Linux methods before or alongside Windows/SMB methods to avoid ordering bias.
  • Expand explanations of Linux/NFS permission management to match the detail given for Windows/SMB.
  • Clarify differences in inheritance handling between NFSv3 and NFSv4.1 with practical examples.
GitHub Create Pull Request
Azure Netapp Files Understand NAS protocols in Azure NetApp Files ...ure-netapp-files/network-attached-storage-protocols.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. SMB (Windows protocol) is described with more official support and detail, and Windows terminology (NTFS, SID, Active Directory) is used throughout, often before or instead of Linux equivalents. Linux (NFS/Samba) support is described as unofficial for SMB, and there are no explicit Linux command-line examples for SMB access or configuration. Windows tools and concepts (NTFS ACLs, SID translation, Active Directory) are referenced more frequently and in greater detail than their Linux counterparts.
Recommendations
  • Provide Linux/Samba command-line examples for accessing SMB shares and managing permissions, alongside Windows instructions.
  • Clarify and expand on official support for Linux SMB clients (Samba), including troubleshooting and configuration guidance.
  • Mention Linux equivalents (e.g., POSIX ACLs, idmap, Kerberos configuration) whenever Windows-specific tools or terminology are introduced.
  • Balance references to Windows and Linux identity management systems (Active Directory vs. LDAP/SSSD) and explain integration steps for both.
  • Include examples and documentation for configuring dual-protocol volumes from both Windows and Linux clients, not just Windows-centric workflows.
  • Ensure that Linux tools and patterns (e.g., getfacl/setfacl, mount.cifs, nfs-utils) are described with equal prominence to Windows tools.
GitHub Create Pull Request
Azure Netapp Files Understand NAS share permissions in Azure NetApp Files ...e-netapp-files/network-attached-storage-permissions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: SMB share management is described exclusively via Windows tools (MMC console, Windows Explorer), with no mention of Linux or cross-platform alternatives for managing SMB shares or ACLs. Examples and screenshots for SMB features (access-based enumeration, nonbrowsable shares, encryption) are all shown in a Windows context, with no Linux or macOS equivalents. The documentation does not provide Linux command-line examples (e.g., using smbclient, setfacl, or mount.cifs) for SMB share access or permission management, nor does it discuss how Linux clients interact with these features.
Recommendations
  • Include Linux-based examples for managing and accessing SMB shares, such as using smbclient, mount.cifs, or setfacl.
  • Describe how SMB share permissions and features (access-based enumeration, nonbrowsable shares, encryption) behave or can be verified from Linux clients.
  • Mention cross-platform tools or methods for managing SMB ACLs, such as using Samba utilities or Azure CLI/REST API, if available.
  • Add screenshots or command-line output from Linux environments to illustrate parity with Windows examples.
  • Clarify any limitations or differences in feature support between Windows and Linux clients for Azure NetApp Files SMB shares.
GitHub Create Pull Request
Azure Netapp Files Understand NFS group memberships and supplemental groups for Azure NetApp Files ...-netapp-files/network-file-system-group-memberships.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing on Microsoft Active Directory LDAP implementation, referencing Windows group membership logic, and providing examples using Windows tools (e.g., ldp.exe). There are no examples or guidance for Linux LDAP servers (such as OpenLDAP), nor are Linux command-line tools (like ldapsearch) mentioned. The documentation assumes a Windows-centric environment and omits Linux-specific patterns or alternatives.
Recommendations
  • Include examples of configuring and querying group memberships using Linux LDAP servers (e.g., OpenLDAP).
  • Provide sample commands using Linux tools such as ldapsearch to illustrate how supplemental groups can be queried.
  • Mention Linux schema attributes and group management logic alongside Windows/Active Directory equivalents.
  • Clarify whether Azure NetApp Files supports non-Active Directory LDAP servers and, if so, provide parity documentation for those environments.
  • Balance screenshots and walkthroughs by showing both Windows and Linux administrative interfaces or command-line outputs.
GitHub Create Pull Request
Azure Netapp Files Access an Azure NetApp Files object REST API-enabled volume with S3-compatible clients ...articles/azure-netapp-files/object-rest-api-browser.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by describing certificate installation using Windows GUI tools and terminology (Edge browser, Certificate window, Trusted Root Certification Authorities) without mentioning Linux equivalents. S3 Browser, a Windows-only tool, is featured with no alternative for Linux users. AWS CLI installation is described for both Windows and Linux, but the certificate installation steps are only detailed for Windows, leaving Linux users without guidance.
Recommendations
  • Add instructions for installing certificates on Linux systems (e.g., using update-ca-certificates or trust anchors).
  • Include a cross-platform S3 client example (e.g., Cyberduck, rclone, or s3cmd) with Linux installation and usage steps.
  • Present certificate installation steps for both Windows and Linux in parallel, or in separate sections, to ensure parity.
  • Avoid using Windows-specific terminology exclusively; clarify steps for macOS and Linux environments.
  • Explicitly mention limitations of S3 Browser (Windows-only) and suggest alternatives for other platforms.
GitHub Create Pull Request
Azure Netapp Files Azure VMware Solution datastore performance considerations for Azure NetApp Files ...p-files/performance-azure-vmware-solution-datastore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. Windows tools and patterns (NTFS, volume shadow copies, Windows Server disk striping) are mentioned alongside Linux equivalents, but Windows examples and links are often listed before Linux ones. The 'Next steps' section lists Windows disk striping before Linux NFS mount options. There is a lack of explicit Linux command examples (e.g., for LVM or xfs_freeze), and monitoring instructions focus on vCenter Server and Azure Console/API, omitting Linux CLI or open-source monitoring tools. Powershell or Windows-centric management is implied in some recommendations.
Recommendations
  • Provide explicit Linux command examples for disk striping (e.g., LVM, mdadm) and snapshot operations (e.g., xfs_freeze).
  • List Linux and Windows options in parallel, or alternate which is mentioned first to avoid 'windows_first' ordering.
  • Include links to Linux documentation for disk striping and filesystem management (e.g., LVM, XFS, ext4).
  • Add Linux monitoring tool examples (e.g., iostat, nmon, atop) for datastore performance, alongside vCenter and Azure Console/API.
  • Clarify that recommendations apply equally to Linux and Windows, and provide parity in example depth and detail.
GitHub Create Pull Request
Azure Netapp Files Understand NFSv4.x access control lists in Azure NetApp Files ...rticles/azure-netapp-files/nfs-access-control-lists.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a Windows bias in several ways: Windows terminology and concepts (NTFS, SMB, ACE/ACL links to Windows docs) are introduced before or alongside Linux/NFS equivalents, and Windows-centric patterns (user mapping, dual-protocol behaviors) are described in detail. References to Windows tools, documentation, and concepts are frequent, while Linux/NFS-specific tools and workflows are less emphasized or introduced later. The page does provide Linux command examples (nfs4_getfacl, nfs4_setfacl), but Windows concepts are often foregrounded.
Recommendations
  • Introduce NFS/Linux concepts first before referencing Windows/NTFS/SMB equivalents.
  • Link to Linux/NFS documentation (e.g., man pages for nfs4_acl, nfs4_getfacl, nfs4_setfacl) before or alongside Windows docs.
  • Provide more Linux/NFS-specific workflows and troubleshooting steps, such as common Linux errors, configuration files, and best practices.
  • Reduce reliance on Windows-centric terminology (e.g., ACE/ACL links to Windows docs) and ensure parity with Linux/NFS documentation.
  • Clarify dual-protocol sections to equally address Linux and Windows user mapping and access control, not just Windows-to-Linux mapping.
  • Add Linux-specific examples for LDAP integration, troubleshooting, and ACL management.
  • Ensure that all screenshots and UI references are relevant to both Linux and Windows users, or provide Linux equivalents where possible.
GitHub Create Pull Request
Azure Netapp Files Re-establish deleted volume replication relationships in Azure NetApp Files ...tapp-files/reestablish-deleted-volume-relationships.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing Azure PowerShell commands as the primary method for feature registration, with CLI alternatives mentioned only secondarily and without explicit Linux shell examples. No Linux-specific instructions or screenshots are provided, and the initial registration steps focus on PowerShell, which is most commonly used on Windows.
Recommendations
  • Provide explicit Azure CLI examples for feature registration and status checking, including full command syntax and sample output.
  • Include Linux shell (bash) usage patterns for Azure CLI commands, such as how to install the CLI and run the commands on Linux.
  • Clarify that both PowerShell and CLI methods are supported on all platforms, and avoid presenting PowerShell as the default or first option.
  • Add screenshots or instructions showing the process on Linux/macOS terminals where relevant.
  • Ensure parity in troubleshooting and operational steps for both Windows and Linux environments.
GitHub Create Pull Request
Azure Netapp Files Understand Server Message Block support in Azure NetApp Files ...cles/azure-netapp-files/sever-message-block-support.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a Windows bias in several ways: Windows terminology, tools, and features are referenced throughout, often without equivalent Linux examples or explanations. Windows-centric features (such as NTFS semantics, VSS shadow copy for Hyper-V, and references to Windows-specific FSCTL codes) are described in detail, while Linux client behaviors and configuration patterns are rarely mentioned or are only briefly noted. The documentation often links to Windows documentation and uses Windows terminology as the default, with Linux or UNIX features described as exceptions or disabled. There is a lack of Linux-specific configuration examples, troubleshooting guidance, and parity in feature explanations.
Recommendations
  • Add explicit examples and guidance for configuring and accessing SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or relevant Linux tools).
  • Include Linux/UNIX equivalents for Windows-specific features or clarify how features behave for Linux clients (e.g., file permissions, delete semantics, offline files, symlink handling).
  • Provide troubleshooting steps and performance tuning recommendations for Linux clients, not just Windows.
  • Reference Linux documentation and tools alongside Windows ones, ensuring that links and explanations are balanced.
  • Clarify which features are relevant or behave differently for Linux clients, especially in dual-protocol or mixed environments.
  • Where Windows terminology is used (e.g., NTFS, VSS, FSCTL), provide Linux analogs or explain the impact for non-Windows clients.
GitHub Create Pull Request
Azure Netapp Files How Azure NetApp Files snapshots work .../articles/azure-netapp-files/snapshots-introduction.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by listing PowerShell as a primary tool for snapshot management, mentioning it before Linux alternatives, and providing direct links to PowerShell modules. There are no explicit Linux shell (bash) or scripting examples, nor references to Linux-specific tools or workflows. The documentation refers to Windows-centric scripting (PowerShell) and omits parity for Linux users, such as bash scripts or Linux CLI usage patterns.
Recommendations
  • Add explicit Linux CLI/bash examples for snapshot management alongside PowerShell examples.
  • Mention Linux tools and workflows (e.g., shell scripts, cron jobs) for automation and management.
  • Ensure that references to Azure CLI are accompanied by Linux usage notes and examples.
  • Present both Windows and Linux options together, or alternate their order to avoid 'Windows first' bias.
  • Include links to Linux-specific documentation or community resources for Azure NetApp Files.
  • Clarify that all listed tools (Azure CLI, REST API, PowerShell) are cross-platform, and provide usage guidance for Linux environments.
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files tools ...ob/main/articles/azure-netapp-files/tools-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page lists several tools for Azure NetApp Files, but only provides explicit mention of a PowerShell-based tool (ANFHealthCheck), with no equivalent Linux shell or cross-platform alternatives described. The monitoring and automation examples (ANFCapacityManager, ANFHealthCheck) are Windows-centric, and there are no Linux CLI, Bash, or cross-platform scripting examples. This suggests a bias toward Windows and PowerShell environments, with missing Linux-specific guidance.
Recommendations
  • Provide equivalent Linux/Bash examples or scripts for monitoring and reporting tasks, such as an ANFHealthCheck alternative using Bash, Python, or Azure CLI.
  • Explicitly mention cross-platform compatibility for tools, or clarify if they are Windows-only.
  • Include references to Linux-native automation (e.g., cron jobs, shell scripts) for capacity management and health checks.
  • Add documentation or links for using Azure CLI and REST API for NetApp Files management on Linux.
  • Ensure that infrastructure-as-code examples (Terraform, Bicep) include Linux usage notes or examples.
GitHub Create Pull Request
Azure Netapp Files Understand data encryption in Azure NetApp Files ...icles/azure-netapp-files/understand-data-encryption.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows/SMB encryption topics, referencing Windows-specific tools and patterns (such as UNC hardening, Group Policy, and registry settings), and providing configuration guidance primarily for Windows Active Directory environments. Linux/NFS encryption is covered, but with less depth and without explicit Linux client configuration examples. There are no Linux-specific command-line or tool references, and Windows terminology and features are introduced before their Linux equivalents.
Recommendations
  • Include Linux client configuration examples for NFS Kerberos encryption, such as how to set up krb5p on a Linux system.
  • Provide parity in example commands and troubleshooting steps for both Windows (PowerShell, Group Policy) and Linux (shell commands, configuration files).
  • Reference Linux-based LDAP servers (e.g., OpenLDAP) and describe how to enable LDAP signing and StartTLS in those environments.
  • Balance the order of presentation so that Linux/NFS and Windows/SMB topics are introduced with equal prominence.
  • Add links to Linux documentation for SMB and NFS encryption, such as Samba and NFS client/server guides.
  • Clarify which features and recommendations apply to non-Windows environments, and provide guidance for mixed OS deployments.
GitHub Create Pull Request
Azure Netapp Files Understand path lengths in Azure NetApp Files ...articles/azure-netapp-files/understand-path-lengths.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing more detailed explanations, examples, and screenshots for Windows/SMB scenarios than for Linux/NFS. Windows tools and configuration steps (such as registry edits, Group Policy, and UNC path handling) are covered extensively, while Linux/NFS examples and troubleshooting are minimal and less visually supported. Windows terminology and tools are introduced first and in greater detail, and Linux equivalents (such as mounting options or path querying) are not given equal prominence or depth.
Recommendations
  • Add more Linux/NFS-focused examples, including screenshots of error messages and configuration dialogs where applicable.
  • Provide step-by-step instructions for extending NFS path limits or troubleshooting NFS path errors, similar to the Windows registry and Group Policy sections.
  • Introduce Linux tools and commands (e.g., getconf, mount options, fstab settings) with the same level of detail as Windows tools.
  • Ensure that both Windows and Linux approaches are presented in parallel, with neither platform given priority in order or depth.
  • Include guidance for Linux users on handling dual-protocol scenarios, such as mapping NFS mounts to deeper directories to avoid path length issues.
  • Balance the use of screenshots and visual aids between Windows and Linux environments.
GitHub Create Pull Request
Azure Netapp Files Troubleshoot volume errors for Azure NetApp Files ...in/articles/azure-netapp-files/troubleshoot-volumes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: troubleshooting steps and error resolutions frequently reference Active Directory Domain Services (AD DS), Microsoft Entra Domain Services, and Windows-centric concepts (such as machine accounts, OU paths, and Kerberos errors) without equivalent detail for Linux-based directory services or environments. PowerShell commands are provided for Kerberos configuration, but Linux CLI alternatives are not. Examples and troubleshooting steps for mounting, authentication, and user mapping focus on Windows/AD scenarios, with Linux/NFS details appearing only in specific sections and often as secondary considerations. There are no Linux-specific troubleshooting commands (e.g., ldapsearch, klist, systemctl) for diagnosing LDAP/Kerberos/NFS issues, and Windows tools/patterns are mentioned first or exclusively in many cases.
Recommendations
  • Provide Linux CLI equivalents for all PowerShell commands (e.g., using ldapsearch, kinit, klist, samba-tool, etc.).
  • Include troubleshooting steps for common Linux directory services (such as OpenLDAP, FreeIPA, or Samba AD) where relevant.
  • Balance examples by presenting both Windows and Linux scenarios for mounting, authentication, and user mapping errors.
  • Add Linux-specific error messages and their resolutions, especially for NFS, Kerberos, and LDAP troubleshooting.
  • When referencing AD DS or Microsoft Entra, also mention how similar issues would be approached in Linux environments.
  • Ensure that Linux tools and commands are mentioned alongside or before Windows tools where appropriate.
GitHub Create Pull Request
Azure Netapp Files Understand guidelines for Active Directory Domain Services site design and planning ...rstand-guidelines-active-directory-domain-service-site.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-centric tools (such as Active Directory Sites and Services), using Windows terminology and examples first, and omitting Linux-specific configuration steps or tools. While Linux clients are mentioned in the context of Kerberos authentication, there are no Linux-focused examples, screenshots, or guidance for managing AD DS site topology or verifying connectivity from Linux systems.
Recommendations
  • Include Linux-specific examples for verifying AD DS connectivity, such as using 'dig', 'ldapsearch', or 'kinit' from Linux clients.
  • Provide guidance or screenshots for managing AD DS site topology using cross-platform or command-line tools (e.g., PowerShell Core, samba-tool, or relevant Linux utilities).
  • Add explicit instructions for Linux administrators on how to validate DNS SRV records and Kerberos configuration from Linux systems.
  • Balance the order of presentation so that Linux scenarios and tools are described alongside or before Windows equivalents when relevant.
  • Clarify any differences in AD DS integration steps for Linux vs. Windows clients, especially for NFSv4.1 Kerberos and LDAP authentication.
GitHub Create Pull Request
Azure Netapp Files Use DFS-N and DFS Root Consolidation with Azure NetApp Files ...s-n-and-dfs-root-consolidation-with-azure-netapp-files.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows Server DFS Namespaces, Windows GUI tools, and PowerShell commands. All examples, instructions, and screenshots are for Windows environments, with no mention of Linux equivalents, cross-platform alternatives, or guidance for non-Windows users. The use of Windows-specific terminology and tooling (Server Manager, DFS Management console, Windows DNS server, PowerShell) is pervasive throughout the document, and Linux or open-source alternatives are not discussed.
Recommendations
  • Explicitly state that DFS Namespaces is a Windows-only technology and clarify if there are any cross-platform alternatives for Linux environments.
  • Provide guidance or references for Linux users who may need similar namespace or migration functionality, such as using NFS referrals, autofs, or alternative SMB namespace management tools.
  • Include a section comparing DFS-N with Linux-based solutions for namespace virtualization and file share migration, highlighting differences and possible integration points.
  • If possible, offer instructions or best practices for accessing Azure NetApp Files SMB shares from Linux clients, including relevant mount commands and authentication considerations.
  • Mention any limitations or considerations for mixed Windows/Linux environments, especially in organizations with heterogeneous infrastructure.
GitHub Create Pull Request
Azure Netapp Files Understand volume languages in Azure NetApp Files ...cles/azure-netapp-files/understand-volume-languages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (Explorer, PowerShell, Notepad, Notepad++, CMD, PowerShell ISE, Windows Terminal) are frequently mentioned, often before or in more detail than Linux equivalents. PowerShell examples and screenshots are prevalent, while Linux commands (aside from basic shell and iconv/file usage) are less detailed. Windows-specific troubleshooting (fonts, region settings, code pages) is covered extensively, whereas Linux troubleshooting is more limited. Some conversion and encoding examples are shown only for Windows tools, and Linux alternatives are referenced but not illustrated as thoroughly.
Recommendations
  • Ensure Linux command-line examples (e.g., encoding conversion, file viewing) are provided with equal detail and screenshots as Windows/PowerShell examples.
  • Mention Linux tools (e.g., Vim, Gedit, nano, locale settings, font configuration) alongside Windows tools for file encoding and display troubleshooting.
  • Present Linux and Windows examples in parallel, rather than focusing on Windows first or in greater depth.
  • Include troubleshooting steps for Linux clients (e.g., handling font/display issues, locale misconfigurations) similar to the Windows font/code page guidance.
  • Reference cross-platform tools (e.g., VS Code, Sublime Text) for encoding management where appropriate.
  • Add more Linux-specific scenarios for dual-protocol environments, such as how Linux NFS clients handle SMB-created files and vice versa.
GitHub Create Pull Request
Azure Relay Authenticate from an application - Azure Relay .../main/articles/azure-relay/authenticate-application.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ dotnet_heavy
Summary
The documentation page demonstrates a Windows/.NET bias by primarily featuring .NET (C#) sample code and console applications, with instructions and highlighted code only for .NET. There are no Linux-specific instructions, nor are there examples for running the sample on Linux or using Linux-native tools. The main sample is for a Windows-oriented technology stack, and the instructions implicitly assume a Windows environment (e.g., console app, .NET, Azure portal UI). Although Java and JavaScript samples are linked, they are not described or highlighted, and there is no parity in walkthroughs or code snippets for those platforms.
Recommendations
  • Add explicit instructions and code samples for running the authentication flow on Linux, including using Java and JavaScript sample applications.
  • Provide parity in walkthroughs and highlighted code for Java and JavaScript samples, not just .NET.
  • Include guidance for using cross-platform tools (e.g., Azure CLI) for steps like app registration and secret creation, rather than relying solely on Azure portal UI.
  • Clarify that the sample applications can be run on Linux and provide any necessary setup steps (e.g., installing .NET Core on Linux, running Java/Node.js samples).
  • Consider including troubleshooting notes or platform-specific caveats for Linux users.
GitHub Create Pull Request
Azure Relay Authenticate with managed identities for Azure Relay resources .../articles/azure-relay/authenticate-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Windows-based Azure VMs, including references to RDP and Windows-specific VM creation guides. There are no equivalent Linux VM instructions, nor is there guidance for running the sample app on Linux. The sample walkthrough assumes a Windows environment throughout, and Windows tools (RDP) are mentioned without Linux alternatives.
Recommendations
  • Add explicit instructions for enabling managed identity on Linux VMs, including links to relevant documentation.
  • Provide a walkthrough for running the sample application on a Linux VM, including build and execution steps.
  • Mention Linux-compatible remote access tools (e.g., SSH) alongside RDP, and provide links to Linux VM connection guides.
  • Ensure that code samples and instructions are platform-agnostic or include both Windows and Linux variants where applicable.
GitHub Create Pull Request
Azure Netapp Files What's new in Azure NetApp Files ...ocs/blob/main/articles/azure-netapp-files/whats-new.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure NetApp Files 'What's new' demonstrates some Windows bias. Features and enhancements related to Windows technologies (such as SMB, Active Directory, Windows Server, and Windows File Explorer) are frequently highlighted, sometimes before or without equivalent Linux/NFS examples. Windows-centric terminology (e.g., 'Windows client', 'Windows File Explorer') is used in feature descriptions, and some features (like Access-based Enumeration, Non-browsable shares, SMB Continuous Availability) are described primarily in the context of Windows environments. Linux/NFS features are present, but often less detailed or not given parity in example or explanation, and Linux tools/commands are rarely mentioned.
Recommendations
  • For every Windows/SMB feature or example, provide a Linux/NFS equivalent where applicable (e.g., describe how Access-based Enumeration or non-browsable shares work for NFS clients, or clarify if not supported).
  • When referencing Windows tools (e.g., Windows File Explorer), also mention Linux alternatives (e.g., NFS client commands, file browsers).
  • Avoid using Windows-centric terminology exclusively; use cross-platform language (e.g., 'file browser' instead of 'Windows File Explorer') where possible.
  • Ensure that Linux/NFS features and enhancements are described with equal detail and clarity as Windows/SMB features.
  • Include Linux command-line examples (e.g., mount, showmount, chown) when discussing features that apply to both platforms.
  • Where features are only available for Windows/SMB, explicitly state this and, if possible, provide guidance or workarounds for Linux/NFS users.
GitHub Create Pull Request
Azure Relay Configure IP firewall for Azure Relay namespace ...n/articles/azure-relay/ip-firewall-virtual-networks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates Windows bias by referencing Azure portal (which is most commonly used on Windows), and by directing users to deploy Resource Manager templates using a PowerShell-specific guide, without mentioning or providing examples for Linux-native tools or CLI workflows. There are no Linux or cross-platform command-line examples (such as Azure CLI or Bash), and no mention of Linux-specific deployment instructions.
Recommendations
  • Add instructions and examples for deploying Resource Manager templates using Azure CLI (az deployment group create) and Bash scripts, which are cross-platform and widely used on Linux.
  • Reference both PowerShell and Azure CLI deployment guides, and present them side-by-side or in a neutral order.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, and clarify any OS-specific steps if relevant.
  • Include Linux-specific notes or troubleshooting tips where appropriate.
  • Ensure that any referenced guides (such as 'deploy-powershell.md') have equivalent Linux/CLI versions and link to them.
GitHub Create Pull Request
Azure Relay Azure Relay API overview | Microsoft Docs ...s/blob/main/articles/azure-relay/relay-api-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing .NET Framework (Windows-only) APIs and tools before cross-platform or Linux-friendly alternatives. It references Windows Communication Foundation (WCF) and proprietary protocols without mentioning Linux equivalents or alternatives. There are no explicit Linux or cross-platform usage examples, and the focus is on Windows-centric technologies and patterns.
Recommendations
  • Add explicit Linux usage examples for Azure Relay, such as command-line usage or integration with Linux services.
  • Highlight cross-platform capabilities and provide parity in examples for both Windows and Linux environments.
  • Include references to Linux-compatible tools and frameworks (e.g., .NET Core on Linux, Node.js on Linux) and demonstrate their usage.
  • Avoid prioritizing Windows-only technologies (like WCF) in documentation structure; present cross-platform options first or equally.
  • Clarify which APIs and libraries are supported on Linux and provide guidance for Linux users.
GitHub Create Pull Request
Azure Relay Azure Relay Hybrid Connections - WebSockets in .NET ...e-relay/relay-hybrid-connections-dotnet-get-started.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily oriented towards Windows development environments, specifically Visual Studio, with no mention of Linux-compatible development tools or instructions. All examples assume use of Visual Studio and do not provide guidance for Linux users or alternative IDEs. There are no instructions for running or building the applications on Linux, nor any mention of .NET Core/.NET 6+ cross-platform capabilities.
Recommendations
  • Add instructions for setting up and running the sample applications on Linux, including using .NET Core/.NET 6+ and the 'dotnet' CLI.
  • Include examples for building and running the applications using VS Code or other cross-platform editors.
  • Explicitly mention that .NET is cross-platform and provide parity in steps for Linux and macOS users.
  • Provide troubleshooting notes or prerequisites for Linux (e.g., installing .NET SDK, using terminal commands).
  • Avoid assuming Visual Studio as the only development environment; offer alternatives.
GitHub Create Pull Request
Azure Relay What is Azure Relay? | Microsoft Docs ...ocs/blob/main/articles/azure-relay/relay-what-is-it.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. It prominently features Windows-centric technologies such as WCF Relay (which is tightly coupled with the full .NET Framework and Windows Communication Foundation), and all WCF Relay examples are inherently Windows-only. The quick start and sample sections list .NET (typically Windows-first) examples before Node and Java, and do not mention Linux-specific instructions, tools, or patterns. There is no explicit mention of Linux/Powershell alternatives, nor are Linux command-line or service management examples provided.
Recommendations
  • Add explicit Linux quick start guides for Hybrid Connections, including setup and usage instructions for common Linux distributions.
  • Clarify which features and samples are cross-platform and which are Windows-only (e.g., WCF Relay).
  • Provide Linux-specific examples for running relay clients/services, including service management and firewall configuration.
  • Include parity in sample ordering, listing cross-platform and Linux/Node/Java examples before or alongside .NET/Windows examples.
  • Mention alternative tools or libraries for Linux environments where Windows-specific technologies (like WCF) are referenced.
GitHub Create Pull Request
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The tutorial exhibits significant Windows bias: all examples use Visual Studio and .NET Framework (Windows-centric tools), instructions reference Windows-specific UI actions (e.g., 'Run as administrator', Solution Explorer), and there are no Linux or cross-platform alternatives provided. The use of WCF and .NET Framework further restricts the tutorial to Windows environments, with no mention of how to achieve similar functionality on Linux or with cross-platform technologies.
Recommendations
  • Add instructions and examples for building and running the service on Linux, using .NET Core/.NET 6+ (which is cross-platform) and compatible editors like VS Code.
  • Include command-line instructions for project creation and package management (e.g., dotnet CLI) instead of relying solely on Visual Studio UI.
  • Clarify which steps are Windows-specific and provide Linux/macOS equivalents (e.g., file paths, running as administrator/sudo).
  • Mention and demonstrate how to use cross-platform alternatives to WCF (such as ASP.NET Core with Azure Relay, if supported) or note platform limitations.
  • Explicitly state the platform requirements and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Azure Relay WCF Relay hybrid on-premises/cloud application (.NET) ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and .NET Framework. All examples, instructions, and tooling references assume the use of Windows, with no mention of Linux alternatives or cross-platform development. There are no instructions for using Linux-based tools, editors, or SDKs, nor any guidance for running the sample applications on Linux. The tutorial does not address how to set up or run the WCF Relay scenario outside of Windows, nor does it mention .NET Core/5+/6+ cross-platform capabilities.
Recommendations
  • Provide equivalent instructions for setting up the development environment on Linux, including installation of .NET SDK and use of cross-platform editors like VS Code.
  • Include examples for creating and running the WCF service and client using .NET Core/6+ on Linux.
  • Document how to use Azure Relay from Linux, including any required configuration or limitations.
  • Mention and demonstrate use of cross-platform tools (e.g., dotnet CLI) instead of or alongside Visual Studio.
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
  • Add troubleshooting notes for common issues encountered on non-Windows platforms.
GitHub Create Pull Request
Azure Relay Expose on-premises WCF REST service to clients ...ain/articles/azure-relay/service-bus-relay-tutorial.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows environments. All examples and instructions assume the use of Visual Studio (a Windows-centric IDE), and there is no mention of Linux or cross-platform development tools. Steps such as 'Run as administrator', project creation, NuGet package installation, and configuration are described exclusively using Windows/Visual Studio workflows. There are no alternative instructions or code samples for Linux users, nor any mention of how to use .NET Core/SDK CLI tools, which are cross-platform. The use of Windows-specific terminology and tools (e.g., Solution Explorer, Visual Studio, App.config, WindowsAzure.ServiceBus NuGet package) further reinforces the Windows bias.
Recommendations
  • Add instructions for using .NET Core/SDK CLI tools (dotnet new, dotnet add package, dotnet build) for project creation and package management, which work on Linux, macOS, and Windows.
  • Include examples and screenshots for popular Linux IDEs (e.g., VS Code) or command-line workflows.
  • Clarify which steps are platform-agnostic and which are Windows-specific; provide Linux/macOS equivalents where possible.
  • Mention that WCF is supported on .NET Framework (Windows-only) and clarify cross-platform alternatives (e.g., gRPC, ASP.NET Core Web APIs) for Linux users.
  • Provide troubleshooting notes for running WCF services on Linux via Mono (if possible), or suggest alternatives for Linux environments.
  • Avoid using Windows-centric language (e.g., 'Run as administrator') without offering Linux/macOS equivalents (e.g., 'use sudo').
GitHub Create Pull Request
Azure Resource Manager Bicep CLI commands ...ain/articles/azure-resource-manager/bicep/bicep-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exhibits Windows bias in several ways: file path examples consistently use Windows-style paths (e.g., c:\jsontemplates) without providing Linux/macOS equivalents; installation and usage instructions frequently reference Azure PowerShell and Windows-specific conventions before or instead of Linux alternatives; and some commands (e.g., install, upgrade, list-versions) are only shown for Azure CLI, which is cross-platform but often associated with Windows. Cache location examples do mention Linux and Mac, but command examples and file paths are predominantly Windows-centric.
Recommendations
  • For every example using a Windows file path (e.g., c:\jsontemplates), provide a Linux/macOS equivalent (e.g., /home/user/jsontemplates) side-by-side.
  • When referencing installation methods, mention Linux and macOS processes equally alongside Windows and PowerShell.
  • Ensure that command examples and explanations do not assume Windows as the default environment; use generic or platform-neutral paths and conventions where possible.
  • Add explicit notes or tabs for Linux/macOS users where behavior, paths, or conventions differ.
  • In sections about named pipes and sockets, clarify platform differences and provide examples for both Windows and Unix-like systems.
  • Review all examples and ensure parity in coverage and clarity for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Bicep functions for Bicep parameters files ...ource-manager/bicep/bicep-functions-parameters-file.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias, particularly in the 'readEnvironmentVariable' section, where all examples for setting environment variables use PowerShell commands and .NET APIs. There are no equivalent Linux/macOS shell examples (e.g., Bash export), and Windows tools and patterns are mentioned exclusively. This may hinder Linux users' understanding and parity.
Recommendations
  • Add equivalent Linux/macOS shell (e.g., Bash) examples for setting environment variables, such as 'export testEnvironmentVariable="Hello World!"'.
  • Include notes on differences in environment variable persistence and scope between Windows and Linux/macOS.
  • Present both Windows (PowerShell/CMD) and Linux/macOS (Bash/Zsh) commands side by side or in tabs to ensure parity.
  • Reference relevant Linux documentation (e.g., man pages for 'export', 'env') alongside Windows/.NET references.
  • Review other sections for implicit Windows assumptions and add cross-platform clarifications where needed.
GitHub Create Pull Request
Azure Resource Manager Data types in ARM templates ...rticles/azure-resource-manager/templates/data-types.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the example command-line tool for ARM template deployment and integer range limitations, without mentioning Linux equivalents such as Azure CLI or Bash. No Linux-specific examples or parity guidance are provided.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell when discussing deployment tools and parameter limitations.
  • Clarify whether integer range limitations apply to Azure CLI, Bash, or other Linux-native tools.
  • Add a section or note explicitly addressing cross-platform usage and differences, ensuring Linux users are equally supported.
  • Present examples and tool references in a neutral or parallel order (e.g., "PowerShell or Azure CLI") rather than Windows-first.
GitHub Create Pull Request
Azure Resource Manager Decompile a JSON Azure Resource Manager template to Bicep ...ain/articles/azure-resource-manager/bicep/decompile.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio Code, Azure PowerShell) are mentioned and described before or more prominently than Linux alternatives. Examples are given for both Azure CLI and Azure PowerShell, but PowerShell is featured as a primary tab and is not explicitly contextualized as Windows-only. Visual Studio Code (a cross-platform tool, but often associated with Windows) is referenced repeatedly, and Windows-specific patterns (e.g., right-click, F2 hotkey) are described without Linux alternatives. There are no explicit Linux shell examples (e.g., Bash), and no mention of Linux-specific workflows or editors.
Recommendations
  • Add explicit Bash shell examples for decompiling and exporting templates, especially for Linux users.
  • Clarify that Azure PowerShell is primarily a Windows tool and suggest cross-platform alternatives (e.g., Azure CLI, Bash).
  • When describing editor actions (e.g., renaming symbols), mention equivalent shortcuts or actions for Linux/Mac (e.g., VS Code on Linux uses the same F2 hotkey, but right-click behavior may differ).
  • Include references to Linux-native editors (e.g., Vim, Nano) or workflows for users who do not use Visual Studio Code.
  • Ensure that cross-platform tools are described before or alongside Windows-specific tools, and avoid implying Windows as the default environment.
GitHub Create Pull Request
Azure Resource Manager Deploy Bicep files with the Azure CLI ...in/articles/azure-resource-manager/bicep/deploy-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ bash_first ⚠ī¸ windows_shell_guidance ⚠ī¸ windows_shell_examples ⚠ī¸ windows_shell_format_notes
Summary
The documentation primarily provides Azure CLI examples in Bash syntax, with explicit notes and guidance for users on Windows (PowerShell/cmd) about how to adapt commands and parameter formats. While Linux/Bash is the default, Windows shell usage is acknowledged and supported, but examples and instructions for Windows shells are secondary and less detailed. There are no PowerShell/cmd-specific code blocks, and Linux tools/patterns are not highlighted beyond Bash.
Recommendations
  • Add explicit PowerShell and Command Prompt (cmd) code blocks for key examples, especially where syntax differs significantly.
  • Provide a table or section summarizing differences in parameter passing and quoting between Bash, PowerShell, and cmd.
  • Include Linux-specific notes or troubleshooting tips, such as file path conventions or permissions.
  • Ensure parity by giving equal prominence to Windows and Linux shell usage in examples and explanations.
  • Consider adding a 'Platform differences' section early in the document to clarify how commands and file handling vary across OSes.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to management group ...e-resource-manager/bicep/deploy-to-management-group.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page provides deployment command examples for both Azure CLI and PowerShell, but the PowerShell example is given equal prominence as the CLI example, and there is no mention of Linux-specific shell usage (e.g., Bash) or cross-platform considerations. The references to Azure CLI are platform-neutral, but PowerShell is traditionally a Windows-first tool, and no explicit Linux/Bash examples or notes are provided. There is also no mention of running these commands in a Linux environment or Cloud Shell context, nor are there instructions for using Bash scripts or Linux-native tools.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, demonstrating usage in Linux/macOS environments.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Add notes or examples for running deployment commands in Azure Cloud Shell (which is Linux-based by default).
  • If PowerShell is mentioned, clarify that Azure PowerShell is available on Linux/macOS and provide installation or usage notes for those platforms.
  • Consider listing Azure CLI (Bash) examples before PowerShell to avoid implicit Windows-first ordering.
  • Include troubleshooting or environment setup notes for Linux users, such as authentication methods or file path differences.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to subscription ...azure-resource-manager/bicep/deploy-to-subscription.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation presents deployment commands for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given its own section and example, while Linux-native tools or shell examples (e.g., Bash) are not provided. The Azure CLI example is present, but there is no explicit mention of running it on Linux or macOS, nor are there Bash script examples or references to Linux-specific usage patterns. The 'Next steps' and references focus on PowerShell and CLI, with PowerShell listed after CLI, but no Linux shell or automation examples are included.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, showing usage in Linux/macOS environments.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Include references or links to Linux/macOS setup guides for Azure CLI.
  • If mentioning PowerShell, also mention Bash or other Linux-native shells where appropriate.
  • Ensure parity in troubleshooting and environment setup instructions for Linux users.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to resource groups ...ure-resource-manager/bicep/deploy-to-resource-group.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation presents deployment commands for both Azure CLI and Azure PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and no explicit Linux shell examples (e.g., Bash, zsh) are provided. There is no mention of Linux-specific considerations, nor are there examples using Linux-native tools or scripting patterns. The page assumes parity between Azure CLI and PowerShell, but PowerShell is still primarily a Windows tool, and its inclusion without Linux alternatives or notes may suggest a Windows bias.
Recommendations
  • Add explicit Bash/zsh shell examples for Azure CLI commands, showing usage in typical Linux environments.
  • Clarify that Azure CLI works cross-platform and is the recommended tool for Linux/macOS users.
  • Note that PowerShell is available on Linux, but is less commonly used than Bash/zsh; consider providing Bash equivalents for any PowerShell examples.
  • Include troubleshooting or environment setup notes for Linux users, such as installing Azure CLI via package managers.
  • Review linked articles to ensure Linux parity and avoid Windows-centric instructions or screenshots.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy resources to tenant ...icles/azure-resource-manager/bicep/deploy-to-tenant.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples and tools before or alongside Azure CLI, referencing PowerShell-specific commands (e.g., New-AzRoleAssignment, New-AzTenantDeployment), and using Windows-centric terminology and patterns. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The documentation assumes familiarity with PowerShell and Windows tools, potentially disadvantaging Linux users.
Recommendations
  • Add explicit Bash/Linux shell examples for all command-line instructions, especially for Azure CLI usage.
  • Where PowerShell commands are given, provide equivalent Bash/CLI commands side-by-side, and clarify which platforms each example targets.
  • Avoid using Windows-centric terminology (e.g., PowerShell) as the default; instead, present Azure CLI (cross-platform) examples first.
  • Include notes or sections on running these commands from Linux/macOS environments, including any platform-specific considerations.
  • Reference Cloud Shell as a cross-platform option and clarify its underlying shell (Bash or PowerShell).
GitHub Create Pull Request
Azure Resource Manager Create and deploy Azure deployment stacks in Bicep ...cles/azure-resource-manager/bicep/deployment-stacks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page exhibits a moderate Windows bias. Azure PowerShell is featured prominently and consistently, with PowerShell examples always presented before Azure CLI equivalents. The use of PowerShell (a Windows-centric tool) and the explicit mention of PowerShell-specific switches and output formats reinforce this bias. There are no Linux-specific shell examples (e.g., Bash), nor is there any mention of Linux-specific tooling or considerations. The CLI examples are generic and do not address platform-specific nuances, such as shell quoting or environment setup differences. The documentation assumes familiarity with PowerShell patterns and terminology, which may disadvantage Linux users.
Recommendations
  • Provide Bash-specific examples alongside PowerShell and Azure CLI, especially for common Linux scenarios.
  • Clarify that Azure CLI commands are cross-platform and provide notes on shell differences (e.g., quoting, line continuation) between Windows (CMD/PowerShell) and Linux (Bash/zsh).
  • Avoid presenting PowerShell examples first; alternate the order or present CLI examples first to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI is available and supported on Linux/macOS, and link to installation instructions for those platforms.
  • Where PowerShell output is shown, also show equivalent CLI output in JSON or other formats commonly used on Linux.
  • Add troubleshooting or environment setup notes for Linux users, especially where file paths, permissions, or shell syntax may differ.
GitHub Create Pull Request
Azure Resource Manager Configure development environment for deployment scripts in Bicep | Microsoft Docs ...manager/bicep/deployment-script-bicep-configure-dev.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a noticeable Windows bias. PowerShell is heavily featured throughout, with most scripting and deployment examples using PowerShell syntax and Azure PowerShell cmdlets. File upload instructions and Bicep deployments are shown using PowerShell, and Docker volume mount examples use Windows-style paths (e.g., d:/docker:/data) without showing Linux equivalents. There are no Bash or Linux shell examples for uploading files or deploying resources, and Linux-specific instructions are missing or mentioned only as alternatives. The page assumes familiarity with Windows tools and patterns, and Linux parity is not fully achieved.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell scripts, especially for uploading files and deploying Bicep templates.
  • Show Docker volume mount examples using Linux paths (e.g., /home/user/docker:/data) alongside Windows paths.
  • Explicitly mention Linux prerequisites and environment setup steps, such as using Bash or zsh terminals.
  • Ensure that instructions for using Azure CLI are as detailed and prominent as those for PowerShell.
  • Add notes or callouts for platform-specific differences, such as file path formats and shell commands.
  • Consider reordering sections so that Azure CLI and Bash examples are presented before or alongside PowerShell examples, not after.
GitHub Create Pull Request
Azure Resource Manager Export Bicep files in Azure portal ...es/azure-resource-manager/bicep/export-bicep-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and the Azure portal (which is commonly used on Windows) before mentioning Azure CLI or REST API. PowerShell is a Windows-centric tool, and its mention alongside CLI as the primary export methods suggests a preference for Windows workflows. There are no explicit Linux-specific examples or references to Linux-native tools or patterns, and the order of presentation puts Windows tools first.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide usage examples for Linux environments.
  • Include screenshots or instructions that show the export process on Linux systems (e.g., using Azure CLI in a Bash shell).
  • Avoid implying that PowerShell is the default or preferred method; clarify platform compatibility for each tool.
  • Add a section on exporting Bicep files using Linux-native workflows, if possible, or clarify any limitations.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot problems with Bicep installation ...re-resource-manager/bicep/installation-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by providing command-line instructions and environment variable paths that are specific to Windows (e.g., using 'where bicep', referencing '%USERPROFILE%\.Azure\bin', and omitting Linux/macOS equivalents such as 'which bicep' or '$HOME/.azure/bin'). There are no examples or troubleshooting steps for Linux or macOS users, and Windows tools and patterns are mentioned exclusively.
Recommendations
  • Include equivalent Linux/macOS commands (e.g., 'which bicep' instead of only 'where bicep').
  • Provide instructions for updating PATH on Linux/macOS (e.g., modifying ~/.bashrc or ~/.zshrc).
  • Mention the default installation paths for Bicep CLI on Linux/macOS (e.g., $HOME/.azure/bin).
  • Add troubleshooting steps and screenshots relevant to Linux/macOS environments.
  • Ensure all steps and examples are presented for both Windows and Linux/macOS, or clearly indicate platform-specific instructions.
GitHub Create Pull Request
Azure Resource Manager Install Bicep tools .../main/articles/azure-resource-manager/bicep/install.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides installation instructions for Bicep tools across Windows, Linux, and macOS, but Windows-specific tools and patterns (such as Chocolatey, Winget, and PowerShell scripts) are given more prominence and detail. The Windows section lists three separate installer options (Windows Installer, Chocolatey, Winget) before presenting a manual PowerShell method, while Linux and macOS primarily focus on direct binary downloads and Homebrew. PowerShell is used heavily for Windows manual installation, and Windows installer options are described in more detail than Linux equivalents. In some sections, Windows instructions or tools are listed before Linux/macOS, and Windows-centric terminology (e.g., %UserProfile%) is used without equivalent Linux/macOS context.
Recommendations
  • Provide parity for Linux/macOS package managers (e.g., apt, yum, zypper for Linux; MacPorts for macOS) if available, or explicitly state their absence.
  • Balance the detail level across platforms: expand Linux/macOS instructions to match the depth of Windows installer options, including troubleshooting and verification steps.
  • List installation methods in a consistent order (e.g., alphabetical by OS or grouped by method) to avoid implicit prioritization of Windows.
  • Where PowerShell is used for Windows, consider providing equivalent shell scripts for Linux/macOS for manual installation steps.
  • Clarify platform-specific environment variable usage (e.g., %UserProfile% for Windows, $HOME for Linux/macOS) in all relevant sections.
  • Add troubleshooting notes and screenshots for Linux/macOS installation similar to those provided for Windows.
GitHub Create Pull Request
Azure Resource Manager Use Azure Key Vault to pass a secret as a parameter during Bicep deployment ...es/azure-resource-manager/bicep/key-vault-parameter.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific scenarios (such as WinRM on Windows VM) are referenced in the introduction and linked as examples, while no Linux VM equivalent is mentioned. Azure PowerShell examples are provided alongside Azure CLI, but PowerShell is a Windows-centric tool and its usage is emphasized throughout. The documentation refers to Windows tools and patterns (e.g., PowerShell, WinRM) without mentioning or prioritizing Linux alternatives or parity.
Recommendations
  • Add references and examples for Linux VM scenarios (e.g., SSH certificate deployment via Key Vault) in the introduction and related links.
  • Ensure that Linux-centric tools (such as Bash, native Azure CLI usage in Linux shells) are mentioned and examples are provided where appropriate.
  • Where PowerShell is shown, clarify cross-platform support or provide Bash/Linux shell equivalents.
  • Avoid referencing Windows-specific quickstarts (such as WinRM on Windows VM) without also mentioning Linux equivalents.
  • Explicitly state that Azure CLI is cross-platform and show usage in Linux environments, including shell syntax (e.g., Bash).
GitHub Create Pull Request
Azure Resource Manager Migrate blueprints to deployment stacks ...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell in the export instructions and linking to a PowerShell-specific guide for blueprint export. There is no mention of Linux or cross-platform alternatives such as Azure CLI in the migration steps, nor are examples provided for non-Windows environments. The instructions and tooling references are Windows-centric, which may hinder Linux users from following the migration process.
Recommendations
  • Include Azure CLI commands and examples alongside PowerShell for blueprint export and migration steps.
  • Update links to reference both PowerShell and Azure CLI documentation where available.
  • Add explicit notes or sections for Linux/macOS users, clarifying cross-platform compatibility of tools and scripts.
  • Ensure sample code and instructions are platform-neutral or provide alternatives for both Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager Migrate Azure resources and JSON ARM templates to use Bicep .../main/articles/azure-resource-manager/bicep/migrate.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by frequently mentioning Windows-specific tools (such as Azure PowerShell), listing Windows before Linux in shortcut instructions, and referencing Windows-centric resource types (e.g., DependencyAgentWindows). There are no explicit Linux shell examples (such as Bash), and PowerShell is presented as a primary method for exporting resources. The documentation does not provide parity for Linux users in terms of CLI usage or resource types.
Recommendations
  • Provide explicit Bash/Azure CLI examples alongside PowerShell commands for resource export and template conversion.
  • Avoid listing Windows before Linux in shortcut instructions; use neutral phrasing or alternate order.
  • Mention Linux-specific resource types or considerations where applicable, not just Windows-centric ones.
  • Include screenshots or instructions for Linux environments (e.g., terminal usage, file paths) where relevant.
  • Ensure that all tooling recommendations (such as Visual Studio Code commands) clarify cross-platform compatibility and usage.
GitHub Create Pull Request
Azure Resource Manager Bicep null-forgiving operator ...zure-resource-manager/bicep/operator-null-forgiving.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by mentioning Azure PowerShell before Azure CLI when describing how to run examples. It also references Visual Studio Code as the editor, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux examples or mentions of Linux-specific tools or workflows, and the guidance leans toward Windows-centric tooling and patterns.
Recommendations
  • Mention Azure CLI before Azure PowerShell, as CLI is more commonly used across platforms including Linux and macOS.
  • Explicitly state that all examples and tools (Azure CLI, Visual Studio Code) are available and supported on Linux and macOS, not just Windows.
  • Add a note or section on how to deploy Bicep files from Linux/macOS terminals, including sample commands.
  • Reference other cross-platform editors (e.g., Vim, Sublime Text) for creating Bicep files, or clarify that any text editor can be used.
  • Ensure that links and instructions do not assume a Windows environment (e.g., avoid referencing Windows-specific paths or shell commands).
GitHub Create Pull Request
Azure Resource Manager Bicep spread operator ...ticles/azure-resource-manager/bicep/operator-spread.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in its 'Next steps' section, where Azure PowerShell is mentioned alongside Azure CLI as the primary methods for deploying Bicep files. Additionally, Visual Studio Code is referenced as the editor for creating Bicep files, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-native tools or deployment patterns. The ordering and selection of tools suggest a Windows-centric approach.
Recommendations
  • Include explicit Bash or Linux shell examples for deploying Bicep files using Azure CLI.
  • Mention Linux-native editors (e.g., Vim, Emacs) or provide guidance for creating Bicep files on Linux systems.
  • Clarify that Azure CLI is cross-platform and can be used on Linux and macOS, not just Windows.
  • Add links or instructions for installing and using Bicep on Linux systems.
  • Balance the mention of Azure PowerShell with Linux alternatives, or note that PowerShell Core is available cross-platform.
GitHub Create Pull Request
Azure Resource Manager Bicep accessor operators ...icles/azure-resource-manager/bicep/operators-access.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where Azure PowerShell is mentioned alongside Azure CLI as the recommended tools for deploying Bicep files, with no explicit mention of Linux or cross-platform usage. There are no examples or instructions tailored for Linux users, and PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, which is cross-platform. No Linux-specific shell commands (e.g., Bash) or deployment patterns are shown.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Provide example deployment commands using Bash or shell scripts for Linux users.
  • Clarify that Azure PowerShell is available on Linux and macOS, but highlight Azure CLI as the default for cross-platform scenarios.
  • Add a note or section on how to deploy Bicep files from Linux environments, including prerequisites and sample commands.
  • Ensure all instructions and examples are platform-neutral or provide parity between Windows and Linux usage.
GitHub Create Pull Request
Azure Resource Manager Quickstart: Use MSBuild tasks to convert Bicep files and parameters to JSON ...les/azure-resource-manager/bicep/msbuild-bicep-file.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a Windows bias by consistently presenting Windows and PowerShell examples first and exclusively, especially in command-line instructions and project setup. Directory paths, shell commands, and cleanup steps are all shown using Windows conventions (e.g., C:\ paths, PowerShell commands), with no equivalent Linux/macOS shell examples. Package references and environment variable configuration do mention Linux and macOS, but practical usage instructions and examples are Windows-centric. There are no bash/zsh or Linux/macOS terminal examples, and the workflow assumes Visual Studio or Visual Studio Code on Windows.
Recommendations
  • Provide equivalent Linux/macOS shell examples (e.g., bash/zsh) alongside PowerShell commands for directory creation, navigation, and cleanup.
  • Show Linux/macOS directory paths (e.g., /home/user/msBuildDemo) in addition to Windows paths.
  • Include instructions for running MSBuild and dotnet CLI on Linux/macOS, including any platform-specific considerations.
  • Demonstrate usage of Azure.Bicep.CommandLine.linux-x64 and osx-x64 in project file examples, not just win-x64.
  • Add guidance for installing prerequisites (e.g., .NET SDK, MSBuild) on Linux/macOS, including package manager commands.
  • Ensure all code and command examples are presented in platform-agnostic tabs or sections, so users can easily find instructions relevant to their OS.
GitHub Create Pull Request
Azure Resource Manager Bicep safe-dereference operator ...re-resource-manager/bicep/operator-safe-dereference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Visual Studio Code (a Microsoft tool) as the primary means to deploy and create Bicep files. Azure CLI is mentioned, but Azure PowerShell is listed first, and there are no explicit Linux-specific instructions or examples. The guidance assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Provide explicit Linux deployment instructions, such as using Azure CLI on Linux or Bash shell examples.
  • List Azure CLI before Azure PowerShell to avoid implying Windows-first workflows.
  • Mention alternative editors (e.g., Vim, VS Code on Linux, or other cross-platform editors) for creating Bicep files.
  • Include notes or links for installing and using Bicep tooling on Linux and macOS.
  • Add example commands for both Windows (PowerShell) and Linux/macOS (Bash) environments.
GitHub Create Pull Request
Azure Resource Manager Bicep comparison operators ...s/azure-resource-manager/bicep/operators-comparison.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell alongside Azure CLI as the primary methods for deploying Bicep files, with PowerShell (a Windows-centric tool) mentioned first. There are no explicit Linux-specific instructions or examples, and the deployment guidance does not clarify cross-platform usage or provide parity for Linux users.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Provide Linux/macOS-specific deployment instructions or examples, such as using bash or shell commands.
  • Avoid listing PowerShell before CLI unless contextually relevant, or alternate the order to avoid perceived prioritization.
  • Include a note or section on platform compatibility for Bicep tooling and deployment.
  • Where possible, add example commands for both PowerShell and bash/shell to ensure parity.
GitHub Create Pull Request
Azure Resource Manager Create a private container registry in Azure for Bicep modules ...zure-resource-manager/bicep/private-module-registry.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a mild Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) examples before Azure CLI (cross-platform) examples. PowerShell is highlighted in both command and instructional sections, and the local cache path for Windows is described in more detail than for Linux/Mac. There are no Linux shell-specific examples or mentions of Linux-native tools, and the documentation assumes familiarity with Windows conventions.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is presented before Azure PowerShell, or present both together without preference.
  • Include Linux shell (bash) and MacOS-specific command examples where relevant, especially for file paths and environment variables.
  • Provide equal detail for Linux and Mac cache paths, including example full paths (e.g., /home/<username>/.bicep/br/<registry-name>.azurecr.io/<module-path>/<tag>).
  • Explicitly state that Azure CLI commands work identically on Windows, Linux, and MacOS, and encourage its use for cross-platform compatibility.
  • Where PowerShell is used, clarify that it is available on Linux and Mac as well, or provide bash equivalents if possible.
GitHub Create Pull Request
Azure Resource Manager Create a parameters file for bicep deployment ...ticles/azure-resource-manager/bicep/parameter-files.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. While Azure CLI examples are provided (which are cross-platform), all PowerShell examples use Azure PowerShell cmdlets with Windows-style paths (e.g., C:\MyTemplates\...), and there is no mention of Linux-specific shell environments or examples using Bash or other Linux-native tools. Visual Studio Code is referenced as the primary editor, which is cross-platform, but no mention is made of Linux-specific editors or shell usage. Windows-style paths and PowerShell are presented before any Linux alternatives, and there are no explicit Linux/Bash examples for deployment commands.
Recommendations
  • Add Linux/Bash shell examples for deployment commands, using typical Linux path formats (e.g., /home/user/templates/storage.bicep).
  • Include notes or examples for using Azure CLI and Bicep CLI in Linux environments, such as running commands in Bash or zsh.
  • Provide guidance for Linux users on installing and using the Bicep CLI and Azure CLI, including any differences in environment variables or file paths.
  • Mention Linux-native editors (such as Vim or VS Code on Linux) where appropriate.
  • Ensure that all examples using file paths show both Windows and Linux formats, or use environment-agnostic paths.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide explicit cross-platform instructions where relevant.
GitHub Create Pull Request
Azure Resource Manager Quickstart: Create Bicep files with Visual Studio Code ...icep/quickstart-create-bicep-use-visual-studio-code.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio Code, Azure PowerShell) are mentioned before or alongside cross-platform alternatives, and PowerShell examples are given equal prominence to Azure CLI. The workflow assumes familiarity with right-click context menus and UI patterns typical of Windows environments. There are no explicit Linux-specific instructions or examples, and the documentation does not address platform differences in setup or usage.
Recommendations
  • Add explicit notes clarifying that Visual Studio Code and the Bicep extension are fully supported on Linux and macOS, not just Windows.
  • Include Linux/macOS-specific instructions for launching Visual Studio Code and interacting with files (e.g., using terminal commands rather than right-click context menus).
  • Provide CLI-only workflows for deployment and resource management, emphasizing that Azure CLI is cross-platform and can be used on Linux/macOS.
  • Mention alternative editors (e.g., Vim, VS Codium) that support Bicep via extensions, for users who do not use Visual Studio Code.
  • Clarify that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the default cross-platform tool.
  • Add screenshots or examples from Linux/macOS environments to visually reinforce cross-platform support.
GitHub Create Pull Request
Azure Resource Manager Publish modules to private module registry ...ce-manager/bicep/quickstart-private-module-registry.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently providing Azure PowerShell examples alongside Azure CLI, referencing Windows-centric tools (Visual Studio, Visual Studio Code), and omitting explicit Linux/macOS shell examples (e.g., Bash). The instructions and screenshots focus on Visual Studio Code and Visual Studio, which are more commonly used on Windows, and do not mention Linux-native editors or shell usage. There is no guidance for Linux-specific environments, nor are there examples using Bash or other Linux command-line conventions.
Recommendations
  • Add explicit Bash shell examples for all Azure CLI commands, showing Linux/macOS syntax (e.g., export, $VAR, file paths with /).
  • Include instructions for using Bicep CLI and Azure CLI in Linux/macOS terminals, noting any differences in environment setup or file paths.
  • Mention Linux-native editors such as Vim, Emacs, or GNOME Text Editor as alternatives to Visual Studio Code.
  • Clarify that Visual Studio Code is cross-platform and provide installation guidance for Linux/macOS.
  • Add notes about running Azure CLI and Bicep CLI on Linux/macOS, including package manager installation commands (apt, yum, brew).
  • Ensure screenshots and examples do not assume a Windows environment (e.g., avoid Windows-style file paths, PowerShell variables).
GitHub Create Pull Request
Azure Resource Manager Create and deploy a deployment stack with Bicep ...e-manager/bicep/quickstart-create-deployment-stacks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, which is good for cross-platform parity. However, there is a subtle Windows bias: PowerShell is featured equally alongside CLI, despite being primarily a Windows-centric tool (even though PowerShell Core is cross-platform, most users associate it with Windows). Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of Linux-specific editors or shell environments. The documentation does not provide any Linux-specific guidance, troubleshooting, or notes, and PowerShell is listed as a prerequisite before Azure CLI, subtly prioritizing Windows tooling.
Recommendations
  • Explicitly mention that Azure CLI works natively on Linux/macOS and is recommended for those platforms.
  • Clarify that PowerShell Core is cross-platform, but most Linux/macOS users will prefer Azure CLI.
  • Add a note or section for Linux/macOS users, including common shell environments (bash/zsh) and editor alternatives (e.g., Vim, nano, etc.).
  • List Azure CLI before PowerShell in prerequisites to reflect its cross-platform nature.
  • Provide troubleshooting tips or links for Linux/macOS users (e.g., file permissions, path formats, installation guides).
GitHub Create Pull Request
Azure Resource Manager Create and deploy template specs in Bicep ...rticles/azure-resource-manager/bicep/template-specs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI, and all command-line examples are given only for Azure PowerShell and Azure CLI, with no mention of Linux-specific shell usage or cross-platform nuances. There are no explicit Linux shell (bash/zsh) examples, nor any notes about platform differences. The documentation assumes familiarity with PowerShell, a Windows-centric tool, and does not acknowledge Linux or macOS environments, which may use different shell conventions or require different setup steps.
Recommendations
  • Add explicit bash/zsh examples for Linux/macOS users alongside PowerShell and Azure CLI examples.
  • Include notes about platform-specific differences, such as command syntax, file paths, and environment setup for Linux/macOS.
  • Clarify that Azure CLI is cross-platform and provide guidance for installing and using it on Linux/macOS.
  • Avoid always presenting PowerShell examples first; alternate or group examples by platform.
  • Mention prerequisites or troubleshooting steps for Linux/macOS environments, such as permissions or shell compatibility.
GitHub Create Pull Request
Azure Resource Manager Create a custom resource provider ...rce-manager/custom-providers/create-custom-provider.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations. However, in the PowerShell sections, it exclusively references and demonstrates the use of ARMClient, a Windows-centric executable, for REST operations. There is no mention of Linux-friendly alternatives (such as curl or httpie), nor guidance for running PowerShell or ARMClient on Linux/macOS. This creates a bias towards Windows users in the PowerShell workflow and REST tooling.
Recommendations
  • Add Linux/macOS instructions for REST operations in PowerShell, including how to install and use ARMClient (if possible) or suggest alternatives like curl or httpie.
  • Mention that PowerShell 7+ is cross-platform and provide explicit steps for Linux/macOS users, including installation and usage notes.
  • Where ARMClient is referenced, clarify its platform support and suggest alternatives for non-Windows environments.
  • Provide example REST calls using curl or httpie alongside ARMClient in PowerShell sections, or at least in a separate tab or note.
  • Review and update prerequisites to include Linux/macOS-specific guidance for environment setup and tooling.
GitHub Create Pull Request
Azure Resource Manager Create and deploy a template spec with Bicep ...urce-manager/bicep/quickstart-create-template-specs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exhibits a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, without providing Linux/macOS equivalents. The examples and instructions assume a Windows environment, and there is no mention of Linux-specific considerations or alternative paths. Additionally, the only editor recommended is Visual Studio Code, which, while cross-platform, is often associated with Windows development. There is also a reference to a known issue with PowerShell on Windows, but no guidance for Linux users.
Recommendations
  • Provide both Windows and Linux/macOS file path examples in all CLI and PowerShell commands (e.g., C:\templates\main.bicep and ~/templates/main.bicep).
  • Explicitly state that the Azure CLI and Bicep tools are cross-platform, and provide any necessary Linux/macOS installation or usage notes.
  • Include notes or tabs for Bash shell usage, especially for variable assignment and command syntax differences.
  • When referencing issues or known problems, clarify if they are Windows-specific and provide Linux/macOS alternatives if available.
  • Consider recommending additional cross-platform editors or tools, or clarify that Visual Studio Code is available on all major operating systems.
GitHub Create Pull Request
Azure Resource Manager Create Azure Managed Application that deploys storage account encrypted with customer-managed key ...ed-applications/create-storage-customer-managed-key.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the first and primary example for building Bicep files, with Azure CLI as a secondary option. There are no explicit Linux/macOS instructions or screenshots, and the workflow assumes familiarity with Windows-centric tools (e.g., Visual Studio Code, PowerShell). The portal instructions and screenshots do not address cross-platform differences, and there is no mention of Linux-specific considerations or alternative editors.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows, and provide any OS-specific notes if needed.
  • Include screenshots or instructions for Linux/macOS environments where UI or tool behavior may differ.
  • Suggest alternative editors (e.g., VS Code is cross-platform, but mention alternatives like Vim, nano, etc. for Linux users).
  • Add a section or callout for Linux/macOS users, confirming parity and noting any differences in setup or workflow.
  • Avoid language that implies Windows is the default platform (e.g., avoid 'open PowerShell' as the only shell option).
GitHub Create Pull Request
Azure Resource Manager Use Bicep to deploy an Azure Managed Application definition ...anager/managed-applications/deploy-bicep-definition.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. PowerShell examples and terminology are consistently presented before Azure CLI (Linux-friendly) alternatives. Visual Studio Code is recommended as the editor, with no mention of Linux-specific editors or environments. The use of PowerShell-specific concepts (such as splatting) and variable syntax ($mrgname) is explained in detail, while Bash/CLI equivalents are less emphasized. There is no explicit mention of Linux or cross-platform considerations, and Windows-centric tools and patterns are referenced throughout.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first in some sections to avoid Windows-first bias.
  • Explicitly mention that all steps and tools are cross-platform, and clarify that Azure CLI and VS Code are available on Linux and macOS.
  • Include references to Linux-native editors (such as Vim, Nano) or terminal environments where appropriate.
  • Provide additional context or explanations for Bash/CLI commands, similar to the detail given for PowerShell (e.g., explain Bash variable syntax and command chaining).
  • Add a short section or note on running these steps in Linux/macOS environments, including any platform-specific considerations.
  • Avoid PowerShell-specific terminology (like 'splatting') without offering equivalent Bash explanations.
GitHub Create Pull Request
Azure Resource Manager Use APIs to create a private link for managing Azure resources ...ager/management/create-private-link-access-commands.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for resource creation and association, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. There is no mention of Linux-specific tools or shell scripting, and PowerShell is referenced before REST in some sections. The 'Create private endpoint' section links to PowerShell documentation before CLI, and does not mention Linux shell or scripting alternatives. No Linux-specific context or troubleshooting is provided.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux users where appropriate.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS.
  • List CLI examples before PowerShell to avoid implicit Windows-first ordering.
  • Include links to Linux-specific documentation, troubleshooting, or environment setup.
  • Mention that PowerShell Core is available cross-platform, but clarify differences for Linux users.
  • Ensure parity in example depth and troubleshooting for both CLI and PowerShell.
GitHub Create Pull Request
Azure Resource Manager Deploy a service catalog managed application ...aged-applications/deploy-service-catalog-quickstart.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples (which are Windows-centric) are consistently presented before Azure CLI (Bash/Linux) examples in each code section. Visual Studio Code is recommended as the editor, but the terminal instructions default to PowerShell first, with Bash mentioned as an alternative only for Azure CLI. There is frequent reference to PowerShell-specific syntax (e.g., backtick for line continuation, PowerShell escape characters) and Windows patterns, while Linux/Bash equivalents are explained second. No explicit Linux-only tools or workflows are discussed, and the overall structure prioritizes Windows/PowerShell users.
Recommendations
  • Alternate the order of examples so that Azure CLI/Bash instructions are presented first in some sections, or present both side-by-side.
  • Explicitly mention Linux and macOS compatibility in prerequisites and instructions, including guidance for using Bash terminals on those platforms.
  • Provide examples using native Linux editors (e.g., Vim, Nano) or clarify that Visual Studio Code is cross-platform.
  • Discuss differences in command syntax and environment setup between Windows and Linux/macOS more thoroughly.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, environment variables).
  • Where PowerShell-specific syntax is explained, provide parallel explanations for Bash/Linux syntax and escape characters.
GitHub Create Pull Request
Azure Resource Manager What are the resource providers for Azure services ...anager/management/azure-services-resource-providers.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits mild Windows bias. In the 'Find resource provider' section, examples are given for Azure CLI (cross-platform), PowerShell (Windows-centric), and Python (cross-platform). However, PowerShell is presented before Python, and no explicit Linux shell (bash) example is provided. The registration section references the 'Windows Azure Service Management API', and several resource providers and services are named with 'Windows' (e.g., Microsoft.WindowsIoT, Microsoft.WindowsDefenderATP), but Linux equivalents are not highlighted or mentioned. There is no explicit Linux shell or scripting example, and Windows terminology appears before or instead of Linux alternatives.
Recommendations
  • Add a bash shell example for listing resources using Azure CLI, to explicitly show Linux usage.
  • When listing scripting examples, alternate the order or explicitly mention cross-platform compatibility.
  • In the registration section, clarify that the Azure Service Management API is not Windows-only, or mention Linux/Unix management APIs if applicable.
  • For resource providers with Windows-specific names, consider mentioning Linux equivalents or clarifying platform support.
  • Ensure that documentation does not imply Windows is the default or preferred platform, and highlight cross-platform capabilities where relevant.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager vs. classic deployment: Understand deployment models and the state of your resources ...azure-resource-manager/management/deployment-models.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only command-line example given, with no Azure CLI or Linux shell equivalents. Windows tools and patterns (such as remote desktop and remote PowerShell traffic) are mentioned before Linux alternatives (SSH), and the example diagrams and links focus on Windows VMs. The migration guidance and next steps also prioritize PowerShell over cross-platform tools, and there is a lack of Linux-specific examples or parity in instructions.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell commands for all resource management operations.
  • Ensure that Linux-specific scenarios (such as SSH access, Linux VM deployment, and migration) are described with equal detail and prominence as Windows scenarios.
  • Add links to Linux VM reference architectures and migration guides, not just Windows VM resources.
  • When listing remote access methods, mention SSH for Linux before or alongside RDP/PowerShell for Windows.
  • Balance the use of Windows-centric terminology and tools with cross-platform alternatives throughout the documentation.
GitHub Create Pull Request
Azure Resource Manager Manage resource management private links ...ager/management/manage-private-link-access-commands.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. PowerShell is a Windows-centric tool and is featured equally alongside Azure CLI, but there are no examples for Linux-native shells (e.g., Bash scripts, curl, or other Linux command-line tools) beyond the generic Azure CLI and REST API calls. The login instructions reference Connect-AzAccount (PowerShell) before az login (CLI), and PowerShell is presented as a primary automation option, which may signal a Windows bias. There are no explicit Linux-specific examples or instructions.
Recommendations
  • Add explicit Bash/curl examples for REST API calls to demonstrate Linux-native usage.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider adding a section or tab for Bash scripting to show parity with PowerShell automation.
  • Avoid presenting PowerShell as the default or primary automation tool; balance with Linux-native alternatives.
  • Mention installation and usage instructions for Azure CLI on Linux systems.
GitHub Create Pull Request
Azure Resource Manager Manage Azure resources by using the REST API ...e-resource-manager/management/manage-resources-rest.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and resource listing, but PowerShell examples are given equal prominence and detail, despite PowerShell being primarily a Windows tool. There are references to Visual Studio Code and PowerShell for template deployment, but no mention of Linux-native editors or tools. The documentation does not provide explicit Linux shell (bash) examples beyond Azure CLI, nor does it reference Linux-specific patterns or alternatives to Windows-centric tools. The order of examples sometimes places PowerShell before or alongside CLI, which may suggest Windows-first thinking. There are no explicit Linux or macOS-specific instructions or troubleshooting notes.
Recommendations
  • Add explicit bash shell examples for REST calls and authentication, especially for steps that use PowerShell.
  • Reference Linux-native editors (e.g., Vim, Nano) or cross-platform alternatives alongside Visual Studio Code.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Provide troubleshooting notes or tips for Linux/macOS users where file paths, environment variables, or authentication flows may differ.
  • Avoid referencing PowerShell as the default or primary method; present Azure CLI or bash examples first when possible.
  • Include links to Linux/macOS installation guides for Azure CLI and other required tools.
GitHub Create Pull Request
Azure Resource Manager Move guidance for Cloud Services (extended support) deployment model resources ...nt/move-limitations/cloud-services-extended-support.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell before Azure CLI and REST API when describing move operations, implicitly prioritizing Windows-centric tools. There are no explicit Linux-specific examples or mentions of Linux tools or shell commands, and the guidance does not provide parity in example commands or workflows for Linux users.
Recommendations
  • List Azure CLI before Azure PowerShell when describing cross-platform operations, or present them together to avoid implicit prioritization.
  • Provide explicit example commands for both Azure PowerShell and Azure CLI, highlighting usage on Linux/macOS terminals.
  • Mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Include links or references to Linux-specific documentation or troubleshooting guides where relevant.
  • Avoid using Windows-centric terminology or tools as defaults unless necessary, and clarify platform applicability.
GitHub Create Pull Request
Azure Resource Manager Configure data boundary ...re-resource-manager/management/manage-data-boundary.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation demonstrates mild Windows bias by consistently providing Azure PowerShell examples alongside Azure CLI and REST API, referencing PowerShell-specific modules, and linking to PowerShell-centric role assignment documentation. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux users. Additionally, PowerShell examples and references often appear before or alongside CLI examples, rather than prioritizing cross-platform CLI tools.
Recommendations
  • Prioritize Azure CLI examples before PowerShell in all code tabs and sections, as CLI is natively cross-platform.
  • Add explicit notes clarifying that Azure CLI works on Linux, macOS, and Windows, while PowerShell may require additional setup on non-Windows platforms.
  • Where PowerShell is referenced, provide equivalent Bash or shell script examples for Linux users.
  • Review and update links to role assignment documentation to include CLI and REST API guides, not just PowerShell.
  • Consider removing or de-emphasizing PowerShell examples unless a specific Windows-only scenario is being described.
GitHub Create Pull Request
Azure Resource Manager Move Azure resources to a new resource group or subscription ...ger/management/move-resource-group-and-subscription.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most operations, but there is a notable emphasis on PowerShell, which is traditionally a Windows-centric tool. In several places, PowerShell is listed before CLI, and there are no explicit Linux/Bash-specific examples or notes about running commands in a Linux environment. The CLI examples are generic and do not clarify Linux-specific nuances (e.g., quoting, environment variables). There are also no references to Linux-native tools or shell scripting, and the PowerShell tab is sometimes shown before the CLI tab. This could make the documentation feel Windows-biased and less approachable for Linux users.
Recommendations
  • Ensure that Azure CLI examples are always presented before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
  • Add explicit notes or sections about running Azure CLI commands in Linux/Bash environments, including any differences in quoting, environment variables, or output parsing.
  • Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, but also provide Bash shell alternatives for scripting scenarios.
  • Include Linux/Bash-specific examples for common tasks, such as using environment variables, piping, and parsing output with jq.
  • Avoid using PowerShell syntax (e.g., $variable = ...) in CLI sections, as this can confuse Linux users who expect Bash syntax.
  • Where possible, mention Linux tools or patterns (e.g., using export for environment variables, using grep/jq for output processing) alongside Windows/PowerShell equivalents.
  • Add a short section or callout at the top clarifying that all CLI examples are cross-platform and tested on both Windows and Linux.
GitHub Create Pull Request
Azure Resource Manager Evaluate a cloud workload for relocation ...azure-resource-manager/management/relocate-evaluate.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure tools and workflows that are primarily accessed through the Azure portal or PowerShell, with no mention of Linux-specific tools, CLI workflows, or cross-platform scripting examples. The only explicit example for moving public IP configurations links to a PowerShell-based guide, and there are no Linux or Azure CLI equivalents provided. The documentation also omits any discussion of Linux-based automation, discovery, or scripting patterns, and does not mention open-source or cross-platform alternatives.
Recommendations
  • Provide Azure CLI examples alongside PowerShell, especially for tasks like moving public IP configurations, to ensure Linux users have parity.
  • Mention cross-platform automation and scripting options (such as Bash scripts, Ansible, or Terraform) when discussing updating scripts and infrastructure as code.
  • Include references to Linux-native tools or workflows for resource discovery and management, such as using Azure CLI on Linux, or open-source visualization tools.
  • Ensure that documentation links and examples are not exclusively PowerShell-based; always offer CLI or REST API alternatives.
  • Explicitly state that all tools and procedures can be performed on Linux as well as Windows, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Resource Manager Handling special cases when moving virtual machines to resource group or subscription .../move-limitations/virtual-machines-move-limitations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell is featured equally or slightly more heavily, and is referenced in several key steps (e.g., accepting Marketplace terms, recreating VMs) as the primary method. There is a subtle Windows bias in the use of PowerShell and Windows-centric terminology, with no explicit mention of Linux shell scripting or Linux-specific tools. The documentation does not provide bash or shell script examples, nor does it discuss Linux-specific patterns or considerations beyond referencing Azure Disk Encryption for Linux VMs.
Recommendations
  • Add bash/shell script examples alongside Azure CLI and PowerShell, especially for steps involving scripting or automation.
  • Explicitly mention that Azure CLI commands can be run natively on Linux/macOS, and provide guidance for Linux users where appropriate.
  • Where PowerShell is referenced as the primary method (e.g., accepting Marketplace terms), clarify that Azure CLI is cross-platform and provide equivalent CLI commands.
  • Include notes or sections highlighting any Linux-specific considerations, such as file system permissions, environment variables, or differences in command-line usage.
  • Review the order of examples to avoid always listing PowerShell first; alternate or lead with Azure CLI where possible, as it is more platform-neutral.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure App Services to another region ...anager/management/relocation/relocation-app-service.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways: Windows-specific paths (e.g., %HOME%\site) are referenced without mention of Linux equivalents; Kudu and FTP credential management are described in a manner that assumes familiarity with Windows tooling; PowerShell is highlighted in the 'Next steps' section for app cloning, with no equivalent Azure CLI or Linux shell examples; and there is a general lack of Linux-specific guidance or examples throughout the document.
Recommendations
  • Include Linux-specific paths and environment variable references (e.g., $HOME/site for Linux).
  • Provide Azure CLI and Bash examples alongside PowerShell for all operations, especially in 'Next steps' and backup/restore procedures.
  • Clarify that Kudu and FTP management are cross-platform, and provide instructions for Linux users where relevant.
  • Explicitly mention that App Service supports both Windows and Linux, and highlight any differences in migration steps or tooling.
  • Ensure that all references to file systems, environment variables, and deployment tools are platform-neutral or have both Windows and Linux variants.
  • Add links to Linux-focused documentation or tutorials where available.
GitHub Create Pull Request
Azure Resource Manager Relocate your Azure Functions app to another Azure region ...-manager/management/relocation/relocation-functions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits subtle Windows bias. When discussing scripting options for recreating infrastructure, 'Azure CLI/PowerShell scripts' are mentioned together, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI, and no explicit mention of Bash or Linux shell scripting. The use of Windows-style environment variables (e.g., '%HOME%\site') is present, with no Linux equivalent ($HOME/site) shown. There are no explicit Linux-specific examples or guidance, and the documentation does not provide parity for Linux users in terms of scripting or file path conventions.
Recommendations
  • Explicitly mention Bash/Linux shell scripting as an option alongside Azure CLI and PowerShell.
  • When referencing environment variables or file paths, provide both Windows ('%HOME%\site') and Linux ('$HOME/site') formats.
  • Include examples or notes for Linux container deployments and Linux-specific storage mounting patterns.
  • Ensure that CLI examples use cross-platform syntax and clarify any OS-specific differences.
  • Add guidance for Linux users where patterns or tools differ from Windows, such as authentication, file system access, or deployment methods.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Backup to another region ...rce-manager/management/relocation/relocation-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific instructions and terminology (e.g., 'install the latest Windows updates') are presented before Linux equivalents, and Linux guidance is less detailed ('refer to distributor guidance'). Examples and scripts are given in Azure PowerShell format, with no mention of Bash or Linux CLI alternatives. The backup agent section references the MARS agent, which is Windows-only, with no mention of Linux backup solutions or agents. Screenshots and step-by-step instructions are focused on Windows environments.
Recommendations
  • Provide Linux-specific examples and step-by-step instructions alongside Windows guidance, especially for certificate updates and VM preparation.
  • Include Bash/Azure CLI script examples for bulk VM protection and resource management, not just Azure PowerShell.
  • Clarify backup agent options for Linux on-premises resources, and reference Linux-compatible solutions where applicable.
  • Ensure that instructions for tasks like certificate management, firewall configuration, and backup agent installation are equally detailed for both Windows and Linux.
  • Add screenshots and walkthroughs for Linux environments where relevant.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Container Registry to another region ...management/relocation/relocation-container-registry.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias by frequently providing PowerShell examples (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Linux/bash or cross-platform alternatives. PowerShell commands are mentioned before or instead of Azure CLI/bash examples, and some tasks (such as repository listing) use Windows-centric tools. There is a lack of explicit Linux/bash examples for several key steps, and the scripting guidance is inconsistent in platform parity.
Recommendations
  • Provide bash/Azure CLI examples alongside PowerShell commands for all tasks, especially for repository listing, image import, and AKS integration.
  • When introducing commands, present Azure CLI/bash examples first or in parallel with PowerShell, to avoid Windows-first ordering.
  • Clarify which commands are cross-platform and which are Windows-specific, and note any platform limitations.
  • Add explicit Linux/macOS instructions for tasks currently only described with PowerShell.
  • Ensure scripting examples (such as the import loop) are clearly marked as bash and provide PowerShell equivalents only as secondary options.
  • Review all tool references to ensure Linux tools (e.g., bash, Azure CLI) are given equal prominence to Windows tools.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Hubs to another region ...-manager/management/relocation/relocation-event-hub.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is given a dedicated tab for template modification, with explicit command examples (Get-AzLocation) and links to Azure PowerShell documentation, while no equivalent Bash, Azure CLI, or Linux shell examples are provided. The instructions for region code lookup reference PowerShell first and exclusively. There are no Linux-specific or cross-platform command-line examples for key steps such as template deployment or resource management. The Azure portal is referenced throughout, but when scripting is discussed, only PowerShell is shown.
Recommendations
  • Add Azure CLI examples and tabs alongside PowerShell for all command-line instructions, including region code lookup and template deployment.
  • Include Bash or shell script examples for Linux users where automation is discussed.
  • Reference Azure CLI documentation equally with PowerShell in all relevant sections.
  • Ensure that cross-platform tools and workflows are presented before or alongside Windows-specific ones, not after.
  • Explicitly state that all steps can be performed on Linux, macOS, and Windows, and provide parity in instructions.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure HDInsight clusters to another region ...-manager/management/relocation/relocation-hdinsight.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently listing Azure PowerShell as a primary method for exporting and deploying templates, often before or alongside Azure CLI. There are no explicit Linux shell (bash) examples, nor references to Linux-specific tools or workflows. The use of terms like 'Azure PowerShell' and the absence of Linux command-line examples or parity in deployment instructions suggest a preference for Windows-centric tools and patterns.
Recommendations
  • Add explicit bash/Linux shell examples for exporting and deploying ARM/Bicep templates, using Azure CLI in a Linux context.
  • Clarify that Azure CLI is cross-platform and provide step-by-step instructions for Linux users, including installation and usage in bash.
  • Reorder examples so that Azure CLI (which is platform-neutral) appears before Azure PowerShell, or present both equally.
  • Mention that Azure Cloud Shell supports both bash and PowerShell, and provide examples for both.
  • Include notes or sections on Linux-specific considerations, such as SSH key management, file permissions, and environment setup.
  • Avoid implying that PowerShell is the default or preferred method unless there is a technical reason.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Storage Account to another region ...er/management/relocation/relocation-storage-account.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. All command-line examples are provided exclusively using Azure PowerShell, with no mention of Azure CLI or Bash equivalents, which are more common on Linux and macOS. The structure consistently presents PowerShell instructions before any alternative, and there are no Linux-specific instructions or examples. This may hinder accessibility for users working on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including template export, modification, deployment, and resource deletion.
  • Include Bash shell instructions where appropriate, especially for AzCopy usage and scripting.
  • Explicitly mention cross-platform compatibility for tools like AzCopy and provide installation and usage notes for Linux/macOS.
  • Reorganize sections so that PowerShell and CLI/Bash examples are presented with equal prominence, possibly using tabs for 'Azure PowerShell', 'Azure CLI', and 'Portal'.
  • Reference Linux/macOS documentation for any tools or procedures that differ from Windows.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure NSG to another region ...anagement/relocation/relocation-virtual-network-nsg.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides detailed instructions for relocating an Azure NSG using the Azure Portal and PowerShell, both of which are Windows-centric tools. There are no examples or instructions for Linux-native tools such as Azure CLI, Bash, or cross-platform scripting. PowerShell is presented as the only command-line option, and Windows tools (e.g., Notepad) are referenced for editing files. This creates a bias towards Windows users and leaves Linux users without direct guidance.
Recommendations
  • Add equivalent step-by-step instructions using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
  • Provide Bash script examples for exporting, modifying, and redeploying NSGs using Azure CLI.
  • Replace or supplement references to Notepad with cross-platform editors (e.g., vim, nano, code) or generic instructions for editing JSON files.
  • Ensure all command-line steps are available in both PowerShell and Azure CLI tabs, with parity in detail and explanation.
  • Mention that Azure CLI can be installed and used on Windows, Linux, and macOS, and provide installation links.
GitHub Create Pull Request
Azure Resource Manager Understand how Azure Resource Manager throttles requests ...ce-manager/management/request-limits-and-throttling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in its examples and guidance. PowerShell is featured prominently with multiple code samples and debugging instructions, and it is presented before Azure CLI. There are no Linux-specific shell (e.g., Bash, curl) examples for retrieving headers, nor is there mention of Linux tools or patterns for interacting with Azure Resource Manager APIs. The focus on PowerShell and lack of Linux-native examples may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add Linux/Bash/curl examples for retrieving rate limit headers from Azure Resource Manager REST API responses.
  • Include examples using common Linux tools (e.g., wget, curl, jq) to demonstrate how to parse response headers.
  • Ensure Azure CLI examples are presented before or alongside PowerShell, and clarify that Azure CLI is cross-platform.
  • Explicitly mention that all shown operations can be performed on Linux, macOS, and Windows, and provide platform-agnostic instructions where possible.
  • Consider adding a section or note about using REST APIs directly from any platform, with sample requests and header parsing.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Key Vault to another region ...-manager/management/relocation/relocation-key-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for key operations (template export, modification, deployment) without equivalent Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and its use is prioritized over cross-platform alternatives. The Azure CLI is mentioned only in passing and not used in any step-by-step instructions. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with PowerShell commands and patterns.
Recommendations
  • Add step-by-step Azure CLI examples for all operations currently covered by PowerShell, including template export, modification, and deployment.
  • Include Bash script examples for common tasks to demonstrate Linux parity.
  • When listing tools or methods (e.g., Azure portal, CLI, PowerShell), present Azure CLI before or alongside PowerShell to avoid 'windows_first' ordering.
  • Explicitly mention that all procedures can be performed on Linux, macOS, and Windows, and provide cross-platform guidance where relevant.
  • Ensure troubleshooting tips and references include CLI-based solutions, not just PowerShell.
  • Consider adding a table or section comparing PowerShell and CLI commands for each major step.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Virtual Network to another region ...er/management/relocation/relocation-virtual-network.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides detailed instructions for relocating an Azure Virtual Network using the Azure Portal and PowerShell, but omits examples for Linux-native tools or cross-platform CLI usage. PowerShell is featured as the sole scripting/automation method, and Windows-specific tools (e.g., Notepad) are referenced. There is no mention of Azure CLI, Bash, or other Linux-friendly approaches, and PowerShell is presented before any alternative automation options.
Recommendations
  • Add Azure CLI examples for each step alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Replace or supplement references to Notepad with platform-neutral editors (e.g., 'edit with your preferred text editor').
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide Bash scripting alternatives.
  • Ensure that automation and scripting sections do not assume a Windows environment; include instructions for Linux and macOS users.
  • Consider reordering or parallelizing instructions so that Windows and Linux approaches are presented together, rather than Windows/PowerShell first.
GitHub Create Pull Request
Azure Resource Manager Azure resource providers and types ...rce-manager/management/resource-providers-and-types.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias. The Azure portal (a GUI tool most commonly used on Windows) is presented first and in greatest detail, with multiple screenshots and step-by-step instructions. Azure PowerShell, a Windows-centric tool, is given a full section with detailed command examples before Azure CLI and Python. The CLI and Python examples are present and comprehensive, but the ordering and emphasis favor Windows-native tools and patterns. There is no mention of Linux-specific tools, shell patterns, or alternative workflows (e.g., Bash scripting, automation via Linux-native tools). The only explicit reference to 'Windows' is in the context of the 'Windows Azure Service Management API' in an informational note, reinforcing the Windows-centric framing.
Recommendations
  • Add Linux-specific instructions or notes, such as using Bash scripts or automation via cron, where relevant.
  • Reorder sections so that cross-platform tools (Azure CLI, Python SDK) appear before Windows-centric tools (Azure PowerShell).
  • Include screenshots or examples of using the Azure portal on Linux/macOS browsers, or clarify that the portal is cross-platform.
  • Mention that Azure CLI and Python SDK are fully supported on Linux and macOS, and provide installation links for those platforms.
  • Consider adding a section for automation using Bash or other Linux-native tools, or link to such resources.
  • Avoid referring to the 'Windows Azure Service Management API' without clarifying its legacy status and cross-platform alternatives.
GitHub Create Pull Request
Azure Resource Manager Use tags to organize your Azure resources and management hierarchy ...les/azure-resource-manager/management/tag-resources.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and REST API as primary tools for tag operations, mentioning Azure PowerShell before Azure CLI in the 'Next steps' section, and highlighting PowerShell support for tag operations in the access control discussion. Linux equivalents (Azure CLI) are mentioned but are not given equal prominence or examples. There are no explicit Linux or Bash examples, and Windows-centric tools/patterns are referenced first.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side throughout the documentation, especially in sections discussing tag operations and access.
  • Mention Azure CLI before or alongside PowerShell in lists and recommendations to avoid implying a Windows-first workflow.
  • Include explicit Linux/Bash usage examples for tag operations, demonstrating parity with PowerShell instructions.
  • Clarify that both Azure CLI and PowerShell are cross-platform, and provide guidance for users on Linux and macOS.
  • Review and update all tool references to ensure equal visibility and instruction for both Windows and Linux users.
GitHub Create Pull Request
Azure Resource Manager Migrating to TLS 1.2 for Azure Resource Manager ...icles/azure-resource-manager/management/tls-support.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Windows versions and tools first, providing examples and troubleshooting steps primarily for Windows environments (e.g., PowerShell, WinHTTP, .NET Framework, Visual Studio, Fiddler), and omitting equivalent guidance or examples for Linux or macOS clients. There are no Linux-specific instructions, tools, or troubleshooting steps mentioned.
Recommendations
  • Add explicit guidance for Linux and macOS users, including how to verify and configure TLS 1.2 support on those platforms.
  • Include examples for popular Linux tools (e.g., curl, openssl, wget) to check TLS versions.
  • Mention how to update or configure TLS settings for common Linux frameworks and runtimes (e.g., Python, Java, Node.js).
  • List Linux distributions and their default TLS support, similar to the Windows version notes.
  • Provide troubleshooting steps and tools for Linux environments (e.g., using OpenSSL s_client, strace, or system logs).
  • Balance the order of examples and recommendations so that Windows and Linux/macOS are treated equally.
GitHub Create Pull Request
Azure Resource Manager CI/CD with Azure Pipelines and templates ...e-manager/templates/add-template-to-azure-pipelines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based deployment examples, referencing Windows-specific tools and patterns (such as Azure PowerShell and AzureFileCopy tasks), and using Windows-based VM images in YAML samples. There is no mention of Bash, Linux-native scripting, or cross-platform alternatives, and Linux examples are missing even though Azure Pipelines supports Ubuntu and other Linux agents.
Recommendations
  • Provide equivalent Bash or cross-platform script examples for ARM template deployment, using the Azure CLI.
  • Include YAML samples that use 'ubuntu-latest' or other Linux agents for all deployment scenarios, not just PowerShell.
  • Mention and demonstrate Linux-native tools (e.g., AzCopy via CLI, Azure CLI for deployments) alongside Windows tools.
  • Clarify which tasks and scripts are cross-platform and which are Windows-specific, and recommend alternatives for Linux users.
  • Add a section or callouts for Linux users, including troubleshooting tips and best practices for non-Windows environments.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of a variable ...les/azure-resource-manager/templates/copy-variables.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias. In the 'Copy limits' section, Azure PowerShell is mentioned before Azure CLI, and the 'Next steps' section links only to PowerShell deployment instructions, omitting Linux-native or cross-platform CLI deployment guides. There are no explicit Linux or Bash examples, and the deployment tooling references prioritize Windows-centric tools.
Recommendations
  • Add explicit examples and instructions for deploying ARM templates using Azure CLI, including Linux and macOS usage.
  • In the 'Next steps' section, include links to both PowerShell and Azure CLI deployment guides to ensure parity.
  • When listing supported tools or versions, alternate the order or mention Azure CLI first to avoid Windows-first perception.
  • Consider including a note or section on cross-platform deployment options, highlighting Bash, CLI, and automation on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Tag support for Azure resources ...icles/azure-resource-manager/management/tag-support.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page contains evidence of Windows bias. In the 'Microsoft.Compute' section, the note on generalizing a virtual machine lists the PowerShell command (Set-AzVm -Generalized) before the Azure CLI equivalent (az vm generalize). Additionally, the only command-line examples given for updating tags on certain resources (e.g., IP groups) use Azure CLI, but there is a tendency to mention PowerShell or Windows-centric tools first. The documentation also references Windows-specific tools and resource types (e.g., AzureStackHCI, Windows365, DevelopmentWindows365) without equivalent Linux-focused examples or resources. There are no explicit Linux shell (bash) examples, and Windows-centric terminology and tools are mentioned more frequently and/or first.
Recommendations
  • Ensure command-line examples are provided for both PowerShell and bash/Azure CLI, and alternate which is listed first.
  • Include Linux-focused resource types and examples where relevant, or clarify parity.
  • Avoid mentioning Windows tools or patterns exclusively; when referencing a Windows tool, provide the Linux equivalent in parallel.
  • Audit documentation for resource types and features that may be Windows-centric and add notes or examples for Linux users.
  • Where possible, use cross-platform terminology and avoid assuming a Windows environment.
GitHub Create Pull Request
Azure Resource Manager Create & deploy Visual Studio resource group projects ...r/templates/create-visual-studio-deployment-project.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows and Visual Studio users, with all examples and workflows based on Visual Studio (a Windows-centric IDE) and PowerShell scripts. There are no examples or guidance for Linux or cross-platform users, such as those using VS Code, Azure CLI, or Bash. The only deployment scripts shown are PowerShell-based, and the workflow assumes the use of Windows file paths and tooling. Linux alternatives, such as Bash scripts or Azure CLI commands, are not mentioned or provided.
Recommendations
  • Add equivalent instructions for Linux users, such as using VS Code or the Azure CLI to create and deploy resource group templates.
  • Provide Bash or shell script examples for deployment, or show how to use Azure CLI (az deployment group create, etc.) instead of only PowerShell scripts.
  • Mention and link to cross-platform tools and workflows earlier in the documentation, not just Visual Studio and PowerShell.
  • Clarify which steps are Windows-specific and provide alternative steps for macOS/Linux environments.
  • Include a section or callout for users who do not use Visual Studio, explaining how to achieve the same results with cross-platform tools.
GitHub Create Pull Request
Azure Resource Manager Azure deployment templates with Azure CLI – Azure Resource Manager | Microsoft Docs ...rticles/azure-resource-manager/templates/deploy-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. While most examples use Azure CLI (which is cross-platform), there are several places where Windows-specific shells (CMD, PowerShell) are mentioned before or instead of Linux equivalents. Formatting for parameters and variables is explained for Windows shells, but Linux/Bash examples are less detailed or appear after Windows instructions. There are no explicit PowerShell script blocks, but Windows command-line patterns and escaping are described in detail, while Linux/Bash usage is less emphasized.
Recommendations
  • Ensure that Bash/Linux examples are provided alongside Windows CMD/PowerShell examples, especially when discussing parameter formatting and variable assignment.
  • When describing shell-specific behaviors (such as escaping quotes or passing arrays), present Linux/Bash instructions first or equally with Windows instructions.
  • Add explicit Bash and Linux shell examples for all command-line snippets, including variable assignment and parameter passing.
  • Clarify which instructions apply to which platforms, and avoid assuming Windows as the default environment.
  • Where possible, use platform-neutral syntax and highlight cross-platform compatibility.
GitHub Create Pull Request
Azure Resource Manager Deploy to Azure button ...e-resource-manager/templates/deploy-to-azure-button.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for URL encoding, omitting equivalent Linux/macOS command-line examples (e.g., Bash, Python, curl). This prioritizes Windows tooling and patterns, potentially making it less accessible for users on Linux or macOS. No Linux-specific tools or cross-platform alternatives are mentioned, and the PowerShell example appears before any suggestion of online tools.
Recommendations
  • Add Linux/macOS command-line examples for URL encoding, such as using Python, Bash, or curl.
  • Explicitly mention that PowerShell is available cross-platform, or provide instructions for installing PowerShell on Linux/macOS if retaining the example.
  • Present cross-platform solutions first or alongside Windows-specific ones to ensure parity.
  • Reference online tools and platform-agnostic methods before platform-specific command-line examples.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager deployment modes ...s/azure-resource-manager/templates/deployment-modes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented first and in detail for deployment mode examples, with a Windows-style file path (c:\MyTemplates\storage.json) used in the PowerShell example. The CLI example follows, but there is no mention of Linux-specific considerations, such as file paths or shell environments. References to deployment with PowerShell are more prominent, and the 'Next steps' section links to PowerShell-specific deployment guidance before more general resources.
Recommendations
  • Provide Linux/Unix shell examples alongside or before PowerShell, including file paths using forward slashes (e.g., ./storage.json).
  • Clarify that Azure CLI works cross-platform and show examples in Bash or other shells.
  • Balance references to PowerShell and CLI in 'Next steps', possibly linking to CLI documentation first or equally.
  • Avoid Windows-specific file paths in generic examples; use neutral or platform-agnostic paths.
  • Explicitly state that both PowerShell and CLI are available on Windows, Linux, and macOS, and mention any platform-specific considerations.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Azure Resource Manager templates ...source-manager/templates/deployment-script-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented first in examples, sample templates, and usage scenarios. Most code samples and walkthroughs use PowerShell, with only a few CLI/bash examples provided later. Windows-specific tools and APIs (e.g., CommandLineToArgvW) are referenced without Linux equivalents. There is a lack of parity in example depth and troubleshooting guidance for Linux/bash users, and some instructions (such as using the Cloud Shell 'Try it' button) default to PowerShell. The documentation does not provide balanced, parallel examples for Linux/bash users, and troubleshooting/development sections are PowerShell-centric.
Recommendations
  • Alternate the order of PowerShell and Azure CLI/bash examples throughout the documentation, or present both side-by-side.
  • Provide equally detailed sample templates and walkthroughs for Azure CLI/bash, including inline and external script usage.
  • Include troubleshooting and development environment guidance specifically for Linux/bash users, not just PowerShell.
  • Reference Linux-native tools and APIs where appropriate, or provide Linux equivalents when mentioning Windows-specific tools (e.g., mention how argument parsing works in bash).
  • Ensure that all instructions (such as 'Try it' in Cloud Shell) offer both PowerShell and Bash options, with clear guidance for each.
  • Expand the 'Work with outputs' and 'Monitor and troubleshoot' sections to include bash/CLI-specific details and examples.
  • Review all sample links and ensure there are as many CLI/bash samples as PowerShell samples, with similar complexity.
GitHub Create Pull Request
Azure Resource Manager Template deployment what-if ...les/azure-resource-manager/templates/deploy-what-if.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell (a Windows-centric tool) is featured heavily throughout the page, with examples and output shown in PowerShell syntax and formatting. In several sections, PowerShell commands and output are presented before Azure CLI equivalents, and the output samples use PowerShell formatting. The installation instructions and command references give prominence to PowerShell modules and patterns. While Azure CLI examples are provided and REST API is mentioned, the overall structure and examples lean toward Windows/PowerShell usage, with little attention to Linux-specific nuances or shell environments.
Recommendations
  • Ensure that CLI examples are presented before or alongside PowerShell examples, especially in introductory and output sections.
  • Provide output samples in both PowerShell and Azure CLI formats, and clarify differences in output formatting between Windows and Linux shells.
  • Include notes or sections on running Azure CLI commands in Linux/macOS environments, including shell-specific tips (e.g., bash/zsh syntax, color handling, file redirection).
  • Mention cross-platform compatibility explicitly when discussing installation and usage of Azure CLI and PowerShell.
  • Add troubleshooting or configuration guidance for Linux users, such as handling color output, environment variables, and file paths.
  • Consider including SDK usage examples in Linux-friendly languages (e.g., Python) before or alongside .NET/PowerShell.
GitHub Create Pull Request
Azure Resource Manager Configure development environment for deployment scripts in templates | Microsoft Docs .../templates/deployment-script-template-configure-dev.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a Windows bias by providing PowerShell-heavy examples, using Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows drive letter notation), and presenting PowerShell/Windows workflows before Linux equivalents. Upload and deployment steps rely on PowerShell scripts, with no Bash/Azure CLI alternatives shown for Linux users. Docker volume mapping examples use Windows paths exclusively, omitting Linux/macOS syntax.
Recommendations
  • Provide Bash/Azure CLI examples for uploading deployment scripts to Azure Storage, alongside PowerShell.
  • Include Docker volume mapping examples using Linux/macOS path syntax (e.g., /home/user/docker:/data), not just Windows drive letters.
  • Present Linux/Azure CLI workflows in parallel with PowerShell, or alternate the order to avoid Windows-first presentation.
  • Reference cross-platform tools and commands where possible, and clarify OS-specific steps.
  • Add notes or sections for Linux/macOS users, especially for file system operations and command-line usage.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Deploy a linked template ...nager/templates/deployment-tutorial-linked-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a bias towards Windows by providing detailed Azure PowerShell scripts for key steps (storage upload, deployment), referencing Windows-centric tools and patterns (PowerShell, Cloud Shell with PowerShell), and presenting PowerShell instructions before Azure CLI equivalents. There is no mention of Linux-specific shell scripting or alternative Linux-native tools for uploading templates to storage. The Azure CLI section is present, but less emphasized and appears after PowerShell. The clean-up instructions reference the Azure portal, which is platform-neutral, but overall, the workflow is oriented towards Windows users.
Recommendations
  • Provide Bash shell script examples for uploading templates to Azure Storage, using azcopy or Azure CLI, to complement the PowerShell example.
  • Present Azure CLI instructions before or alongside PowerShell to avoid Windows-first ordering.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI and Bash, and provide guidance for Linux users.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., file paths, permissions, date command differences) in relevant sections.
  • Reference Linux-native tools (such as azcopy) for template upload and management, and provide links to their documentation.
GitHub Create Pull Request
Azure Resource Manager Create parameter file ...es/azure-resource-manager/templates/parameter-files.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying templates with parameter files, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and the PowerShell section is given equal prominence to CLI. There is also a tip referencing Visual Studio, a Windows-centric tool, and a note about PowerShell-specific parameter name conflicts. No Linux-specific examples (e.g., Bash, Linux file paths) or editor/tooling recommendations are given, and Windows patterns (such as file paths and Visual Studio usage) are mentioned without Linux equivalents.
Recommendations
  • Add Linux/Bash examples for deploying with parameter files, using Linux-style file paths (e.g., /home/user/templates/storage.parameters.json).
  • Clarify that Azure CLI works cross-platform and show examples with Linux file paths.
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio, or provide Linux alternatives.
  • Add a note about PowerShell Core availability on Linux, or clarify any differences in usage.
  • Balance the order of examples so that CLI (cross-platform) is presented before PowerShell, or explicitly state platform applicability.
  • If discussing file paths, show both Windows and Linux formats.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Deploy a local Azure Resource Manager template ...anager/templates/deployment-tutorial-local-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation shows mild Windows bias: Windows-specific installation instructions for Azure CLI are listed before Linux/macOS, Azure PowerShell (a Windows-centric tool) is presented as an equal option to Azure CLI, and PowerShell examples are given first in all code tabs. There is no explicit Linux example for shell scripting (e.g., Bash vs. PowerShell), and Visual Studio Code is suggested as the editor, which, while cross-platform, is often associated with Windows. The cleanup instructions use the Azure portal, which is platform-neutral.
Recommendations
  • List Azure CLI installation instructions for Linux/macOS before Windows, or group them together to avoid Windows-first ordering.
  • Present Azure CLI (which is cross-platform and preferred for Linux) examples before PowerShell, or alternate the order in code tabs.
  • Explicitly state that CLI examples are Bash-compatible and provide any necessary notes for Linux/macOS users (e.g., file path conventions, shell differences).
  • Mention alternative editors for Linux (e.g., Vim, nano) alongside Visual Studio Code.
  • Add a brief note on using the Azure CLI in native Linux environments, and clarify that PowerShell is available cross-platform but is more commonly used on Windows.
GitHub Create Pull Request
Azure Resource Manager Create and deploy template spec ...-manager/templates/quickstart-create-template-specs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation exhibits several signs of Windows bias. File paths are consistently given in Windows format (e.g., C:\Templates\...), with no mention of Linux/macOS equivalents. All command-line examples use Windows-style paths, and there are no examples or notes for Linux/macOS users regarding file locations or path syntax. PowerShell is featured prominently, sometimes before Azure CLI, and references to Azure PowerShell are made without equivalent coverage for Bash or other shells. The 'Grant access' section links only to a PowerShell tutorial. There is no mention of Linux-specific tools, nor are there any screenshots or instructions tailored to non-Windows platforms.
Recommendations
  • Provide Linux/macOS path examples alongside Windows paths (e.g., ~/Templates/createStorageV1.json).
  • Add notes or callouts for Linux/macOS users regarding file system differences and path syntax.
  • Ensure Azure CLI examples use cross-platform path syntax or clarify usage on different OSes.
  • Include links to equivalent tutorials for Bash or Azure CLI where PowerShell is referenced.
  • Balance the order of examples so that Azure CLI and PowerShell are presented equally, or alternate which comes first.
  • Add screenshots or instructions for Linux/macOS environments where relevant.
  • Explicitly state that the instructions apply to all supported platforms and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Resource Manager Develop ARM templates for cloud consistency ...source-manager/templates/template-cloud-consistency.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is frequently used as the primary or sole scripting example for verifying template functions, resource providers, VM images, VM sizes, and VM extensions. Windows-centric tools and patterns (such as PowerShell DSC and Windows VM images) are referenced and shown in code samples, while Linux equivalents are either omitted or mentioned only in passing. Examples and default values often reference Windows-specific resources (e.g., 'dotnet-core-music-windows', 'MicrosoftWindowsServer'), and there is a lack of Linux-focused examples for VM images, extensions, and scripts.
Recommendations
  • Provide Linux-focused examples alongside Windows ones, such as using Bash scripts, Linux VM images, and Linux-specific VM extensions.
  • Include Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
  • Use neutral or Linux-inclusive default values in code samples (e.g., reference both Windows and Linux script repositories, VM images, and artifacts).
  • Mention and demonstrate Linux-compatible tools and extensions (e.g., Custom Script Extension for Linux, OMS Agent for Linux) where relevant.
  • Balance references to Windows-specific technologies (like PowerShell DSC) with Linux equivalents (such as cloud-init or Ansible).
  • Ensure documentation language and examples do not assume a Windows environment by default.
GitHub Create Pull Request
Azure Resource Manager Deploy a template spec as a linked template ...ger/templates/template-specs-deploy-linked-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., c:\Templates\deployTS\azuredeploy.json), presenting PowerShell examples before Azure CLI, and referencing Windows-specific issues (e.g., variable assignment in Windows PowerShell). There are no explicit Linux or macOS examples, and no mention of Linux file path conventions or shell environments.
Recommendations
  • Provide Linux/macOS equivalents for file paths (e.g., /home/user/Templates/deployTS/azuredeploy.json) alongside Windows paths.
  • Alternate the order of PowerShell and CLI examples or present them side-by-side to avoid privileging Windows tools.
  • Include notes or examples for running Azure CLI commands in Bash or other Linux shells.
  • Address any platform-specific issues for Linux/macOS users, not just Windows PowerShell.
  • Explicitly state that the instructions apply to all platforms and highlight any differences where relevant.
GitHub Create Pull Request
Azure Resource Manager Deploy ARM template with SAS token - Azure Resource Manager | Microsoft Docs ...ce-manager/templates/secure-template-with-sas-token.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and file paths in examples use Windows-style (e.g., c:\Templates\azuredeploy.json). There is no explicit mention of Linux or cross-platform considerations, and the CLI section only briefly notes Bash compatibility without providing parity for other shells or platforms. The overall structure and examples favor Windows users and workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to balance platform representation.
  • Use platform-neutral file paths in examples (e.g., ./Templates/azuredeploy.json) or provide both Windows and Linux path examples.
  • Explicitly mention Linux/macOS compatibility for Azure CLI commands, and provide notes or examples for common shell differences (e.g., zsh, fish).
  • Add a section or callout for Linux users, highlighting any differences or considerations when using Azure CLI or PowerShell Core on Linux.
  • Ensure that references to tools and workflows are not Windows-centric, and provide links to cross-platform documentation where relevant.
GitHub Create Pull Request
Azure Resource Manager Create a template spec with linked templates ...urce-manager/templates/template-specs-create-linked.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits a Windows bias by consistently using Windows-style file paths (e.g., c:\Templates\...), presenting PowerShell examples before Azure CLI, and referencing Windows-specific issues (e.g., variable assignment in Windows PowerShell). There are no explicit Linux shell examples, and the directory creation instructions assume Windows conventions.
Recommendations
  • Provide Linux/macOS file path examples alongside Windows paths (e.g., /home/user/Templates/linkedTS/azuredeploy.json).
  • Include bash or shell commands for directory creation and file management, not just implicit instructions.
  • Alternate the order of PowerShell and CLI examples, or present them side-by-side to avoid Windows-first presentation.
  • Explicitly mention cross-platform compatibility and note any differences in behavior between Windows and Linux environments.
  • Add troubleshooting notes for Linux/macOS users where relevant, not just Windows PowerShell issues.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager template specs ...les/azure-resource-manager/templates/template-specs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI throughout, but PowerShell is often listed first in code tabs and command explanations. The documentation refers to 'PowerShell script' as a standard deployment process, and repeatedly mentions Azure PowerShell as a primary tool. There is no explicit mention of Linux shells (e.g., Bash) or cross-platform scripting patterns, and no guidance is given for Linux-specific environments or considerations. All command-line examples are either PowerShell or Azure CLI, with PowerShell generally presented first.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or default to CLI first, as Azure CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh).
  • Add notes or sections for Linux users, such as how to install Azure CLI and run commands in Bash.
  • Avoid referring to 'PowerShell script' as the default automation pattern; mention Bash scripts and other cross-platform options.
  • Where possible, include screenshots or walkthroughs from Linux terminals, not just Windows/PowerShell.
  • Clarify that template specs and related tooling are fully supported on Linux and macOS, not just Windows.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Create and deploy template ...r/templates/template-tutorial-create-first-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and patterns (PowerShell, Windows paths, screenshots) are presented either exclusively or before their Linux equivalents. PowerShell is given equal or greater prominence than Azure CLI, and CLI examples are written for Bash but with notes about adapting for Windows. Installation instructions list Windows first, and there are no explicit Linux-specific workflow examples (e.g., using Linux editors, shell environments, or file paths). Screenshots and instructions assume a Windows-style environment, with no mention of Linux desktop equivalents.
Recommendations
  • Ensure installation instructions for Azure CLI list Linux and macOS before or alongside Windows, not after.
  • Provide explicit Linux workflow examples, including using Linux-native editors (e.g., Vim, nano, gedit) and Linux file paths.
  • Include screenshots from Linux environments (e.g., Ubuntu desktop, GNOME Terminal) alongside Windows screenshots.
  • Clarify that Visual Studio Code is cross-platform and mention alternatives for Linux users.
  • Add notes or tabs for running Azure CLI commands in Linux shells (e.g., zsh, fish) and explain any differences in environment variables or file paths.
  • Avoid assuming Windows-style file paths and explain how to adapt instructions for Linux/macOS file systems.
  • Balance PowerShell and CLI coverage, and consider highlighting Azure CLI as the default for cross-platform scenarios.
GitHub Create Pull Request
Azure Resource Manager Deploy VM extensions with template ...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased toward Windows. All examples use Windows VMs, PowerShell scripts, and Windows-specific tools (e.g., Install-WindowsFeature, powershell.exe). There is no mention of Linux VM extensions, Bash scripts, or Linux configuration patterns. The tutorial title and flow focus exclusively on Windows, with no Linux parity or alternative paths.
Recommendations
  • Add parallel examples for deploying VM extensions to Linux VMs, including Bash scripts and Linux-specific configuration (e.g., installing Apache or Nginx).
  • Include links to both Windows and Linux extension documentation at the start.
  • Show how to use Custom Script Extension with Bash or Python scripts on Linux VMs.
  • Provide a Linux quickstart template (e.g., 'Deploy a simple Linux VM') and walk through editing it.
  • Demonstrate retrieving the public IP address using Azure CLI or Bash commands, not only PowerShell.
  • Clarify in the introduction that the tutorial is Windows-specific, or broaden the scope to cover both platforms.
GitHub Create Pull Request
Azure Resource Manager Template with dependent resources ...ate-tutorial-create-templates-with-dependent-resources.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias by exclusively using a Windows VM template for the example, referencing RDP for VM verification (which is Windows-specific), and omitting any mention of Linux VM templates or SSH access. The deployment instructions do provide both Azure CLI (Bash) and PowerShell examples, but the core scenario is centered on Windows resources and tools, with no Linux equivalents or parity in the walkthrough.
Recommendations
  • Include a parallel example using a Linux VM template (e.g., 'Deploy a simple Linux VM') and provide the corresponding template URL.
  • Add instructions for verifying a Linux VM deployment using SSH, alongside the RDP instructions for Windows.
  • Mention both Windows and Linux VM scenarios in the introduction and throughout the tutorial, making it clear that ARM templates can deploy either.
  • Ensure that resource cleanup and verification steps are platform-neutral or provide both Windows and Linux options.
  • Consider alternating or randomizing the order of PowerShell and CLI examples, or presenting them side-by-side, to avoid implicit prioritization.
GitHub Create Pull Request
Azure Resource Manager Use Azure Key Vault in templates ...e-manager/templates/template-tutorial-use-key-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples for interacting with Azure Key Vault and deploying ARM templates use Azure PowerShell, with no equivalent Azure CLI or Bash examples. The tutorial centers on deploying a Windows VM, referencing Windows-specific password requirements and RDP for validation, while omitting Linux VM scenarios and SSH-based access. Windows tools and patterns (PowerShell, RDP, Windows VM templates) are mentioned exclusively and before any Linux alternatives, which are not covered at all.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell scripts for all deployment and validation steps.
  • Include a parallel tutorial for deploying a Linux VM, referencing Linux-specific password/SSH key requirements and validation via SSH.
  • Reference both Windows and Linux VM quickstart templates, and clarify differences in secret usage for each.
  • Offer instructions for connecting to Linux VMs (e.g., using SSH) and validating credentials stored in Key Vault.
  • Ensure all tooling instructions (Cloud Shell, VS Code) mention parity for Linux users and environments.
GitHub Create Pull Request
Azure Resource Manager Use template reference .../templates/template-tutorial-use-template-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is required as the editor, which is cross-platform but often associated with Windows. The deployment section gives both PowerShell and Azure CLI (Bash) examples, but PowerShell is mentioned first and in more detail. There is no mention of Linux-native editors or workflows, and the file upload instructions reference GUI actions typical of Windows environments. There are no explicit Linux tool recommendations or parity in editor instructions.
Recommendations
  • Include instructions for opening and editing the template using Linux-native editors (e.g., Vim, nano, gedit) alongside Visual Studio Code.
  • Present Azure CLI (Bash) examples before or alongside PowerShell examples, rather than after.
  • Clarify that Visual Studio Code is available on Linux and macOS, or suggest alternatives.
  • Add explicit instructions for file upload and verification using Linux command-line tools (e.g., scp, curl, ls, cat) outside of the Azure Cloud Shell GUI.
  • Ensure that all steps (especially deployment and cleanup) have CLI-first examples, and avoid assuming a Windows GUI workflow.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Export and use Azure portal templates ...manager/templates/template-tutorial-export-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. While both Azure PowerShell and Azure CLI examples are provided for deploying templates, PowerShell is presented first, which can imply a Windows-first approach. The prerequisites mention both Azure PowerShell and Azure CLI, but do not provide explicit Linux-specific guidance or examples for installation or usage. There are no Linux shell (bash) examples for tasks like file manipulation or verification, and portal screenshots and instructions do not address platform differences. The clean-up and verification steps rely solely on the Azure portal, with no CLI or Linux shell alternatives.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to avoid Windows-first perception.
  • Provide explicit instructions for installing and using Azure CLI on Linux, including bash shell examples for common tasks (e.g., verifying deployment, cleaning up resources).
  • Include Linux-specific notes or screenshots where relevant, especially when discussing prerequisites and tool installation.
  • Offer alternative verification and clean-up steps using Azure CLI commands, not just portal navigation.
  • Clarify that both PowerShell and CLI are cross-platform, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Resource Manager Use condition in templates ...-manager/templates/template-tutorial-use-conditions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively using a Windows VM template as the example, providing only PowerShell deployment scripts, and referencing Windows-centric resource names and patterns. There is no equivalent Linux VM example, nor are Azure CLI or Bash deployment scripts provided, despite mentioning Bash as an option in Cloud Shell.
Recommendations
  • Include a parallel example using a Linux VM template (e.g., 'vm-simple-linux') alongside the Windows VM template.
  • Provide Azure CLI and Bash script examples for template deployment, not just PowerShell.
  • Reference both Windows and Linux resource templates in the 'Open a Quickstart template' section.
  • Ensure instructions and screenshots show both PowerShell and Bash environments where relevant.
  • Clarify that the tutorial applies to both Windows and Linux deployments, or specify if it is Windows-only.
GitHub Create Pull Request
Azure Resource Manager SKU not available errors ...rce-manager/troubleshooting/error-sku-not-available.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation exhibits a moderate Windows bias. PowerShell examples and references (e.g., New-AzVM, Get-AzComputeResourceSku) are given equal prominence to Azure CLI, but Windows-specific tools and patterns (PowerShell scripting, Windows file paths in az rest output) are used without Linux equivalents. The REST example uses a Windows-style path (.\sku-list.json) for output, and PowerShell scripting is detailed extensively, while Bash or Linux shell scripting is absent. The ordering of tabs often places PowerShell before Portal or REST, and the initial error example uses New-AzVM before az vm create.
Recommendations
  • Add Bash/Linux shell scripting examples for filtering and processing az vm list-skus output, similar to the PowerShell script provided.
  • In REST examples, use cross-platform file paths (e.g., ./sku-list.json) or show both Windows and Linux variants.
  • Ensure that CLI examples (az vm create, az vm list-skus) are presented before or alongside PowerShell examples, not after.
  • Include notes or examples for Linux users, such as using jq for JSON processing, or grep/awk for filtering output.
  • Balance the depth of scripting examples: if PowerShell scripts are shown, provide equivalent Bash scripts for Linux users.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot common Azure deployment errors ...ce-manager/troubleshooting/common-deployment-errors.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates some Windows bias. In the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are mentioned, but PowerShell (a Windows-centric tool) is listed second, which is positive. However, in other areas, Windows-specific links or examples are given before Linux equivalents (e.g., 'AllocationFailed' lists Linux first, but 'SubnetsNotInSameVnet' lists Windows first). There are also references to Windows-specific troubleshooting pages and tools, such as PowerShell, without always providing parity for Linux users. No explicit Linux command-line examples (e.g., bash) are given, and some links reference Windows VM documentation before Linux VM documentation.
Recommendations
  • Ensure that Linux equivalents (e.g., bash, Azure CLI) are always mentioned alongside Windows tools like PowerShell, and consider listing Linux options first or alternating order.
  • Add explicit Linux command-line examples where PowerShell is referenced, especially for common troubleshooting tasks.
  • Where troubleshooting links are provided for Windows, ensure Linux links are also present and given equal prominence.
  • Review all error mitigation steps to ensure Linux users are not required to infer steps from Windows-centric instructions.
  • Consider a dedicated section or callout for cross-platform troubleshooting tips, highlighting differences and parity between Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager Enable debug logging ...source-manager/troubleshooting/enable-debug-logging.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell (a Windows-centric tool) for enabling debug logging, explicitly stating that debug logging cannot be enabled via Azure CLI (the cross-platform tool). All example commands for enabling debug logging use PowerShell, with no Linux-native or Bash alternatives. The documentation refers to PowerShell cmdlets first and in more detail, while Azure CLI is only mentioned as a way to retrieve debug information, not to enable it. There are no examples or guidance for Linux users to achieve parity, and the documentation does not mention platform-specific limitations or workarounds for non-Windows environments.
Recommendations
  • Provide clear guidance and examples for enabling debug logging using Azure CLI or other cross-platform tools, if possible.
  • If debug logging truly cannot be enabled via Azure CLI, explicitly state this as a platform limitation and suggest alternative troubleshooting approaches for Linux/macOS users.
  • Include Bash or shell script examples where possible, or clarify which steps are Windows-specific and which are cross-platform.
  • Consider advocating for feature parity in Azure CLI to allow enabling debug logging, or link to feature requests/community discussions.
  • Add a table or section summarizing platform/tool support for each operation (enable debug logging, retrieve logs, remove history) to help users quickly identify what is possible on their OS.
GitHub Create Pull Request
Azure Vmware Deploy VMware Cloud Director Availability in Azure VMware Solution ...e-cloud-director-availability-in-azure-vmware-solution.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation focuses exclusively on Azure portal Run commands for deploying and managing VMware Cloud Director Availability, which are Windows-centric tools. There are no examples or instructions for Linux-based management, CLI, or automation, nor are Linux-native tools or patterns mentioned. All operational guidance assumes use of the Azure portal and its Run commands, which are primarily accessed from Windows environments.
Recommendations
  • Add equivalent Linux CLI or automation examples, such as using Azure CLI, PowerShell Core (cross-platform), or REST API calls that can be executed from Linux systems.
  • Document how to deploy and manage VMware Cloud Director Availability using Linux-based tools or scripts, including SSH, Ansible, or Terraform.
  • Include instructions for accessing and managing VMware Cloud Director Availability from Linux workstations, not just via the Azure portal.
  • Explicitly mention cross-platform compatibility for Run commands and clarify if they can be executed from Linux environments.
  • Provide parity in troubleshooting and operational examples for both Windows and Linux users.
GitHub Create Pull Request
Azure Resource Manager Create a troubleshooting template ...ger/troubleshooting/create-troubleshooting-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by mentioning Azure PowerShell (a Windows-centric tool) first when describing how to deploy the troubleshooting template, and by linking to PowerShell documentation before Azure CLI. There are no explicit Linux-specific examples or references to Linux shell usage, and no mention of platform differences or considerations for Linux users.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
  • Include explicit Linux shell usage examples (e.g., bash commands) for deploying ARM templates and Bicep files.
  • Clarify that both Azure CLI and PowerShell are available on Windows, macOS, and Linux, and provide guidance for installation and usage on Linux.
  • Avoid implying that PowerShell is the default or preferred method, and use neutral language when listing deployment options.
  • Add troubleshooting steps or notes relevant to Linux environments, such as file path conventions or shell differences.
GitHub Create Pull Request
Azure Resource Manager Deployment quota exceeded ...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples for managing deployment quotas. However, the PowerShell section is given equal prominence, despite PowerShell being primarily a Windows tool (though it is cross-platform now). The Bash example is explicitly mentioned as requiring a Bash environment, but there is no mention of Windows Command Prompt equivalents or clarification for Linux users. The documentation does not provide explicit Linux-specific instructions or highlight platform differences, which may cause confusion for Linux users. The CLI examples assume Bash, which is standard on Linux but not on Windows by default.
Recommendations
  • Explicitly state platform requirements for each example (e.g., Bash for Linux/macOS, PowerShell for Windows).
  • Provide Windows Command Prompt equivalents for Azure CLI commands, or clarify that Bash is required on Windows (e.g., via WSL or Git Bash).
  • Add notes or tabs for Linux-specific instructions, especially for scripting and environment setup.
  • Clarify that PowerShell is available cross-platform, but is most commonly used on Windows, and provide guidance for Linux users who may not have PowerShell installed.
  • Consider reordering examples or adding a 'Platform' note to ensure Linux users are not overlooked.
GitHub Create Pull Request
Azure Vmware Deploy Traffic Manager to balance Azure VMware Solution workloads ...ure-vmware/deploy-traffic-manager-balance-workloads.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft IIS Servers as backend pool members, with no mention of Linux-based alternatives (e.g., Apache, Nginx). All examples and screenshots focus on Windows-centric tools and environments (IIS, vSphere, NSX), and there are no instructions or examples for deploying or verifying Linux web servers. This may lead Linux users to feel unsupported or unclear about how to adapt the guidance for their environments.
Recommendations
  • Include examples and screenshots showing Linux-based web servers (such as Apache or Nginx) as backend pool members.
  • Explicitly mention that backend pool members can be running on Linux VMs, and provide configuration steps for popular Linux web servers.
  • Add verification steps for Linux VMs, such as using SSH or Linux command-line tools to confirm connectivity and configuration.
  • Clarify that the Traffic Manager and Application Gateway integration is platform-agnostic, and provide parity in instructions for both Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager Resource not found errors ...re-resource-manager/troubleshooting/error-not-found.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell and Azure CLI together, but listing PowerShell first and providing a direct link to the Set-AzContext PowerShell cmdlet before the Azure CLI equivalent. No explicit Linux shell examples (e.g., Bash) are provided, and no mention is made of Linux-specific considerations or tools. The portal instructions are platform-neutral, but command-line guidance assumes familiarity with Windows tools and patterns.
Recommendations
  • Alternate the order of PowerShell and Azure CLI references, or list Azure CLI first to balance platform representation.
  • Provide explicit Bash/Linux shell examples for Azure CLI commands, including syntax and environment notes.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Include troubleshooting steps or notes relevant to Linux users, such as verifying environment variables or shell context.
  • Where possible, add links to Linux-specific documentation or guides for managing Azure resources.
GitHub Create Pull Request
Azure Resource Manager Resource quota errors ...source-manager/troubleshooting/error-resource-quota.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides troubleshooting steps for resource quota errors in Azure, with command-line examples for both Azure CLI and PowerShell. However, the PowerShell example is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific patterns or tools. The portal instructions are platform-neutral, but the command-line guidance leans toward Windows-centric tooling.
Recommendations
  • Add explicit bash/Linux shell examples for quota checks using Azure CLI, demonstrating usage in a Linux environment.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell (Windows-centric), or explicitly state platform applicability for each example.
  • Mention that PowerShell Core is available on Linux/macOS, if relevant, but clarify typical usage patterns.
  • Include a note or section for Linux users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Azure Resource Manager Overview of deployment troubleshooting for Bicep files and ARM templates ...les/azure-resource-manager/troubleshooting/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. It references Azure PowerShell before Azure CLI when discussing error details, and provides PowerShell-specific command examples. There are no explicit Linux shell (bash) examples or references to Linux-specific troubleshooting tools or workflows. The guidance assumes Visual Studio Code as the editor, which is cross-platform, but does not mention alternative editors or command-line tools commonly used on Linux.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell examples, as CLI is platform-agnostic and widely used on Linux.
  • Include bash or shell script examples for common troubleshooting tasks, such as querying deployment operations or activity logs.
  • Mention Linux-native editors (e.g., Vim, Emacs) or command-line validation tools for Bicep/ARM templates, if available.
  • Clarify that Visual Studio Code and the listed extensions are available on Linux, and suggest installation instructions for Linux users.
  • Ensure that troubleshooting steps and tools are described in a way that is not platform-specific, or explicitly provide parity for Linux environments.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot Bicep file deployments ...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup tasks, but PowerShell is a Windows-centric tool and is presented alongside Azure CLI without explicit Linux shell examples (e.g., Bash). There are no Linux-specific instructions, nor are Linux tools or shell patterns mentioned. The prerequisites mention Azure PowerShell before Azure CLI, and there is no mention of Linux-specific editors or shell environments. The documentation assumes Visual Studio Code, which is cross-platform, but does not discuss any Linux-specific considerations or alternatives.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, including shell syntax for Linux/macOS users (e.g., use $HOME, clear line continuations, etc.).
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide any necessary environment setup instructions for those platforms.
  • Reorder prerequisites to mention Azure CLI before Azure PowerShell, as CLI is cross-platform and PowerShell is more Windows-centric.
  • Include notes or sections for Linux/macOS users, such as using terminal editors (vim, nano) or running commands in Bash.
  • Where PowerShell is mentioned, clarify its cross-platform availability or provide alternative instructions for native Linux shells.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot ARM template JSON deployments ...ubleshooting/quickstart-troubleshoot-arm-deployment.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI for every deployment operation, and references to PowerShell are present in the prerequisites. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. The documentation mentions PowerShell before Azure CLI in the prerequisites and includes PowerShell-specific commands throughout. There is no explicit mention of Linux-specific tools, shell environments, or troubleshooting patterns, and no examples using Bash or Linux-native editors.
Recommendations
  • Ensure Azure CLI examples are presented first, or alternate the order with PowerShell to avoid Windows-first bias.
  • Add explicit references to Linux environments (e.g., Bash, zsh) and clarify that Azure CLI commands work natively on Linux and macOS.
  • Include troubleshooting steps or examples using Linux-native editors (e.g., Vim, nano) or mention their usage for ARM template editing.
  • Clarify that Visual Studio Code is available on Linux and macOS, and suggest alternatives for those platforms.
  • Add notes or examples for using Azure CLI in Linux shell environments, including command syntax for Bash (e.g., environment variable usage, quoting differences).
  • Consider mentioning cross-platform installation instructions for Azure CLI and PowerShell, or link to Linux/macOS-specific guides.
GitHub Create Pull Request
Azure Signalr Move an Azure SignalR resource to another region ...les/azure-signalr/signalr-howto-move-across-regions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure portal and Azure PowerShell. All command-line examples use PowerShell, and Windows-specific tools (e.g., notepad) are referenced. There are no examples or guidance for Linux users (e.g., Bash, Azure CLI, Linux text editors), and PowerShell is presented as the only scripting option. This creates a bias towards Windows users and leaves Linux users without parity in instructions.
Recommendations
  • Add equivalent instructions using Azure CLI (az commands) for exporting, editing, and deploying Resource Manager templates.
  • Include examples of editing JSON files with cross-platform editors (e.g., vim, nano, code) instead of only referencing notepad.
  • Provide explicit Bash shell command examples for Linux/macOS users.
  • Mention that PowerShell Core is available cross-platform, but also offer Azure CLI alternatives for common operations.
  • Ensure that all steps (resource group creation, deployment, verification, deletion) have both PowerShell and Azure CLI examples side-by-side.
GitHub Create Pull Request
Azure Signalr Troubleshooting practice for Azure SignalR Service ...les/azure-signalr/signalr-howto-troubleshoot-method.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (Fiddler, web.config, Windows Phone 8) are mentioned before or more prominently than Linux equivalents. Logging and tracing instructions often reference Windows-centric configuration (web.config, Windows desktop apps) and platforms (Windows Phone 8) without equivalent Linux or cross-platform guidance. Linux tools (tcpdump) are mentioned, but typically after Windows tools and without detailed parity in examples.
Recommendations
  • Present Linux tools (e.g., tcpdump) alongside Windows tools (e.g., Fiddler), giving equal prominence and detail.
  • Provide explicit Linux configuration examples for logging and tracing (e.g., alternatives to web.config for .NET Core on Linux).
  • Include troubleshooting steps and examples for Linux and macOS environments, such as using systemd, journalctl, or other native logging mechanisms.
  • Avoid referencing Windows-only platforms (e.g., Windows Phone 8) without noting their obsolescence and providing alternatives for other platforms.
  • Ensure all code/configuration samples are cross-platform or provide separate samples for Windows and Linux.
  • Add a section or callouts for Linux-specific troubleshooting tips and common issues.
GitHub Create Pull Request
Azure Web Pubsub Tutorial - Publish and subscribe messages using WebSocket API and Azure Web PubSub service SDK ...articles/azure-web-pubsub/tutorial-pub-sub-messages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates mild Windows bias. Windows command shell (cmd.exe) is mentioned as an alternative to Bash early in the tutorial, and Windows-specific instructions (such as using 'set' instead of 'export' for environment variables) are provided before or alongside Linux equivalents. Some commands and directory creation steps use Windows syntax (e.g., 'cmd' blocks, single backslashes), and there is an explicit mention of Windows tools and patterns. However, most code and CLI examples are cross-platform, and Linux/Bash instructions are present throughout.
Recommendations
  • Present Linux/Bash instructions before Windows-specific alternatives, or side-by-side, to avoid implying Windows primacy.
  • Clearly mark platform-specific instructions and provide parity for Linux and macOS users (e.g., mention 'export' before 'set').
  • Avoid using Windows-only command syntax (e.g., 'cmd' blocks, backslashes) unless necessary; prefer POSIX-compliant examples.
  • Add explicit notes or tabs for Linux/macOS where Windows alternatives are mentioned.
  • Ensure all tooling and workflow steps are equally documented for Linux (e.g., virtual environment activation, environment variable setting, directory navigation).
GitHub Create Pull Request
Backup Back up Azure Kubernetes Service (AKS) using Azure CLI ...p/azure-kubernetes-service-cluster-backup-using-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias primarily through the use of Windows-specific syntax (PowerShell backticks) in command examples, mentions Azure PowerShell as an alternative before Linux equivalents, and includes Windows-centric tools and patterns (e.g., PowerShell variable assignment, backtick line continuation). There are no explicit Linux shell (bash) examples, and the only alternative to Azure CLI is Azure PowerShell, which is Windows-focused. The documentation does not provide parity for Linux users in terms of shell syntax or tool recommendations.
Recommendations
  • Replace PowerShell-specific command syntax (such as backticks for line continuation and $variable assignment) with bash-compatible syntax (e.g., backslash for line continuation, export for variable assignment) or provide both Windows and Linux examples side by side.
  • Explicitly mention bash or Linux shell usage in examples, especially for Azure CLI commands, as Azure CLI is cross-platform.
  • Where Azure PowerShell is referenced as an alternative, also mention bash scripting or Linux-native tools if available.
  • Add a section or note clarifying cross-platform compatibility and provide links to Linux-specific documentation or guides.
  • Ensure that all command examples are tested and presented in both Windows (PowerShell) and Linux (bash) formats to improve accessibility for Linux users.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Data Lake Storage using ARM or Bicep template ...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides only PowerShell deployment examples for both ARM and Bicep templates, with no mention of Azure CLI, Bash, or Linux-native deployment methods. This approach assumes users are familiar with PowerShell, which is more common on Windows, and does not offer parity for Linux or cross-platform users. The deployment instructions do not reference Azure CLI, Bash, or provide alternative commands for non-Windows environments.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell for both ARM and Bicep templates.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide Bash/CLI instructions.
  • Include notes or links for Linux/macOS users on how to run deployments using Azure CLI.
  • Ensure that PowerShell is not presented as the only or primary method; alternate methods should be given equal prominence.
  • Where possible, provide cross-platform guidance and clarify any differences in command syntax or prerequisites.
GitHub Create Pull Request
Backup Recover data from an Azure Backup Server by using Azure Backup ...n/articles/backup/backup-azure-alternate-dpm-server.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Azure Backup Server and System Center Data Protection Manager (DPM), which are Windows-only tools. All instructions, screenshots, and terminology are specific to the Windows ecosystem, with no mention of Linux equivalents, cross-platform tools, or CLI alternatives. There are no examples or guidance for Linux-based recovery scenarios, and Windows patterns (e.g., right-click, management console) are assumed throughout.
Recommendations
  • Add explicit notes clarifying platform support and limitations, especially that Azure Backup Server and DPM are Windows-only.
  • Provide guidance or links for Linux-based backup and recovery scenarios using Azure Backup (e.g., MARS agent, Azure CLI, or third-party tools).
  • Include parity examples for Linux environments, such as command-line recovery steps or references to supported Linux backup agents.
  • Reorganize content to mention platform support up front, and offer alternative workflows for non-Windows users.
  • Where possible, use neutral terminology and avoid assuming a GUI/Windows workflow as the default.
GitHub Create Pull Request
Azure Signalr Troubleshooting guide for Azure SignalR Service ...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-specific tools (Fiddler, Performance Monitor), using Windows-centric terminology (e.g., HTTP.SYS), and providing troubleshooting steps and code samples that assume a Windows environment. There is a lack of Linux-specific guidance, examples, or parity in troubleshooting instructions, especially for diagnostics, logging, and network inspection. Linux alternatives are not mentioned or are omitted entirely.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside Windows instructions, especially for diagnostics and network inspection.
  • Mention and demonstrate Linux tools such as tcpdump, Wireshark, strace, and journalctl for viewing outgoing requests, logs, and performance metrics.
  • Include guidance for configuring TLS and .NET on Linux (e.g., using OpenSSL, configuring Kestrel, setting environment variables).
  • Add instructions for collecting and analyzing thread pool starvation and memory dumps on Linux (e.g., using dotnet-dump, perf, or gdb).
  • Ensure all code samples and configuration steps are cross-platform or clearly indicate platform-specific differences.
  • Reference Linux container scenarios (e.g., Docker, Kubernetes) with relevant links and examples.
GitHub Create Pull Request
Azure Signalr Use Azure SignalR Service .../blob/main/articles/azure-signalr/signalr-howto-use.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias in several areas: installation instructions for the legacy ASP.NET SignalR SDK use PowerShell/Package Manager Console (Windows-only), configuration references web.config (Windows/IIS-centric), and there are no Linux-specific equivalents or examples (e.g., Bash, Linux environment variable setup, or cross-platform configuration guidance). Windows tools and patterns are mentioned exclusively or before any Linux alternatives, and Linux users are left to infer how to adapt instructions.
Recommendations
  • Provide Linux/macOS equivalents for SDK installation (e.g., dotnet CLI, NuGet CLI, or Bash commands).
  • Include instructions for setting environment variables on Linux (e.g., using export in Bash, or systemd service files).
  • Document configuration alternatives for non-Windows environments (e.g., appsettings.json for .NET Core, environment variables, or other cross-platform config files).
  • Avoid referencing Windows-specific tools (like Package Manager Console and web.config) without mentioning cross-platform alternatives.
  • Add explicit notes or sections for Linux/macOS users to ensure parity and clarity.
GitHub Create Pull Request
Backup Configure Vaulted Backup for Azure Data Lake Storage using Azure portal, PowerShell, or Azure CLI ...les/backup/azure-data-lake-storage-configure-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured as a primary automation method, with detailed step-by-step instructions and example cmdlets, which are inherently Windows-centric. The prerequisites for PowerShell specifically mention installation of Azure PowerShell, a tool most commonly used on Windows. The structure of the page and the zone pivots present the Azure portal (GUI, often accessed from Windows) and PowerShell before the Azure CLI, which is more cross-platform and Linux-friendly. There is no mention of Linux-specific shell usage, nor are Bash or Linux-native scripting examples provided. The CLI section does not reference Linux environments or shell integration, and the overall documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including how to run them in typical Linux environments.
  • Include notes or sections on installing and using Azure CLI and PowerShell on Linux and macOS, not just Windows.
  • Present CLI examples before PowerShell in the documentation, or at least give them equal prominence.
  • Reference Linux-native tools or scripting patterns where appropriate, such as using environment variables, jq for JSON parsing, or shell scripting for automation.
  • Clarify that Azure CLI is cross-platform and provide links to installation instructions for Linux and macOS.
  • Avoid assuming the use of Windows-only tools; mention alternatives for Linux users when discussing prerequisites and setup.
GitHub Create Pull Request
Backup Offline seeding workflow for MARS using customer-owned disks with Azure Import/Export - Azure Backup ...n/articles/backup/backup-azure-backup-import-export.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All workflow steps, prerequisites, and tooling (MARS agent, AzureOfflineBackupDiskPrep utility, Azure PowerShell, Recovery Services Agent) are exclusively described for Windows environments. There are no Linux equivalents or examples, and requirements such as Internet Explorer/Edge, BitLocker, and Windows-specific agent installation further reinforce the Windows-centric approach. The documentation does not mention or support Linux systems for offline seeding with customer-owned disks.
Recommendations
  • Explicitly state Windows-only support at the beginning of the article if Linux is not supported, or clarify platform limitations.
  • If Linux support is possible, provide equivalent instructions, tooling, and examples for Linux environments (e.g., using az CLI, Linux-compatible disk preparation tools, and browser requirements).
  • Reference or link to any Linux-compatible workflows or alternatives for offline seeding, if available.
  • Where possible, use cross-platform tools (such as Azure CLI) and document their usage alongside PowerShell.
  • Avoid requiring Windows-only features (e.g., BitLocker, Internet Explorer) unless strictly necessary, and suggest Linux alternatives (e.g., LUKS for disk encryption).
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup support matrix ...azure-kubernetes-service-cluster-backup-support-matrix.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Kubernetes Service (AKS) backup support matrix exhibits mild Windows bias. It references Azure PowerShell as a primary tool for backup and restore operations, listing it alongside Azure CLI, ARM, Bicep, and Terraform in the 'Next steps' section. However, there is no mention of Linux-specific command-line tools or shell examples (e.g., Bash), nor are Linux-native patterns (such as shell scripting or Linux package management) discussed. The documentation does not provide explicit Linux command examples, and PowerShell is listed before ARM/Bicep/Terraform, which may suggest a Windows-first approach. Additionally, while the documentation states that the backup extension can only be installed on Ubuntu or Azure Linux node pools, it does not provide guidance or examples for Linux users, nor does it mention Linux-specific troubleshooting or usage patterns.
Recommendations
  • Add explicit Bash or Linux shell command examples for backup and restore operations, especially in sections referencing Azure CLI.
  • Include Linux-native troubleshooting steps and usage patterns, such as using systemd, journalctl, or Linux file permissions.
  • Reorder the 'Next steps' section to list Azure CLI and Linux-native tools before PowerShell, reflecting the AKS platform's Linux-centric nature.
  • Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI and Bash are recommended for Linux environments.
  • Provide guidance on installing and using the Azure CLI on Linux, including package manager commands (apt, yum, etc.).
  • Add links or references to Linux documentation for AKS node pool management and backup extension installation.
GitHub Create Pull Request
Backup About the MARS Agent ...s/blob/main/articles/backup/backup-azure-about-mars.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for the MARS Agent is heavily focused on Windows environments. All backup and recovery scenarios explicitly mention Windows files, folders, volumes, and system state. The agent's reliance on Windows-specific technologies such as VSS (Volume Shadow Copy Service) and USN change journal is highlighted, with no mention of Linux support, examples, or equivalent tooling. There are no Linux or cross-platform instructions, examples, or references, and the documentation implicitly assumes the reader is operating in a Windows context.
Recommendations
  • Explicitly state platform support (e.g., clarify if MARS Agent is Windows-only or provide Linux support status).
  • If Linux is supported, add equivalent Linux examples and instructions for installation, backup, and recovery.
  • Mention Linux backup tools or patterns where appropriate, or provide links to Azure Backup solutions for Linux.
  • If MARS Agent is not supported on Linux, suggest alternative Azure Backup solutions for Linux workloads.
  • Avoid using Windows-specific terminology (e.g., VSS, USN) without noting platform limitations or alternatives.
GitHub Create Pull Request
Backup Back up SQL Server to Azure as a DPM workload ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, specifically Data Protection Manager (DPM), which is a Windows-only tool. All examples, screenshots, and instructions assume the use of Windows Server, DPM, and related Windows concepts (such as NTAuthority\System, Logical Disk Manager, and protection group workflows). There are no references to Linux-based SQL Server deployments, nor are there examples or guidance for backing up SQL Server on Linux. The only automation reference is to PowerShell, further reinforcing Windows bias.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server on Linux, including supported scenarios and limitations.
  • Reference and provide parity for Linux-native backup tools and workflows (e.g., Azure Backup agent for Linux, CLI commands, or REST API usage).
  • Include screenshots and walkthroughs for Linux environments where SQL Server is supported.
  • Mention differences in prerequisites, permissions, and backup/restore processes for Linux-based SQL Server deployments.
  • Provide automation examples using Bash, Azure CLI, or other cross-platform tools, not just PowerShell.
  • Clarify in the introduction and prerequisites which operating systems are supported and whether DPM is required or if alternatives exist for Linux.
GitHub Create Pull Request
Azure Signalr Quickstart: Create an Azure SignalR Service - ARM template ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. PowerShell is presented as a primary deployment option alongside Portal and CLI, and PowerShell examples are given in full detail. In the CLI prerequisites, Bash is mentioned, but the example specifically suggests Git Bash (a Windows-centric Bash implementation) before any native Linux shell, and does not mention Linux or macOS shells explicitly. The documentation does not provide explicit Linux-specific instructions or acknowledge Linux environments directly, and the ordering of PowerShell before CLI in all sections subtly prioritizes Windows tooling.
Recommendations
  • Explicitly mention Linux and macOS compatibility in CLI sections, and recommend native Bash shells for those platforms.
  • Provide instructions or notes for running Azure CLI commands on Linux and macOS, including installation links for those platforms.
  • Avoid suggesting Git Bash as the default Bash shell for CLI usage; instead, mention it as an option for Windows users, and recommend native Bash for Linux/macOS.
  • Consider alternating the order of PowerShell and CLI examples, or grouping them under 'Command-line' to avoid Windows-first presentation.
  • Add a short section or note confirming that all CLI commands work natively on Linux and macOS, and provide troubleshooting tips for those platforms if needed.
GitHub Create Pull Request
Azure Signalr Develop with ASP.NET - Azure SignalR Service ...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows tools (Visual Studio, NuGet Package Manager, Package Manager Console), providing instructions tailored for Windows environments, and omitting Linux equivalents or cross-platform alternatives. There are no examples or guidance for developing or running the sample on Linux (e.g., using VS Code, CLI tools, or Mono), and PowerShell is used for package installation without mention of dotnet CLI or NuGet CLI alternatives.
Recommendations
  • Add instructions for setting up and running the sample on Linux, including using VS Code or JetBrains Rider.
  • Include package installation steps using dotnet CLI (e.g., 'dotnet add package') and NuGet CLI, not just PowerShell/Package Manager Console.
  • Mention cross-platform prerequisites, such as Mono or .NET Core SDK, where applicable.
  • Clarify that the sample can be run on Linux and macOS, and provide any necessary configuration steps.
  • Provide troubleshooting steps or notes specific to non-Windows environments.
  • Avoid assuming Visual Studio as the only IDE; suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Vmware Architecture - API Management ...n/articles/azure-vmware/architecture-api-management.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and the Azure portal as primary management tools, without mentioning Linux command-line alternatives (such as Azure CLI or Bash). Windows-centric tools and patterns are presented first and exclusively, with no examples or guidance for Linux users. There are no references to Linux-specific workflows or tools, and the documentation does not provide parity for cross-platform management.
Recommendations
  • Include Azure CLI (cross-platform) examples alongside or before PowerShell examples.
  • Explicitly mention that management tasks can be performed from Linux/macOS environments using Azure CLI or REST APIs.
  • Provide sample commands for both PowerShell and Bash/CLI where relevant.
  • Reference automation tools and patterns that are platform-agnostic (e.g., Terraform, Ansible) if applicable.
  • Clarify that the Azure portal and developer portal are accessible from any OS/browser.
GitHub Create Pull Request
Backup Monitor Azure Backup protected workloads ...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and linking to 'manage-windows-server' resources. There are no explicit examples or mentions of Linux backup agents or Linux-specific monitoring workflows. Windows tools and patterns are mentioned exclusively, with no Linux parity in examples or guidance.
Recommendations
  • Include examples and guidance for monitoring Azure Backup workloads protected by Linux servers and agents.
  • Reference Linux backup agents (such as Azure Backup for Linux VM or Azure Backup Agent for Linux) alongside Windows tools.
  • Add links to documentation pages specifically for managing and monitoring Linux backup items.
  • Ensure that instructions and screenshots cover both Windows and Linux scenarios where applicable.
  • Mention any differences in monitoring or notification workflows for Linux workloads.
GitHub Create Pull Request
Backup Restore Key Vault key & secret for encrypted Azure VM ...ain/articles/backup/backup-azure-restore-key-secret.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-style file paths (e.g., C:\). There are no CLI/bash examples, and Linux scenarios are only briefly mentioned as a variant of the Windows PowerShell workflow, not as a first-class workflow. The documentation assumes the use of Windows tools and patterns throughout, making it less accessible for Linux users or those preferring Azure CLI or bash scripting.
Recommendations
  • Provide equivalent Azure CLI/bash examples for all steps, including disk restore, key/secret extraction, and Key Vault operations.
  • Use platform-neutral file paths and examples (e.g., /home/user/vmencryption_config.json for Linux).
  • Explicitly document Linux workflows, including prerequisites and environment setup, not just as a variant of Windows/PowerShell.
  • Mention and link to cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and clarify which steps are platform-specific.
  • Reorder examples so that Linux and cross-platform approaches are presented alongside or before Windows-specific instructions.
GitHub Create Pull Request
Backup Manage and monitor MARS Agent backups .../blob/main/articles/backup/backup-azure-manage-mars.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows environments. All instructions, screenshots, and tool references are specific to the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only backup solution. There are no Linux equivalents, examples, or even mentions of Linux support or alternative tooling. The documentation assumes the use of Windows consoles, directories (e.g., %ProgramFiles%), and Windows-specific management patterns throughout.
Recommendations
  • Clearly state at the beginning that the MARS Agent is only supported on Windows, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI-based solutions).
  • Where possible, include references or links to documentation for managing and monitoring backups on Linux systems using Azure services.
  • If the product is Windows-only, make this explicit in the prerequisites and scope, and suggest alternative Azure-native backup approaches for Linux workloads.
  • Consider providing a comparison table or section outlining backup options for both Windows and Linux, guiding users to the appropriate documentation for their OS.
GitHub Create Pull Request
Backup Back up SQL Server by using Azure Backup Server ...ocs/blob/main/articles/backup/backup-azure-sql-mabs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented towards Windows environments, specifically referencing Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), which are Windows-only tools. All examples, screenshots, and instructions assume the use of Windows Server and SQL Server on Windows. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for backing up SQL Server running on Linux. Windows-specific concepts (NTAuthority\System, Windows Azure Blob storage, Windows failover clustering) are referenced without Linux equivalents.
Recommendations
  • Explicitly state platform limitations at the beginning, clarifying that MABS/DPM are Windows-only tools.
  • Provide alternative backup solutions or references for SQL Server running on Linux, such as using Azure Backup with Linux agents, or native SQL Server backup/restore commands.
  • Include examples and guidance for backing up SQL Server on Linux, if supported, or link to relevant documentation for Linux environments.
  • Mention Linux-specific considerations (e.g., service accounts, file permissions, storage paths) where appropriate.
  • If Azure Backup supports Linux SQL Server, add parity in screenshots, CLI commands, and workflows.
GitHub Create Pull Request
Backup Back up Exchange server with Azure Backup Server ...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively describes backup and recovery procedures for Microsoft Exchange Server using Microsoft Azure Backup Server (MABS), which is a Windows-only product. All examples, instructions, and referenced tools (such as Eseutil.exe, MABS Administrator Console) are Windows-centric, with no mention of Linux equivalents, cross-platform alternatives, or guidance for Exchange deployments on non-Windows platforms. The documentation assumes the use of Windows GUIs and tools, and does not provide parity for Linux users.
Recommendations
  • Clarify early in the documentation that MABS is a Windows-only solution and suggest cross-platform alternatives (such as Azure Backup integration with Linux servers or third-party tools) for Linux environments.
  • Provide links or references to backup solutions for Exchange-like workloads on Linux (e.g., for mail servers such as Postfix, Dovecot, or Zimbra).
  • If possible, include a section on backing up Linux-based mail servers to Azure, with example commands and procedures.
  • Explicitly state platform limitations and guide users to appropriate documentation for non-Windows scenarios.
GitHub Create Pull Request
Azure Vmware Azure VMware Solution known issues ...les/azure-vmware/azure-vmware-solution-known-issues.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for Azure VMware Solution known issues demonstrates a Windows bias in several ways. Remediation steps frequently reference PowerShell cmdlets (e.g., Set-vSANCompressDedupe, Set-Tools-Repo) without providing Linux or cross-platform alternatives. There are no Bash, shell, or Linux CLI examples, and the use of 'Run command' appears to assume a Windows-centric management pattern. Additionally, the only explicit mention of OS-specific tooling is for 'VMware Tools for Windows', with no mention of Linux equivalents or guidance for Linux VM users. Overall, the documentation assumes Windows as the default platform for management and remediation tasks.
Recommendations
  • Provide Linux/Bash/CLI equivalents for all PowerShell cmdlet examples, or clarify if the commands are available via REST API or other cross-platform interfaces.
  • Include explicit instructions or references for managing VMware Tools on Linux VMs, especially when security advisories affect both Windows and Linux guests.
  • When referencing 'Run command', clarify platform requirements and provide parity for Linux administrators (e.g., via SSH, Ansible, or other automation tools).
  • Avoid assuming Windows as the default platform; mention both Windows and Linux where applicable, especially in remediation steps and tool usage.
  • Add notes or links to VMware documentation for Linux-specific management tasks, such as updating VMware Tools or configuring vSAN from Linux environments.
GitHub Create Pull Request
Backup Azure Backup support matrix ...ocs/blob/main/articles/backup/backup-support-matrix.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias in several areas: Windows backup scenarios and tools (MARS agent, DPM, MABS) are described first and in greater detail, with Linux support often mentioned as 'not supported' or as a secondary note. Many backup features (such as direct on-premises backup with MARS agent, app-aware backup, deduplication, and compression) are available only for Windows, with Linux support either missing or limited to VM-level backups via extensions or third-party virtualization platforms. Windows-specific tools and patterns (MARS agent, DPM, MABS) are referenced throughout, while Linux equivalents are not provided or are explicitly unsupported.
Recommendations
  • Provide Linux-first or Linux-parity examples and scenarios alongside Windows ones, especially in tables and feature lists.
  • Explicitly state Linux limitations and offer alternative solutions or workarounds where possible.
  • Include Linux-specific backup tools or recommend open-source alternatives for on-premises Linux backup.
  • Clarify which features are Windows-only and which are available for Linux, and avoid presenting Windows features as the default.
  • Add more detail and guidance for configuring app-consistent backups on Linux, including sample scripts and best practices.
  • Where a feature is not supported for Linux, link to roadmap or feedback channels for future support.
GitHub Create Pull Request
Backup Enable Backup During Azure VM Creation by Using Azure Backup ...blob/main/articles/backup/backup-during-vm-creation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows is mentioned before Linux in instructions, and the only Resource Manager template example provided is for deploying a Windows VM with backup enabled. There are no explicit Linux-focused examples or templates, and PowerShell is referenced as the automation method for configuring backup resource groups, with no mention of Linux CLI alternatives.
Recommendations
  • Present Windows and Linux instructions/examples in parallel, or alternate which is mentioned first.
  • Include Resource Manager template examples for Linux VMs with backup enabled.
  • Provide equivalent automation instructions using Azure CLI or Bash scripts, not just PowerShell.
  • Explicitly mention that all backup features and steps apply equally to Linux VMs where applicable.
  • Add screenshots and walkthroughs for Linux VM creation and backup configuration.
GitHub Create Pull Request
Backup Back up Azure Managed Disks ...docs/blob/main/articles/backup/backup-managed-disks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page primarily focuses on using the Azure portal for backup operations, which is cross-platform. However, when mentioning automation or scripting, PowerShell is listed before Azure CLI, and there are no explicit Linux-specific examples or references to Linux tools or workflows. The page does not provide parity in examples or guidance for Linux users, especially in scripting and automation contexts.
Recommendations
  • When referencing automation, mention Azure CLI before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Provide explicit Linux/Unix shell examples (e.g., Bash scripts using Azure CLI) for backup and restore operations.
  • Clarify that all portal operations are OS-agnostic, but scripting examples should be balanced between PowerShell and CLI.
  • Add a section or links for Linux administrators, highlighting best practices or common patterns for managing Azure Disk backups from Linux environments.
  • Ensure that any downloadable script templates or role assignment instructions include both PowerShell and Bash/CLI versions.
GitHub Create Pull Request
Backup Back up SQL Server on Azure Stack using Azure Backup ...ob/main/articles/backup/backup-mabs-sql-azure-stack.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All workflow steps, screenshots, and terminology reference Windows environments (e.g., NTAuthority\System, SQL Server on Windows, Windows-style wizards and blades). There are no examples, instructions, or mentions of Linux-based SQL Server deployments or backup tools. The documentation assumes the use of Windows tools and patterns throughout, with no Linux parity.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning, including that MABS is Windows-only.
  • Provide guidance or links for backing up SQL Server on Azure Stack when running on Linux, if supported, or clarify that Linux is not supported.
  • Include alternative backup workflows or tools for Linux-based SQL Server deployments, such as Azure Backup integration with Linux or third-party solutions.
  • Add examples and screenshots for Linux environments if/when support is available.
  • Mention Linux equivalents for system accounts, permissions, and backup/restore procedures where applicable.
GitHub Create Pull Request
Backup Release notes for Microsoft Azure Backup Server v3 ...b/main/articles/backup/backup-mabs-release-notes-v3.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation for Microsoft Azure Backup Server v3 is heavily focused on Windows environments. All examples, instructions, and tools referenced (such as SQL Server Management Studio, SQL Server Reporting Services, and file paths) are Windows-specific. There are no mentions of Linux equivalents, nor any guidance for Linux-based backup scenarios. The documentation assumes the use of Windows Server and related Microsoft tools, with no consideration for cross-platform or Linux users.
Recommendations
  • Include explicit statements about platform support (e.g., clarify if MABS is Windows-only or provide Linux guidance if supported).
  • If Linux is supported, add equivalent instructions for Linux environments, such as using sqlcmd or Azure CLI for database operations.
  • Reference Linux file paths and tools where applicable, or note their absence if not supported.
  • Provide parity in troubleshooting steps and examples for both Windows and Linux users.
  • Mention any limitations or requirements for non-Windows platforms early in the documentation.
GitHub Create Pull Request
Azure Vmware Back up Azure VMware Solution VMs with Azure Backup Server ...mware/backup-azure-vmware-solution-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments. All instructions and screenshots assume the use of Windows OS and Windows-specific tools (e.g., Registry Editor, Certificate Import Wizard, Azure Backup Server console). There are no examples or guidance for performing equivalent tasks on Linux systems, nor is there mention of Linux-compatible tooling or workflows. The registry modification and certificate import steps are Windows-only, and individual file recovery is only supported for Windows VMs.
Recommendations
  • Provide equivalent instructions for Linux environments, such as how to import CA certificates using Linux tools (e.g., update-ca-certificates, openssl, etc.).
  • Clarify whether Azure Backup Server can be run or managed from Linux hosts, or explicitly state Windows-only support.
  • Offer guidance for Linux VM backup and recovery, including individual file recovery options for Linux VMs.
  • Include Linux command-line examples and screenshots where applicable.
  • Note any feature limitations for non-Windows VMs and suggest alternative approaches for Linux workloads.
GitHub Create Pull Request
Azure Vmware Use Azure VMware Solution with Azure Elastic SAN ...n/articles/azure-vmware/configure-azure-elastic-san.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell before Azure CLI when listing tooling options, and by omitting any Linux-specific examples or guidance. All procedural steps are described in terms of Azure portal UI or PowerShell commands, with no mention of Linux shell commands or Linux-centric workflows. There is no discussion of Linux-based administration, nor are any Linux tools or patterns referenced.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting tooling options, or present both equally.
  • Provide explicit Linux shell/CLI examples for key operations, such as creating Elastic SAN resources and managing datastores.
  • Include guidance for Linux administrators, such as how to use Bash scripts or Linux-based automation tools for these tasks.
  • Mention Linux compatibility and any platform-specific considerations for Elastic SAN and Azure VMware Solution.
  • Ensure screenshots and UI references are supplemented with CLI instructions that work on Linux.
GitHub Create Pull Request
Backup Offline Backup with Azure Data Box for DPM and MABS ...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_only ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased toward Windows environments. All instructions, examples, and supported platforms are Windows Server only (2016/2019), with no mention of Linux or cross-platform alternatives. The setup steps rely on Windows-specific tools (PSExec, registry editing, Windows command prompt, PowerShell modules), and troubleshooting is entirely Windows-centric. There are no Linux equivalents or examples, nor any guidance for non-Windows users.
Recommendations
  • Explicitly state Windows-only support in the introduction and platform requirements.
  • If possible, add support for Linux-based backup servers and document the equivalent steps for Linux environments (e.g., mounting NFS shares, certificate management, Azure CLI usage).
  • Where PowerShell is used, provide Azure CLI or REST API alternatives for cross-platform compatibility.
  • Replace or supplement Windows-specific tools (e.g., PSExec, regedit) with platform-agnostic or Linux-native alternatives.
  • Include troubleshooting steps and examples for Linux environments if/when supported.
  • If Linux is not supported, clarify this limitation early in the documentation and provide links to alternative solutions for Linux users.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server using a Terraform template ...p/quick-backup-postgresql-flexible-server-terraform.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-centric tools (PowerShell) and patterns before Linux equivalents. In the prerequisites, PowerShell is listed as a client for Azure Backup before CLI and other cross-platform tools. There is a specific note about PowerShell authentication, and the documentation refers to the Azure PowerShell module, which is primarily used on Windows. No Linux-specific instructions, examples, or troubleshooting are provided, and the CLI is mentioned only in passing.
Recommendations
  • List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) in all tool lists.
  • Provide explicit Linux usage instructions, including installation and authentication steps for Azure CLI and Terraform on Linux.
  • Include troubleshooting steps and examples for Linux environments.
  • Avoid mentioning PowerShell unless necessary, and always provide equivalent CLI/bash examples.
  • Clarify that all steps are cross-platform, and highlight any OS-specific differences where relevant.
GitHub Create Pull Request
Backup Create and use private endpoints for Azure Backup ...re-docs/blob/main/articles/backup/private-endpoints.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. Most command-line examples and scripts are provided only for PowerShell, with no Bash, CLI, or Linux shell equivalents. Windows-centric tools and patterns (PowerShell, ARMClient with Windows file paths, MARS agent, DPM server) are referenced exclusively or before any cross-platform alternatives. There are no explicit instructions or examples for Linux users, and the workflow assumes familiarity with Windows environments and tooling.
Recommendations
  • Provide Azure CLI (az) and Bash examples alongside PowerShell for all command-line operations, including role assignment, private endpoint creation, and DNS management.
  • Reference cross-platform tools (e.g., Azure CLI, REST API via curl) before or alongside Windows-specific tools like PowerShell and ARMClient.
  • Include Linux-specific instructions for tasks such as DNS configuration, file uploads, and script execution (e.g., using scp, curl, or az commands).
  • Clarify that the process is applicable to both Windows and Linux VMs, and provide troubleshooting steps for Linux environments.
  • Offer guidance for using Linux-based backup agents or alternatives to MARS/DPM where possible.
  • Ensure all file path examples use cross-platform formats or provide both Windows and Linux path formats.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure CLI ...cles/backup/quick-backup-azure-files-vault-tier-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates subtle Windows bias. While the main focus is on Azure CLI (which is cross-platform), references to Azure PowerShell and the Azure portal are given as alternatives, with PowerShell mentioned before the portal in several places. The example CLI output includes a Windows-style path (C:\Users\testuser\Downloads\...), which may confuse Linux users. Installation instructions mention Windows and macOS specifically, but do not explicitly mention Linux, and Docker is suggested for Windows/macOS users, leaving Linux users without tailored guidance.
Recommendations
  • Provide explicit Linux installation instructions for Azure CLI, alongside Windows and macOS.
  • Ensure example CLI output uses neutral or Linux-style paths (e.g., ~/Downloads/...), or clarify that the CLI works identically on Linux.
  • When listing alternatives (PowerShell, portal), alternate the order or mention Linux-native tools if available.
  • Add notes or examples for common Linux shell environments (e.g., bash, zsh), and clarify that all CLI commands work on Linux.
  • Avoid Windows-centric terminology (such as 'Terminal' with capital T) unless also referencing Linux equivalents (e.g., 'terminal, shell, or command prompt').
GitHub Create Pull Request
Backup Quickstart - Resource Manager template VM Backup .../blob/main/articles/backup/quick-backup-vm-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a strong Windows bias. It exclusively provides Azure PowerShell examples for deploying and managing VM backups via ARM templates, with no equivalent Azure CLI or Bash examples. The template referenced is for a Windows VM, and Windows-centric tools and workflows (PowerShell, Windows VM creation) are mentioned first and used throughout. Linux-specific instructions, examples, or parity are missing.
Recommendations
  • Add Azure CLI and Bash examples for deploying ARM templates and managing backups, alongside PowerShell.
  • Include a template example for Linux VMs, or clarify how to adapt the template for Linux workloads.
  • Mention Linux-compatible tools and workflows (e.g., Azure CLI in Bash, Cloud Shell Bash) at the same prominence as PowerShell.
  • Ensure cleanup instructions include Azure CLI/Bash equivalents, not just PowerShell cmdlets.
  • Balance references to Windows and Linux VMs in both the template and explanatory text.
GitHub Create Pull Request
Backup Offline backup for Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS) - previous versions ...cles/backup/offline-backup-server-previous-versions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily oriented towards Windows environments, with all examples, screenshots, and tool references assuming Windows Server, Windows client, or Windows-specific utilities (e.g., .exe files, registry edits, Certlm.msc, regedit, PowerShell commands). There are no Linux equivalents, nor any mention of how to perform these steps on Linux systems. The workflow, prerequisites, and troubleshooting steps are all described from a Windows perspective, and Linux support is not addressed.
Recommendations
  • Explicitly state platform limitations (e.g., if offline backup is not supported on Linux, clarify this early in the documentation).
  • If Linux support exists, provide equivalent instructions, tools, and examples for Linux environments (e.g., shell commands, Linux file paths, certificate management via OpenSSL, etc.).
  • Include screenshots and workflow steps for Linux-based systems, if applicable.
  • Mention any cross-platform alternatives or limitations, and provide guidance for users on non-Windows platforms.
  • If only Windows is supported, add a clear note at the beginning to prevent confusion for Linux users.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure CLI .../main/articles/backup/quick-blob-vaulted-backup-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Azure PowerShell and linking to PowerShell-based instructions before or alongside CLI examples. The 'create a Backup vault' link points to a PowerShell guide, and the 'Next step' section lists Azure PowerShell before Azure CLI, suggesting a Windows-first approach. There is no explicit mention of Linux-specific considerations or examples, and no references to Linux-native tools or shell environments.
Recommendations
  • Ensure that all linked instructions (such as creating a Backup vault) have Azure CLI equivalents and link to those as the primary or at least equally prominent option.
  • List Azure CLI instructions before PowerShell in all sections to avoid Windows-first ordering.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide examples or notes for Linux users where relevant.
  • Review included files to confirm they do not contain Windows-specific commands or assumptions (e.g., PowerShell syntax, Windows paths).
  • Add troubleshooting or environment setup notes for Linux users if there are platform-specific considerations.
GitHub Create Pull Request
Backup Accidental Delete Protection for Azure Files ...b/main/articles/backup/soft-delete-azure-file-share.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing a 'Undelete File Share Script' that is specifically a PowerShell script, without mentioning or providing equivalent Linux or cross-platform CLI examples. The instructions and links focus on the Azure Portal and PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling for undelete or management operations. This may disadvantage Linux users or those preferring non-Windows environments.
Recommendations
  • Provide equivalent examples and scripts using Azure CLI and Bash for undelete and management operations.
  • Explicitly mention cross-platform options where PowerShell scripts are referenced, and link to Linux-compatible instructions.
  • Add a section or FAQ entry addressing how Linux users can perform these operations, including sample commands.
  • Ensure that future documentation includes parity between Windows/PowerShell and Linux/Azure CLI approaches for all major tasks.
GitHub Create Pull Request
Backup Transport Layer Security in Azure Backup .../blob/main/articles/backup/transport-layer-security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows environments, providing only Windows-specific instructions (such as registry edits and KB articles) for enabling TLS 1.2 in Azure Backup. There are no examples or guidance for Linux systems, nor any mention of Linux-specific tools or configuration patterns. All troubleshooting and configuration steps assume a Windows platform.
Recommendations
  • Add a dedicated section for enabling and verifying TLS 1.2 on Linux systems, including common distributions (e.g., Ubuntu, CentOS).
  • Provide examples for configuring TLS on Linux, such as updating OpenSSL or modifying system-wide crypto policies.
  • Include troubleshooting steps for Linux backup agents or services, and reference relevant Linux documentation.
  • Ensure parity in FAQs and related content by mentioning both Windows and Linux scenarios.
  • List Linux equivalents for any Windows tools or registry changes (e.g., config files, command-line utilities).
GitHub Create Pull Request
Backup Selective Disk Backup and Restore for Azure Virtual Machines .../main/articles/backup/selective-disk-backup-restore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring selective disk backup and restore, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and there are no explicit Linux shell (bash) or Linux-native scripting examples. Windows-specific terminology and tools (such as drive C, BitLocker, and PowerShell cmdlets) are mentioned directly, while Linux equivalents are referenced but not illustrated with concrete examples. Linux-specific requirements (like lsblk and lsscsi) are mentioned, but no step-by-step Linux command-line walkthrough is provided. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users in terms of example scripts or troubleshooting steps.
Recommendations
  • Add explicit bash/Linux shell examples for configuring selective disk backup and restore, including sample scripts using az CLI in bash.
  • Provide troubleshooting steps and examples for common Linux issues (e.g., verifying lsblk/lsscsi availability, handling permissions, etc.).
  • Include Linux-native terminology and patterns (e.g., referencing /dev/sdX, using sudo, etc.) alongside Windows terms.
  • Balance the use of PowerShell and CLI by prioritizing CLI examples (which are cross-platform) and relegating PowerShell to a secondary section.
  • Add a section with Linux-specific best practices for disk backup and restore, including handling logical volumes and encrypted disks.
  • Ensure that screenshots and UI references are not Windows-centric, and clarify any OS-specific differences in the Azure portal experience.
GitHub Create Pull Request
Backup Upgrade the Microsoft Azure Recovery Services (MARS) agent for Azure Backup ...e-docs/blob/main/articles/backup/upgrade-mars-agent.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation exclusively describes upgrading the MARS agent in the context of Windows environments, referencing Remote Desktop, Windows login URLs, and Windows-specific tools (DPM Console, agent upgrade wizard). There are no Linux examples, instructions, or mentions of Linux compatibility, and the 'Next steps' section further reinforces a Windows-only focus.
Recommendations
  • Clarify whether the MARS agent is supported on Linux. If not, explicitly state this early in the documentation.
  • If Linux support exists, add parallel instructions for Linux environments, including command-line steps (e.g., using SSH, Linux package managers) and screenshots.
  • Mention Linux equivalents for remote access (e.g., SSH) and agent installation/upgrade procedures.
  • Provide examples of firewall configuration for Linux servers.
  • Ensure parity in troubleshooting and next steps for both Windows and Linux platforms.
GitHub Create Pull Request
Azure Vmware Configure DNS forwarder for Azure VMware Solution ...es/azure-vmware/configure-dns-azure-vmware-solution.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides DNS forwarder configuration steps exclusively via the Azure portal UI and NSX-T Manager, which are platform-neutral. However, for command-line verification, only PowerCLI (PowerShell) examples are provided, with no Linux CLI or cross-platform alternatives. The use of PowerShell cmdlets and lack of Linux-native tools (e.g., dig, nslookup from shell) demonstrates a Windows-first and PowerShell-heavy bias, and omits Linux parity in example commands.
Recommendations
  • Add equivalent Linux CLI examples for DNS verification, such as using 'dig' or 'nslookup' directly from a Linux shell.
  • Mention how to perform DNS lookups from Linux VMs or via SSH, not just PowerCLI.
  • If possible, provide REST API or curl-based examples for NSX-T Policy API usage, which are cross-platform.
  • Clarify that PowerCLI is optional and not required if users prefer Linux or other platforms.
  • Ensure screenshots and instructions do not assume a Windows environment unless necessary.
GitHub Create Pull Request
Azure Vmware Set an external identity source for VMware NSX ...ure-vmware/configure-external-identity-source-nsx-t.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Windows Server Active Directory and related Windows tools (such as Windows Server Active Directory Certificate Services), both in prerequisites and configuration steps. All examples, screenshots, and instructions are tailored to Windows environments, with no mention of Linux-based LDAP servers (e.g., OpenLDAP) or Linux certificate authorities. The guidance assumes the use of Windows infrastructure and omits alternative LDAP sources or cross-platform considerations.
Recommendations
  • Include examples and instructions for configuring NSX with Linux-based LDAP servers, such as OpenLDAP.
  • Provide guidance on using non-Windows certificate authorities, including open-source options like Let's Encrypt or OpenSSL.
  • Add notes or sections describing how to adapt the process for organizations using Linux or mixed environments.
  • Ensure screenshots and terminology are not exclusively Windows-centric; consider generic LDAP terminology and visuals.
  • Clarify that NSX supports LDAP servers beyond Windows Server Active Directory, and provide parity in documentation for those scenarios.
GitHub Create Pull Request
Azure Vmware Set an external identity source for vCenter Server ...cles/azure-vmware/configure-identity-source-vcenter.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively focusing on Windows Server Active Directory as the external identity source for vCenter Server. All examples, prerequisites, and instructions reference Windows-specific tools (MMC, Windows domain controllers, NetBIOS names), and there are no examples or guidance for integrating with Linux-based LDAP servers (such as OpenLDAP) or using Linux tools. The documentation assumes the use of Windows environments and omits Linux alternatives, both in conceptual explanations and step-by-step procedures.
Recommendations
  • Add explicit examples and instructions for integrating vCenter Server with Linux-based LDAP servers (e.g., OpenLDAP), including configuration steps and required attributes.
  • Include Linux tool equivalents for certificate export and management (e.g., using openssl or certtool) alongside MMC instructions.
  • Generalize terminology and steps to refer to 'LDAP servers' rather than exclusively 'Windows Server Active Directory' where possible.
  • Provide sample configuration parameters and troubleshooting steps for non-Windows LDAP sources.
  • Clarify which steps are Windows-specific and which are applicable to any LDAP-compliant directory service.
GitHub Create Pull Request
Bastion Azure Bastion FAQ ...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias in several areas: browser recommendations are Windows-centric, keyboard layout instructions are only provided for Windows, and references to RDP and Microsoft Entra authentication focus on Windows VMs. There are no Linux-specific examples or instructions for common scenarios such as setting keyboard layouts, connecting via SSH, or managing permissions on Linux VMs. Linux tools, patterns, and user needs are not addressed, leading to a lack of parity for Linux administrators.
Recommendations
  • Provide Linux-specific instructions alongside Windows ones, especially for tasks like setting keyboard layouts, connecting via SSH, and managing user permissions.
  • When mentioning browser support, clarify compatibility for Linux distributions and suggest browsers commonly used on Linux.
  • Include examples and documentation links for connecting to Linux VMs (e.g., SSH key management, Linux user groups for SSH access).
  • When describing features like file transfer or native client support, specify any differences or additional steps for Linux users.
  • Avoid assuming Windows as the default environment; use neutral language and parallel examples for both Windows and Linux where applicable.
GitHub Create Pull Request
Azure Vmware Configure a Storage Policy ...main/articles/azure-vmware/configure-storage-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses PowerShell-style cmdlets and 'Run command' workflows, which are typically associated with Windows environments. There are no examples or references to Linux-native tools, shell commands, or cross-platform alternatives. All operational instructions assume the use of Windows-centric tooling, and there is no guidance for users who may prefer or require Linux-based automation or CLI workflows.
Recommendations
  • Provide equivalent Linux/bash command examples for each operation, using tools like VMware's govc CLI, vSphere API calls via curl, or Python scripts.
  • Clarify whether the 'Run command' interface is accessible from Linux environments, and if so, document how to invoke these commands from a Linux shell.
  • Include cross-platform automation guidance, such as using REST APIs or SDKs (e.g., Python, Go) that work on both Windows and Linux.
  • Add notes or sections for Linux users, specifying any prerequisites or differences in workflow.
  • Ensure screenshots and UI references are not exclusively Windows-centric, or provide Linux alternatives where applicable.
GitHub Create Pull Request
Azure Vmware Configure VMware vSAN ESA .../blob/main/articles/azure-vmware/configure-vsan-esa.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by exclusively referencing PowerShell cmdlets (e.g., Set-vSANDataInTransitEncryption), Windows-centric tools (Azure portal Run command), and features like Windows Server Failover Clusters. There are no Linux CLI examples, nor are Linux tools or workflows mentioned. Windows terminology and tools are presented as the default or only method for configuration.
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using VMware's ESXCLI, SSH, or REST APIs) for all configuration steps.
  • Mention Linux-supported guest OS features and how TRIM/UNMAP or encryption settings can be managed from Linux VMs.
  • Include instructions for running commands via Linux shells or automation tools (e.g., Bash scripts, Ansible) where possible.
  • Clarify whether the documented commands and procedures are OS-agnostic or provide OS-specific guidance for both Windows and Linux environments.
  • Reference Linux-based clustering solutions or note support for Linux guest clustering if applicable.
GitHub Create Pull Request
Azure Vmware Deploy disaster recovery using JetStream DR ...ure-vmware/deploy-disaster-recovery-using-jetstream.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Azure VMware Solution and Windows-centric tooling. All operational examples use Azure portal 'Run command' and PowerShell-style cmdlets (e.g., Invoke-PreflightJetDRInstall), with no mention of Linux CLI, shell scripts, or cross-platform alternatives. The installation, configuration, and management steps are exclusively described using Windows/Azure tools, and there are no Linux-specific instructions or examples. The documentation assumes the use of Azure portal and Windows-style automation, omitting guidance for Linux administrators or those using non-Windows environments.
Recommendations
  • Provide equivalent Linux CLI or shell script examples for JetStream DR installation, configuration, and management.
  • Document how to perform JetStream DR operations using Linux-based tools (e.g., SSH, curl, or native JetStream APIs) where possible.
  • Clarify whether the Azure portal 'Run command' and cmdlets can be invoked from Linux environments, and provide instructions if so.
  • Add explicit guidance for Linux administrators, including prerequisites, environment setup, and troubleshooting steps relevant to Linux.
  • Include references to JetStream DR documentation or tools that support Linux platforms, and highlight any differences or limitations.
GitHub Create Pull Request
Azure Vmware Deploy Zerto disaster recovery on Azure VMware Solution ...rticles/azure-vmware/deploy-zerto-disaster-recovery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. While it describes both Linux and Windows components, the only Windows-specific tool (Zerto Cloud Appliance, ZCA) is highlighted as necessary for Azure IaaS VM recovery, and its subcomponents (ZVM, VRA) are described as Windows services. There are no Linux-based equivalents or examples for this scenario, nor are Linux deployment or troubleshooting steps provided for ZCA. The documentation also lists Windows tools before Linux alternatives in the ZCA section and omits Linux command-line or automation examples, despite mentioning Linux-based appliances elsewhere.
Recommendations
  • Provide Linux-based examples or alternatives for ZCA deployment and management, if available.
  • Include Linux command-line or automation instructions for Zerto components where applicable.
  • Ensure that both Windows and Linux tools/services are described with equal detail and order, or clarify platform requirements up front.
  • Add troubleshooting and log collection steps for Linux-based Zerto components, not just Windows.
  • Where Windows-only components are required (e.g., ZCA), explicitly state the lack of Linux support and suggest workarounds or alternatives if possible.
GitHub Create Pull Request
Azure Vmware Trusted Launch for Azure VMware Solution ...re-vmware/configure-virtual-trusted-platform-module.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific security features (BitLocker, credential protection, malware prevention on Windows) before Linux equivalents, and by mentioning Windows guest OS support prior to Linux in the prerequisites. No Linux-specific security tooling (e.g., LUKS, dm-crypt) or configuration examples are provided, and the benefits and use cases focus on Windows scenarios.
Recommendations
  • Include Linux-specific security features that benefit from vTPM, such as LUKS/dm-crypt disk encryption, Secure Boot for Linux distributions, and Linux attestation tools.
  • Provide configuration examples or references for enabling and using vTPM with Linux guest operating systems.
  • List Linux guest OS support before or alongside Windows in prerequisites to avoid ordering bias.
  • Discuss Linux-specific migration scenarios and tooling in the 'Unsupported scenarios' section.
  • Balance references to Windows and Linux security benefits throughout the documentation.
GitHub Create Pull Request
Azure Vmware Configure VMware vSAN ...docs/blob/main/articles/azure-vmware/configure-vsan.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing examples using PowerShell cmdlets and Azure portal workflows, which are most familiar to Windows users. There is no mention of Linux command-line tools or workflows, nor are there Linux-specific examples for configuring vSAN. Windows prerequisites are listed before Linux, and related content references Windows Server AD integration, further reinforcing the Windows-centric approach.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using SSH, Bash, or VMware CLI tools) for each configuration task.
  • Include instructions for accessing and running vSAN configuration commands from Linux environments, such as using the vSphere CLI or REST APIs.
  • List Linux prerequisites and workflows alongside or before Windows examples to ensure parity.
  • Reference Linux identity sources and integration options in related content, not just Windows Server AD.
  • Clarify which tools and commands are cross-platform, and note any platform-specific differences or limitations.
GitHub Create Pull Request
Azure Vmware Deploy Arc-enabled VMware vSphere for Azure VMware Solution private cloud ...s/azure-vmware/deploy-arc-for-azure-vmware-solution.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. In the onboarding section, Windows/PowerShell instructions are presented before Linux equivalents, and the need to bypass PowerShell execution policy is highlighted. File paths in configuration examples use Windows-style (C:\Users\...), and proxy certificate instructions reference Windows locations. While Linux instructions are present, they are secondary and less detailed. There is also a focus on Windows Server and SQL Server benefits in Azure, with no mention of Linux VM use cases or parity.
Recommendations
  • Present Linux and Windows instructions in parallel or with equal prominence, rather than Windows-first.
  • Use OS-agnostic file path examples (e.g., /home/user/sampleUser.sslProxy.crt or generic placeholders) in configuration samples.
  • Include explicit Linux use cases and benefits (e.g., managing Linux VMs, guest management for Linux, parity with Windows features).
  • Ensure that all tooling and script instructions are equally detailed for both platforms.
  • Avoid referencing Windows-specific tools or patterns unless there is no Linux equivalent, and provide alternatives where possible.
GitHub Create Pull Request
Azure Vmware vCenter Server access and identity description ...vmware/includes/vcenter-access-identity-description.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server Active Directory for user and group management, without mentioning or providing examples for Linux-based identity solutions (such as OpenLDAP). The documentation also refers to Windows tools and patterns first and does not provide Linux equivalents or alternatives.
Recommendations
  • Include references to Linux-based identity sources (e.g., OpenLDAP) and explain how they can be integrated, if supported.
  • Provide examples or guidance for configuring user and group management using non-Windows identity providers.
  • Ensure that documentation does not assume Windows Server Active Directory as the only or primary solution; mention alternatives where applicable.
  • If certain features are only available with Windows tools, explicitly state this and clarify any limitations for Linux users.
GitHub Create Pull Request
Azure Vmware Install Cloud Backup for Virtual Machines .../azure-vmware/install-cloud-backup-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure portal 'Run command' workflows and PowerShell-style cmdlets (e.g., Install-NetAppCBSA, Invoke-UpgradeNetAppCBSAppliance), with no mention of Linux CLI, shell, or automation alternatives. All operational steps are described using Windows-centric tools and patterns, and there are no examples or guidance for Linux users or administrators who may prefer command-line or automation via bash, SSH, or REST API.
Recommendations
  • Provide equivalent Linux CLI or shell-based instructions for installation, upgrade, and uninstallation steps, such as using Azure CLI, REST API, or SSH.
  • Include examples of how to automate these tasks from Linux environments, such as bash scripts or Ansible playbooks.
  • Mention cross-platform tools and clarify whether the 'Run command' workflow is accessible via non-Windows environments.
  • Add notes or sections specifically addressing Linux administrators, including troubleshooting and operational tips relevant to Linux.
  • Ensure parity in screenshots and field descriptions, showing how the process appears or is executed from Linux or cross-platform interfaces.
GitHub Create Pull Request
Azure Vmware Migrate Microsoft SQL Server Always On Availability Group to Azure VMware Solution ...are/migrate-sql-server-always-on-availability-group.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily oriented toward Windows environments, specifically Windows Server and Microsoft SQL Server Always On Availability Groups, which are only supported on Windows. All examples, tooling, and configuration steps reference Windows Server Failover Clustering, SQL Server Management Studio (SSMS), and Windows-based clustering concepts. There are no Linux equivalents, examples, or alternative approaches mentioned, and all references to clustering, quorum, and migration are Windows-centric.
Recommendations
  • Explicitly state that SQL Server Always On Availability Groups are only supported on Windows, and clarify if there are any Linux-based alternatives or similar high-availability solutions for SQL Server on Linux.
  • If Linux-based SQL Server deployments are supported in Azure VMware Solution, provide a parallel section or note describing the migration process for those environments, including any differences in tooling or steps.
  • Include references to Linux tools (such as sqlcmd or Azure Data Studio) where applicable, or clarify their (in)applicability in this scenario.
  • Where Windows-specific tools or concepts are used (e.g., Failover Cluster, SSMS), briefly mention that these are not available on Linux and suggest alternative approaches or documentation for Linux users if relevant.
  • Add a note in the prerequisites or introduction to acknowledge the Windows-centric nature of the guide and direct Linux users to appropriate resources if available.
GitHub Create Pull Request
Azure Vmware Monitor and protect VMs with Azure native services ...ticles/azure-vmware/integrate-azure-native-services.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias. Windows-specific concepts (such as registry and Microsoft services) are mentioned before Linux equivalents, and Windows terminology is more prominent. While Linux is referenced (e.g., Linux daemons), there are no concrete Linux command-line examples for monitoring or extension installation, and the only explicit Linux instruction is for sudoers configuration. No Linux-specific monitoring or troubleshooting tools are discussed, and the focus is on Azure portal GUI steps, which may be more familiar to Windows administrators.
Recommendations
  • Provide parallel Linux and Windows examples for monitoring, extension installation, and troubleshooting (e.g., show both PowerShell and Bash/CLI commands).
  • Mention Linux-specific monitoring targets (e.g., systemd services, log files) alongside Windows registry and services.
  • Include Linux command-line instructions for installing and verifying Azure extensions, not just sudoers configuration.
  • Balance the order of presentation so that Linux and Windows are given equal prominence when discussing supported platforms and features.
  • Reference Linux-native tools and patterns (e.g., journalctl, systemctl) where appropriate.
GitHub Create Pull Request
Azure Vmware Migrate SQL Server Failover cluster to Azure VMware Solution ...es/azure-vmware/migrate-sql-server-failover-cluster.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows Server Failover Clustering and SQL Server on Windows. All examples, procedures, and screenshots reference Windows Server tools (e.g., Failover Cluster Manager, SQL Server Management Studio) and Windows-specific clustering concepts. There are no examples, mentions, or guidance for Linux-based SQL Server clusters or cross-platform scenarios.
Recommendations
  • Include guidance or at least a note for users running SQL Server on Linux, clarifying if the procedure is applicable or not.
  • Add examples or references for migrating Linux-based SQL Server clusters, if supported, or explicitly state limitations.
  • Mention Linux equivalents (such as Pacemaker for clustering) where appropriate, or explain why only Windows Server Failover Clustering is covered.
  • Provide parity in tooling instructions, e.g., mention Linux command-line tools or management interfaces if relevant.
  • If the migration process is fundamentally different or unsupported for Linux, make this clear early in the documentation.
GitHub Create Pull Request
Azure Vmware Migrate Microsoft SQL Server Standalone to Azure VMware Solution .../azure-vmware/migrate-sql-server-standalone-cluster.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server and Microsoft SQL Server. All examples, prerequisites, and tested configurations reference only Windows Server editions, with no mention of Linux-based SQL Server deployments or migration scenarios. Tools and best practices referenced are Windows-centric (e.g., SQL Server Management Studio, Windows Server Failover Clustering), and there are no Linux equivalents or alternative instructions provided.
Recommendations
  • Include tested configurations and migration steps for SQL Server running on Linux (e.g., Ubuntu, Red Hat) to ensure parity.
  • Provide Linux-specific prerequisites, such as backup procedures and network configuration steps for Linux VMs.
  • Add examples using Linux tools (e.g., sqlcmd, Azure Data Studio) for post-migration verification.
  • Reference Linux clustering solutions (e.g., Pacemaker, Corosync) where applicable.
  • Link to relevant Linux documentation for SQL Server and clustering.
  • Clarify whether the migration process is supported for Linux-based SQL Server instances and, if so, provide guidance.
GitHub Create Pull Request
Azure Vmware Protect web apps on Azure VMware Solution with Azure Application Gateway ...protect-azure-vmware-solution-with-application-gateway.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All configuration examples for backend web servers use Windows Server 2016 and Internet Information Services (IIS), with setup instructions provided exclusively via PowerShell commands. There are no Linux-based examples, nor are Linux web server tools (such as Apache or Nginx) mentioned. The use of Windows tools and patterns is exclusive and presented as the default, with no parity for Linux environments.
Recommendations
  • Add parallel examples using Linux VMs (e.g., Ubuntu or CentOS) as backend servers.
  • Include setup instructions for popular Linux web servers such as Apache (httpd) and Nginx, using bash commands.
  • Present Linux configuration examples alongside Windows examples, or alternate their order to avoid Windows-first bias.
  • Explicitly mention that both Windows and Linux VMs are supported as backend pools for Application Gateway.
  • Provide troubleshooting and validation steps for Linux-based web servers, not just IIS/Windows.
  • Reference cross-platform tools and commands where possible, or clarify OS-specific instructions.
GitHub Create Pull Request
Azure Vmware Restore guest files and folders using Cloud Backup for Virtual Machines ...n/articles/azure-vmware/restore-guest-files-folders.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows environments. All examples, instructions, and credential requirements are specific to Windows guest OS, with explicit statements that Linux guest OS restore is not supported. Windows tools, patterns (e.g., UNC paths, administrator account requirements), and terminology are used exclusively, with no Linux equivalents or guidance. Linux users are only told they can manually restore files after attaching a VMDK, with no further detail or parity in workflow.
Recommendations
  • Add explicit instructions or examples for manual file restore from Linux guest OS after VMDK attachment, including recommended tools (e.g., mount, guestmount, etc.).
  • Clarify limitations and provide guidance for Linux users, such as steps to mount VMDK on a Linux system and copy files.
  • Where possible, support automated or wizard-based file restore for Linux guest OS, or document alternative workflows.
  • Include credential and access patterns relevant to Linux (e.g., root, sudo, SSH keys) alongside Windows examples.
  • Avoid language that implies Windows is the only supported or primary platform; clearly state platform limitations and roadmap for Linux support.
GitHub Create Pull Request
Azure Vmware Enable first-party application service principal for Azure VMware Solution Generation 2 Private Clouds .../azure-vmware/native-first-party-principle-security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides step-by-step instructions for enabling the service principal using the Microsoft Entra ID portal (GUI), Azure PowerShell, and Azure CLI. The PowerShell example is detailed and appears before the CLI example, which may indicate a Windows-first and PowerShell-heavy bias. PowerShell is a Windows-centric tool, and its prominence over cross-platform CLI options suggests a preference for Windows tooling. There are no explicit Linux-specific instructions, nor are there mentions of Linux shell environments or alternative Linux-native tools.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more accessible to Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for Linux users where appropriate.
  • Add troubleshooting notes or examples for common Linux shell environments (e.g., bash) if relevant.
  • Consider including references to automation via Linux shell scripts or integration with Linux-based CI/CD pipelines.
  • Avoid implying PowerShell is the default or preferred method unless there is a technical reason.
GitHub Create Pull Request
Azure Vmware Remove Arc-enabled Azure VMware Solution vSphere resources from Azure ...led-azure-vmware-solution-vsphere-resources-from-azure.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation presents Windows uninstall instructions before Linux, and references Windows-specific tools (Control Panel, Programs and Features) in detail. The Linux instructions are less detailed and grouped together, while the Windows steps are more granular and described first. There is a general tendency to present Windows patterns and terminology before Linux equivalents.
Recommendations
  • Present Linux and Windows uninstall instructions in parallel or in separate, equally detailed sections, alternating which OS is presented first in different documentation pages.
  • Provide more detailed Linux instructions, including common troubleshooting steps and file locations to remove residual agent files, similar to the Windows instructions.
  • Avoid using Windows-centric terminology (e.g., Control Panel) without providing equivalent Linux context (e.g., package manager, service management).
  • Include screenshots or step-by-step guidance for Linux environments, not just Windows.
  • Explicitly mention parity of features and steps between Windows and Linux, and clarify any OS-specific differences.
GitHub Create Pull Request
Azure Vmware Set up Azure Backup Server for Azure VMware Solution ...ware/set-up-backup-server-for-azure-vmware-solution.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a strong Windows bias. All VM creation and management instructions reference Windows Server, with no mention of Linux alternatives. Disk attachment and management examples are exclusively for Windows VMs. The installation steps, prerequisites, and backup/restore scenarios are tailored to Windows environments, including references to Windows-specific tools (e.g., ReFS, VSS, Windows Update, PowerShell for SSRS configuration). There are no Linux-specific examples, instructions, or parity in tooling or process, despite brief mentions that Linux VMs are supported for application-consistent backups via scripts.
Recommendations
  • Add explicit instructions and examples for deploying Azure Backup Server on Linux-based VMs, if supported.
  • Provide parity in disk attachment and management documentation for Linux VMs (e.g., using Azure CLI or portal for Linux, mounting disks, file system recommendations).
  • Include Linux-specific backup/restore scenarios, including how to achieve application-consistent backups (with sample pre/post scripts).
  • Reference Linux equivalents for tools and processes (e.g., ext4/xfs file systems, cron jobs for updates, Linux authentication and domain join instructions if applicable).
  • If Azure Backup Server is Windows-only, clarify this limitation early in the documentation and provide guidance for Linux VM backup alternatives.
GitHub Create Pull Request
Azure Vmware Azure Hybrid Benefit for Windows Server, SQL Server, or Linux subscriptions ...ain/articles/azure-vmware/sql-server-hybrid-benefit.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page, while mentioning Linux subscriptions in the title and description, focuses almost exclusively on Windows Server and SQL Server use cases, licensing, and migration scenarios. All examples and next steps are centered around Microsoft SQL Server and Windows Server, with no concrete examples, instructions, or migration paths provided for Linux workloads or tools. Windows technologies and patterns (e.g., Windows Server Failover Cluster, SQL Server licensing) are discussed in detail, whereas Linux equivalents are absent.
Recommendations
  • Add concrete examples and migration scenarios for Linux workloads, such as migrating Linux-based databases (e.g., MySQL, PostgreSQL) to Azure VMware Solution.
  • Include instructions and licensing details for applying Azure Hybrid Benefit to Linux subscriptions, with step-by-step guides.
  • Provide parity in 'Next steps' by listing Linux-specific guides (e.g., configuring Linux clustering solutions, enabling hybrid benefit for Linux VMs).
  • Mention Linux tools and patterns (e.g., Pacemaker, Corosync for clustering) alongside Windows equivalents.
  • Ensure that Linux is not only referenced in the title/description but also receives equal coverage in the main content and examples.
GitHub Create Pull Request
Azure Vmware Tutorial - Access an Azure VMware Solution private cloud ...articles/azure-vmware/tutorial-access-private-cloud.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively describes creating and using a Windows VM as a jump box to access Azure VMware Solution resources. All examples, screenshots, and instructions are Windows-centric, with no mention of Linux alternatives or parity. References to connecting to the VM and authentication are tailored to Windows, and no Linux VM or SSH-based access patterns are discussed.
Recommendations
  • Add instructions and examples for creating a Linux VM as a jump box, including relevant screenshots.
  • Provide guidance for connecting to the Linux VM (e.g., via SSH) and accessing vCenter Server and NSX Manager from Linux-based browsers.
  • Mention Linux authentication options (e.g., SSH keys) alongside Windows password authentication.
  • Ensure parity in troubleshooting and connectivity documentation for both Windows and Linux jump boxes.
  • Explicitly state that either Windows or Linux VMs can be used as jump boxes, and discuss pros/cons or considerations for each.
GitHub Create Pull Request
Azure Vmware Using Run Command in Azure VMware Solution ...s/blob/main/articles/azure-vmware/using-run-command.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing PowerShell cmdlets and not providing any Linux or cross-platform CLI examples. The term 'cmdlet' is specific to PowerShell, a Windows-centric tool, and there is no mention of Bash, shell scripts, or Linux-native tooling. All operational instructions and screenshots are based on the Azure portal UI or PowerShell concepts, with no guidance for Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI or Bash scripts where possible, especially for Run Command operations.
  • Clarify whether Run Command supports only PowerShell or if Linux shell scripts are also supported; if so, include Linux examples.
  • Use more platform-neutral language (e.g., 'command' instead of 'cmdlet') where appropriate.
  • Add a section or note for Linux/macOS users explaining how to perform similar tasks from their environments, including any prerequisites or limitations.
  • If PowerShell Core (cross-platform) is supported, explicitly mention it and provide examples for both Windows and Linux terminals.
GitHub Create Pull Request
Azure Vmware Use VMware HCX Run Commands ...lob/main/articles/azure-vmware/use-hcx-run-commands.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively describes the use of VMware HCX Run Commands via PowerShell-style cmdlets and the Azure portal, with no mention of Linux command-line equivalents, Bash scripting, or cross-platform tooling. All examples and instructions are tailored to Windows-centric workflows, such as PowerShell cmdlets and Azure portal navigation, without providing parity for Linux users or alternative approaches. This creates a bias towards Windows environments and may hinder Linux administrators from efficiently following the guidance.
Recommendations
  • Provide equivalent Linux/Bash command-line examples for each operation, using tools like Azure CLI, SSH, or REST API where possible.
  • Explicitly mention whether the Run Commands can be executed from Linux environments and, if so, how (e.g., via Azure CLI, REST API, or other cross-platform tools).
  • Include references to Linux-friendly automation and scripting approaches, such as Bash scripts or Ansible playbooks.
  • Clarify any platform-specific requirements or limitations, and ensure instructions are not solely focused on Windows/PowerShell.
  • Add a section comparing Windows and Linux workflows for managing VMware HCX in Azure, highlighting similarities and differences.
GitHub Create Pull Request
Azure Web Pubsub Add a custom domain .../main/articles/azure-web-pubsub/howto-custom-domain.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell/cmd examples before Bash, referencing Windows-specific tools (curl.exe, PS prompt), and using screenshots and instructions that are tailored to the Azure Portal GUI, which is more familiar to Windows users. There is little mention of Linux-specific workflows, and command-line examples default to Windows conventions.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell examples, especially in command-line sections.
  • Use platform-neutral commands and prompts (e.g., 'curl' instead of 'curl.exe', '$' instead of 'PS C:\>').
  • Include instructions and screenshots for Azure CLI and cross-platform tools, not just the Azure Portal GUI.
  • Explicitly mention Linux and macOS compatibility where relevant, and provide guidance for those platforms.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., certificate validation, DNS configuration).
GitHub Create Pull Request
Azure Web Pubsub Move an Azure Web PubSub resource to another region | Microsoft Docs ...articles/azure-web-pubsub/howto-move-across-regions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides detailed instructions for moving an Azure Web PubSub resource using the Azure Portal and Azure PowerShell. The PowerShell section is extensive and uses Windows-centric tools (e.g., notepad for editing JSON files), with no mention of Linux or cross-platform CLI alternatives. There are no Bash, Azure CLI, or Linux editor examples, and PowerShell is presented as the only scripting option. This creates a bias towards Windows users and workflows.
Recommendations
  • Add equivalent instructions using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
  • Include examples for editing JSON files using cross-platform editors (e.g., vim, nano, code) or generic instructions not tied to notepad.
  • Explicitly mention that PowerShell Core is available cross-platform, or provide Bash script alternatives for Linux users.
  • Reorder or parallelize the documentation so that Azure CLI and PowerShell instructions are presented together, rather than PowerShell-only.
  • Add notes or links for Linux/macOS users on how to perform each step, including authentication and file manipulation.
GitHub Create Pull Request
Azure Web Pubsub Quickstart - Publish messages using Azure Web PubSub service SDK ...b/main/articles/azure-web-pubsub/quickstart-use-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is given equal prominence to Bash, and is explicitly called out as a required shell in prerequisites. There is a slight Windows bias in the consistent inclusion of Azure PowerShell examples, even for steps that are natively cross-platform (Azure CLI), and in the assumption that users may use PowerShell locally. There are no explicit Linux-only examples or mentions of Linux-specific tools or patterns. The language SDK examples (Python, JavaScript, Java, C#) are Bash-centric, but the overall parity between Windows and Linux is not fully clear, and PowerShell is sometimes presented before Bash in variable naming conventions and explanations.
Recommendations
  • Clarify that Azure CLI commands work equally well on Linux, macOS, and Windows, and that Bash is available on all platforms.
  • Make Bash the default/primary example, with PowerShell as an optional tab for Windows users.
  • Add explicit notes for Linux/macOS users, including shell environment setup and common editors (e.g., mention nano/vim in addition to VS Code).
  • Where PowerShell is used, explain its cross-platform availability, or clarify when it is Windows-specific.
  • Consider including Linux-specific troubleshooting or environment setup steps, such as package manager commands for dependencies.
  • Avoid listing PowerShell as a prerequisite unless it is strictly required; emphasize Bash or sh for cross-platform compatibility.
GitHub Create Pull Request
Backup Restore options with Microsoft Azure Recovery Services (MARS) agent ...kup/about-restore-microsoft-azure-recovery-services.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Windows environments, with all examples and instructions referencing Windows Server, PowerShell, and Windows-specific utilities like robocopy. There are no Linux equivalents or examples provided, and the restore options are described exclusively in the context of Windows systems. This creates a strong Windows bias and excludes Linux administrators from understanding how (or if) the MARS agent can be used in non-Windows environments.
Recommendations
  • Clarify whether the MARS agent supports Linux systems, and if not, explicitly state its Windows-only scope.
  • If Linux support exists or is planned, provide equivalent restore instructions and examples for Linux environments, including command-line tools and workflows.
  • Mention Linux file copy tools (e.g., rsync, cp) alongside robocopy when discussing file transfer from mounted recovery points.
  • Add a section comparing restore options and limitations between Windows and Linux (if applicable).
  • Ensure that prerequisites and automation examples include Linux-specific guidance where relevant.
GitHub Create Pull Request
Backup About the Azure Virtual Machine restore process ...cs/blob/main/articles/backup/about-azure-vm-restore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways: examples and links for encrypted VM restore are exclusively for Windows VMs, and the restore process for encrypted VMs specifically mentions using PowerShell (a Windows-centric tool) without mentioning Linux alternatives. There are no references to Linux VM restore scenarios, nor are Linux-specific tools or commands provided. The documentation links for disk encryption also point only to Windows VM guides.
Recommendations
  • Add equivalent Linux VM restore scenarios and examples, especially for encrypted VMs.
  • Include instructions for restoring encrypted Linux VMs, referencing Azure CLI or other cross-platform tools instead of only PowerShell.
  • Provide links to Linux disk encryption documentation (e.g., for VMs using DM-Crypt or Azure Disk Encryption for Linux).
  • Ensure that restore steps and troubleshooting guides cover both Windows and Linux VMs equally, with clear parity in examples and tool recommendations.
GitHub Create Pull Request
Backup Azure Backup - Archive tier overview ...docs/blob/main/articles/backup/archive-tier-support.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Azure Virtual Machines (which are often Windows-based), SQL Server (a Windows-centric workload), and SAP HANA in Azure VMs. The 'Supported clients' section lists PowerShell before CLI, and there are no explicit Linux or Bash examples, nor any mention of Linux-specific workloads or tools. Screenshots and step-by-step instructions reference the Azure portal and PowerShell, with no parity for Linux command-line usage or Linux VM scenarios.
Recommendations
  • Add explicit examples for Linux VMs, including backup and archive operations for Linux workloads.
  • Provide Bash/CLI command examples alongside PowerShell, and list CLI before or alongside PowerShell in 'Supported clients'.
  • Include screenshots or instructions for Linux users, such as using Azure CLI on Linux systems.
  • Mention Linux-specific backup scenarios and clarify if archive tier support applies equally to Linux VMs.
  • Ensure documentation covers both Windows and Linux environments with equal depth and visibility.
GitHub Create Pull Request
Azure Web Pubsub Tutorial - Visualize IoT device data from IoT Hub using Azure Web PubSub service and Azure Functions ...n/articles/azure-web-pubsub/tutorial-serverless-iot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific tools (Storage Emulator), mentions enabling the Storage Emulator for local development without suggesting Linux/macOS alternatives, and refers to PowerShell modules and commands. There is no mention of Linux/macOS equivalents for the Storage Emulator, nor are cross-platform alternatives or instructions provided for those environments. The order of presentation and tool recommendations (e.g., Storage Emulator) assume a Windows environment by default.
Recommendations
  • Explicitly mention and provide instructions for using Azure Storage Emulator alternatives on Linux/macOS, such as Azurite.
  • When referencing PowerShell or Windows-specific tools, also provide equivalent Bash/Azure CLI commands and instructions for Linux/macOS users.
  • Add notes or sections clarifying cross-platform compatibility for all tools and commands.
  • Ensure that examples and troubleshooting steps do not assume a Windows environment by default; present cross-platform options equally or in parallel.
  • Where possible, use platform-neutral language and tools (e.g., recommend Azurite for local storage emulation instead of Storage Emulator).
GitHub Create Pull Request
Backup Back up and restore Active Directory using Azure Backup ...ain/articles/backup/active-directory-backup-restore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, with all examples, scripts, and tools (e.g., PowerShell, ntdsutil.exe, Active Directory Domain Services) being Windows-specific. There are no Linux equivalents or examples, and the guidance assumes the use of Windows Server for domain controllers. Windows terminology and tools are used exclusively and presented first, with no mention of Linux-based alternatives or cross-platform scenarios.
Recommendations
  • Include explicit statements clarifying that Active Directory domain controllers are Windows-only, but acknowledge Samba as a potential open-source alternative for Linux environments.
  • Provide guidance or links for backing up and restoring Samba-based domain controllers on Linux, if relevant to Azure Backup.
  • Add examples or notes for Linux-based backup tools and procedures where possible, or clarify Azure Backup's limitations regarding non-Windows domain controllers.
  • Where PowerShell is used, offer Bash or shell script equivalents for any operations that could be performed on Linux (e.g., querying backup status, interacting with Azure Backup APIs).
  • Clearly state platform limitations and recommend best practices for Linux administrators who may be seeking similar functionality.
GitHub Create Pull Request
Backup Automation in Azure Backup ...re-docs/blob/main/articles/backup/automation-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by repeatedly mentioning PowerShell as a primary automation method and example, listing PowerShell before CLI and other cross-platform tools, and providing workflow examples that center on PowerShell and Azure Automation Runbooks (which are often Windows-centric). There are no explicit Linux shell (bash) or cross-platform CLI examples, and no mention of Linux-specific patterns or considerations. The video walkthroughs also appear to focus on PowerShell-based workflows.
Recommendations
  • Add explicit bash/CLI examples alongside PowerShell for each automation scenario.
  • When listing automation methods, alternate or randomize the order, or explicitly state both Windows and Linux options.
  • Include Linux-centric automation workflows, such as using bash scripts, cron jobs, or Linux-native tools in conjunction with Azure CLI.
  • Provide sample code snippets for both PowerShell and bash/CLI in key sections.
  • Clarify which automation methods are cross-platform and highlight any differences in usage or capabilities between Windows and Linux.
  • Ensure video walkthroughs or linked resources include Linux/CLI demonstrations.
GitHub Create Pull Request
Backup Azure Backup glossary ...ocs/blob/main/articles/backup/azure-backup-glossary.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The glossary page for Azure Backup documentation demonstrates a Windows bias in several ways. Windows-specific technologies (such as VSS, DPM, MABS, MARS Agent) are referenced and explained in detail, while Linux equivalents are either omitted or mentioned only briefly. For example, application-consistent backup describes VSS in detail and only refers to 'pre or post scripts for Linux' without further explanation or links. Many backup scenarios and tools (e.g., Bare Metal Backup, System State Backup, DPM, MABS) are Windows-centric, with no Linux alternatives or parity. References to Azure PowerShell are explicit, but Linux CLI or scripting approaches are not highlighted. The glossary also links to Windows-specific documentation (e.g., VSS) and provides examples and terminology that are more relevant to Windows workloads.
Recommendations
  • Add equivalent Linux backup concepts and tooling (e.g., LVM snapshots, fsfreeze, etc.) where Windows-specific technologies like VSS are mentioned.
  • Provide links to Linux documentation and examples for backup scenarios, especially for application-consistent and file-system-consistent backups.
  • Include Linux-centric backup agents or methods (such as Azure Backup for Linux VMs, or third-party Linux backup solutions) alongside Windows tools like MARS, DPM, and MABS.
  • Ensure parity in examples and terminology, describing both Windows and Linux approaches for each relevant glossary entry.
  • Highlight Azure CLI usage and scripting for Linux environments as prominently as Azure PowerShell is for Windows.
GitHub Create Pull Request
Backup Support matrix for Azure Data Lake Storage Vaulted Backup ...ackup/azure-data-lake-storage-backup-support-matrix.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page references configuration and management via Azure portal, PowerShell, or Azure CLI, but lists PowerShell before Azure CLI and does not provide explicit Linux-oriented examples or mention Bash/Shell scripting. There are no references to Linux-specific tools, nor are Linux command-line patterns highlighted. The ordering and emphasis suggest a Windows-first approach, and the lack of Linux examples or parity in tooling may hinder Linux users.
Recommendations
  • Ensure that Azure CLI (cross-platform) is mentioned before or alongside PowerShell in all instructions and links.
  • Provide explicit Bash/Shell scripting examples for common backup and restore operations.
  • Include notes or sections highlighting Linux compatibility and any platform-specific considerations.
  • Avoid listing Windows-centric tools (PowerShell) before cross-platform tools (Azure CLI) unless contextually justified.
  • Add troubleshooting tips or FAQs for Linux environments, especially for command-line operations.
GitHub Create Pull Request
Backup What is Azure Kubernetes Service (AKS) Backup? ...les/backup/azure-kubernetes-service-backup-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits mild Windows bias. While the main content is platform-neutral and focuses on AKS concepts, the 'Related content' section lists 'Back up AKS by using Azure PowerShell' before 'Restore AKS by using the Azure CLI', suggesting a Windows-first orientation. The explicit mention of PowerShell as a backup tool and the absence of Linux-specific examples or references to Bash or Linux-native tools further reinforce this bias. There are no explicit Linux examples, and PowerShell (a Windows-centric tool) is highlighted as a primary method for backup operations.
Recommendations
  • Provide backup examples using Bash scripts or Linux-native tools alongside PowerShell.
  • List Azure CLI and Bash-based instructions before or alongside PowerShell in 'Related content' and throughout the documentation.
  • Explicitly mention cross-platform compatibility for all command-line tools and clarify that both Windows and Linux users are supported.
  • Include links to Linux-specific guides or troubleshooting for AKS backup and restore operations.
  • Ensure parity in example scripts, showing both PowerShell and Bash/CLI equivalents where possible.
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup using Azure Backup prerequisites ...kup/azure-kubernetes-service-cluster-backup-concept.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure portal and PowerShell as primary management interfaces for AKS backup operations. Examples and next steps reference Azure PowerShell before Azure CLI, and there are no explicit Linux shell or bash examples. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell and the Azure portal, while Linux-native workflows (e.g., bash scripting, kubectl usage from Linux terminals) are not mentioned or illustrated.
Recommendations
  • Provide explicit bash/Linux shell examples for AKS backup operations using Azure CLI and kubectl.
  • List Azure CLI instructions before or alongside PowerShell in all relevant sections and next steps.
  • Include guidance for managing AKS backup from Linux/macOS environments, such as using terminal commands and scripting.
  • Clarify that all operations can be performed from Linux systems, and highlight any platform-specific differences or requirements.
  • Add references to Linux-native tools and workflows where applicable, ensuring parity in documentation for non-Windows users.
GitHub Create Pull Request
Backup Restore Azure Kubernetes Service (AKS) using Azure Backup ...les/backup/azure-kubernetes-service-cluster-restore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by explicitly referencing Azure PowerShell as an alternative restore method and linking to a PowerShell-specific guide, without mentioning or providing equivalent examples for Linux-native tools (such as Azure CLI or Bash scripting). The main restore workflow is GUI-based, which is cross-platform, but the only command-line option highlighted is PowerShell. There are no Linux or Azure CLI examples, nor is there guidance for Linux users, which may hinder parity and accessibility for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI (az) examples and workflows for restoring AKS clusters using Azure Backup.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to Linux/Bash-friendly documentation.
  • Include sample scripts or walkthroughs for Linux users, such as Bash shell commands, to complement the PowerShell instructions.
  • Ensure that references to command-line tools do not prioritize Windows/PowerShell over cross-platform alternatives.
  • Review screenshots and UI instructions to confirm they are not Windows-specific, and clarify any OS-agnostic steps.
GitHub Create Pull Request
Backup Back up file data with MABS ...re-docs/blob/main/articles/backup/back-up-file-data.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation for backing up file data with MABS is heavily oriented toward Windows environments. It references Windows-specific features (such as Data Deduplication and VSS), uses terminology and UI patterns from Windows (e.g., 'Properties', 'Previous Versions'), and does not provide examples or guidance for Linux systems. There are no Linux-specific instructions, screenshots, or parity notes, despite mentioning that MABS can protect both server and client computers.
Recommendations
  • Add explicit instructions and examples for backing up Linux machines with MABS, including agent installation, supported file systems, and recovery procedures.
  • Include Linux-specific prerequisites, such as required packages, permissions, and supported distributions.
  • Document any differences in backup and recovery workflows between Windows and Linux clients.
  • Mention Linux equivalents for Windows features (e.g., alternatives to VSS, deduplication support) or clarify limitations.
  • Provide screenshots or CLI examples for Linux systems where applicable.
  • Ensure that references to features or UI elements are not exclusively Windows-centric, or provide Linux alternatives where possible.
GitHub Create Pull Request
Backup Back up Azure Kubernetes Service by using Azure Backup ...cles/backup/azure-kubernetes-service-cluster-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell as the only CLI alternative to the Azure Portal, both in the introduction and in the 'Next steps' section. There are no examples or instructions for using Azure CLI, Bash, or Linux-native tools for AKS backup operations. The documentation does not mention or provide parity for Linux users, who typically use Azure CLI and Bash scripts, nor does it provide cross-platform command examples.
Recommendations
  • Add Azure CLI examples alongside or before Azure PowerShell examples for all backup and restore operations.
  • Explicitly mention that both Azure CLI and PowerShell can be used, and provide links to Linux/Bash instructions where relevant.
  • Ensure screenshots and step-by-step instructions are not Windows-centric (e.g., avoid only showing PowerShell or Windows UI).
  • Include Bash script samples for deploying backup hooks and configuring AKS backup, in addition to kubectl commands.
  • Review all references to command-line tools and ensure Linux parity is maintained throughout the documentation.
GitHub Create Pull Request
Backup Back up Azure Local virtual machines with MABS ...e-stack-hyperconverged-infrastructure-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Windows tools (PowerShell, .exe installers), and instructions for agent installation and firewall configuration are exclusively Windows-centric. Linux prerequisites are mentioned briefly, but there are no Linux-specific backup or recovery examples, nor any guidance for Linux users on how to perform equivalent operations. Windows terminology and patterns (Hyper-V, VHD, Windows authentication methods) are used throughout, with no parity for Linux environments.
Recommendations
  • Provide Linux-specific command-line examples for agent installation, configuration, and backup/recovery operations (e.g., using shell commands or Linux package managers).
  • Include instructions for managing firewall rules and agent deployment on Linux VMs, not just Windows/PowerShell.
  • Clarify which steps are applicable to Linux VMs and highlight any differences or limitations.
  • Add screenshots or walkthroughs of the process for Linux VMs where the UI or workflow differs.
  • Expand the 'Linux prerequisites' section to include troubleshooting, supported distributions, and recovery procedures.
  • Where Windows authentication methods are mentioned, note Linux equivalents (e.g., SSH keys, certificate-based auth).
GitHub Create Pull Request
Backup Back up Hyper-V virtual machines with MABS ...ticles/backup/back-up-hyper-v-virtual-machines-mabs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server. All examples, procedures, and screenshots are for Windows Server and Windows-based tools (MABS, Hyper-V, VSS). Linux is only mentioned briefly as a supported guest OS, with no detailed instructions, examples, or screenshots for Linux VMs. Windows-specific features and registry keys are referenced, and there is no parity in guidance for Linux VM backup or recovery.
Recommendations
  • Add detailed backup and recovery procedures for Linux VMs, including step-by-step instructions and screenshots.
  • Provide examples of item-level recovery for Linux VMs, noting any limitations or differences compared to Windows VMs.
  • Include Linux-specific prerequisites and troubleshooting steps, such as supported file systems, integration services, and consistency levels.
  • Clarify which features are Windows-only and suggest Linux alternatives or workarounds where possible.
  • Ensure that Linux scenarios are presented with equal prominence and detail as Windows scenarios.
GitHub Create Pull Request
Backup Tutorial - Back up Azure Managed Disks using Azure Backup ...main/articles/backup/back-up-managed-disks-tutorial.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page primarily describes backing up Azure Managed Disks using the Azure portal, which is platform-agnostic. However, when scripting is mentioned, PowerShell is listed before Azure CLI, and the only explicit script references in the main flow are to PowerShell and CLI, with PowerShell mentioned first. There are no Linux-specific examples, nor is Bash or Linux tooling highlighted. The documentation does not provide parity in examples or guidance for Linux users, and the scripting section implicitly prioritizes Windows/PowerShell.
Recommendations
  • When mentioning scripting options, list Azure CLI before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Provide explicit Bash/Linux shell examples for common tasks, such as automating disk backup, alongside PowerShell examples.
  • Include notes or sections clarifying that all portal-based steps are OS-agnostic, and highlight any differences for Linux users if applicable.
  • Reference Linux-friendly tools or workflows (e.g., Bash scripts, automation via cron) where appropriate.
  • Ensure that links to scripting guides (PowerShell/CLI) are presented with equal prominence and that Linux users are not implicitly directed to Windows-centric tools.
GitHub Create Pull Request
Backup Architecture Overview ...-docs/blob/main/articles/backup/backup-architecture.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: backup scenarios and tooling (MARS agent, DPM, MABS) are described exclusively for Windows, with Linux support either omitted or explicitly stated as unsupported. Windows tools and patterns (VSS, MARS agent) are discussed in detail, while Linux equivalents or alternatives are not mentioned. Examples and instructions for backup setup focus on Windows environments, with no Linux parity or guidance.
Recommendations
  • Add explicit coverage of Linux backup scenarios, including supported methods and limitations.
  • Provide Linux-specific examples and tooling (such as Azure Backup integration with Linux agents or third-party solutions).
  • If Linux is not supported for certain backup methods, clarify alternatives or workarounds for Linux users.
  • Ensure that backup architecture diagrams and walkthroughs include both Windows and Linux environments where applicable.
  • List Linux support status in tables and matrices, not just as a footnote or omission.
  • Consider parity in terminology and process explanations (e.g., mention Linux snapshot mechanisms if discussing VSS for Windows).
GitHub Create Pull Request
Backup Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup ...ckup/backup-azure-alternate-dpm-server-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Microsoft Azure Backup Server (MABS), which is a Windows-only product. All troubleshooting steps, error messages, and recommendations refer to Windows Server, Windows Client, and Windows-specific agents (such as DPM and Azure Backup agent). There are no examples, references, or troubleshooting steps for Linux systems or Linux backup agents, nor is there mention of Linux-compatible recovery workflows.
Recommendations
  • Clearly state in the introduction that MABS is a Windows-only product, and provide links to equivalent Linux backup and recovery documentation for Azure.
  • Add a section or cross-reference for troubleshooting data recovery on Linux systems using Azure Backup (e.g., for Azure Backup for Linux VMs or Azure File shares).
  • Include examples and error messages relevant to Linux backup agents and recovery scenarios, if supported.
  • If the product does not support Linux, clarify this limitation and guide Linux users to appropriate Azure solutions.
GitHub Create Pull Request
Backup Restore VMs by using the Azure portal using Azure Backup ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific examples, links, and terminology are frequently presented before or instead of Linux equivalents. PowerShell is referenced as the primary automation tool for VM creation and disk restore, with no equivalent Bash or Azure CLI examples. Many guidance links and scenarios point to Windows documentation or use Windows-centric terminology (e.g., Hybrid Use Benefit, domain controller restore, NSG examples, and references to RDP and CMD commands). Linux-specific restore scenarios are only briefly mentioned, and there are no step-by-step Linux restore examples or references to Linux tools (such as SSH, cloud-init, or Azure CLI) in the main restore workflows.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows examples, especially for disk restore, VM creation, and post-restore steps.
  • Include Azure CLI and Bash script examples for all automation steps currently described with PowerShell.
  • Add links to Linux documentation (e.g., restoring Linux VMs, troubleshooting Linux VM restores, managing SSH keys) wherever Windows documentation is referenced.
  • Explicitly mention Linux restore considerations in all relevant scenarios (e.g., network configuration, managed identities, availability sets, cloud-init password resets).
  • Ensure parity in screenshots and UI walkthroughs by including examples with Linux VMs.
  • Clarify when guidance applies to both Windows and Linux, and avoid using Windows terminology as the default (e.g., RDP, CMD, domain controllers) without Linux equivalents.
GitHub Create Pull Request
Backup Create backup policies via REST API in Azure Backup ...up/backup-azure-arm-userestapi-createorupdatepolicy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_timezones ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits subtle Windows bias primarily through the use of Windows-centric time zones (e.g., 'Pacific Standard Time') in examples and the ordering of examples, which consistently start with Azure VM (typically Windows workloads) before Linux or cross-platform workloads. There is no explicit mention of Linux-specific patterns, tools, or time zone formats, nor are there examples tailored to Linux VMs or Linux-specific backup scenarios. The documentation does not provide parity for Linux users in terms of examples, time zone handling, or guidance for Linux-centric environments.
Recommendations
  • Include explicit examples for Linux VMs, such as Ubuntu or CentOS, demonstrating backup policy creation for Linux workloads.
  • Use cross-platform or IANA time zone identifiers (e.g., 'America/Los_Angeles') in examples, or clarify how to specify time zones for Linux environments.
  • Add notes or sections highlighting any differences or considerations when backing up Linux VMs versus Windows VMs.
  • Ensure that examples and guidance are balanced between Windows and Linux, possibly by alternating the order or providing tabs for both OS types.
  • Reference Linux command-line tools (e.g., curl, jq) for REST API calls alongside any PowerShell or Windows tools, if mentioned elsewhere.
GitHub Create Pull Request
Backup Back Up Azure VMs in a Recovery Services Vault ...b/main/articles/backup/backup-azure-arm-vms-prepare.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed, step-by-step instructions for installing the VM agent on Windows, including download links, file paths, and verification steps. In contrast, the Linux instructions are brief, generic, and lack concrete examples or commands. Windows-specific tools and patterns (MSI installer, file paths, right-click actions) are mentioned exclusively, while Linux equivalents (e.g., package manager commands, verification steps) are omitted. The Windows instructions are presented first, reinforcing a Windows-first bias.
Recommendations
  • Provide explicit Linux installation commands (e.g., apt-get, yum, zypper) for installing/updating the Azure Linux agent.
  • Include Linux-specific verification steps, such as checking agent version via command line (e.g., waagent --version) and relevant file paths.
  • Present Windows and Linux instructions with equal detail and in parallel, rather than listing Windows first.
  • Mention Linux troubleshooting steps or links alongside Windows troubleshooting.
  • Avoid Windows-centric language (e.g., 'right-click', 'MSI installer') without Linux equivalents.
GitHub Create Pull Request
Backup Back up an Exchange server via System Center DPM ...articles/backup/backup-azure-backup-exchange-server.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation exclusively describes backup procedures for Microsoft Exchange using System Center DPM, a Windows-only tool, with all examples and steps referencing Windows environments, tools, and paths. There is no mention of Linux equivalents, alternative cross-platform solutions, or parity for Linux-based Exchange deployments. PowerShell is referenced in related content, reinforcing the Windows-centric approach.
Recommendations
  • Clarify early in the documentation that System Center DPM is a Windows-only solution and suggest alternatives for Linux environments.
  • Provide guidance or links for backing up Exchange on Linux (if supported) or for Linux-based mail servers (e.g., Postfix, Dovecot) using Azure Backup or other Microsoft-supported tools.
  • Include examples or references for cross-platform backup tools where possible.
  • Balance related content by including automation or backup management examples for Linux (e.g., using Bash scripts or Azure CLI).
GitHub Create Pull Request
Backup Back up VMware VMs using Azure Backup Server ...n/articles/backup/backup-azure-backup-server-vmware.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions assume the use of Windows tools (e.g., Registry Editor, Certificate Import Wizard, PowerShell scripts), and there are no Linux equivalents or cross-platform alternatives provided. The documentation presumes Azure Backup Server is installed on Windows and omits any guidance for Linux-based administration or scripting. PowerShell is used exclusively for scripting tasks, and Windows registry modifications are required for configuration. Linux users are not addressed, and no Bash or Linux-native instructions are present.
Recommendations
  • Add instructions and examples for Linux environments, such as how to import certificates using Linux tools (e.g., openssl, update-ca-certificates).
  • Provide Bash script equivalents for PowerShell scripts, or clarify if the functionality is unavailable on Linux.
  • Clarify platform requirements early in the documentation (e.g., if MABS is Windows-only, state this explicitly).
  • Where registry edits are required, suggest alternative configuration methods for Linux (if supported), or note platform limitations.
  • Include notes or sections for Linux administrators, even if only to state that certain features/tools are not available.
  • If possible, provide cross-platform CLI examples (e.g., using Azure CLI, REST API) instead of only Windows GUI or PowerShell.
GitHub Create Pull Request
Backup Back up a SharePoint farm to Azure with DPM ...main/articles/backup/backup-azure-backup-sharepoint.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows-centric tools and workflows, specifically System Center Data Protection Manager (DPM), which is a Windows-only product. All examples, instructions, and screenshots reference DPM and Windows interfaces, with no mention of Linux equivalents or cross-platform alternatives. The only automation reference is to PowerShell, a Windows-first scripting language, and there are no Linux command-line or tool examples provided.
Recommendations
  • Explicitly state DPM's platform limitations and mention if Linux support is unavailable.
  • Provide alternative solutions or workflows for Linux-based SharePoint deployments, if supported.
  • Include examples using cross-platform tools or Azure-native backup solutions that work on both Windows and Linux.
  • Offer parity in automation examples, such as Bash scripts or Azure CLI commands, alongside PowerShell.
  • Clarify prerequisites and supported environments, highlighting any OS-specific requirements.
GitHub Create Pull Request
Backup Offline seeding workflow for DPM and MABS using customer-owned disks with Azure Import/Export - Azure Backup ...les/backup/backup-azure-backup-server-import-export.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented towards Windows environments, specifically System Center Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS), both of which are Windows-only products. All examples, prerequisites, and tooling references (such as AzureOfflineBackupDiskPrep.exe, Azure PowerShell, and requirements for Microsoft Edge/Internet Explorer) are Windows-specific. There is no mention of Linux equivalents, nor are there instructions or examples for performing offline seeding from Linux systems. The workflow assumes the use of Windows servers and tools throughout.
Recommendations
  • Explicitly state that DPM and MABS are Windows-only, and clarify Linux support status at the top of the article.
  • If Azure Backup supports offline seeding from Linux systems (e.g., via MARS agent or other means), provide equivalent Linux workflows, including supported tools and commands.
  • Include examples using Linux-compatible utilities (such as azcopy, Azure CLI, or shell scripts) for disk preparation and import job creation.
  • Mention browser requirements for Linux users (e.g., Chrome, Firefox) if applicable.
  • Reference documentation or workflows for Linux-based backup solutions where possible, or provide links to relevant Linux documentation.
GitHub Create Pull Request
Backup Back up a SharePoint farm to Azure with MABS ...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All instructions, tools, and examples assume the use of Windows servers, Windows command-line tools (CMD, Registry Editor), and Windows-specific paths and permissions. There are no references to Linux equivalents, nor any guidance for SharePoint deployments on non-Windows platforms. The use of tools like ConfigureSharePoint.exe, Registry Editor, and explicit references to Windows groups and permissions further reinforce the Windows-centric approach.
Recommendations
  • Clarify early in the documentation that MABS and SharePoint are Windows-only products, if that is the case. If Linux support is possible, provide explicit guidance for Linux environments.
  • If any part of the backup or restore process can be performed from Linux (e.g., Azure Backup operations, monitoring, or scripting), include Linux shell examples and instructions.
  • Mention cross-platform alternatives or limitations, and provide links to documentation for Linux-based backup solutions if SharePoint or MABS is not supported on Linux.
  • Where possible, abstract instructions to be OS-agnostic (e.g., use generic file paths, avoid registry-specific steps, provide both CMD and Bash equivalents for commands).
  • Add a section on prerequisites and limitations that clearly states OS requirements and whether Linux is supported or not.
GitHub Create Pull Request
Backup Create Backup Policies for PostgreSQL Databases by Using the Data Protection REST API ...rotection-use-rest-api-create-update-postgresql-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by repeatedly referencing PowerShell objects as the default or primary method for describing backup policy configuration, without providing equivalent Linux or cross-platform CLI examples. The term 'PowerShell object' is used to describe the policy structure, and no examples are given for Linux shell (bash), Azure CLI, or other non-Windows tooling. This may lead Linux users to feel unsupported or unclear about how to perform the same operations on their platform.
Recommendations
  • Replace or supplement references to 'PowerShell object' with neutral terms like 'policy object' or 'JSON policy definition'.
  • Provide equivalent examples using Azure CLI commands, which are cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that the REST API can be invoked from any platform, and provide sample curl or httpie commands for Linux users.
  • Add a section or note highlighting Linux and macOS compatibility, and link to platform-agnostic tooling.
  • Avoid implying that PowerShell is the default or only supported method for interacting with the API.
GitHub Create Pull Request
Backup Overview of Azure Database for PostgreSQL Backup ...es/backup/backup-azure-database-postgresql-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the pgAdmin GUI tool for database management tasks, without mentioning or providing examples for Linux-native or CLI alternatives (such as psql or Azure CLI). Screenshots and instructions are tailored to the Windows/GUI experience, and there is no guidance for users who may prefer or require Linux command-line workflows. The order of presentation and tool selection implicitly prioritizes Windows-centric patterns.
Recommendations
  • Include examples using psql, the standard PostgreSQL CLI tool available on Linux and Windows, for database connection, user creation, and privilege assignment.
  • Provide Azure CLI or Azure PowerShell command examples for resource and permission management, with explicit mention of cross-platform compatibility.
  • Add instructions and screenshots for connecting to Azure Database for PostgreSQL from Linux environments, including firewall rule configuration and credential management.
  • Reference Linux package managers (apt, yum) for installing PostgreSQL tools, alongside the pgAdmin download link.
  • Clearly state that all procedures can be performed on both Windows and Linux, and highlight any platform-specific differences where relevant.
GitHub Create Pull Request
Backup Back Up Azure Database for PostgreSQL by Using the Azure Portal ...in/articles/backup/backup-azure-database-postgresql.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas: environment variable setup is described exclusively using Windows Control Panel and System Properties, with screenshots and instructions tailored to Windows users. The PowerShell script is presented as the primary method for granting database privileges, with alternatives (pgAdmin, PSQL) mentioned only briefly and without example commands. There are no explicit Linux or macOS instructions or screenshots for environment variable configuration or script execution, and Windows tools/patterns (e.g., Notepad, Control Panel) are referenced without Linux equivalents.
Recommendations
  • Add step-by-step instructions and screenshots for configuring environment variables on Linux and macOS (e.g., using ~/.bashrc or ~/.profile).
  • Provide example commands for running the PowerShell script on Linux/macOS (using PowerShell Core), or offer equivalent Bash/PSQL scripts.
  • Include Linux/macOS alternatives for editing connection strings (e.g., using nano, vim, or gedit instead of Notepad).
  • Mention and demonstrate how to use pgAdmin and PSQL for privilege assignment with concrete example commands.
  • Ensure that CLI and REST API documentation links are given equal prominence to PowerShell, and consider including direct examples inline.
  • Review screenshots and UI references to ensure cross-platform applicability, or clarify when instructions are OS-specific.
GitHub Create Pull Request
Backup Back up blobs in a storage account using Azure Data Protection REST API. ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily by mentioning Windows-centric tools (Azure PowerShell) before Linux-friendly alternatives (Azure CLI), and by referencing PowerShell in related content without providing equivalent Linux shell or CLI examples. The main workflow is described using REST API calls, which are cross-platform, but there is a lack of explicit Linux command-line examples (e.g., curl, az CLI) and no mention of Linux-specific patterns or tools. The only tool-specific references are to PowerShell and the Azure portal, with CLI mentioned last in related content. There are no examples showing how to perform these REST API operations from a Linux shell environment.
Recommendations
  • Add explicit examples using Azure CLI for all major operations (assigning permissions, configuring backup, validating requests, deleting backup instances).
  • Provide sample curl commands for REST API calls to demonstrate usage from a Linux shell.
  • When listing tools or methods (e.g., 'Azure portal, PowerShell, or REST API'), mention Azure CLI alongside PowerShell, and alternate the order to avoid Windows-first bias.
  • Include a section or note clarifying that all REST API operations can be performed from any OS, and provide guidance for Linux/macOS users.
  • In related content, ensure parity by linking to both PowerShell and CLI guides, and consider providing Bash script examples for common tasks.
GitHub Create Pull Request
Backup Delete a Microsoft Azure Recovery Services vault ...blob/main/articles/backup/backup-azure-delete-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by prioritizing PowerShell and Windows-specific tools (such as MARS, MABS, DPM, and ARMClient via Chocolatey), providing detailed instructions and examples for Windows environments, and omitting equivalent Linux instructions or alternatives. PowerShell is presented as the primary automation method, and ARMClient installation is described only for Windows (via Chocolatey). There is no mention of Bash, Linux-native CLI usage, or cross-platform alternatives for on-premises scenarios.
Recommendations
  • Provide Bash and Linux CLI examples alongside PowerShell, especially for automation and scripting tasks.
  • Document ARMClient installation and usage for Linux (e.g., via npm or direct download), not just via Chocolatey.
  • Clarify which steps and tools are cross-platform, and explicitly note any Windows-only limitations.
  • Include guidance for managing on-premises backup items from Linux servers, or note if such scenarios are unsupported.
  • Where possible, reference Azure CLI as a cross-platform alternative to PowerShell for supported operations.
  • Add parity in screenshots and instructions for Linux environments (e.g., terminal commands, file paths).
GitHub Create Pull Request
Backup Troubleshoot encrypted Azure VM backup errors ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the only command-line automation example for configuring permissions, without mentioning Linux equivalents such as Azure CLI or Bash. No Linux-specific troubleshooting steps, tools, or examples are provided, and Windows-centric terminology (PowerShell) appears before any cross-platform alternatives.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for all automation steps, especially for permission configuration.
  • Explicitly mention that troubleshooting steps apply to both Windows and Linux VMs, or provide separate guidance if there are platform-specific differences.
  • Add references to Linux tools and workflows where relevant (e.g., using SSH, Linux disk management commands).
  • Ensure that links and instructions for restoring or backing up VMs include both Windows and Linux scenarios.
GitHub Create Pull Request
Backup Prepare the DPM server to back up workloads .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily oriented toward Windows environments, specifically System Center DPM, which is a Windows-only backup solution. All examples, prerequisites, and instructions reference Windows tools (PowerShell, .NET Framework, MARSAgentInstaller.exe), and there is no mention of Linux equivalents or cross-platform considerations. The documentation assumes the administrator is working on Windows, and does not provide guidance for Linux-based workloads or backup agents.
Recommendations
  • Clarify early in the documentation that DPM is a Windows-only solution, and provide links or references to Azure Backup solutions for Linux workloads.
  • Where possible, mention Azure Backup agents or procedures for Linux servers, even if only to direct users to relevant documentation.
  • If PowerShell or Windows-specific tools are required, note their lack of cross-platform support and suggest alternatives for Linux (e.g., Azure CLI, REST API).
  • Add a section comparing backup strategies for Windows and Linux workloads in Azure, and how to achieve parity in protection and management.
  • Ensure troubleshooting and prerequisites sections mention Linux considerations, or explicitly state their scope is limited to Windows/DPM.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup Server ...main/articles/backup/backup-azure-mabs-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation for Azure Backup Server troubleshooting is heavily Windows-centric. All examples, folder paths, registry keys, and troubleshooting steps reference Windows tools, services, and conventions (e.g., Service console, registry edits, Windows Server Backup, csc.exe, DPM, MARS agent, Internet Explorer, psexec). There are no Linux-specific instructions, examples, or parity for troubleshooting on Linux systems. The documentation assumes the administrator is working in a Windows environment and does not mention or support Linux-based deployments.
Recommendations
  • Add troubleshooting steps and examples for Linux-based backup servers, if supported.
  • Include Linux equivalents for antivirus exclusions, service management, and folder paths.
  • Provide command-line examples using bash or shell scripts for Linux, alongside Windows CMD/PowerShell.
  • Mention Linux tools and patterns (e.g., systemctl, journalctl, /etc directories) where relevant.
  • Clarify platform support at the beginning of the documentation and explicitly state if Linux is not supported.
  • If Azure Backup Server is Windows-only, add a note explaining this and direct Linux users to appropriate Azure backup solutions.
GitHub Create Pull Request
Backup Troubleshoot the Azure Backup agent ...main/articles/backup/backup-azure-mars-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily focused on Windows environments, with all troubleshooting steps, examples, and tool references tailored to Windows systems. There are no Linux-specific instructions, examples, or references to Linux tools. Windows tools (MMC console, Task Scheduler, Internet Explorer, Device Manager, Registry Editor, vssadmin, PowerShell) are mentioned exclusively and repeatedly, and all paths, error codes, and procedures assume a Windows OS. There is no mention of Linux equivalents or guidance for users running Azure Backup agent on Linux systems.
Recommendations
  • Add troubleshooting steps and examples for Linux environments where Azure Backup agent is supported.
  • Include Linux-specific commands and tools (e.g., systemctl, journalctl, cron, bash scripts) alongside Windows instructions.
  • Provide parity in error messages and their resolution for Linux systems.
  • Reference Linux file paths and configuration locations in addition to Windows paths.
  • Clarify in the introduction which OSes are supported and, if only Windows is supported, state this explicitly to avoid confusion.
  • If Azure Backup agent is Windows-only, provide links or guidance for Linux backup solutions in Azure.
GitHub Create Pull Request
Backup How to move Azure Backup Recovery Services vaults ...es/backup/backup-azure-move-recovery-services-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing PowerShell examples for moving Recovery Services vaults, referencing Windows-specific update instructions before Linux equivalents, and omitting Linux-specific CLI or shell script examples. While Azure CLI is mentioned, the scripting guidance and troubleshooting steps prioritize Windows tools and patterns, and do not offer parity for Linux administrators.
Recommendations
  • Provide Bash or shell script examples for moving Recovery Services vaults, especially for Linux users.
  • Include Linux-specific instructions and troubleshooting steps alongside Windows guidance (e.g., how to update certificates on Linux with concrete commands).
  • Ensure that CLI examples are given equal prominence to PowerShell, and consider presenting CLI/Bash examples before or alongside PowerShell.
  • Reference cross-platform tools (like Azure CLI) as the primary method, with PowerShell as an alternative, to avoid Windows-first perception.
  • Add explicit notes or sections for Linux administrators, clarifying any differences in process or requirements.
GitHub Create Pull Request
Backup Manage and monitor Azure VM backups ...s/blob/main/articles/backup/backup-azure-manage-vms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways. The detailed instructions for reinstalling the VMSnapshot backup extension are provided first and extensively for Windows, including PowerShell cmdlets, registry edits, and use of Windows-specific tools (services.msc, regedit, command prompt). In contrast, the Linux section is much shorter, lacks step-by-step guidance, and omits example commands for common operations (e.g., deleting directories, restarting agents). Throughout the page, examples and screenshots are Windows-centric, with little parity for Linux users.
Recommendations
  • Provide Linux instructions with equal detail and step-by-step guidance, including example shell commands for deleting extension directories, restarting the waagent, and verifying extension status.
  • Include screenshots or terminal output examples for Linux operations where appropriate.
  • Present Windows and Linux instructions side-by-side or in parallel sections to avoid implicit prioritization of Windows.
  • Where PowerShell or Windows tools are mentioned, also mention equivalent Linux commands and tools (e.g., Azure CLI, shell commands).
  • Clarify any differences in backup management workflows between Windows and Linux VMs, and ensure both are covered in all relevant sections.
GitHub Create Pull Request
Backup Use Azure Backup Server to back up workloads ...articles/backup/backup-azure-microsoft-azure-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. All installation, configuration, and operational instructions are exclusively for Windows Server environments, with no mention of Linux support or examples. Windows-specific tools (e.g., PowerShell cmdlets, registry edits, Windows Server Deduplication) are referenced throughout, and the only supported platforms listed are Windows Server editions. There are no Linux equivalents, nor any guidance for deploying or managing Azure Backup Server on Linux systems.
Recommendations
  • Explicitly state platform limitations early in the document (e.g., 'Azure Backup Server is only supported on Windows Server').
  • If Linux support is planned or available, add parallel instructions/examples for Linux environments.
  • Where possible, mention alternatives for Linux users (e.g., Azure Backup agent for Linux, or other backup solutions).
  • Include a comparison table of supported platforms and features for Windows and Linux.
  • Avoid assuming Windows-only environments in introductory and summary sections.
  • If PowerShell is referenced, note whether cross-platform PowerShell Core is supported or provide Bash/CLI alternatives for Linux.
  • Clarify whether any components (e.g., SQL Server, DPM) can be run on Linux, or provide links to Linux-specific backup documentation.
GitHub Create Pull Request
Backup Troubleshoot monitoring issues for Azure Backup ...n/articles/backup/backup-azure-monitor-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (Task Manager, Control Panel), Windows-specific processes and file paths, and omitting any mention of Linux equivalents or troubleshooting steps for Linux-based Azure Backup agents.
Recommendations
  • Add troubleshooting steps for Linux environments, such as using 'ps', 'systemctl', or 'journalctl' to check and manage the agent process.
  • Include Linux file path examples for agent logs (e.g., /var/lib/azurebackup/...).
  • Mention Linux service management commands and tools alongside Windows instructions.
  • Clarify whether the guidance applies only to Windows or provide parity for Linux users.
GitHub Create Pull Request
Backup Overview of Recovery Services vaults ...ackup/backup-azure-recovery-services-vault-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-centric backup tools (System Center DPM, Windows Server, Azure Backup Server) before or instead of Linux equivalents. Examples and links for backing up Windows Server are provided, but there are no equivalent Linux server backup examples or references to Linux-native backup tools. The documentation lists Windows workloads and tools first and does not provide parity for Linux server backup scenarios.
Recommendations
  • Include explicit examples and links for backing up Linux servers, not just Linux VMs.
  • Mention Linux-native backup tools or workflows supported by Recovery Services vaults, if available.
  • Ensure that references to backup scenarios and tools are balanced between Windows and Linux, listing both platforms equally.
  • Add a section or FAQ entry addressing Linux server backup support and best practices.
  • Provide step-by-step guides or links for Linux server backup using Recovery Services vaults, similar to the Windows Server example.
GitHub Create Pull Request
Backup Recover files and folders from Azure VM backup .../articles/backup/backup-azure-restore-files-from-vm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows examples, tools, and troubleshooting steps are often presented before their Linux equivalents, and Windows-specific registry edits and GUI tools (e.g., File Explorer) are described in detail. PowerShell is referenced in the 'Next steps' section before Azure CLI. Linux instructions are present and reasonably detailed, but Windows is generally prioritized in ordering and depth.
Recommendations
  • Alternate the order of Windows and Linux instructions throughout the documentation, or present them in parallel sections to avoid implicit prioritization.
  • Provide equally detailed troubleshooting steps for Linux as are given for Windows (e.g., registry edits for Windows are described in detail; ensure Linux config changes are similarly explained).
  • Include Linux-specific tools and file browsing methods (e.g., mention using Nautilus, Dolphin, or command-line tools for browsing recovered files, not just File Explorer for Windows).
  • In the 'Next steps' section, list Azure CLI and Linux automation options before or alongside PowerShell to avoid reinforcing Windows-first patterns.
  • Where screenshots or images are used, ensure parity by including Linux equivalents, not just Windows GUI images.
  • Explicitly mention Linux desktop environments and file managers where relevant, to help Linux users navigate recovered files.
GitHub Create Pull Request
Backup Restore System State to a Windows Server ...n/articles/backup/backup-azure-restore-system-state.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_only ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is exclusively focused on Windows Server system state restore, using only Windows-specific tools (MARS agent, Windows Server Backup, wbadmin, Win RE) and providing no mention or examples for Linux systems. All instructions, screenshots, and command-line examples are Windows-centric, with no Linux parity or alternatives discussed.
Recommendations
  • Clarify in the introduction that the procedure is Windows-specific, and provide links to equivalent Linux backup/restore documentation if available.
  • If Azure Backup supports Linux system state or similar functionality, add parallel sections for Linux, including examples using Linux tools (e.g., rsync, tar, Azure CLI, etc.).
  • Where possible, mention cross-platform backup/restore strategies and tools, or provide guidance for Linux administrators on how to achieve similar outcomes.
  • Ensure future documentation on backup and restore covers both Windows and Linux scenarios, or clearly scopes the content as Windows-only to avoid confusion.
GitHub Create Pull Request
Backup Private Endpoints Overview: Version 2 Experience ...icles/backup/backup-azure-private-endpoints-concept.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Windows-specific backup tools (MARS agent, DPM, MABS) and scenarios, with no mention of Linux equivalents or examples. All workload and agent references are for Windows environments, and there are no instructions, recommendations, or clarifications for Linux-based backup agents or VM workloads. The documentation assumes the use of Microsoft-centric backup solutions and does not address how private endpoints interact with Linux backup scenarios.
Recommendations
  • Include examples and scenarios for Linux-based Azure VM backups, such as using Azure Backup for Linux VMs and any Linux-specific agents or extensions.
  • Clarify whether private endpoints support Linux workloads and describe any differences or considerations for Linux environments.
  • Mention Linux-compatible backup tools or third-party solutions where applicable, and provide guidance for configuring DNS and network connectivity for Linux VMs.
  • Add explicit instructions or notes for Linux users, including any required ports, FQDNs, or configuration steps that differ from Windows.
  • Ensure parity in documentation by listing both Windows and Linux scenarios in tables and recommendations.
GitHub Create Pull Request
Backup Security features that protect hybrid backups .../main/articles/backup/backup-azure-security-feature.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is heavily focused on Windows-centric backup tools (MARS, DPM, MABS) and provides examples, instructions, and troubleshooting steps exclusively for these Windows-based solutions. There is no mention of Linux backup agents, Linux-specific recovery procedures, or parity for Linux workloads. PowerShell commands and Windows UI screenshots are used, and Linux equivalents or cross-platform alternatives are absent.
Recommendations
  • Include information about Azure Backup support for Linux workloads, if available, and document any Linux agents or integration methods.
  • Provide Linux-specific examples for enabling security features, recovering deleted backup data, and troubleshooting errors.
  • Add CLI-based instructions (e.g., Azure CLI, Bash) alongside PowerShell and Windows UI steps.
  • Mention Linux backup tools or third-party solutions that integrate with Azure Backup, if applicable.
  • Ensure that parity in security features and immutability support for Linux workloads is clearly documented.
  • Add screenshots or walkthroughs for Linux environments where relevant.
GitHub Create Pull Request
Backup Troubleshoot System Center Data Protection Manager .../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively references Windows-centric tools and patterns, such as Data Protection Manager (DPM), Azure Backup agent, MARS agent, and command-line instructions using 'net stop/start dpmra'. There are no examples, troubleshooting steps, or references for Linux environments or equivalent Linux backup solutions. The guidance assumes the reader is operating in a Windows ecosystem, with no mention of Linux commands, services, or compatibility.
Recommendations
  • Include troubleshooting steps and examples for Linux-based backup solutions, if supported.
  • Provide equivalent Linux commands or service management instructions (e.g., systemctl) alongside Windows command prompt examples.
  • Clarify platform support and limitations at the beginning of the documentation.
  • Mention or link to Linux-compatible backup tools or agents, if available.
  • Ensure parity in error resolution steps for both Windows and Linux environments.
GitHub Create Pull Request
Backup Troubleshoot System State Backup ...icles/backup/backup-azure-system-state-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Windows environments, specifically on-premises Windows servers. All troubleshooting steps, prerequisites, and examples use Windows-specific tools (PowerShell, Server Manager, Windows Server Backup, wbadmin, VSS, MARS agent) with no mention of Linux equivalents or cross-platform scenarios. The documentation assumes the user is operating in a Windows-only context and does not provide guidance for Linux systems or alternative backup tools.
Recommendations
  • Clearly state in the introduction that System State Backup is a Windows-only feature and provide links to Linux backup documentation for parity.
  • If Azure Backup supports Linux in other contexts, add a section or cross-reference for troubleshooting Linux backup issues.
  • Where possible, mention Linux backup tools (e.g., rsync, tar, Azure Backup for Linux) and provide guidance or links for similar troubleshooting steps.
  • Ensure that examples and troubleshooting steps are balanced or, if not applicable, explicitly state platform limitations to avoid confusion.
  • Consider adding a comparison table of backup features and troubleshooting steps for Windows vs. Linux environments.
GitHub Create Pull Request
Backup Back up SQL Server databases to Azure ...blob/main/articles/backup/backup-azure-sql-database.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias. All examples, instructions, and tooling references are exclusively for Windows environments (e.g., NT SERVICE accounts, SSMS, PowerShell, Windows file paths, Task Manager, SMB shares). There is no mention of Linux-based SQL Server VMs, nor are Linux equivalents for permissions, file paths, or automation provided. The documentation assumes the use of Windows-specific features and tools throughout.
Recommendations
  • Add explicit guidance for SQL Server running on Linux VMs, including how to install and configure the Azure Backup extension in Linux environments.
  • Provide Linux-specific instructions for setting up permissions, such as using systemd service accounts or local users, and configuring SQL Server authentication on Linux.
  • Include automation examples using Bash scripts or sqlcmd on Linux, rather than only PowerShell.
  • Show Linux file path conventions (e.g., /var/opt/mssql/backups) alongside Windows paths.
  • Describe how to manage local backup folders and permissions using Linux tools (chmod, chown) and explain how to mount network shares (e.g., using CIFS).
  • Clarify any differences or limitations in Azure Backup support for SQL Server on Linux VMs, and link to relevant support matrix sections.
GitHub Create Pull Request
Backup Restore SQL server databases in Azure VMs using Azure Backup via CLI ...b/main/articles/backup/backup-azure-sql-restore-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing SQL Server (a Microsoft/Windows-centric database), using Windows-style resource and naming conventions (e.g., MSSQLSERVER, testSQLVM), and omitting any mention or example of restoring non-Windows SQL workloads (such as Linux-based SQL Server or other database engines). All examples and terminology assume a Windows VM and SQL Server instance, with no guidance for Linux VMs or alternative database platforms.
Recommendations
  • Add explicit guidance and examples for restoring SQL Server databases running on Linux Azure VMs, including any differences in CLI usage, file paths, or prerequisites.
  • Clarify whether the documented process applies to both Windows and Linux SQL Server deployments, and note any limitations or required steps for Linux.
  • Include examples using Linux-style file paths and VM naming conventions to demonstrate parity.
  • Mention support (or lack thereof) for other database engines (e.g., PostgreSQL, MySQL) if applicable, or link to relevant documentation.
  • Where possible, use neutral terminology (e.g., 'SQL VM' instead of 'testSQLVM', '/home/sql/restoreasfiles' instead of Windows paths) and clarify platform-specific requirements.
GitHub Create Pull Request
Backup Back up Windows system state to Azure using Azure Backup ...blob/main/articles/backup/backup-azure-system-state.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is exclusively focused on backing up Windows Server system state to Azure using the Microsoft Azure Recovery Services (MARS) Agent, a Windows-only tool. All instructions, screenshots, and examples are tailored for Windows environments, with no mention of Linux equivalents, Linux system state backup, or cross-platform alternatives. The documentation assumes the user is operating on Windows and does not provide parity for Linux users.
Recommendations
  • Add a section or a separate article for backing up Linux system state or equivalent data to Azure, using supported tools (e.g., Azure Backup for Linux, Azure CLI, or third-party solutions).
  • Include cross-platform backup strategies and mention Linux support (if available) early in the documentation, not just Windows.
  • If system state backup is not supported for Linux, explicitly state this limitation and provide guidance on alternative backup approaches for Linux systems.
  • Provide links to Linux backup documentation and tools where relevant.
  • Ensure that future documentation covers both Windows and Linux scenarios, or clearly scopes the content as Windows-only in the title and introduction.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup failures caused by agent or extension issues ...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: Windows troubleshooting steps and tools (e.g., services.msc, Event Viewer, Control Panel, .NET, Visual C++ Redistributable) are described in detail, often with screenshots, while Linux equivalents are less detailed or omitted. Windows is frequently mentioned first in lists and instructions, and PowerShell is referenced for operations without equivalent Bash/CLI commands for Linux. Some troubleshooting steps (e.g., antivirus exclusions, COM+/MSDTC, VSS writer) are Windows-specific, with no Linux alternatives or explanations. Linux instructions are present but less comprehensive, and examples for Linux (e.g., log locations, service management) are brief and lack visual aids.
Recommendations
  • Provide Linux troubleshooting steps with equal detail, including screenshots or terminal output where appropriate.
  • Include Linux equivalents for all Windows tools mentioned (e.g., show how to check agent status with systemctl, view logs with journalctl or tail, manage packages, etc.).
  • When listing steps or causes, alternate or group by OS rather than always listing Windows first.
  • Add Bash/CLI commands for operations currently only described with PowerShell (e.g., cancelling backup jobs, configuring static IPs).
  • For Windows-specific features (e.g., VSS, COM+/MSDTC, Event Viewer), clarify their Linux equivalents or note if not applicable.
  • Expand Linux agent troubleshooting to cover common issues (e.g., permissions, SELinux/AppArmor, dependency installation) and provide links to relevant Linux documentation.
  • Ensure antivirus and application control troubleshooting covers common Linux solutions (e.g., ClamAV, SELinux policies) where applicable.
GitHub Create Pull Request
Backup Troubleshoot slow backup of files and folders ...ackup-azure-troubleshoot-slow-backup-performance-issue.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. All troubleshooting steps, examples, and tool recommendations are specific to Windows environments. Only Windows tools (such as Performance Monitor) are mentioned, and all file paths, agent references, and troubleshooting guidance assume the use of Windows. There are no Linux equivalents, examples, or guidance for users running Azure Backup on Linux systems.
Recommendations
  • Add troubleshooting steps and examples for Linux environments, including common performance bottlenecks and how to diagnose them.
  • Mention and provide guidance for Linux monitoring tools (e.g., top, iostat, vmstat, sar) alongside Windows Performance Monitor.
  • Include Linux-specific file paths and log locations for the Azure Backup agent.
  • Clarify which recommendations apply to both Windows and Linux, and explicitly call out any platform-specific differences.
  • Provide parity in antivirus and backup process troubleshooting for Linux systems, including common interfering processes and exclusion rules.
GitHub Create Pull Request
Backup Troubleshoot Azure VM file recovery ...s/backup/backup-azure-vm-file-recovery-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows troubleshooting steps and tools (e.g., Server Manager, Disk Management, ISCSI initiator Properties) are described in detail with screenshots and step-by-step instructions, while Linux troubleshooting is often referenced via links to other documentation or summarized briefly. Some troubleshooting sections present Windows solutions first or exclusively, with Linux guidance provided as a secondary note or omitted entirely. Linux examples are less detailed, and Linux-specific errors are sometimes addressed only by referencing external guides.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux troubleshooting, including screenshots of relevant Linux tools (e.g., GNOME Disks, terminal commands for mounting/unmounting, LVM/RAID management).
  • Include Linux command-line equivalents for all Windows GUI actions (e.g., mounting disks, changing drive letters/paths, checking disk status).
  • Present Windows and Linux solutions in parallel, rather than listing Windows first or exclusively.
  • Expand Linux troubleshooting sections to cover common scenarios (e.g., handling encrypted volumes, manual mounting, dealing with raw partitions) with concrete examples.
  • Avoid referencing Linux solutions only via external links; summarize key steps directly in the documentation.
  • Add troubleshooting for Linux-specific features (e.g., SELinux, file permissions, systemd services) where relevant.
GitHub Create Pull Request
Backup About agentless multi-disk crash-consistent backup for Azure Virtual Machines by using Azure Backup ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by mentioning Windows-specific tools (VSS) before Linux equivalents (fsfreeze) when discussing backup consistency mechanisms. References to VM Agent and snapshot extension link only to Windows documentation, omitting direct Linux equivalents or links. There are no Linux-specific examples, commands, or links to Linux agent documentation, and Linux patterns (such as pre/post scripts) are mentioned only in passing, without detail.
Recommendations
  • Provide equal coverage of Linux backup mechanisms, including direct links to Linux VM Agent and snapshot extension documentation.
  • Include Linux-specific examples or scenarios, such as how crash-consistent backup interacts with Linux filesystems and typical Linux workloads.
  • Mention Linux tools (e.g., fsfreeze) alongside Windows tools (VSS), and avoid listing Windows tools first.
  • Clarify Linux support and limitations for agentless backups, including any differences in implementation or recommended practices.
  • Add references to Linux documentation and best practices for backup consistency.
GitHub Create Pull Request
Backup Move VM backup - standard to enhanced policy in Azure Backup ...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and CLI versions for trusted launch support before mentioning REST API, and by not providing any Linux-specific examples or guidance. All command-line references are generic or Windows-centric (PowerShell), and there is no mention of Linux shell usage, nor are there screenshots or instructions tailored for Linux users. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux-specific considerations or workflows.
Recommendations
  • Include explicit Linux shell (bash) examples for CLI commands, showing usage in Linux environments.
  • Add notes or sections addressing Linux-specific considerations, such as differences in Azure CLI installation or authentication on Linux.
  • Provide parity in screenshots or instructions for Linux users, such as terminal examples or references to Linux desktop environments.
  • Mention Linux tools (e.g., shell scripting, cron integration) where relevant, alongside PowerShell.
  • Ensure REST API usage examples are platform-neutral and provide sample requests using curl or similar Linux tools.
GitHub Create Pull Request
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is the only command-line example provided for identifying a VM's associated key vault, with no equivalent Linux (bash/Azure CLI) example. Windows tools and terminology (such as BitLocker) are mentioned before Linux equivalents (dm-crypt), and Windows is often referenced first in lists and explanations. There are no explicit Linux command examples or instructions, and the documentation assumes familiarity with Windows-centric workflows.
Recommendations
  • Provide Azure CLI and/or bash examples alongside PowerShell commands, especially for tasks like identifying key vault associations.
  • Ensure that Linux-specific encryption tools and workflows (e.g., dm-crypt) are described with equal prominence and detail as Windows tools (BitLocker).
  • Alternate the order of Windows and Linux references in lists and explanations to avoid implicit prioritization.
  • Include screenshots or instructions that are relevant for Linux VMs, such as those created from Linux Marketplace images or with custom Linux configurations.
  • Add troubleshooting and automation guidance for Linux users, including common Linux-specific issues and solutions.
GitHub Create Pull Request
Backup About Azure VM backup .../main/articles/backup/backup-azure-vms-introduction.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows tools (VSS) are mentioned before Linux equivalents, Windows backup mechanisms are described in more detail, and PowerShell is referenced for restore operations without Linux CLI parity. Linux instructions are less detailed, relying on users to create custom scripts, and Linux-specific examples or tools are not provided with the same clarity or prominence.
Recommendations
  • Provide Linux CLI (az CLI, Bash) examples for backup and restore operations alongside PowerShell examples.
  • Describe Linux backup mechanisms (such as fsfreeze) with the same level of detail as VSS for Windows, including troubleshooting and best practices.
  • Include explicit Linux restore instructions and automation options, not just PowerShell.
  • Ensure that Linux tools and patterns are mentioned with equal prominence and before or alongside Windows equivalents.
  • Add sample pre/post script templates for common Linux workloads to help users achieve application consistency.
  • Clarify any differences in backup/restore behavior or limitations between Windows and Linux VMs.
GitHub Create Pull Request
Backup Troubleshoot backup errors with Azure VMs .../main/articles/backup/backup-azure-vms-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: troubleshooting steps and examples frequently reference Windows-specific tools (Event Viewer, Services.msc, Registry Editor, command prompt commands like net start/stop, icacls, msdtc, vssadmin, regedit, MSIEXEC, etc.) and registry modifications. Windows troubleshooting is often described in more detail and appears before Linux equivalents. PowerShell is mentioned as the automation method for VM restore, with no Linux CLI or Azure CLI alternatives. Some error resolutions and examples are exclusively Windows-focused, and Linux guidance is sometimes brief or missing.
Recommendations
  • Provide equivalent Linux troubleshooting steps and examples for each Windows-specific instruction (e.g., show how to check agent status, logs, and services on Linux).
  • Include Azure CLI and Bash examples alongside PowerShell for automation and scripting tasks.
  • Ensure Linux tools (systemctl, journalctl, /var/log, etc.) are referenced where appropriate, especially for agent/service management and log review.
  • Present Windows and Linux instructions in parallel, or clearly separate them under distinct headings, to avoid Windows-first ordering.
  • Expand Linux error handling and configuration guidance to match the detail provided for Windows (e.g., registry changes should have Linux config file or environment variable equivalents if applicable).
  • Add troubleshooting steps for common Linux backup/restore issues, such as SELinux, file system consistency, and agent installation/validation.
  • Where screenshots or examples are Windows-only, add Linux equivalents (e.g., log file output, config file locations).
GitHub Create Pull Request
Backup Overview of Backup center for Azure Backup and Azure Site Recovery ...cs/blob/main/articles/backup/backup-center-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias, primarily through references to PowerShell scripts and Microsoft Database Backup scripts in the Community Hub section. There is no mention of Linux-specific tools, shell scripts, or examples, nor are cross-platform CLI examples highlighted. The documentation does not provide parity for Linux administrators or mention Linux-native backup patterns, despite Azure supporting Linux VMs and workloads.
Recommendations
  • Include sample Bash shell scripts and Linux-native backup automation examples alongside PowerShell scripts.
  • Explicitly mention Azure CLI commands as cross-platform alternatives to PowerShell, and provide examples for both.
  • Reference Linux backup tools and patterns where relevant, especially for scenarios involving Linux VMs.
  • Ensure that documentation for automated deployments and scripting covers both Windows and Linux environments equally.
  • Add a note clarifying that Backup center supports both Windows and Linux workloads, and link to Linux-specific guidance where available.
GitHub Create Pull Request
Backup Use Modern Backup Storage with Azure Backup Server ...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily Windows-centric, with all instructions, screenshots, and tooling focused on Windows Server environments. There are no Linux examples, and the use of Windows-specific tools (Server Manager, PowerShell cmdlets, ReFS filesystem) is pervasive. The documentation assumes the user is operating on Windows and does not mention Linux support or alternatives.
Recommendations
  • Clarify whether Azure Backup Server or Modern Backup Storage is supported on Linux. If not, explicitly state this in the prerequisites.
  • If Linux support exists or is planned, provide equivalent instructions and examples for Linux environments, including CLI commands and supported filesystems.
  • Mention Linux backup solutions or integration points if Azure Backup Server is Windows-only, to help Linux administrators understand their options.
  • Avoid assuming Windows as the default platform; structure documentation to address cross-platform scenarios or highlight platform limitations up front.
  • If PowerShell is used, offer Bash or shell script equivalents for Linux where possible.
GitHub Create Pull Request
Backup Install Azure Backup Server on Azure Stack Hub ...ain/articles/backup/backup-mabs-install-azure-stack.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily oriented toward Windows environments. It exclusively references Windows Server images, Windows file paths (C:\, D:\), Windows domain joining, and Windows-specific tools (PowerShell, .NET Framework, SQL Server, Windows Update). There are no instructions, examples, or notes for Linux-based environments, nor any mention of Linux compatibility or alternatives. All examples and screenshots are Windows-centric, and PowerShell is the only command-line tool referenced.
Recommendations
  • Explicitly state whether Azure Backup Server supports Linux-based VMs or not. If not, clarify this early in the documentation.
  • If Linux support exists, provide equivalent instructions for Linux environments, including prerequisites, installation steps, and command-line examples (e.g., Bash, CLI).
  • Mention Linux-compatible backup solutions or alternatives if Azure Backup Server is Windows-only.
  • Include notes or links for users running non-Windows workloads, clarifying what is and isn't supported.
  • Where possible, provide parity in tooling (e.g., Azure CLI commands for connectivity checks, Linux-based SQL installation guidance).
  • Add a comparison table or section outlining differences between Windows and Linux support for Azure Backup Server.
GitHub Create Pull Request
Backup Azure Instant Restore Capability ...n/articles/backup/backup-instant-restore-capability.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides configuration instructions for Instant Restore using the Azure portal and PowerShell, but does not mention or provide examples for Linux users or CLI tools commonly used on Linux (such as Azure CLI or Bash scripts). The only command-line example is in PowerShell, which is Windows-centric. There is no mention of Linux-specific considerations, nor are Linux-friendly tools or workflows presented alongside or before Windows options.
Recommendations
  • Add equivalent Azure CLI examples for configuring snapshot retention and other Instant Restore operations, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell is available on Linux and macOS, or clarify if the instructions are Windows-only.
  • Provide Bash script examples or reference automation options for Linux environments.
  • Ensure that any tool or workflow mentioned (such as PowerShell) is paired with its Linux-friendly counterpart (such as Azure CLI) and present both options side-by-side.
  • Include a note or section addressing Linux-specific considerations for VM backup and restore operations, if any exist.
GitHub Create Pull Request
Backup Back up files in Azure Stack VMs ...s/backup/backup-mabs-files-applications-azure-stack.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively describes backup and recovery procedures using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions and screenshots are for the Azure Backup Server console, with no mention of Linux tools, command-line alternatives, or cross-platform methods. There are no examples or guidance for Linux VMs, nor are Linux-native backup patterns or tools referenced. The documentation assumes a Windows-centric workflow and environment.
Recommendations
  • Add equivalent instructions for backing up files and applications on Linux-based Azure Stack VMs, including use of Linux-native tools and integration with Azure Backup.
  • Provide command-line examples (e.g., Bash scripts, CLI commands) for Linux environments alongside the GUI-based Windows instructions.
  • Mention and link to documentation for cross-platform backup solutions or third-party tools that support Linux workloads in Azure Stack.
  • Clarify any limitations or requirements for Linux VM backup in Azure Stack, and provide guidance for mixed Windows/Linux environments.
  • Ensure screenshots and step-by-step guides include both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V4 protection matrix .../main/articles/backup/backup-mabs-protection-matrix.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation for Azure Backup Server v4 is heavily focused on Windows workloads, with detailed support matrices and examples for Windows Server, SQL Server, Exchange, SharePoint, and Hyper-V. Windows-specific tools and technologies (NTFS, VSS, Visual C++, Windows Management Framework) are referenced throughout, while Linux support is limited to a single table row describing backup of Linux VMs as guests on Windows-based Hyper-V/VMware hosts. There are no Linux-specific backup scenarios, examples, or instructions, and Linux is only mentioned after all Windows scenarios. Recovery options for Linux are limited compared to Windows (only file-consistent snapshots, no item-level recovery).
Recommendations
  • Add explicit Linux backup scenarios, including direct backup of Linux workloads and filesystems, not only as VMs hosted on Windows.
  • Provide Linux-specific instructions and examples, including supported filesystems, recovery options, and agent installation steps.
  • Mention Linux support earlier in the documentation and in parity with Windows, rather than as an afterthought.
  • Clarify limitations and differences for Linux protection, and offer guidance for Linux administrators.
  • Reference Linux tools and patterns (e.g., ext4, XFS, LVM snapshots) where relevant, not just NTFS/VSS.
  • Include parity in recovery options, such as item-level recovery for Linux files and folders if supported, or document alternatives.
GitHub Create Pull Request
Backup Back up a SharePoint farm on Azure Stack using Microsoft Azure Backup Server .../articles/backup/backup-mabs-sharepoint-azure-stack.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily biased toward Windows environments. All instructions, tools, and examples assume the use of Windows servers, Windows command-line tools (CMD, Registry Editor), and Windows-specific services (VSS Writer, DCOM, NT AUTHORITY\SYSTEM). There is no mention of Linux-based SharePoint deployments, nor any examples or guidance for Linux systems. The documentation exclusively references Windows patterns and tools, and does not provide parity for Linux users.
Recommendations
  • Explicitly state that MABS and SharePoint farm protection are only supported on Windows, if that is the case. If Linux support is possible, add equivalent instructions and examples for Linux environments.
  • Provide a section clarifying platform requirements and limitations, including whether Linux-based SharePoint or SQL Server deployments are supported.
  • If any components (such as Azure Backup Server or SQL Server) can run on Linux, include Linux-specific setup, configuration, and recovery steps.
  • Add notes or links to documentation for Linux backup solutions if MABS is not supported on Linux.
  • Ensure that any command-line instructions, file paths, and registry settings are accompanied by Linux equivalents or a statement of non-applicability.
GitHub Create Pull Request
Backup System state and bare-metal recovery protection for Azure Backup ...in/articles/backup/backup-mabs-system-state-and-bmr.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Windows environments, referencing only Windows Server, Windows Server Backup, WinRE, and PowerShell cmdlets. All workflows, examples, and recovery steps are specific to Windows, with no mention of Linux or cross-platform support. Linux equivalents, tools, or procedures are absent throughout the page.
Recommendations
  • Add explicit statements about Linux support or limitations for Azure Backup Server, clarifying whether Linux system state/BMR is supported.
  • If Linux is supported, provide equivalent workflows, examples, and recovery steps for Linux systems, including relevant tools (e.g., rsync, tar, dd, or native Linux backup utilities).
  • Include Linux command-line examples and configuration file locations alongside Windows/Powershell examples.
  • Mention Linux-specific prerequisites, limitations, and recovery environments (e.g., using a live CD, systemd, or GRUB for recovery).
  • If Azure Backup Server is Windows-only, state this clearly at the beginning to set expectations for cross-platform users.
GitHub Create Pull Request
Backup Manage Backups with Azure role-based access control ...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by referencing Windows-specific backup agents and tools (e.g., Azure Backup agent client UI, System Center Data Protection Manager UI, Azure Backup Server UI) when discussing on-premises backup registration and management. These Windows tools are mentioned exclusively, with no mention of equivalent Linux backup agents or procedures. Additionally, the registration and deletion operations for on-premises resources are explicitly tied to Windows Server/client/SCDPM or Azure Backup Server, with no Linux alternatives or parity. Examples and instructions for backup management focus on Windows-centric scenarios, and there are no CLI or Linux-specific examples for agent-based backup operations.
Recommendations
  • Include references to Linux-based backup agents or procedures for on-premises backup registration and management, if supported.
  • Provide parity by mentioning Linux equivalents (such as MARS agent alternatives, if available) alongside Windows tools.
  • Add examples or instructions for managing backups on Linux servers, including CLI commands and agent installation/configuration steps.
  • Clarify whether agent-based backup operations are supported for Linux, and if not, explicitly state the limitation.
  • Ensure that documentation for backup management operations is platform-neutral where possible, or provides clear guidance for both Windows and Linux environments.
GitHub Create Pull Request
Backup Troubleshoot SQL Server database backup ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments. All examples, file paths, extension names, and troubleshooting steps reference Windows-specific tools, directories (e.g., C:\Program Files), and services (e.g., NT AUTHORITY\SYSTEM, Local Security Policy). The AzureBackupWindowsWorkload extension is mentioned exclusively, and instructions for re-registering the extension refer only to PowerShell. There is no mention of Linux-based SQL Server VMs, nor are any Linux-specific troubleshooting steps, file paths, or commands provided.
Recommendations
  • Include explicit guidance for SQL Server running on Linux-based Azure VMs, if supported.
  • Provide Linux equivalents for file paths, extension installation, and configuration steps (e.g., /opt/ or /var/ directories, systemd services).
  • Add troubleshooting steps and error messages relevant to Linux environments (e.g., permissions, SELinux/AppArmor, systemd service status).
  • Offer examples using Bash or Linux-native tools alongside PowerShell, where applicable.
  • Clarify in the introduction whether the documentation applies only to Windows VMs, or update the scope to include Linux VMs if supported.
GitHub Create Pull Request
Backup What's new in Microsoft Azure Backup Server ...lob/main/articles/backup/backup-mabs-whats-new-mabs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation for Microsoft Azure Backup Server (MABS) is heavily Windows-centric. Features and examples almost exclusively reference Windows Server, Windows-specific technologies (ReFS, Hyper-V, registry keys), and Windows tools (PowerShell cmdlets). There is no mention of Linux support, Linux workloads, or Linux-specific backup scenarios, nor are any Linux equivalents or examples provided. Windows features and tools are consistently presented first and often exclusively.
Recommendations
  • Explicitly state the level of Linux support in MABS, if any, and document limitations.
  • Add examples and instructions for backing up Linux-based VMs and workloads, if supported.
  • Include Linux equivalents for Windows-centric features (e.g., registry key changes, PowerShell cmdlets), or clarify if such features are unavailable on Linux.
  • Document backup and recovery procedures for Linux file systems and workloads.
  • If MABS is Windows-only, clarify this early in the documentation and provide links to Azure backup solutions for Linux environments.
  • Ensure parity in feature tables and examples by including Linux alongside Windows where applicable.
GitHub Create Pull Request
Backup Back Up a PostgreSQL Databases by Using the Azure CLI ...ocs/blob/main/articles/backup/backup-postgresql-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways. It repeatedly references PowerShell objects and workflows as the default or primary method for policy manipulation, even in an Azure CLI-focused article. Windows/PowerShell terminology is used to explain concepts before their Linux/CLI equivalents, and file path examples use Windows-style syntax (e.g., .\file.json) without showing Linux alternatives. There are no explicit Linux shell or cross-platform examples for file manipulation, and the guidance assumes familiarity with Windows tools and patterns.
Recommendations
  • Provide Linux/macOS shell examples alongside Windows/PowerShell examples, especially for file manipulation (e.g., use ./file.json instead of .\file.json, and show both syntaxes).
  • Avoid referencing PowerShell objects as the default; clarify that Azure CLI is cross-platform and show equivalent Linux workflows.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows, and highlight any OS-specific considerations.
  • Add notes or sections for Linux users, such as using Bash scripts, file redirection, and path conventions.
  • Ensure that terminology and examples do not assume a Windows environment; use neutral or cross-platform language and patterns.
GitHub Create Pull Request
Backup Azure Backup release notes - Archive .../main/articles/backup/backup-release-notes-archived.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Backup release notes demonstrates a moderate Windows bias. Several features and examples reference Windows-specific tools (such as MARS agent, Microsoft Azure Backup Server, and PowerShell) without equivalent Linux alternatives or examples. Windows-centric solutions (MARS, MABS) are described in detail, while Linux backup scenarios (other than SAP HANA on RHEL) are rarely mentioned. PowerShell is frequently referenced for management tasks, with less emphasis on Azure CLI or Linux-native tooling. In some cases, Windows features are listed before Linux equivalents, and Linux-specific backup scenarios are underrepresented.
Recommendations
  • Provide Linux-specific examples and tooling (e.g., CLI commands, shell scripts) alongside or before Windows/PowerShell examples.
  • Highlight Linux-compatible backup agents and solutions where available, and clarify platform support for each feature.
  • Ensure parity in documentation for both Windows and Linux environments, especially for agent-based backup solutions and management workflows.
  • Explicitly mention support for popular Linux distributions and workloads (beyond SAP HANA on RHEL), such as Ubuntu, CentOS, and containerized applications.
  • Include cross-platform guidance for backup and restore operations, avoiding exclusive reliance on Windows tools or terminology.
GitHub Create Pull Request
Backup Back up multiple SQL Server VMs from the vault ...rticles/backup/backup-sql-server-database-azure-vms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: it consistently references Windows-specific components (e.g., AzureBackupWindowsWorkload extension, NT Service accounts), links to Windows-only troubleshooting scripts, and omits any mention of Linux-based SQL Server VMs or their backup procedures. All examples, instructions, and screenshots assume a Windows environment, with no guidance for Linux users. The documentation also references Windows tools and patterns (such as service accounts and extensions) without Linux equivalents or alternatives.
Recommendations
  • Explicitly state whether Linux-based SQL Server VMs are supported or not, and provide guidance for Linux users if supported.
  • Include examples, troubleshooting steps, and scripts for Linux environments (e.g., Bash, systemd services, Linux VM agent).
  • Reference and link to Linux-specific documentation, tools, and extensions where applicable.
  • Clarify any differences in backup configuration, agent installation, and permissions for Linux SQL Server VMs.
  • Provide parity in screenshots and step-by-step instructions for both Windows and Linux scenarios.
  • If certain features are Windows-only, clearly call this out and suggest alternatives for Linux users.
GitHub Create Pull Request
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias in several areas. Windows-specific tools (MARS agent, DPM, MABS) are discussed in detail and supported for backup and restore, while their Linux equivalents are either unsupported or not mentioned. Windows scenarios and OS support are presented first and in greater detail, with Linux support relegated to separate, shorter sections. Restore instructions and examples frequently reference PowerShell and Windows-centric workflows, with no equivalent Linux CLI or automation examples. Linux backup options are limited, and unsupported scenarios are listed without alternative solutions or workarounds.
Recommendations
  • Provide Linux CLI (az CLI) and automation examples alongside PowerShell instructions for restore and backup operations.
  • Present Windows and Linux support matrices side-by-side or in parallel sections to avoid Windows-first ordering.
  • Expand Linux backup and restore documentation to include more detailed workflows, troubleshooting, and supported scenarios.
  • Mention Linux-native backup tools or third-party solutions where Azure-native options are unavailable.
  • Clarify limitations for Linux and offer guidance or alternatives for unsupported scenarios (e.g., file-level restore on LVM/RAID, Docker mount points).
  • Ensure parity in documentation detail, examples, and troubleshooting between Windows and Linux environments.
GitHub Create Pull Request
Backup MABS & System Center DPM support matrix ...main/articles/backup/backup-support-matrix-mabs-dpm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Windows environments, with all examples, supported operating systems, and deployment scenarios centered around Windows Server versions and Microsoft technologies. There is no mention of Linux support, Linux-based workloads, or cross-platform backup scenarios. All instructions, requirements, and compatibility matrices are exclusively for Windows, and Windows terminology and tools are used throughout.
Recommendations
  • Explicitly state whether Linux operating systems and workloads are supported or not in the context of MABS/DPM.
  • If Linux support exists, add equivalent examples, compatibility matrices, and deployment instructions for Linux environments.
  • Include guidance on backing up Linux VMs or workloads, both on-premises and in Azure, using MABS/DPM or alternative Azure Backup solutions.
  • Mention any limitations or differences in backup/restore workflows for Linux compared to Windows.
  • Provide links to documentation for Linux backup scenarios if MABS/DPM does not support them, or suggest alternative Azure Backup products for Linux workloads.
GitHub Create Pull Request
Backup Support matrix for the MARS agent ...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
⚠ī¸ windows_only ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, and instructions pertain only to Windows (including Windows Server and Windows desktop editions). There is no mention of Linux support, Linux equivalents, or cross-platform considerations. Windows-specific tools and patterns (such as PowerShell, MMC, registry edits, NTFS, VSS, DISM.exe) are referenced throughout, with no alternatives or parity for Linux systems. The documentation assumes a Windows-centric audience and does not address Linux users or scenarios.
Recommendations
  • Clearly state at the beginning that the MARS agent is only supported on Windows, and suggest alternatives for Linux environments (such as Azure Backup for Linux or other agents).
  • Provide links or references to documentation for Linux backup solutions within Azure, so Linux users can find relevant guidance.
  • If partial Linux support exists or is planned, include a support matrix for Linux operating systems and examples of installation, configuration, and backup/restore operations on Linux.
  • Avoid using Windows-specific terminology (e.g., registry edits, MMC, PowerShell) without clarifying that these are not applicable to Linux, and provide Linux equivalents where possible.
  • Add a comparison table or section that highlights differences between Windows and Linux backup approaches in Azure, helping users choose the right solution for their platform.
GitHub Create Pull Request
Backup Back up SQL Server from the Azure VM blade using Azure Backup ...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page is heavily focused on backing up SQL Server databases on Azure VMs using Windows-specific tools and patterns. It exclusively references the AzureBackupWindowsWorkload extension, NT Service accounts, and Windows-based SQL Server VM configurations. There are no examples, instructions, or mentions of Linux-based SQL Server VMs or their backup processes. The documentation assumes a Windows environment throughout and does not provide parity for Linux users.
Recommendations
  • Add explicit guidance for backing up SQL Server databases running on Linux-based Azure VMs, if supported.
  • Mention and document any Linux-specific extensions, agents, or service accounts required for backup operations.
  • Include Linux command-line examples (e.g., Bash, Azure CLI on Linux) alongside Windows/PowerShell examples.
  • Clarify any differences in backup configuration steps between Windows and Linux SQL Server VMs.
  • If Linux is not supported, state this clearly in the prerequisites or introduction to avoid confusion.
GitHub Create Pull Request
Backup Back up SQL Server always on availability groups ...les/backup/backup-sql-server-on-availability-groups.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page focuses exclusively on backing up SQL Server Always On Availability Groups in Azure VMs, implicitly assuming a Windows environment. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for Linux VMs. All references to backup extensions, registration, and failover scenarios are described in the context of Windows VMs, with no parity for Linux tools, commands, or patterns.
Recommendations
  • Explicitly state whether Linux-based SQL Server AGs are supported or not, and provide guidance for Linux if supported.
  • Include examples and instructions for configuring backups on Linux VMs, including any differences in extension installation, registration, and failover handling.
  • Mention Linux-specific tools or commands (e.g., shell scripts, systemd services) where appropriate, alongside Windows/Powershell equivalents.
  • Clarify any limitations or differences in Azure Backup support for SQL Server AGs on Linux versus Windows.
  • Ensure that diagrams and deployment scenarios include Linux VM nodes if supported, and describe their registration and backup processes.
GitHub Create Pull Request
Backup Automation in Azure Backup support matrix ...blob/main/articles/backup/backup-support-automation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation consistently lists PowerShell as the first automation method for nearly every operation and workload, reflecting a Windows-centric approach. PowerShell examples are always present, even for workloads where CLI or REST API are more cross-platform. There is little mention of Linux-specific tools, patterns, or scripting environments (e.g., Bash, shell scripts), and no explicit Linux examples or guidance. The structure and example links reinforce PowerShell as the primary automation tool, which may disadvantage Linux users or those preferring non-Windows environments.
Recommendations
  • Alternate the order of PowerShell and CLI in tables and examples, or list CLI first for workloads where Linux is common (e.g., SAP HANA, PostgreSQL).
  • Add explicit Linux/Bash shell script examples for common automation scenarios, especially for VM, disk, and file operations.
  • Where PowerShell is referenced, clarify that Azure CLI commands work natively on Linux/macOS and provide equivalent Bash examples.
  • Include notes or sections on Linux automation best practices, such as using cron jobs, shell scripting, or integrating with Ansible.
  • Review example links to ensure parity between PowerShell and CLI, and avoid PowerShell-only deep dives.
  • Highlight cross-platform compatibility for REST API, Terraform, and other tools, and provide sample scripts for Linux environments.
GitHub Create Pull Request
Backup Back up the MABS server ...cs/blob/main/articles/backup/backup-the-mabs-server.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation for backing up the Microsoft Azure Backup Server (MABS) is heavily biased towards Windows environments. All examples, instructions, and tooling references are Windows-centric, including exclusive use of Windows command-line tools (psexec.exe, mountvol.exe, diskshadow.exe, Vssadmin), PowerShell commands, and Windows file paths. There is no mention of Linux equivalents, nor any guidance for performing these operations on non-Windows platforms. The documentation assumes the administrator is using Windows Server and Windows-based management tools throughout.
Recommendations
  • Explicitly state platform requirements and limitations at the top of the documentation, clarifying if MABS is Windows-only.
  • If Linux support is possible (e.g., for SQL Server, backup storage, or Azure agent), provide parallel instructions and examples for Linux environments.
  • Where possible, mention cross-platform alternatives to Windows tools (e.g., using native SQL backup commands, Azure CLI, or REST APIs from Linux).
  • Avoid using only Windows file paths and commands; include generic or Linux-compatible examples where applicable.
  • If MABS is strictly Windows-only, make this clear to avoid confusion for Linux administrators.
GitHub Create Pull Request
Backup Configure and manage backup for Azure Blobs using Azure Backup ...b/main/articles/backup/blob-backup-configure-manage.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page primarily describes backup configuration and management for Azure Blobs using the Azure portal, with references to Azure PowerShell and REST API. While Azure CLI is mentioned in the 'Related content' section, the main body of the documentation does not provide CLI examples or Linux-specific instructions. PowerShell is referenced before CLI, and there are no explicit Linux shell or cross-platform command examples. The instructions and screenshots are focused on the Azure portal, which is platform-agnostic, but the scripting and automation references favor Windows tools.
Recommendations
  • Include Azure CLI examples alongside PowerShell in the main documentation body, not just in 'Related content'.
  • Add explicit Linux shell instructions or notes where relevant, especially for automation scenarios.
  • Present CLI and PowerShell options together, or alternate which is shown first, to avoid Windows-first bias.
  • Reference cross-platform tools and patterns, such as Bash scripting, where applicable.
  • Ensure that all automation and scripting guidance is platform-neutral, or provide parity for Linux users.
GitHub Create Pull Request
Backup Overview of Azure Disk Backup ...docs/blob/main/articles/backup/disk-backup-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows Server Failover Cluster is mentioned before Linux clusters in the cluster scenario example. Windows-specific technologies (Volume Shadow Copy Service, VSS) are referenced for application-consistent backup, with no Linux equivalent (such as fsfreeze or LVM snapshots) mentioned. There are no concrete Linux-specific examples, tools, or patterns provided, and no Linux command-line or scripting references (e.g., Bash, CLI) are present. The examples and scenarios tend to mention Windows first or exclusively, with Linux only as a secondary consideration.
Recommendations
  • Provide Linux-specific examples and scenarios, such as using Azure Disk Backup with Linux clusters (e.g., Pacemaker, Corosync) and Linux file systems.
  • Mention Linux tools and patterns for application-consistent backup (e.g., fsfreeze, LVM snapshots) alongside VSS for Windows.
  • Include references to Linux scripting or automation (e.g., Bash scripts, Azure CLI) in the 'Related content' or example sections.
  • Ensure parity in the order of mention: alternate between Windows and Linux or group them together, rather than listing Windows first.
  • Add troubleshooting or best practices sections for both Windows and Linux environments.
GitHub Create Pull Request
Backup Encrypt backup data by using customer-managed keys ...ob/main/articles/backup/encryption-at-rest-with-cmk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is featured prominently and in detail throughout all procedural sections, often with more elaborate examples than Azure CLI. There are multiple warnings and notes about PowerShell-specific behaviors, and the use of PowerShell is recommended for key management tasks. The documentation references Windows-specific tools (e.g., BitLocker) before mentioning Linux equivalents (DM-Crypt), and PowerShell is often listed before CLI in tabbed instructions. There are no explicit Linux shell examples (e.g., bash scripts), nor is there discussion of Linux-specific considerations for backup encryption workflows.
Recommendations
  • Add bash and Linux shell script examples for all CLI procedures, demonstrating parity with PowerShell workflows.
  • Include explicit references to Linux environments and any unique considerations for Linux users (e.g., file permissions, integration with DM-Crypt, SELinux contexts).
  • Balance the order of examples in tabbed instructions, sometimes listing CLI or bash before PowerShell to avoid 'windows_first' bias.
  • Expand documentation of Linux backup agents and clarify limitations or alternatives to the MARS agent for Linux users.
  • Provide troubleshooting and FAQ sections that address Linux-specific scenarios and common issues.
GitHub Create Pull Request
Backup Install the Microsoft Azure Recovery Services (MARS) agent ...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
⚠ī¸ windows_only ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily biased toward Windows environments. All instructions, examples, and prerequisites are specific to Windows, including references to Windows-only installers (.exe), Windows PowerShell, and Windows-specific tools (MABS, DPM). There are no Linux equivalents, examples, or mentions, and the documentation does not address cross-platform scenarios. The customer intent and all workflow steps assume the user is operating on Windows, with no guidance for Linux users.
Recommendations
  • Clearly state in the introduction that the MARS agent is only supported on Windows, and provide links to Linux backup solutions (e.g., Azure Backup for Linux VMs).
  • Add a comparison table or section that explains backup options for both Windows and Linux, including which agent or extension to use on each platform.
  • If possible, provide parity in documentation by including Linux backup workflows, or link to relevant Linux documentation.
  • Avoid using 'Windows machines' as the default context throughout; instead, specify platform limitations and alternatives.
  • Include a FAQ or guidance for users seeking to back up Linux machines, directing them to appropriate Azure solutions.
GitHub Create Pull Request
Backup Encrypt backup data in a Backup vault by using customer-managed keys ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides step-by-step instructions and code samples for Azure portal, PowerShell, and Azure CLI. PowerShell examples are prominent and detailed, with explicit parameter lists and sample commands, while CLI examples are present but less detailed. There is a notable absence of Linux-specific shell examples (e.g., Bash scripts), and no mention of Linux-native tools or workflows. The documentation implicitly prioritizes Windows/PowerShell by presenting PowerShell examples before CLI, and by not acknowledging Linux environments or shell differences.
Recommendations
  • Add explicit Bash shell examples for all CLI commands, including environment variable usage and scripting patterns common on Linux.
  • Include notes or sections on running Azure CLI commands in Linux environments, addressing authentication, file paths, and shell differences.
  • Provide parity in example detail between PowerShell and CLI, ensuring CLI examples are as comprehensive and annotated as PowerShell ones.
  • Mention cross-platform compatibility for Azure CLI and clarify that all CLI commands work on Linux, macOS, and Windows.
  • Consider adding troubleshooting steps or tips specific to Linux environments (e.g., handling permissions, environment setup).
GitHub Create Pull Request
Backup Guidance and best practices ...s/blob/main/articles/backup/guidance-best-practices.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: examples and automation references prioritize PowerShell, Windows-centric tools (MARS agent, DPM/MABS) are mentioned exclusively or first, and there are no explicit Linux or cross-platform CLI examples. The guidance and scenarios focus on workloads and management patterns typical of Windows environments, with little attention to Linux-specific backup needs or tools.
Recommendations
  • Include CLI (az) examples alongside or before PowerShell examples for all automation scenarios.
  • Explicitly mention Linux workloads and provide guidance/examples for backing up Linux VMs and files.
  • Reference Linux-native backup agents or integration options (e.g., Azure Backup for Linux, integration with rsync, tar, etc.) where applicable.
  • Ensure that cross-platform tools and patterns (such as REST API, SDKs) are given equal prominence to Windows-specific tools.
  • Add sections or callouts for Linux-specific considerations (e.g., file system consistency, application-consistent backups for Linux apps).
  • When mentioning automation, alternate between PowerShell and CLI, or show both in parallel.
  • Review all tool references (MARS, DPM/MABS) and clarify their OS compatibility, or suggest Linux alternatives if available.
GitHub Create Pull Request
Backup Manage Backup vaults ...-docs/blob/main/articles/backup/manage-backup-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily by referencing PowerShell as a method for moving Backup vaults before mentioning Azure CLI, and by not providing explicit Linux/bash examples or guidance. The use of 'PowerShell' as a named tool and the lack of parity in command-line examples for Linux users suggest a preference for Windows tooling and workflows.
Recommendations
  • Provide explicit bash/Azure CLI examples for all operations where PowerShell is mentioned, including full command syntax and usage notes for Linux/macOS environments.
  • When listing command-line options, mention Azure CLI before or alongside PowerShell, and clarify cross-platform compatibility.
  • Add screenshots or walkthroughs using Azure CLI in a Linux terminal for parity with portal and PowerShell instructions.
  • Include notes or links for installing and using Azure CLI on Linux/macOS.
  • Review all references to scripts and tools to ensure examples are not Windows-centric (e.g., avoid only referencing .ps1 scripts or Windows paths).
GitHub Create Pull Request
Backup What Azure Backup Server V3 RTM can back up .../backup/microsoft-azure-backup-server-protection-v3.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for Azure Backup Server V3 RTM is heavily Windows-centric. The protection matrix almost exclusively lists Windows operating systems, Windows-based workloads (SQL Server, Exchange, SharePoint, Hyper-V), and Windows file systems (NTFS, ReFS). Linux is mentioned only briefly as a guest VM, with limited support (entire VM backup only, file-consistent snapshots), and there are no Linux-specific examples, tools, or recovery scenarios. Windows tools and patterns (e.g., VSS, NTFS, Windows Management Framework) are referenced throughout, with no Linux equivalents or parity.
Recommendations
  • Add explicit Linux workload support details, including supported distributions, file systems, and backup/recovery scenarios.
  • Provide Linux-specific examples for backup and recovery, including item-level recovery if supported.
  • Mention Linux tools and patterns (e.g., LVM snapshots, ext4/xfs file systems) where applicable.
  • Clarify limitations for Linux and provide guidance or alternatives for Linux users.
  • Ensure Linux is represented in the protection matrix with equal detail as Windows workloads.
  • If Azure Backup Server does not support Linux workloads beyond VM-level backup, state this clearly and suggest alternative Azure backup solutions for Linux.
GitHub Create Pull Request
Backup Manage telemetry settings in Microsoft Azure Backup Server (MABS) ...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively references the Microsoft Azure Backup Server (MABS) console, which is a Windows-only application. All instructions and screenshots pertain to the Windows GUI, with no mention of Linux equivalents, command-line alternatives, or cross-platform considerations. There are no examples or guidance for managing telemetry settings on Linux systems, nor are any Linux tools or patterns referenced.
Recommendations
  • Clarify in the introduction that MABS is a Windows-only product, if applicable. If cross-platform support exists, include instructions for Linux environments.
  • Provide command-line alternatives (e.g., PowerShell, CMD, or CLI) for managing telemetry settings, and note whether these are available on Linux.
  • If telemetry management is possible via configuration files, document the file location and format for both Windows and Linux systems.
  • Add explicit statements about platform support and limitations, so Linux administrators are aware of their options.
  • If there is no Linux support, consider linking to equivalent Azure Backup solutions for Linux and their telemetry management documentation.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V3 UR1 protection matrix ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. Windows workloads, tools, and filesystems (NTFS, VSS, ReFS) are mentioned exclusively or before Linux equivalents. Linux support is limited to guest VM backup with minimal detail, and there are no Linux-specific examples, recovery scenarios, or parity in feature descriptions. Windows tools and patterns (e.g., Volume Shadow Copy Service, NTFS, ReFS, Windows Management Framework) are referenced throughout, while Linux tools and filesystems are not discussed.
Recommendations
  • Provide Linux-specific protection and recovery examples, including supported filesystems (e.g., ext4, xfs) and backup scenarios beyond VM-level protection.
  • Include parity in feature descriptions for Linux workloads, such as item-level recovery, application-aware backup, and supported distributions.
  • Mention Linux tools or backup patterns where relevant (e.g., LVM snapshots, integration with Linux backup agents).
  • List Linux limitations and supported features in the same detail as Windows, and avoid presenting Windows as the default or only scenario.
  • Where Windows tools (e.g., VSS, NTFS) are referenced, provide Linux equivalents or clarify their applicability.
GitHub Create Pull Request
Backup Monitor your backups with Backup Explorer ...es/backup/monitor-azure-backup-with-backup-explorer.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for Backup Explorer demonstrates a Windows bias by focusing exclusively on Azure virtual machines (VMs) without specifying support for Linux VMs. Examples and references are generic but implicitly assume Windows environments, such as exporting to Excel (a Windows-centric tool) and referencing Azure VM actions without clarifying Linux support. There are no examples or mentions of Linux-specific backup scenarios, tools, or workflows, and no parity guidance for Linux administrators.
Recommendations
  • Explicitly state whether Backup Explorer supports both Windows and Linux Azure VMs, and provide examples for each.
  • Include screenshots or walkthroughs that demonstrate monitoring and managing backups for Linux VMs.
  • Mention Linux-friendly export formats (e.g., CSV, JSON) alongside Excel, and provide instructions for using them.
  • Clarify whether actions such as configuring backup or responding to alerts work identically for Linux VMs, and note any differences.
  • Add references to Linux command-line tools or automation options (such as Azure CLI or Bash scripts) for interacting with Backup Explorer data.
GitHub Create Pull Request
Backup Backup Classic Alerts using Azure Backup ...b/main/articles/backup/move-to-azure-monitor-alerts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (MARS agent, SC-DPM, MABS) and patterns (PowerShell, portal) without mentioning Linux equivalents or providing Linux-specific examples. Notification exceptions and job status are described in terms of portal/PowerShell/CLI, but PowerShell is listed first and no Linux shell commands or workflows are shown. There are no examples or guidance for Linux-based backup agents or workflows, and the alert scenarios focus on Windows-centric backup solutions.
Recommendations
  • Include examples and references for Linux-based backup agents and workflows, such as Azure Backup for Linux VMs.
  • Provide CLI and Bash shell command examples alongside PowerShell, especially for alert management and job status checking.
  • Mention Linux-specific backup scenarios and tools where relevant, and ensure parity in alerting and notification documentation.
  • Avoid listing Windows tools and interfaces (PowerShell, portal) before cross-platform or Linux alternatives; present them together or in parallel.
  • Clarify whether features and notifications apply equally to Linux workloads and agents, and document any differences.
GitHub Create Pull Request
Backup Monitoring and reporting solutions for Azure Backup ...main/articles/backup/monitoring-and-alerts-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by consistently mentioning Azure PowerShell before Azure CLI, listing Windows-centric backup solutions (such as Azure Backup Agent, DPM, Azure Backup Server) prominently, and omitting explicit Linux-focused examples or tools. While Azure CLI is referenced, there are no Linux-specific usage patterns, troubleshooting, or monitoring scenarios provided. The documentation does not address Linux backup agents or provide parity in example commands or tool recommendations for Linux environments.
Recommendations
  • Include Linux-specific examples and usage patterns for monitoring and reporting Azure Backup, such as using Azure CLI on Linux, Bash scripts, or REST API calls from Linux environments.
  • Explicitly mention Linux-compatible backup agents or solutions where relevant, and clarify which monitoring features are available for Linux workloads.
  • Provide troubleshooting and alerting scenarios for Linux-based Azure VMs and workloads, including any differences in alert categories or supported features.
  • Ensure that CLI and REST API examples are given equal prominence to PowerShell, and avoid listing PowerShell first unless there is a technical reason.
  • Add documentation sections or notes highlighting best practices for monitoring Azure Backup in Linux environments, including integration with Linux-native tools (e.g., cron jobs, syslog, etc.).
GitHub Create Pull Request
Backup Configure Multi-user authorization using Resource Guard .../blob/main/articles/backup/multi-user-authorization.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides command-line examples for both Azure PowerShell and Azure CLI, but PowerShell examples are consistently presented before CLI examples. There is no mention of Linux-specific tools, shell environments, or considerations, and no explicit Linux/Bash examples are given. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not address Linux users' needs or provide parity in example ordering or environment-specific guidance.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI (which is cross-platform) first to avoid implicit Windows-first bias.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash) where appropriate.
  • Add notes or sections for Linux users, such as prerequisites for installing Azure CLI on Linux, and troubleshooting tips specific to Linux environments.
  • Include screenshots or walkthroughs using Linux terminals where applicable, not just Azure portal or PowerShell.
  • Clarify that PowerShell Core is available on Linux, but most users on Linux will prefer Azure CLI, and link to installation guides for both tools on Linux.
GitHub Create Pull Request
Backup Offline backup by using Azure Data Box .../main/articles/backup/offline-backup-azure-data-box.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is heavily biased towards Windows environments. All supported platforms listed are Windows SKUs, with no mention of Linux or macOS. All examples and instructions use Windows-specific tools (PowerShell, Control Panel, PsExec, Windows command prompt), and there are no Linux equivalents or alternatives provided. The MARS Agent and backup workflow are described exclusively for Windows, and troubleshooting steps rely on Windows-only features (registry, certificate manager).
Recommendations
  • Explicitly state whether Linux and macOS are unsupported, or provide instructions for those platforms if support exists.
  • If possible, add Linux-compatible backup agent instructions or clarify the absence of such support.
  • Provide parity in examples: include Linux shell commands and tools (e.g., Bash, CLI, NFS mounting on Linux) where applicable.
  • Mention Linux alternatives for PowerShell commands (e.g., Azure CLI) and provide step-by-step instructions for Linux environments.
  • If the MARS Agent is Windows-only, suggest or link to alternative backup solutions for Linux users in Azure.
GitHub Create Pull Request
Backup Overview of offline backup ...s/blob/main/articles/backup/offline-backup-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Azure Backup Server (MABS), System Center Data Protection Manager (DPM), and the MARS Agent—all Windows-centric backup solutions. There are no mentions of Linux backup tools, nor are there examples or workflows for Linux environments. The documentation assumes the use of Windows-based utilities and patterns, omitting guidance for Linux users or cross-platform scenarios.
Recommendations
  • Include examples and workflows for Linux-based backup solutions compatible with Azure offline backup, such as using Azure CLI or third-party Linux backup tools.
  • Explicitly mention whether Linux servers are supported for offline backup and provide parity documentation for Linux environments.
  • Add instructions for preparing disks and staging locations using Linux tools (e.g., dd, mkfs, cryptsetup for encryption) alongside Windows utilities.
  • Clarify any platform limitations and offer guidance for mixed Windows/Linux environments.
  • Ensure that references to utilities and agents are balanced, mentioning both Windows and Linux options where available.
GitHub Create Pull Request
Backup Using Pre-Backup and Post-Backup Scripts ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows file paths, Windows-specific tools (such as cscript for VBScript), and Windows-centric data source naming conventions. There are no examples or guidance for Linux environments, nor is there mention of Linux-compatible scripting or file locations.
Recommendations
  • Add equivalent instructions and examples for Linux-based protected computers, including typical file paths and script execution methods.
  • Mention Linux shell scripting (e.g., Bash, Python) as supported script types, and clarify any platform-specific limitations.
  • Provide sample ScriptingConfig.xml entries for Linux data sources, using Linux-style paths and conventions.
  • Clarify whether MABS supports Linux agents and, if so, document any differences in script configuration and execution.
GitHub Create Pull Request
Backup Query your backups using Azure Resource Graph (ARG) ...les/backup/query-backups-using-azure-resource-graph.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as the first automation client for Azure Resource Graph queries, referencing a PowerShell-specific guide before mentioning Azure CLI and SDK alternatives. There are no explicit Linux or bash examples, nor is there mention of Linux-specific tooling or patterns. All automation examples are generic or Windows-centric, and there is no guidance for Linux users on running queries or integrating with Linux-native tools.
Recommendations
  • List Azure CLI before PowerShell when mentioning automation clients, or present both equally.
  • Provide explicit Linux/bash examples for running ARG queries, such as using Azure CLI in a bash shell.
  • Reference Linux-specific guides or documentation for ARG usage.
  • Mention cross-platform compatibility and clarify that all tools (PowerShell, CLI, SDK) are available on Linux, macOS, and Windows.
  • Include sample scripts or command lines for Linux users, e.g., using az resource-graph query in bash.
  • Avoid implying PowerShell is the default or preferred method unless justified by technical reasons.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Bicep ...es/backup/quick-backup-azure-files-vault-tier-bicep.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell deployment instructions and examples, referencing Azure PowerShell modules in prerequisites, and omitting equivalent Azure CLI or Bash instructions. The deployment workflow and next steps prioritize PowerShell, with Linux-friendly alternatives mentioned only as secondary options or not at all in the main walkthrough.
Recommendations
  • Add Azure CLI and Bash deployment instructions alongside PowerShell, especially in the 'Deploy the template' section.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI, with installation links for each.
  • Ensure that examples and code snippets are provided for both Windows (PowerShell) and Linux/macOS (CLI/Bash) users.
  • Reorder next steps to present Azure CLI and REST API options equally or before PowerShell, or group them together for parity.
  • Clearly indicate cross-platform compatibility for all steps, and avoid assuming a Windows environment by default.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Resource Manager ...cles/backup/quick-backup-azure-files-vault-tier-arm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell deployment examples, mentioning PowerShell before other methods, and omitting explicit Linux/CLI deployment instructions. The 'Next steps' section also lists PowerShell-based management tasks before CLI or REST API alternatives, reinforcing a Windows-centric approach.
Recommendations
  • Add explicit Azure CLI deployment instructions alongside PowerShell examples, including sample commands for Linux/macOS users.
  • Reorder 'Next steps' to present Azure CLI and REST API options before or alongside PowerShell, ensuring equal visibility.
  • Include a note clarifying that ARM template deployment can be performed from any OS using Azure CLI, and provide links to cross-platform instructions.
  • Where PowerShell is referenced, also mention Bash/CLI equivalents to avoid implying PowerShell is the preferred or only method.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Terraform ...ackup/quick-backup-azure-files-vault-tier-terraform.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by mentioning Azure PowerShell alongside Azure CLI for authentication, despite Terraform only supporting Azure CLI. The references to Azure PowerShell are frequent and often listed before Azure CLI in 'Next steps', and there are no explicit Linux shell or Bash examples. The troubleshooting and implementation steps do not mention Linux-specific patterns or tools, and the use of 'Console' for command blocks is ambiguous but leans toward Windows conventions.
Recommendations
  • Remove or clarify references to Azure PowerShell in authentication steps, emphasizing that only Azure CLI is supported for Terraform.
  • Provide explicit Bash/Linux shell examples for all command-line instructions, including authentication and Terraform commands.
  • In 'Next steps', list Azure CLI and REST API before Azure PowerShell to avoid Windows-first ordering.
  • Add troubleshooting tips for common Linux-specific issues with Terraform on Azure.
  • Use 'Bash' or 'Shell' as the code block language for command-line examples where appropriate, and clarify cross-platform compatibility.
GitHub Create Pull Request
Backup Quick start - Back up Azure Database for PostgreSQL server ...cles/backup/quick-backup-postgresql-database-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell scripts as the primary method for granting privileges to database users, both in the prerequisites and in the main configuration flow. While alternatives like PG admin or PSQL are mentioned, they are listed after PowerShell and lack concrete examples or guidance. There are no Linux shell (bash) or cross-platform CLI examples provided, and the documentation does not address how to perform these steps on non-Windows environments, which may leave Linux users at a disadvantage.
Recommendations
  • Provide explicit bash/psql command examples for granting database privileges, alongside PowerShell.
  • Include step-by-step instructions for using PG admin and psql on Linux, not just mention them as alternatives.
  • Ensure that any ARM template or script references include cross-platform instructions for running them (e.g., via Azure CLI or bash).
  • Reorder examples so that Windows and Linux methods are presented with equal prominence, or group them together under platform-specific headings.
  • Add a note clarifying that all operations can be performed from Linux, macOS, or Windows, and link to platform-specific setup guides if needed.
GitHub Create Pull Request
Backup Quickstart - Bicep file VM Backup ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All deployment and management instructions use Azure PowerShell, with no mention of Azure CLI or Bash alternatives suitable for Linux or cross-platform users. The Bicep template provisions only Windows VMs, with no Linux VM options or examples. References to tools and follow-up steps (such as cleanup) are exclusively PowerShell-based, and the template's OS selection is limited to Windows versions.
Recommendations
  • Provide Azure CLI/Bash examples for deploying the Bicep template, in addition to PowerShell.
  • Include a Linux VM option in the Bicep template (e.g., Ubuntu, CentOS) and show how to select it.
  • Add instructions for starting and monitoring backup jobs using Azure CLI, not just PowerShell.
  • Offer cleanup steps using Azure CLI commands (e.g., az group delete) alongside PowerShell.
  • Balance references to Windows and Linux in both the template and procedural steps, ensuring parity for cross-platform users.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server with an Azure Resource Manager template .../backup/quick-backup-postgresql-flexible-server-arm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell deployment instructions for the ARM template, referencing Azure PowerShell modules in prerequisites, and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The 'Next steps' section also links exclusively to PowerShell-based restore instructions.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, alongside PowerShell.
  • Mention installation steps for Azure CLI in the prerequisites, not just PowerShell.
  • Provide links to both PowerShell and CLI/Bash restore guides in the 'Next steps' section.
  • Ensure that all instructions and code snippets are platform-agnostic or include both Windows and Linux variants.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Servers with a Bicep file ...ackup/quick-backup-postgresql-flexible-server-bicep.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a clear Windows bias by exclusively providing PowerShell deployment instructions and referencing Azure PowerShell for next steps. No Azure CLI or Linux shell examples are given, and the guidance assumes use of Windows tools and patterns throughout. Linux users are not provided with equivalent instructions or parity in deployment workflow.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, including example commands for deploying the Bicep template from Bash or other Linux shells.
  • Explicitly mention that the Bicep CLI and Azure CLI are cross-platform and provide installation and usage guidance for Linux/macOS.
  • Include links to Linux/macOS-specific documentation for installing prerequisites and running deployments.
  • Ensure that next steps reference both PowerShell and CLI-based restore workflows, or provide parity in supported tooling.
  • Avoid language that assumes a Windows shell (e.g., 'right-click the shell window and then select Paste') and use platform-neutral instructions.
GitHub Create Pull Request
Backup Quickstart - Create a backup policy for Azure Database for PostgreSQL - Flexible Server using Azure CLI .../backup/quick-backup-postgresql-flexible-server-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias by referencing PowerShell objects and workflows as the default or primary approach, especially in the 'Modify the policy template' section. It describes PowerShell object manipulation first, then contrasts it with Azure CLI file-based editing, implying PowerShell (and thus Windows) is the more natural or preferred environment. File path examples use Windows-style backslashes (e.g., .\OSSPolicy.json), and there is no mention of Linux shell equivalents or examples. The documentation does not provide Linux-specific guidance or examples for file handling, scripting, or path formats.
Recommendations
  • Provide Linux shell equivalents for all CLI examples, including file path formats (e.g., ./OSSPolicy.json instead of .\OSSPolicy.json).
  • Include explicit instructions or notes for Linux users on how to perform file-based edits, such as using cat, jq, or sed.
  • Avoid presenting PowerShell as the default or preferred workflow; instead, treat CLI and PowerShell approaches equally, or provide parallel examples.
  • Mention cross-platform compatibility of Azure CLI and clarify any OS-specific differences in scripting or file handling.
  • Add a section or callout for Linux/macOS users with tips for adapting the examples to their environment.
GitHub Create Pull Request
Backup Quickstart - Install Azure Backup extension in an AKS cluster ...main/articles/backup/quick-install-backup-extension.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page primarily describes installation of the Azure Backup extension in AKS using the Azure Portal, which is platform-agnostic, but in the 'Next steps' section, Azure PowerShell is listed before Azure CLI, and there is no mention of Linux-specific tools or shell examples. There are no explicit Linux command-line instructions or screenshots, and the guidance does not address Linux users directly, potentially leading to a Windows-centric impression.
Recommendations
  • Provide explicit Linux shell (bash) examples for installing and configuring the extension, especially for command-line steps.
  • List Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform and widely used on Linux.
  • Include screenshots or instructions for Linux environments where relevant, such as using the Azure CLI in a Linux terminal.
  • Mention platform compatibility for each tool (Portal, PowerShell, CLI) and clarify which are recommended for Linux users.
  • Add troubleshooting or notes for Linux-specific scenarios, such as permissions or networking configurations.
GitHub Create Pull Request
Backup Quickstart: Back up a virtual machine in Azure with Terraform ...blob/main/articles/backup/quick-backup-vm-terraform.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively demonstrates backing up a Windows virtual machine in Azure using Terraform. All examples, descriptions, and resource creation steps focus on Windows VMs, with no mention of Linux VM equivalents or how to adapt the process for Linux. The page title, summary, and next steps reinforce a Windows-centric approach, and there are no Linux-specific instructions, code samples, or troubleshooting advice.
Recommendations
  • Add parallel instructions and code samples for creating and backing up a Linux VM in Azure using Terraform.
  • Update the introduction and checklist to mention both Windows and Linux VM scenarios.
  • Include Linux-specific Azure CLI commands and considerations, such as SSH key generation and Linux VM resource names.
  • Provide troubleshooting tips relevant to Linux VMs.
  • Offer 'Next steps' links to articles about Azure Linux VMs and their backup procedures.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Resource Manager ...ob/main/articles/backup/quick-kubernetes-backup-arm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by providing only Azure PowerShell deployment instructions, referencing PowerShell and its installation in the prerequisites, and omitting equivalent Azure CLI or Linux shell examples. The deployment workflow and scripting guidance are tailored to Windows/PowerShell users, with no mention of Linux or cross-platform alternatives.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, including example commands for template deployment.
  • Reference both PowerShell and Azure CLI in prerequisites, with installation links for Linux/macOS users.
  • Explicitly mention that the ARM template can be deployed from any OS and shell, and provide cross-platform guidance.
  • Consider providing Bash or shell script examples for Linux users.
  • Ensure that next steps and related links highlight both PowerShell and CLI options equally.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Bicep .../main/articles/backup/quick-kubernetes-backup-bicep.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing PowerShell deployment instructions for the Bicep template, with no equivalent Bash, Azure CLI, or Linux shell examples. The prerequisites and deployment steps focus on Azure PowerShell, which is most commonly used on Windows, and do not mention or prioritize cross-platform tools. The 'Next steps' section lists PowerShell before CLI, further reinforcing Windows-first ordering.
Recommendations
  • Add equivalent deployment instructions using Azure CLI and Bash shell, which are cross-platform and commonly used on Linux and macOS.
  • In the prerequisites section, mention both Azure PowerShell and Azure CLI as supported options for deploying Bicep templates.
  • In the 'Next steps' section, alternate or randomize the order of PowerShell and CLI links to avoid Windows-first ordering.
  • Explicitly state that the deployment steps can be performed on any OS, and provide guidance for Linux/macOS users.
  • Where possible, provide examples for both PowerShell and Bash/CLI side-by-side to ensure parity and inclusivity.
GitHub Create Pull Request
Backup Restore VMware virtual machines using Azure Backup Server .../articles/backup/restore-azure-backup-server-vmware.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server VMs for individual file recovery, omitting Linux VM examples and recovery procedures. All item-level restore instructions are limited to Windows, and registry key modifications (a Windows-specific tool) are used for advanced configuration. There are no Linux-specific recovery steps, tools, or troubleshooting guidance, and the documentation does not mention parity or limitations for Linux VMs.
Recommendations
  • Add explicit instructions and examples for restoring individual files from Linux VMs, or clarify if this feature is unavailable for Linux.
  • Include Linux-specific recovery options, such as mounting VMDK files on a Linux system and extracting files.
  • Document any limitations or differences in recovery features between Windows and Linux VMs.
  • If registry modifications are required for advanced configuration, provide equivalent steps for Linux environments (if supported), or state that such configuration is Windows-only.
  • Ensure troubleshooting and next steps sections include guidance for Linux VM recovery scenarios.
GitHub Create Pull Request
Backup Restore SQL Server databases on an Azure VM .../main/articles/backup/restore-sql-database-azure-vm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: it exclusively references Windows tools (e.g., PsExec, NT AUTHORITY\SYSTEM, C:\Program Files), provides examples and instructions tailored to Windows environments, and omits Linux-specific guidance or parity (e.g., no mention of restoring SQL Server on Linux VMs, no Linux file system paths, no Linux commands or service management). The use of Windows-centric terminology and tools appears throughout, and there are no examples or instructions for SQL Server on Linux VMs, even though SQL Server is supported on Linux in Azure.
Recommendations
  • Add explicit instructions and examples for restoring SQL Server databases on Linux-based Azure VMs.
  • Include Linux file system paths (e.g., /var/opt/mssql/data) and relevant commands for file permissions and service management (e.g., systemctl for SQL Server service).
  • Provide Linux equivalents for Windows tools and procedures, such as using sudo and chown/chmod for file permissions instead of PsExec and NT AUTHORITY\SYSTEM.
  • Clarify which steps are Windows-specific and which are applicable to Linux, or provide parallel sections for both platforms.
  • Mention any differences or limitations in restore functionality between Windows and Linux SQL Server on Azure VMs.
  • Ensure screenshots and UI references are not exclusively Windows-oriented, or note any platform-specific differences.
GitHub Create Pull Request
Backup Restore encrypted Azure VMs ...les/backup/restore-azure-encrypted-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits several signs of Windows bias. Windows terminology and tools (such as PowerShell) are mentioned before Linux equivalents, and examples for restoring VMs using PowerShell are provided without corresponding Linux CLI or script examples. The process for restoring encrypted Linux VMs is described only briefly, lacking step-by-step instructions or command-line examples, while Windows-specific operations (like OS disk swap) are referenced directly. The use of Windows-centric documentation links and the absence of Linux-focused guidance further reinforce the bias.
Recommendations
  • Provide equivalent Linux CLI (az CLI, Bash) examples for restoring VMs and disks, alongside PowerShell examples.
  • Include step-by-step instructions for restoring encrypted Linux VMs, including reinstallation of the ADE extension, with sample commands.
  • Reference Linux-specific documentation and tools where appropriate, such as links to Linux OS disk swap procedures.
  • Ensure that both Windows and Linux scenarios are covered equally in all sections, including troubleshooting and next steps.
  • Avoid mentioning Windows tools or patterns before Linux equivalents; present both in parallel or in separate, clearly labeled sections.
GitHub Create Pull Request
Backup Restore SQL server databases in Azure VMs with REST API .../main/articles/backup/restore-azure-sql-vm-rest-api.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based SQL Server instances, using Windows-style directory paths (e.g., C:\SQLfiles\Default.ldf), and omitting any mention of Linux-based SQL Server or examples relevant to Linux VMs. All resource names, directory paths, and restore scenarios assume a Windows environment, with no guidance for Linux users or parity in examples.
Recommendations
  • Add explicit examples and instructions for restoring SQL Server databases on Linux-based Azure VMs, including Linux-style directory paths (e.g., /var/opt/mssql/data).
  • Clarify whether the REST API supports SQL Server on Linux VMs and document any differences or prerequisites.
  • Provide alternate request body examples using Linux file paths and container names relevant to Linux VMs.
  • Include a note or section on cross-platform support, outlining any limitations or additional steps for Linux users.
  • Ensure terminology and resource naming do not assume a Windows-only environment (e.g., avoid only using 'C:\' paths or Windows hostnames).
GitHub Create Pull Request
Backup Restore SAP HANA database instances on Azure VMs ...articles/backup/sap-hana-database-instances-restore.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing the use of PowerShell or CLI scripts for permission management, but does not provide explicit Linux shell (bash) examples or mention Linux tools. The workflow and screenshots are centered around the Azure portal, which is platform-agnostic, but the only command-line references are to PowerShell and CLI, with PowerShell mentioned first. There are no examples or instructions tailored for Linux users, such as bash scripts or Linux-specific commands for disk attachment or mounting.
Recommendations
  • Provide explicit bash shell examples for Linux users alongside PowerShell/CLI instructions.
  • Mention Linux-native tools (e.g., mount, fdisk) for disk management and mounting operations.
  • Ensure that command-line instructions are presented in a platform-neutral order, or group them by OS.
  • Clarify when Azure CLI commands are cross-platform and provide examples for both Windows (PowerShell) and Linux (bash).
  • Include screenshots or references to Linux desktop environments where relevant.
GitHub Create Pull Request
Backup Save and manage MARS agent passphrase securely in Azure Key Vault ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/save-backup-passphrase-securely-in-azure-key-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on the Windows platform, specifically the MARS agent (which is Windows-only), and provides examples using Windows-centric tools such as PowerShell and the MARS console. There are no Linux-specific instructions, nor any mention of Linux backup agents or workflows. The automation and scripting examples are all in PowerShell or Azure CLI, but the operational steps (installation, passphrase management) are exclusively described for Windows environments.
Recommendations
  • Clearly state at the beginning that the MARS agent is Windows-only, and provide links or references to equivalent Linux backup solutions (e.g., Azure Backup for Linux VMs or Azure Backup Server).
  • Where possible, add parity documentation for Linux backup agents, including how to securely store and retrieve encryption credentials using Azure Key Vault.
  • If Azure CLI is cross-platform, clarify which steps can be performed from Linux/macOS and which are Windows-only.
  • Provide alternative examples or workflows for Linux users, or direct them to relevant documentation.
  • Avoid assuming the use of Windows tools (e.g., MARS console, PowerShell) in generic Azure Key Vault instructions—offer platform-agnostic guidance where feasible.
GitHub Create Pull Request
Backup Script Sample - Create a new or modify the current file and folder backup policy ...ticles/backup/scripts/set-file-folder-backup-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively provides a PowerShell script for managing backup policies with the MARS agent, which is a Windows-specific tool. There are no examples, instructions, or mentions of Linux equivalents, nor is there guidance for Linux administrators. The focus on PowerShell and Windows registry paths further reinforces a Windows-centric approach.
Recommendations
  • Add equivalent script samples for Linux environments, using Bash or Python.
  • Mention and provide guidance for Linux-compatible backup tools (e.g., rsync, cron, Azure CLI for Linux).
  • Clarify platform support for the MARS agent and suggest alternatives for Linux if MARS is not supported.
  • Structure documentation so that both Windows and Linux approaches are presented, ideally side-by-side.
  • Explicitly state any platform limitations at the beginning of the page.
GitHub Create Pull Request
Backup Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads ...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by providing detailed instructions and code examples exclusively for Azure PowerShell, a Windows-centric tool, with no mention of Linux-native CLI tools or workflows. The examples and guidance prioritize Windows patterns and do not offer parity for Linux users, such as Bash/CLI commands or references to Linux tooling. The documentation also refers to PowerShell before any other automation or scripting options, and does not acknowledge Linux environments or alternatives.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and preferred by many Linux users.
  • Explicitly mention that the operations can be performed from Linux/macOS environments using Azure CLI or REST API, not just PowerShell.
  • Include screenshots or instructions for Linux users where UI or command-line differences exist.
  • Clarify any prerequisites or environment-specific requirements for both Windows and Linux users.
  • Review terminology and tool references to ensure Linux parity (e.g., avoid assuming PowerShell is the default automation tool).
GitHub Create Pull Request
Backup Azure Backup support matrix for SQL Server Backup in Azure VMs ...e-docs/blob/main/articles/backup/sql-support-matrix.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily biased towards Windows environments. Only Windows Server operating systems are supported and listed, with explicit mention that Linux is not supported. All examples and tooling references (such as PowerShell) are Windows-centric, and there is no mention of Linux equivalents or parity. The documentation does not provide guidance or examples for Linux users, nor does it discuss future support or alternatives for Linux-based SQL Server deployments.
Recommendations
  • Clearly state the roadmap or plans for Linux support, if any, to inform users of future parity.
  • Add a dedicated section for Linux users explaining current limitations, possible workarounds, or alternative backup strategies.
  • If possible, provide examples or references for Linux-based backup solutions (e.g., using Azure CLI, third-party tools, or manual backup procedures).
  • Ensure that tooling references (such as PowerShell) are balanced with Azure CLI or other cross-platform tools, and clarify their platform compatibility.
  • Regularly review and update the documentation to reflect any changes in Linux support or cross-platform capabilities.
GitHub Create Pull Request
Backup Script Sample - Create a new or modify the current system state backup policy ...icles/backup/scripts/set-system-state-backup-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively provides a PowerShell script sample for managing system state backup policy with the MARS agent, which is a Windows-centric tool. All instructions, code, and next steps reference Windows tools and workflows, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux users, and Windows patterns are presented as the default.
Recommendations
  • Include equivalent script samples for Linux environments, such as Bash or Python, if supported.
  • Clarify whether the MARS agent and system state backup policy management are available or supported on Linux, and provide alternatives if not.
  • Mention and link to Linux backup tools (e.g., rsync, tar, cron jobs, Azure CLI for Linux) where appropriate.
  • Add a section comparing Windows and Linux backup management approaches, highlighting platform-specific considerations.
  • Ensure that documentation titles and descriptions specify platform limitations or provide cross-platform guidance where possible.
GitHub Create Pull Request
Backup Soft delete for virtual machines ...b/main/articles/backup/soft-delete-virtual-machines.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for managing soft delete operations, referencing Windows-centric tools and patterns, and omitting equivalent Linux CLI or automation examples. The PowerShell section is given prominence and detail, while there are no Bash/CLI or Linux-native instructions. The use of 'Az.RecoveryServices' and PowerShell cmdlets further reinforces the Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI (az backup ...) examples for all operations shown in PowerShell, including delete, undelete, and resume backup.
  • Explicitly mention cross-platform support and clarify that operations can be performed from Linux/macOS environments using Azure CLI or REST API.
  • Provide Bash script snippets for automation tasks, ensuring Linux administrators have parity in guidance.
  • Reorder or parallelize example sections so that Azure CLI (cross-platform) instructions appear before or alongside PowerShell, rather than after.
  • Reference Linux tools and automation patterns where relevant, such as cron jobs or shell scripting for backup management.
GitHub Create Pull Request
Backup Troubleshoot Azure Files backup .../blob/main/articles/backup/troubleshoot-azure-files.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for troubleshooting and recovery operations (e.g., finding Recovery Services vaults, undeleting file shares). No Linux or cross-platform CLI (such as Azure CLI, Bash, or shell script) alternatives are provided. Additionally, references to tools and portals (such as 'Files portal') are Windows-centric, and there is a lack of parity for Linux administrators who may need to perform similar tasks.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for all PowerShell scripts referenced, ensuring Linux users can perform the same troubleshooting and recovery operations.
  • Explicitly mention cross-platform tools and workflows (e.g., Azure CLI, REST API) alongside Windows-specific instructions.
  • Add notes or sections clarifying how Linux/macOS administrators can access or perform operations (such as undeleting file shares, finding Recovery Services vaults) without relying on PowerShell.
  • Ensure screenshots and UI references are not exclusively Windows-oriented, and clarify if the portal experience is identical across platforms.
  • Regularly review documentation for platform-specific language and update to reflect Azure's cross-platform capabilities.
GitHub Create Pull Request
Backup Tutorial - Back up Azure Database for PostgreSQL server ...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing PowerShell scripts as the primary method for granting database privileges, mentioning PowerShell before alternatives like PG admin or PSQL, and lacking explicit Linux or cross-platform command-line examples. There are no bash, Linux shell, or platform-neutral instructions for privilege assignment, and the only script-based example is PowerShell, which is native to Windows environments.
Recommendations
  • Provide equivalent examples using Linux-native tools such as bash scripts, psql CLI commands, or instructions for using PG admin on Linux.
  • Present privilege assignment methods in a platform-neutral order, listing psql and PG admin before or alongside PowerShell.
  • Explicitly state cross-platform compatibility for all steps and scripts, and clarify how Linux users can perform each operation.
  • Include screenshots or walkthroughs for Linux environments where appropriate.
  • Add a dedicated section or callout for Linux users, summarizing the steps and tools available on Linux.
GitHub Create Pull Request
Backup Tutorial - Back Up SQL Server Databases to Azure ...-docs/blob/main/articles/backup/tutorial-sql-backup.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific components and patterns. All instructions and background processes assume the SQL Server VM is running Windows, with references to Windows-only extensions (AzureBackupWindowsWorkload), service accounts (NT Service\AzureWLBackupPluginSvc), and permissions models. There are no examples, instructions, or notes for Linux-based SQL Server VMs, nor are Linux tools or patterns mentioned. The documentation does not acknowledge or support SQL Server on Linux, and all technical details are Windows-centric.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server databases running on Linux-based Azure VMs, if supported.
  • Clarify whether the Azure Backup solution supports SQL Server on Linux VMs, and if not, provide alternative backup strategies or links to relevant documentation.
  • Mention Linux-specific requirements, such as service accounts, permissions, and extension installation steps, if applicable.
  • Include screenshots and walkthroughs for the Linux experience in the Azure portal or via CLI.
  • If only Windows is supported, state this clearly at the beginning of the tutorial to avoid confusion for Linux users.
GitHub Create Pull Request
Backup Use Archive tier .../blob/main/articles/backup/use-archive-tier-support.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits a moderate Windows bias. The Azure portal (GUI) instructions are Windows-centric, as the Azure portal is most commonly used on Windows environments, and the workloads discussed are all Azure VMs or databases running on Windows-based platforms (SQL Server, SAP HANA in Azure VMs). The PowerShell section is extensive and presented before the CLI section, with detailed step-by-step instructions and sample scripts, reinforcing a Windows-first approach. PowerShell, a Windows-native tool, is given prominence over the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, nor any mention of Linux-native tools or patterns, and the CLI section is less detailed than PowerShell. The documentation does not address Linux-specific backup scenarios or provide parity in example depth for Linux users.
Recommendations
  • Add explicit Linux shell (bash) examples for all CLI commands, including sample scripts for automation.
  • Include instructions for using Azure CLI on Linux, such as installation via apt/yum and running commands in bash.
  • Mention Linux-native tools and patterns for scripting and automation, such as cron jobs or shell scripts.
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including error handling and output parsing.
  • Add a section or notes addressing backup scenarios for Linux VMs and workloads, if supported.
  • Avoid assuming the Azure portal is only used on Windows; clarify cross-platform access and usage.
  • Balance the order of presentation so CLI and PowerShell are given equal prominence, or alternate their order.
GitHub Create Pull Request
Baremetal Infrastructure About Nutanix Cloud Clusters on Azure ...structure/workloads/nc2-on-azure/about-nc2-on-azure.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific benefits and tooling, such as Azure Hybrid Benefit for Windows and SQL Server, and free Extended Security Updates for Windows Server. These features are described in detail, including step-by-step instructions for requesting ESU keys for Windows VMs, while Linux equivalents are only briefly mentioned or omitted. There are no Linux-specific examples, instructions, or benefits highlighted, and Windows features are discussed first and in greater depth.
Recommendations
  • Include explicit examples and instructions for Linux workloads, such as how to leverage Azure Hybrid Benefit for Linux and supported distributions.
  • Provide parity in describing security update processes for Linux VMs, including how to manage updates and compliance in NC2 on Azure.
  • Add Linux-focused cost-saving opportunities and licensing details, similar to those provided for Windows.
  • Ensure that Linux and open source tooling (e.g., KVM, libvirt) are discussed with equal prominence as Windows tools and benefits.
  • Present Windows and Linux benefits side-by-side, rather than listing Windows features first and in greater detail.
GitHub Create Pull Request
Bastion Deploy Bastion:PowerShell ...ain/articles/bastion/bastion-create-host-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily focused on deploying Azure Bastion using PowerShell, with all code examples and step-by-step instructions provided only for PowerShell. The VM creation quickstart links and references are Windows-centric, and there are no equivalent Linux CLI or Bash examples. Although Azure CLI is mentioned as an alternative in a bullet list, it is not demonstrated or prioritized. Linux users are left without direct guidance or parity in deployment steps.
Recommendations
  • Add equivalent Azure CLI (bash) examples alongside PowerShell for all deployment steps.
  • Provide explicit Linux VM creation instructions and quickstart links, not just Windows.
  • Ensure that connection steps and port requirements are illustrated for both Windows (RDP) and Linux (SSH) with equal prominence.
  • Reorganize the documentation so that cross-platform options (PowerShell, Azure CLI, Portal) are presented together, rather than PowerShell-first.
  • Include notes or callouts for platform-specific differences, especially for users running Linux or macOS.
GitHub Create Pull Request
Bastion Working with VMs and NSGs in Azure Bastion ...s/azure-docs/blob/main/articles/bastion/bastion-nsg.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides only a PowerShell script for configuring NSG rules, which is a Windows-centric tool. There are no equivalent examples using Azure CLI, Bash, or other cross-platform tools commonly used on Linux/macOS. The exclusive use of PowerShell and lack of Linux-friendly instructions or parity examples indicate a bias toward Windows users and tooling.
Recommendations
  • Add equivalent Azure CLI (az network nsg rule create ...) examples for all NSG rule configurations.
  • Provide Bash script snippets for Linux/macOS users where appropriate.
  • Explicitly mention that PowerShell is available cross-platform, but also provide instructions for installing and using Azure CLI on Linux.
  • Consider reordering or balancing example sections so that Linux-friendly tools (Azure CLI, Bash) are presented alongside or before PowerShell.
  • Include notes or links to official Azure CLI documentation for NSG management.
GitHub Create Pull Request
Bastion About Azure Bastion configuration settings ...s/blob/main/articles/bastion/configuration-settings.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently listing Azure PowerShell (a Windows-centric tool) before Azure CLI in configuration tables, and by providing detailed PowerShell references while omitting equivalent Linux shell or Bash examples. There are no explicit Linux-specific instructions or examples, and the use of PowerShell as a primary automation method may alienate Linux users. The documentation does not mention Linux tools or patterns, nor does it provide parity in example commands for Linux environments.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for each configuration method.
  • List Azure CLI before or alongside PowerShell in tables to reflect cross-platform parity.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide links to installation guides for those platforms.
  • Include notes or sections for Linux administrators, highlighting any differences or considerations when configuring Azure Bastion from Linux environments.
  • Avoid assuming PowerShell as the default automation tool; clarify that both PowerShell and CLI are supported and cross-platform.
GitHub Create Pull Request
Bastion Connect to a Linux VM using SSH .../main/articles/bastion/bastion-connect-vm-ssh-linux.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page, while focused on connecting to Linux VMs, demonstrates a bias towards Windows tooling and patterns. References to creating and managing Azure Key Vault resources and secrets consistently point to PowerShell-based instructions and links, with no equivalent Linux shell (bash) or cross-platform CLI examples. The guidance for storing SSH keys in Azure Key Vault recommends PowerShell or Azure CLI, but only links to PowerShell instructions. There are no explicit Linux shell examples or links, and the documentation does not provide parity for Linux users in terms of command-line instructions or tooling references.
Recommendations
  • Add links and examples for creating and managing Azure Key Vault resources and secrets using Bash or Azure CLI on Linux.
  • Where PowerShell is mentioned, also mention and link to equivalent Linux shell or Azure CLI instructions.
  • Ensure all references to tooling (such as storing SSH keys) include both Windows and Linux approaches, with clear parity.
  • Include explicit Linux command-line examples for common operations, such as storing SSH keys in Key Vault, to support Linux users.
  • Review all external links to ensure they are not Windows/PowerShell-centric and provide alternatives for Linux environments.
GitHub Create Pull Request
Bastion Add scale units for host scaling: Azure portal ...s/blob/main/articles/bastion/configure-host-scaling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the only command-line alternative to the Azure portal, with no mention of Linux-native tools (e.g., Azure CLI or Bash scripting). The example and instructions are portal-based, which is cross-platform, but the only scriptable method highlighted is PowerShell, a Windows-centric tool. There are no Linux-specific examples or parity in command-line instructions.
Recommendations
  • Include Azure CLI instructions for host scaling alongside PowerShell, as Azure CLI is cross-platform and commonly used on Linux.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide parity in scriptable examples for both Windows (PowerShell) and Linux (Azure CLI/Bash).
  • Add links or references to Linux-friendly documentation or tutorials for configuring host scaling.
  • Review other related documentation to ensure Linux users are equally supported in automation and scripting scenarios.
GitHub Create Pull Request
Bastion Configure Bastion for Kerberos authentication - Azure portal ...ain/articles/bastion/kerberos-authentication-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page is heavily biased toward Windows environments. All examples, instructions, and templates assume Windows Server and Windows 10 VMs, with no mention of Linux equivalents. Kerberos configuration references only Windows documentation, and all automation uses PowerShell scripts and Windows-specific tools (e.g., Local Group Policy Editor, ADDSDeployment PowerShell module). There are no Linux VM deployment examples, nor guidance for configuring Kerberos authentication with Linux domain controllers or clients.
Recommendations
  • Add examples and instructions for deploying and configuring Kerberos authentication with Linux VMs (e.g., Ubuntu, CentOS) as both domain controllers and clients.
  • Provide equivalent Linux automation scripts (e.g., Bash, cloud-init) for domain join and Kerberos configuration.
  • Reference Linux Kerberos documentation (e.g., MIT Kerberos, Samba/Active Directory integration) alongside Windows resources.
  • Include guidance for verifying Kerberos authentication on Linux (e.g., using kinit, klist, and system logs).
  • Offer ARM template parameters or examples that allow selection of Linux images for domain controller and client roles.
GitHub Create Pull Request
Bastion Quickstart: Connect to a VM using Azure Bastion Developer: Azure portal ...ocs/blob/main/articles/bastion/quickstart-developer.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a mild Windows bias. Windows is mentioned first in several contexts, such as in the quickstart links for creating VMs and in the required inbound ports section. Keyboard shortcut examples are Windows-centric, and there is a focus on Windows tools and patterns (e.g., CTRL+ALT+END for Windows VMs, references to Windows client behavior). There are no explicit Linux command-line or SSH examples, and Linux-specific details are minimal.
Recommendations
  • Alternate the order of Windows and Linux references throughout the documentation to avoid always listing Windows first.
  • Provide Linux-specific examples and notes where relevant, such as SSH connection instructions, Linux keyboard shortcuts, and expected desktop/session differences.
  • Include Linux client behaviors and shortcuts for connecting to both Windows and Linux VMs, especially when discussing remote desktop or terminal access.
  • Ensure parity in troubleshooting and feature explanations for both Windows and Linux VM scenarios.
  • Add explicit examples or links for connecting to Linux VMs using Bastion Developer, including any differences in authentication or session management.
GitHub Create Pull Request
Bastion Quickstart: Deploy Azure Bastion automatically ...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows VM creation is mentioned before Linux in prerequisites, and Windows-specific details (such as port 3389 and keyboard shortcuts for Windows VMs) are given more prominence. There are no Linux-specific connection examples, troubleshooting tips, or equivalent keyboard shortcut guidance for Linux VMs. The documentation also references Windows tools and patterns (e.g., RDP, Windows keyboard shortcuts) without providing Linux alternatives.
Recommendations
  • Present Linux VM creation instructions before or alongside Windows instructions to avoid 'windows_first' bias.
  • Include Linux-specific connection details, such as SSH client usage, keyboard shortcuts, and troubleshooting tips for Linux VMs.
  • Provide parity in examples and guidance for both RDP (Windows) and SSH (Linux) connections, including screenshots or step-by-step instructions for Linux users.
  • Mention Linux tools and patterns (e.g., SSH clients, terminal usage) where Windows tools are referenced.
  • Add notes about differences in clipboard and keyboard shortcut behavior for Linux VMs and clients.
GitHub Create Pull Request
Bastion Create a shareable link for Azure Bastion ...zure-docs/blob/main/articles/bastion/shareable-link.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a web GUI most commonly used on Windows) and PowerShell cmdlets for permissions management, without mentioning or providing equivalent CLI examples for Linux users (such as Azure CLI or Bash). There are no Linux-specific instructions, nor are Linux tools or workflows (e.g., SSH from a Linux terminal, az CLI) discussed, even though Bastion supports SSH and RDP, both relevant to Linux environments.
Recommendations
  • Add Azure CLI and Bash examples for managing shareable links and permissions, alongside PowerShell.
  • Include instructions for connecting to VMs using SSH from Linux/macOS terminals, not just via the browser.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
  • Where PowerShell cmdlets are listed, also provide equivalent az CLI commands.
  • Add screenshots or walkthroughs showing Linux workflows (e.g., using a Linux desktop to access Bastion links).
GitHub Create Pull Request
Batch Use Microsoft Entra ID to authenticate Batch Management solutions .../blob/main/articles/batch/batch-aad-auth-management.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing examples and instructions for the .NET library and C# sample code, which are traditionally Windows-centric. The registration and configuration steps are described using the Azure portal UI, which is most commonly accessed from Windows environments. There are no Linux-specific instructions, examples, or references to cross-platform alternatives (such as Python, Java, or CLI usage on Linux). The documentation also refers to the 'Windows Azure Service Management API' and does not mention Linux tools or shell commands.
Recommendations
  • Include equivalent examples for Linux environments, such as using Azure CLI or PowerShell Core on Linux.
  • Provide sample code in cross-platform languages (e.g., Python, Java) alongside .NET/C#.
  • Explicitly mention that the Azure portal and MSAL libraries are accessible from Linux and macOS, and provide any necessary platform-specific notes.
  • Add instructions for registering applications and acquiring tokens using command-line tools (Azure CLI, Bash scripts) that work on Linux.
  • Reference Linux-compatible authentication flows and tools where appropriate.
GitHub Create Pull Request
Batch APIs and tools for developers ...zure-docs/blob/main/articles/batch/batch-apis-tools.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page shows moderate Windows bias. PowerShell cmdlets are listed first in the command-line tools section, and Windows-specific tools like Remote Desktop (RDP) are mentioned for node access without Linux equivalents (e.g., SSH). The Azure portal example references downloading RDP files for node login, which is a Windows-centric workflow. While Azure CLI and cross-platform tools are mentioned, Windows tools and patterns are prioritized or exclusively described in some areas.
Recommendations
  • List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform parity.
  • Include SSH-based instructions or references for logging into Linux compute nodes, alongside RDP for Windows nodes.
  • When describing troubleshooting (e.g., downloading stderr.txt), clarify that this applies to both Windows and Linux nodes.
  • Add explicit examples or tutorials for Linux environments, especially for node access and management.
  • Ensure that all tools and workflows described have Linux equivalents or alternatives mentioned where applicable.
GitHub Create Pull Request
Bastion File transfer via native client ...lob/main/articles/bastion/vm-upload-download-native.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting Windows RDP and native client instructions first, focusing on Windows-specific tools (MSTSC, right-click Copy/Paste), and omitting explicit Linux file transfer examples (e.g., no Linux RDP client instructions, no Linux GUI workflow). Linux instructions are referenced generically and only in the context of SSH/SCP, without concrete Linux-native client usage details.
Recommendations
  • Add explicit Linux file transfer examples, including step-by-step instructions using popular Linux RDP clients (e.g., Remmina, rdesktop, FreeRDP) for RDP-based transfer.
  • Provide screenshots or workflow descriptions for file transfer on Linux, similar to the Windows right-click Copy/Paste method.
  • Present Linux and Windows instructions in parallel sections, or alternate which platform is described first.
  • Mention macOS workflows and clients where relevant to ensure cross-platform parity.
  • Clarify which features or workflows are platform-specific and which are universal, to avoid implying Windows is the default or only supported platform.
GitHub Create Pull Request
Batch Create a Batch account in the Azure portal ...lob/main/articles/batch/batch-account-create-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several areas. The only command-line example provided for accepting marketplace terms uses PowerShell cmdlets, with no equivalent Azure CLI or Bash example for Linux users. References to command-line tooling (e.g., 'Batch PowerShell cmdlets') appear before Azure CLI in the list of management options. There are no explicit Linux-specific instructions or examples, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell cmdlets for all command-line operations, especially for accepting marketplace terms.
  • List Azure CLI management options before or alongside PowerShell cmdlets to avoid Windows-first ordering.
  • Explicitly mention Linux compatibility and provide guidance for Linux users where relevant.
  • Include screenshots or instructions that demonstrate usage from Linux environments, such as Azure Cloud Shell (Bash).
  • Review all command references to ensure Linux users are not required to use Windows-only tools.
GitHub Create Pull Request
Batch Deploy application packages to compute nodes ...blob/main/articles/batch/batch-application-packages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits a Windows bias by providing only Windows-centric code examples (e.g., C#/.NET, Windows VM images, Windows command lines), referencing Windows-specific tools (cmd.exe), and presenting Windows details before Linux equivalents. Linux-specific code samples, shell commands, and VM configuration examples are missing, and Linux environment variable usage is described only after Windows. The documentation does not offer parity in examples or guidance for Linux users.
Recommendations
  • Add Linux-specific code samples, including shell (bash) command lines for task execution.
  • Include examples of pool creation using Linux VM images (e.g., Ubuntu, CentOS) in addition to Windows.
  • Show how environment variables are used in Linux tasks, with sample bash scripts referencing the application package paths.
  • Present Windows and Linux instructions side-by-side or in parallel sections to ensure equal visibility.
  • Reference cross-platform tools and APIs, and clarify any OS-specific differences in application package deployment and usage.
  • Expand documentation to include .NET alternatives (e.g., Python SDK, REST API) with Linux-focused examples.
GitHub Create Pull Request
Batch Copy applications and data to pool nodes ...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns (e.g., .exe, .msi installers) without mentioning Linux equivalents. There are no examples or guidance for Linux application packaging or installation methods, and Windows terminology appears first and exclusively in relevant sections.
Recommendations
  • Include examples for Linux application and data deployment, such as using .sh scripts, .deb/.rpm packages, or tarballs.
  • Mention Linux installation patterns (e.g., using apt, yum, or custom shell scripts) alongside Windows (.msi/.exe) references.
  • Provide guidance on handling Linux-specific scenarios, such as file permissions, symbolic links, and environment setup.
  • Ensure that terminology and examples are balanced between Windows and Linux, or presented in parallel where appropriate.
GitHub Create Pull Request
Batch Autoscale compute nodes in an Azure Batch pool ...cs/blob/main/articles/batch/batch-automatic-scaling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways: Windows-based VM images are used first and exclusively in .NET examples, with no Linux equivalent shown; PowerShell and Windows tools are referenced before or instead of cross-platform or Linux alternatives; C#/.NET examples dominate code samples, with limited Python coverage and no Linux shell/CLI examples; and there is a lack of explicit Linux-focused instructions or parity in SDK usage and pool configuration examples.
Recommendations
  • Provide Linux VM configuration examples in .NET code samples, e.g., using Ubuntu or other Linux images, alongside Windows examples.
  • Include Linux shell (bash) and Azure CLI examples for pool creation and autoscale configuration, not just PowerShell or .NET.
  • Ensure that references to PowerShell are balanced with equivalent bash/CLI instructions, and mention Linux tools where appropriate.
  • Add explicit instructions and code samples for enabling autoscale on Linux pools using .NET, Python, and CLI.
  • Present Windows and Linux options side-by-side in tables and code blocks, rather than Windows-first or Windows-only.
  • Reference cross-platform SDKs and tools (e.g., Azure CLI) before platform-specific ones, or at least equally.
GitHub Create Pull Request
Batch Use Azure Pipelines to build and deploy an HPC solution ...ocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a clear Windows bias. The example solution exclusively deploys Windows software (FFmpeg for Windows) on Windows-based Batch nodes, with ARM templates specifying Windows images and node agents. The repository setup and build pipeline only reference the Windows version of FFmpeg. The agent pool for Azure Pipelines is set to 'windows-latest', and Azure CLI tasks are configured to use PowerShell Core, a Windows-centric scripting environment. There are no Linux equivalents or examples provided, and Linux support is only mentioned briefly in a note, without actionable guidance.
Recommendations
  • Provide parallel examples for deploying Linux software on Linux-based Batch nodes, including ARM template snippets for Linux VM images and node agents.
  • Include instructions for downloading and packaging the Linux version of FFmpeg, and update repository setup steps to show both Windows and Linux application folders.
  • Demonstrate how to set the agent pool to 'ubuntu-latest' or another Linux agent in Azure Pipelines, with corresponding YAML and release pipeline steps.
  • Show Azure CLI tasks using Bash scripts in addition to PowerShell Core, and clarify cross-platform compatibility.
  • Add explicit guidance and code samples for users who wish to deploy HPC solutions on Linux, ensuring equal visibility and parity with Windows instructions.
GitHub Create Pull Request
Batch Task runtime environment variables ...cles/batch/batch-compute-node-environment-variables.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and patterns (e.g., cmd.exe, drive letters, backslash paths) are mentioned first or exclusively in several places. Examples often use Windows conventions before Linux equivalents, and some explanations (such as app package environment variable naming) provide more detail for Windows than Linux. Linux-specific tools and patterns are sometimes mentioned secondarily or with less detail, and some examples (e.g., directory postfix tables) use Windows-style paths without Linux equivalents.
Recommendations
  • Present Linux and Windows examples side-by-side, with equal detail and prominence.
  • Ensure all tables and examples include both Windows and Linux path formats (e.g., use both backslash and forward slash, drive letters and mount points).
  • When describing environment variable naming conventions, provide parallel details for both platforms.
  • Avoid using Windows tools (cmd.exe, drive letters) as the default or primary example; alternate or combine with Linux tools (sh, mount points).
  • Include Linux-specific notes where Windows-specific notes are given (e.g., for app package naming, directory structures).
  • Review all examples and tables for parity, ensuring Linux users can easily find relevant information.
GitHub Create Pull Request
Batch Use ephemeral OS disk nodes for Azure Batch pools ...b/main/articles/batch/create-pool-ephemeral-os-disk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the sole example for programmatically querying VM capabilities, without mentioning Linux alternatives such as Azure CLI or Bash. The mention of PowerShell comes before any code examples, and no Linux-specific tools or command-line patterns are provided. The SDK code examples themselves are cross-platform (Python and C#), but the operational guidance favors Windows tooling.
Recommendations
  • Add Azure CLI and Bash examples for querying VM capabilities, alongside the PowerShell example.
  • Explicitly mention that both Windows and Linux users can use the SDK code samples, and provide guidance for installing and running them on Linux.
  • Where PowerShell is referenced, include equivalent commands for Linux shells (e.g., Bash, zsh) to ensure parity.
  • Review other operational instructions to ensure Linux tools and workflows are represented equally and not as an afterthought.
GitHub Create Pull Request
Batch Persist job and task output to a data store ...ure-docs/blob/main/articles/batch/batch-task-output.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates bias towards Windows by providing examples and references that are Windows-centric, such as referencing Windows executables in custom file movement solutions (e.g., 'doMyWork.exe && uploadMyFilesToSql.exe'), and omitting explicit Linux or cross-platform examples. The sample project linked is C#-based, which is most commonly used on Windows. There are no Linux shell or cross-platform scripting examples, nor are Linux-specific tools or patterns mentioned.
Recommendations
  • Add explicit Linux and cross-platform examples for custom file movement, such as using bash scripts (e.g., './doMyWork.sh && ./uploadMyFilesToSql.sh') or Python scripts.
  • Mention Linux tools and patterns for file movement, such as using 'scp', 'rsync', or Azure CLI commands.
  • Provide sample projects or code snippets in languages commonly used on Linux (e.g., Python, bash) alongside C#.
  • Clarify that the guidance applies to both Windows and Linux compute nodes, and highlight any platform-specific considerations.
  • Ensure that references to executables or scripts are platform-neutral, or provide parallel examples for both Windows and Linux.
GitHub Create Pull Request
Batch Azure Quickstart - Create a Batch account - Azure Resource Manager template ...docs/blob/main/articles/batch/quick-create-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by primarily describing deployment via the Azure portal (which is most commonly used on Windows), and referencing Azure PowerShell as an alternative before mentioning Azure CLI or REST API. There are no explicit Linux or cross-platform command-line examples, and the deployment instructions focus on GUI-based steps typical of Windows environments. Linux-specific tools or CLI examples are missing.
Recommendations
  • Add explicit Azure CLI examples for template deployment, including commands for Linux/macOS users.
  • Present deployment options in a cross-platform order (e.g., Azure CLI before PowerShell, or side-by-side).
  • Include screenshots or instructions for using the Azure CLI on Linux/macOS.
  • Clarify that the Azure portal and CLI tools are available on all major operating systems.
  • Provide links to Linux-specific documentation or quickstarts where relevant.
GitHub Create Pull Request
Batch Persist output data to Azure Storage with .NET File Conventions library ...n/articles/batch/batch-task-output-file-conventions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing .NET/C# code samples, referencing Windows-specific tools (Visual Studio), and omitting Linux or cross-platform examples for persisting output data to Azure Storage with Azure Batch. There are no mentions of Linux development environments, alternative languages, or command-line workflows, and the instructions assume a Windows-centric development setup.
Recommendations
  • Add equivalent code samples for Linux environments, such as using .NET Core on Linux, or other supported languages (Python, Java).
  • Include instructions for setting up and running the sample project on Linux or macOS, such as using VS Code, JetBrains Rider, or command-line tools.
  • Reference cross-platform tools and editors, not just Visual Studio.
  • Provide guidance for developers using Linux containers or running Batch tasks on Linux nodes.
  • Clarify that the File Conventions standard can be implemented in any language and provide links or samples for non-.NET implementations.
GitHub Create Pull Request
Batch Create a Batch pool with specified public IP addresses ...docs/blob/main/articles/batch/create-pool-public-ip.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation displays Windows bias by listing Azure PowerShell as a method for creating public IP addresses alongside the Azure portal and CLI, with PowerShell mentioned explicitly and before any Linux-specific tools. No Linux shell or scripting examples (e.g., Bash) are provided, and the use of PowerShell is highlighted without equivalent Linux command-line alternatives. The documentation does not offer parity in examples or tooling for Linux users.
Recommendations
  • Add explicit Bash shell examples for creating public IP addresses using Azure CLI, including sample commands.
  • Reorder the list of public IP creation methods to mention cross-platform tools (Azure CLI) before platform-specific ones (PowerShell).
  • Include notes or guidance for Linux users on how to install and use Azure CLI for these tasks.
  • If PowerShell is mentioned, clarify that it is available cross-platform, or provide equivalent Linux-native commands.
  • Ensure future examples and instructions are platform-neutral or provide both Windows and Linux variants.
GitHub Create Pull Request
Batch Container workloads on Azure Batch ...ain/articles/batch/batch-docker-container-workloads.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Windows VM images and considerations are discussed before Linux equivalents in several sections, and Windows-specific tools, paths, and behaviors (e.g., C:\ProgramData\Docker, c:\app\myApp.exe) are referenced in examples and explanations. Most code samples use C# and Python, but all container configuration and task examples use Linux images and commands, with only one C# task example using a Windows path. There is a lack of explicit Linux shell command examples for troubleshooting and task execution, and Windows-specific limitations and behaviors are described in more detail than Linux equivalents.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, with equal detail and order.
  • Provide explicit Linux shell command examples for troubleshooting and task execution, not just C# or Python code.
  • Include Windows PowerShell or CMD examples for container configuration and task execution, especially in troubleshooting sections.
  • Clarify Linux-specific limitations and behaviors (e.g., working directory, file paths, environment variables) to match the detail given for Windows.
  • Avoid referencing Windows tools and paths (e.g., C:\ProgramData\Docker, c:\app\myApp.exe) without providing Linux equivalents (e.g., /var/lib/docker, /app/myApp.sh).
  • When discussing VM images, alternate the order of Windows and Linux, or present them together for parity.
GitHub Create Pull Request
Batch Use multi-instance tasks to run MPI applications ...tDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All code samples, setup instructions, and tooling references are focused on Windows environments, specifically using MS-MPI, Batch .NET, and Visual Studio. Windows-specific commands (cmd, .exe files) and resource files are used throughout, with no equivalent Linux code samples or step-by-step instructions. Linux and Intel MPI are mentioned only in passing, and Linux-specific guidance is relegated to notes or external links.
Recommendations
  • Add parallel Linux-focused code samples using Python or Bash, demonstrating Intel MPI setup and execution.
  • Include explicit instructions for creating pools with Linux VM images, including sample configuration code.
  • Provide StartTask examples for installing Intel MPI on Linux nodes, using shell commands and package managers.
  • Show application and coordination command lines for Linux (e.g., using mpiexec, referencing shell scripts, using $AZ_BATCH_TASK_SHARED_DIR).
  • Offer a Linux-based walkthrough, including building and packaging an MPI application (e.g., with gcc and mpicc), uploading resources, and running tasks.
  • Reference Linux development tools (e.g., VS Code, gcc, Python) alongside Visual Studio.
  • Ensure that both Windows and Linux scenarios are presented side-by-side or in separate sections for parity.
GitHub Create Pull Request
Cloud Services Extended Support List of updates applied to the Azure Guest OS | Microsoft Docs ...es-guestos-microsoft-security-response-center-releases.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_only ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
This documentation page exclusively lists updates for the Azure Guest OS, which are all Windows-based. There is no mention of Linux distributions, Linux update mechanisms, or Linux security advisories. All update references, KB articles, and product categories are specific to Windows technologies (e.g., .NET Framework, Internet Explorer, Windows Security, Servicing Stack Update, Microcode, etc.). There are no Linux equivalents, examples, or even an acknowledgement of Linux-based guest OS options. The documentation is entirely Windows-centric.
Recommendations
  • Add a parallel section or a separate page listing updates and advisories for Linux-based Azure guest OS images, including references to upstream security advisories, distribution-specific update mechanisms (e.g., apt, yum, zypper), and kernel/security patching policies.
  • Clearly indicate at the top of the page that the content is specific to Windows guest OS images, and provide a link to Linux guest OS update documentation if available.
  • Include a comparison or cross-reference table that helps users of both Windows and Linux guest OSes understand the update/patching lifecycle and mechanisms for each platform.
  • If Azure supports both Windows and Linux guest OSes, ensure that documentation parity is maintained by providing equivalent update tracking and guidance for Linux images.
GitHub Create Pull Request
Cloud Services Extended Support Learn about the latest Azure Guest OS Releases | Microsoft Docs ...tended-support/cloud-services-guestos-update-matrix.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively covers Windows Server-based Guest OS families (Windows Server 2022, 2019, 2016, 2012 R2, 2012, 2008 R2 SP1) and related .NET Framework versions, with no mention of Linux-based Guest OSes, Linux tools, or cross-platform considerations. All examples, configuration strings, and recommendations are Windows-centric, and there are explicit references to Windows development tools (Visual Studio, Azure Workload). There are no Linux equivalents, examples, or guidance provided.
Recommendations
  • Add information about Linux-based Guest OS releases if supported by Azure Cloud Services, including versioning, update cycles, and configuration strings.
  • Include examples and guidance for managing and updating Linux-based Cloud Service roles, if available.
  • Reference Linux development tools (such as VS Code, JetBrains Rider, or command-line utilities) alongside Visual Studio.
  • Clarify in the introduction whether Linux-based Cloud Services are supported or not, and provide links to relevant documentation if they are.
  • If Linux is not supported for Cloud Services (classic), explicitly state this to avoid confusion for cross-platform users.
GitHub Create Pull Request
CDN What is a content delivery network? - Azure ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary CLI management tool for Azure CDN endpoints, without mentioning Linux-friendly alternatives such as Azure CLI or Bash. The 'Next steps' section lists PowerShell before other automation options and omits explicit Linux or cross-platform command-line examples, which may disadvantage Linux users or those preferring non-Windows environments.
Recommendations
  • Include Azure CLI examples alongside PowerShell for managing CDN endpoints, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that management tasks can be performed from Linux, macOS, and Windows, and provide links to relevant documentation for each platform.
  • Add Bash script examples or references for common CDN management tasks.
  • Reorder or parallelize tool mentions so that PowerShell and Azure CLI are presented together, rather than PowerShell first.
  • Clarify that the Azure portal is accessible from any OS with a web browser.
GitHub Create Pull Request
Cloud Services Extended Support Deploy Azure Cloud Services (extended support) - ARM template ...les/cloud-services-extended-support/deploy-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently referencing Azure PowerShell for resource creation and deployment steps, omitting equivalent Azure CLI or Bash examples. Windows-centric tools such as Visual Studio and RDP extensions are mentioned, with no discussion of Linux alternatives or cross-platform tooling. The use of Windows-specific publishers and extension types further reinforces the bias. Linux users are left without guidance for performing these tasks on their platform.
Recommendations
  • Add Azure CLI examples for all resource creation and deployment steps alongside PowerShell commands.
  • Mention Bash scripting and provide sample commands for uploading files and managing resources.
  • Include references to cross-platform tools (e.g., VS Code, Azure CLI) in addition to Visual Studio.
  • Discuss Linux-compatible remote access options (e.g., SSH) and extensions, not just RDP.
  • Ensure that instructions for certificate management and key vault access include CLI and Bash alternatives.
  • Explicitly state that all steps can be performed on Linux and macOS, and provide links to relevant documentation.
GitHub Create Pull Request
Cloud Services Extended Support Prerequisites for deploying Cloud Services (extended support) ...cloud-services-extended-support/deploy-prerequisite.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is frequently mentioned as a primary automation tool, often listed before or alongside Azure CLI and ARM templates. Visual Studio is referenced as a deployment tool, but Linux alternatives (such as VS Code or CLI-only workflows) are not discussed. There are no explicit Linux shell examples, and the use of Windows-centric terminology (e.g., PowerShell, Visual Studio) may imply a preference for Windows environments.
Recommendations
  • Include Azure CLI examples and links wherever PowerShell is mentioned, and ensure CLI is listed before or alongside PowerShell.
  • Mention cross-platform editors (such as VS Code) and CLI-based deployment workflows as alternatives to Visual Studio.
  • Add explicit Linux shell (bash) examples for common tasks, such as creating resources or deploying services.
  • Clarify that all configuration and deployment steps can be performed from Linux, macOS, or Windows environments.
  • Review related content and ensure that Linux-compatible tools and workflows are equally represented.
GitHub Create Pull Request
Batch Use compute-intensive Azure VMs with Batch ...n/articles/batch/batch-pool-compute-intensive-sizes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux examples and tables, but Windows-specific tools and patterns (e.g., PowerShell, Remote Desktop, Microsoft MPI, Windows Server SKUs) are described in more detail and sometimes appear before Linux equivalents. The Windows example for installing GPU drivers is more step-by-step and uses Windows-centric tooling (cmd, MSI installers), while the Linux example is less detailed and omits command-line specifics. The Microsoft MPI example is only given for Windows, with no Linux MPI example. Windows pool configuration options and deprecated features are discussed in more depth than Linux equivalents.
Recommendations
  • Provide equally detailed, step-by-step Linux examples for installing drivers and configuring pools, including command-line instructions (e.g., bash scripts, apt commands).
  • Include a Linux MPI example (e.g., using Intel MPI or OpenMPI) with sample installation and pool configuration steps.
  • Mention Linux tools and patterns (e.g., SSH, bash, Linux package managers) wherever Windows tools (PowerShell, RDP, MSI installers) are referenced.
  • Ensure that Linux and Windows examples are presented in parallel, with neither platform consistently prioritized or described first.
  • Expand Linux pool configuration options and troubleshooting guidance to match the depth provided for Windows.
GitHub Create Pull Request
Batch Use the Azure Compute Gallery to create a custom image pool ...zure-docs/blob/main/articles/batch/batch-sig-images.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates several forms of Windows bias. Windows and Windows-specific tools (PowerShell, RDP) are mentioned before or more prominently than their Linux equivalents. Examples and instructions often reference Windows first, and PowerShell is listed as a primary method for discovering supported images, with Linux alternatives (Azure CLI) mentioned second. The portal workflow emphasizes RDP for Windows and only briefly mentions SSH for Linux. There are missing Linux-specific examples for some steps, such as mounting and formatting disks, and the documentation does not provide parity in command-line or scripting examples for Linux users.
Recommendations
  • Ensure that Linux-specific instructions and examples (e.g., mounting disks, SSH usage, CLI commands) are presented alongside or before Windows equivalents.
  • Provide Bash shell and Linux CLI examples wherever PowerShell is used, and avoid listing PowerShell first unless there is a technical reason.
  • Expand portal instructions to equally detail SSH connection steps for Linux, including troubleshooting and verification.
  • Include explicit Linux-focused guidance for preparing VMs, such as commands for formatting and mounting disks, and avoiding Windows-centric terminology.
  • Review all SDK code samples to ensure they are OS-agnostic or provide both Windows and Linux variants where OS-specific steps are required.
GitHub Create Pull Request
Batch Persist output data to Azure Storage with Batch service API ...cs/blob/main/articles/batch/batch-task-output-files.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows bias: all code samples use C# and Windows command syntax (cmd.exe), with no Linux shell equivalents provided. Visual Studio is referenced as the development environment, and .NET libraries are exclusively used. Linux usage is only briefly mentioned as a note to change path delimiters, but no Linux-specific code or workflow is shown. There are no examples using Bash, Linux tools, or cross-platform SDKs, and the documentation does not address how to persist output from Linux-based tasks in detail.
Recommendations
  • Provide equivalent code samples using Bash shell commands for Linux tasks, demonstrating how to generate output files and persist them.
  • Include examples using cross-platform SDKs (e.g., Azure SDK for Python, Java, or Node.js) to show how to interact with Azure Storage from non-Windows environments.
  • Add instructions for setting up and running sample projects on Linux (e.g., using VS Code, JetBrains Rider, or CLI tools), not just Visual Studio.
  • Explicitly document any differences in file path handling, environment setup, and authentication for Linux pools.
  • Reference Linux tools (e.g., tar, zip, Bash scripting) for consolidating output files and troubleshooting.
  • Ensure that all major steps (creating containers, generating SAS tokens, uploading files) have both Windows and Linux examples.
GitHub Create Pull Request
Cloud Services Extended Support Migrate cloud services not in a virtual network to a virtual network .../cloud-services-extended-support/non-vnet-migration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page primarily describes migration steps using the Azure portal, which is platform-agnostic but typically more familiar to Windows users. In the 'Next steps' section, PowerShell is mentioned explicitly as a migration method, with no reference to Linux-native tools (such as Azure CLI or Bash scripts). There are no examples or instructions for Linux users or cross-platform command-line tools, and the only command-line migration path highlighted is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Add migration instructions using Azure CLI, including example commands for Linux/macOS users.
  • Include references to Bash scripting or other cross-platform automation methods alongside PowerShell.
  • Ensure that command-line examples are provided for both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash).
  • Clarify that the Azure portal is accessible from any OS and provide screenshots or notes relevant to non-Windows environments if there are differences.
GitHub Create Pull Request
Cloud Services Extended Support Available States for Azure Cloud Services (extended support) ...ain/articles/cloud-services-extended-support/states.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page displays Windows bias in the 'Next steps' section, where deployment options are listed as Azure portal, PowerShell, Template, and Visual Studio. PowerShell and Visual Studio are Windows-centric tools, and PowerShell is mentioned before any Linux-friendly alternatives (such as Azure CLI or Bash). There are no explicit Linux or cross-platform examples or tools referenced, and the documentation does not mention Azure CLI, which is commonly used on Linux and macOS.
Recommendations
  • Add deployment instructions and links for Azure CLI, which is cross-platform and widely used on Linux.
  • Include Bash or shell script examples where relevant.
  • List cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools like PowerShell and Visual Studio.
  • Explicitly mention Linux/macOS compatibility where possible, and provide parity in examples and tooling.
GitHub Create Pull Request
Cloud Services Extended Support Swap or switch deployments in Azure Cloud Services (extended support) .../cloud-services-extended-support/swap-cloud-service.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows PowerShell commands (Get-AzRole) as the only CLI example for checking instance status, listing PowerShell and Visual Studio as deployment options, and omitting equivalent Linux CLI (Azure CLI) or cross-platform scripting examples. Windows tools and patterns are mentioned exclusively or before Linux alternatives, and there are no Linux-specific instructions or parity in examples.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, especially for checking instance status and deployment management.
  • Explicitly mention Linux and macOS support where relevant, and provide instructions or screenshots from those platforms.
  • List cross-platform deployment options (such as Azure CLI and ARM templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
  • Ensure that all code samples and walkthroughs are usable on both Windows and Linux, or provide platform-specific sections as needed.
  • Include troubleshooting and operational guidance for Linux users, not just Windows/PowerShell users.
GitHub Create Pull Request
Cloud Shell Predictive IntelliSense in Azure Cloud Shell ...les/cloud-shell/cloud-shell-predictive-intellisense.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on PowerShell and its modules (PSReadLine, Az.Tools.Predictor), with all examples and instructions given in PowerShell syntax. There is no mention of Bash or Linux shell equivalents, nor any guidance for users who may prefer or require Bash in Azure Cloud Shell. The documentation assumes the use of PowerShell-specific tools and patterns, which may exclude or confuse Linux/Bash users.
Recommendations
  • Add equivalent instructions and examples for Bash users in Azure Cloud Shell, including how to enable, configure, or disable predictive features (if available) in Bash.
  • Explicitly state that the features described are specific to PowerShell, and clarify what options exist for Bash users.
  • Provide links or references to documentation about Bash shell customization and prediction features, if any.
  • Consider including a comparison table showing feature parity (or lack thereof) between PowerShell and Bash in Azure Cloud Shell.
  • Ensure that introductory sections acknowledge both PowerShell and Bash as supported shells in Azure Cloud Shell.
GitHub Create Pull Request
Batch Update pool properties ...ob/main/articles/batch/batch-pool-update-properties.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by providing a C# SDK example that exclusively uses a Windows VM image (MicrosoftWindowsServer) and node agent SKU for Windows. There are no examples or references for updating pools with Linux VM images or Linux node agent SKUs. Additionally, the examples and property values are Windows-centric, and there is no parity shown for Linux scenarios.
Recommendations
  • Add equivalent examples for updating pools with Linux VM images (e.g., Ubuntu, CentOS) and Linux node agent SKUs.
  • Explicitly mention both Windows and Linux options when discussing VM image configuration and pool properties.
  • Provide sample code snippets for Linux scenarios (e.g., using a Linux VM image in the C# SDK example).
  • Ensure REST API examples include both Windows and Linux property values.
  • Reference Linux-specific documentation or considerations where relevant.
GitHub Create Pull Request
Batch Storage and data movement for rendering ...rticles/batch/batch-rendering-storage-data-movement.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides more detailed examples and instructions for Windows environments, especially for mounting Azure Files shares and copying files with azcopy. Windows-specific tools and commands (cmdkey, net use) are shown with explicit examples, while equivalent Linux instructions (e.g., mounting Azure Files via SMB on Linux) are missing. The azcopy examples use Windows-style syntax and parameters, and Linux equivalents are not provided. The Azure Files section is focused on Windows, with no mention of Linux mounting procedures or examples.
Recommendations
  • Add explicit Linux examples for mounting Azure Files shares (e.g., using mount.cifs or SMB on Linux).
  • Provide azcopy command examples using Linux syntax and parameters, including shell usage.
  • Include Linux equivalents for Windows-specific tools (e.g., alternatives to cmdkey and net use for credential management and mounting).
  • Ensure that instructions and examples for both platforms are presented in parallel, or at least mention Linux options where Windows tools are discussed.
  • Add sample job/task configuration snippets for Linux environments, similar to the detailed Windows examples.
GitHub Create Pull Request
Batch Create task dependencies to run tasks ...cs/blob/main/articles/batch/batch-task-dependencies.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias by exclusively providing examples that use Windows command-line tools (cmd.exe, echo), with no mention or examples for Linux shells or commands. All code snippets use Windows-specific patterns, and there is no guidance for users running Batch tasks on Linux nodes. The documentation implicitly assumes a Windows environment, omitting Linux equivalents and cross-platform considerations.
Recommendations
  • Add Linux shell examples (e.g., bash, sh) alongside Windows cmd.exe examples for all code snippets.
  • Explicitly mention that Azure Batch supports both Windows and Linux compute nodes, and clarify any platform-specific behaviors.
  • Provide guidance on writing cross-platform tasks, including how to specify commands for Linux nodes (e.g., using '/bin/bash -c' instead of 'cmd.exe /c').
  • Include notes or tables comparing Windows and Linux task configuration patterns.
  • Reference documentation or samples for Batch usage on Linux, and link to relevant resources.
GitHub Create Pull Request
Batch Provision a pool with Auto OS Upgrade ...-docs/blob/main/articles/batch/batch-upgrade-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias by exclusively providing Windows-based examples in both the REST API and SDK (C#) sections. The image references, node agent SKUs, and configuration properties are all tailored to Windows (e.g., 'MicrosoftWindowsServer', 'batch.node.windows amd64', 'windowsConfiguration'). There are no Linux equivalents or examples, nor is there mention of Linux-specific configuration options or agent SKUs. Windows terminology and tools are used throughout, with no parity for Linux users.
Recommendations
  • Add Linux-based examples for both REST API and SDK sections, including image references (e.g., 'Canonical', 'UbuntuServer'), node agent SKUs (e.g., 'batch.node.ubuntu 20.04'), and relevant configuration properties.
  • Include documentation and guidance for configuring pools with Linux OS images, such as specifying 'linuxConfiguration' in the pool definition.
  • Mention Linux-specific considerations, such as patching and upgrade mechanisms, and clarify any differences in upgrade behavior between Windows and Linux pools.
  • Ensure that both Windows and Linux options are presented side-by-side or in parallel, rather than Windows-first or Windows-only.
  • Review and update FAQs and requirements to include Linux scenarios and terminology.
GitHub Create Pull Request
Communication Services Teams controls for Teams external user ...ervices/concepts/interop/guest/teams-administration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by consistently referencing PowerShell modules and cmdlets for configuration and policy management, listing 'Teams Admin Center or PowerShell' as the primary tools for administration, and linking to PowerShell documentation. There are no examples or mentions of equivalent Linux tools, CLI commands, or cross-platform alternatives for managing Teams settings. The documentation assumes the administrator is using Windows-based tools and does not provide guidance for Linux users.
Recommendations
  • Include cross-platform CLI examples (e.g., Azure CLI, Microsoft Graph API) for all administrative tasks currently shown with PowerShell.
  • Explicitly mention which tools are available on Linux/macOS and provide installation or usage instructions for those platforms.
  • Where PowerShell is referenced, note that PowerShell Core is available on Linux and macOS, and provide examples for those environments.
  • Add links to Microsoft Graph API documentation for policy and configuration management as an alternative to PowerShell.
  • Ensure that administrative workflows are described in a platform-neutral way, or provide parallel instructions for both Windows and Linux users.
GitHub Create Pull Request
Batch Run tasks under user accounts ...e-docs/blob/main/articles/batch/batch-user-accounts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits several forms of Windows bias. Windows-specific tools and APIs (such as Windows Data Protection API and RDP) are mentioned before or more prominently than their Linux equivalents. Code examples often use Windows-centric commands (e.g., 'cmd /c echo hello') and the .NET example for named user accounts is explicitly labeled as 'Windows' and appears before the Linux equivalent. There is a lack of parity in examples for Linux-specific scenarios (e.g., no Linux shell command examples for running tasks, limited discussion of Linux security tools). Windows terminology and patterns are introduced first or exclusively in several sections.
Recommendations
  • Provide Linux shell command examples (e.g., using bash/sh) alongside Windows 'cmd' examples for running tasks.
  • Mention Linux tools and APIs (such as GnuPG, OpenSSL, or native Linux file permissions) where Windows-specific tools like DPAPI are referenced.
  • Ensure that Linux and Windows examples are presented with equal prominence and in parallel, rather than Windows first.
  • Include more Linux-specific scenarios and best practices, such as SELinux/AppArmor, SSH key management, and Linux file sharing.
  • Where possible, use cross-platform language in code samples and documentation, or explicitly note differences between platforms.
  • Add explicit guidance for configuring user accounts and permissions on Linux, including security considerations unique to Linux environments.
GitHub Create Pull Request
Batch Best practices .../azure-docs/blob/main/articles/batch/best-practices.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (e.g., PowerShell) are mentioned before or more prominently than Linux equivalents in several places, such as for discovering image EOL dates and preparing data disks. Windows examples (PowerShell) are provided in detail, while Linux examples are less frequent or less detailed. Some guidance is Windows-centric (directory junctions, Windows Services, user/group names) and appears before or in more detail than Linux alternatives. In some cases, Linux examples or commands are missing or less emphasized.
Recommendations
  • Ensure that Linux examples and tools (e.g., Bash, CLI, system utilities) are provided alongside Windows/PowerShell examples, with equal detail and prominence.
  • When mentioning tools for tasks (e.g., listing supported images/SKUs), list Azure CLI and Linux-native methods before or alongside PowerShell, not after.
  • Provide Linux-specific troubleshooting and best practice sections where Windows-specific advice is given (e.g., file cleanup, service management).
  • Avoid Windows-first ordering in lists and examples; alternate or group by OS where possible.
  • Where Windows-specific artifacts (users/groups, directory junctions) are discussed, ensure Linux equivalents are also described.
  • Expand Linux guidance for areas like disk preparation, log collection, and service management to match the depth of Windows coverage.
GitHub Create Pull Request
Batch Use extensions with Batch pools ...ocs/blob/main/articles/batch/create-pool-extensions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides parity between Linux and Windows in listing supported extensions and example payloads for both platforms. However, there is a slight bias toward Windows in the number of Windows-only extensions listed (e.g., Antimalware, Diagnostics, DSC, multiple GPU drivers), and some extension types (like Diagnostics and DSC) are only available for Windows. The troubleshooting section does not provide Linux-specific log file locations or commands, and there are no Linux shell or command-line examples (e.g., Bash, SSH) for interacting with extensions or troubleshooting, whereas Windows tools and patterns (such as certificateStoreLocation: LocalMachine) are mentioned. The Application Health section describes a generic HTTP server setup but does not provide Linux-specific guidance or examples.
Recommendations
  • Add Linux-specific troubleshooting steps, including log file locations and example commands for viewing logs (e.g., using journalctl, tail, or cat).
  • Provide shell/Bash examples for interacting with extensions, retrieving status, and troubleshooting on Linux nodes.
  • Ensure that extension documentation links are balanced, and highlight Linux equivalents where only Windows tools are mentioned (e.g., for Diagnostics, DSC, Antimalware).
  • If certain extensions are Windows-only, explicitly state this and suggest Linux alternatives or workarounds.
  • Include examples of using SSH to connect to Linux nodes for troubleshooting, alongside any Windows RDP/PowerShell guidance.
GitHub Create Pull Request
Batch Jobs and tasks in Azure Batch .../azure-docs/blob/main/articles/batch/jobs-and-tasks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation generally presents Windows-specific tools and patterns before or more prominently than Linux equivalents. For example, in the section about invoking shells for task command lines, the Windows example (cmd.exe) is shown first, and in the start task section, Windows-specific tools like 'robocopy', 'MSI', and 'setup.exe' are mentioned exclusively. There is also a lack of parity in tool examples for Linux (e.g., no mention of 'cp', 'tar', or 'sh' for similar operations), and Windows environment variable syntax is listed before Linux. While Linux is acknowledged, the documentation tends to default to Windows-first explanations and tool references.
Recommendations
  • Provide Linux tool examples alongside Windows ones, such as mentioning 'cp' or 'rsync' in addition to 'robocopy', and '.sh' scripts in addition to '.exe' installers.
  • Alternate the order of Windows and Linux examples to avoid always listing Windows first.
  • Include explicit Linux shell command examples (e.g., using 'tar' for unzipping archives) where only Windows tools are currently mentioned.
  • When describing environment variable syntax, present both Windows (%VAR%) and Linux ($VAR) forms together or alternate their order.
  • Where possible, use cross-platform language and avoid assuming Windows as the default operating system.
GitHub Create Pull Request
Batch Provision a pool in a virtual network ...docs/blob/main/articles/batch/batch-virtual-network.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias. It references Windows-specific concepts and tools (e.g., RDP, port 3389) before Linux equivalents (SSH, port 22) in several places, and mentions Azure PowerShell as a primary method for creating resources before the Azure CLI. There are no explicit Linux command-line examples or references to Linux-native tooling, and remote access instructions focus on Windows (RDP) before Linux (SSH).
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is listed first (e.g., mention SSH/port 22 before RDP/port 3389 in some sections).
  • Include explicit Azure CLI examples for all resource creation steps, not just mention it as an option.
  • Add Linux-specific guidance for remote access, such as SSH key setup and firewall configuration.
  • Reference Linux-native tools and patterns (e.g., bash scripting, cloud-init) where appropriate.
  • Ensure screenshots and UI instructions are platform-neutral or provide both Windows and Linux perspectives if relevant.
GitHub Create Pull Request
Batch Use certificates and securely access Azure Key Vault with Batch ...lob/main/articles/batch/credential-access-key-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples are provided exclusively in PowerShell, with no equivalent Bash, CLI, or Linux-native instructions. Windows-specific tools and patterns (such as .msi installers, Windows Management Framework, and PowerShell cmdlets) are referenced throughout, and there is no guidance for Linux users on how to generate certificates, install required libraries, or access Azure Key Vault from Linux-based Batch nodes.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for certificate creation, service principal setup, and Key Vault access.
  • Include instructions for installing required Azure libraries (e.g., Azure CLI, Azure SDK for Python) on Linux Batch nodes.
  • Mention Linux-compatible certificate management tools (e.g., openssl) alongside PowerShell alternatives.
  • Clarify any differences in workflow or prerequisites for Linux nodes, such as file paths, environment setup, and authentication methods.
  • Ensure that Linux examples are presented with equal prominence and detail as Windows/PowerShell examples.
GitHub Create Pull Request
Batch Manage private endpoint connections with Azure Batch accounts .../articles/batch/manage-private-endpoint-connections.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation presents management operations for Azure Batch private endpoint connections. It lists Az PowerShell (Windows-centric) examples before Azure CLI (cross-platform), and provides detailed PowerShell commands, reinforcing a Windows-first and PowerShell-heavy bias. The page references Windows tools and patterns, with no mention of Linux-specific considerations or shell environments.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., bash, zsh).
  • Include notes or sections for Linux/macOS users, such as environment setup or command differences if any.
  • Avoid implying PowerShell is the default or preferred method; clarify parity between tools.
  • Consider adding troubleshooting or tips relevant to Linux users (e.g., permissions, shell variable syntax).
GitHub Create Pull Request
Batch Monitor Batch with Azure Application Insights ...ob/main/articles/batch/monitor-application-insights.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All examples and tooling references are Windows-centric, including exclusive use of Visual Studio, PowerShell commands, Windows-specific NuGet packages (Microsoft.ApplicationInsights.WindowsServer), and Windows VM images for Azure Batch pools. There is no mention of Linux equivalents, nor are any Linux or cross-platform instructions, code samples, or troubleshooting steps provided.
Recommendations
  • Add Linux-specific prerequisites, such as instructions for using VS Code, JetBrains Rider, or .NET CLI on Linux.
  • Provide Linux-friendly package installation examples (e.g., using dotnet CLI: 'dotnet add package Microsoft.ApplicationInsights') instead of only PowerShell/NuGet Package Manager.
  • Include guidance for running Azure Batch pools with Linux VM images, and update code/configuration samples to show how to configure Application Insights on Linux nodes.
  • Mention cross-platform Application Insights packages and clarify which features/packages are Windows-only.
  • Add troubleshooting and deployment notes for Linux environments, including file staging, environment variables, and process management.
  • Ensure screenshots and portal instructions are not Windows-specific and clarify any OS-dependent behaviors.
GitHub Create Pull Request
Batch Plan to manage costs for Azure Batch ...-docs/blob/main/articles/batch/plan-to-manage-costs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific resources and patterns first (e.g., linking to Windows VM pricing before Linux), mentioning Windows tools (such as Windows OS licensing), and omitting explicit Linux examples or cost considerations. There is no discussion of Linux-specific VM options, licensing differences, or cost-saving strategies unique to Linux workloads.
Recommendations
  • Include explicit examples and cost considerations for Linux-based Batch workloads, such as referencing Linux VM pricing and licensing differences.
  • Present both Windows and Linux options in parallel when discussing VM selection, cost estimation, and licensing impacts.
  • Add links to Linux VM documentation and highlight cost-saving strategies specific to Linux (e.g., no OS licensing fees, availability of certain VM sizes).
  • Ensure screenshots and walkthroughs demonstrate both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Batch Quickstart: Use the Azure portal to create a Batch account and run a job ...e-docs/blob/main/articles/batch/quick-create-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for creating pools of Windows compute nodes (specifically Windows Server 2019), and using Windows command-line tools (cmd, set, timeout) in task command lines. There are no examples or guidance for creating Linux-based pools or running Linux shell commands, nor is there mention of Linux options or parity.
Recommendations
  • Include instructions and examples for creating pools with Linux-based compute nodes, such as Ubuntu or CentOS images.
  • Provide Linux shell command examples (e.g., using bash, echo, sleep) alongside Windows cmd examples for task command lines.
  • Explicitly mention both Windows and Linux options when describing pool creation, and clarify how to select the OS type.
  • Add notes or sections highlighting differences in environment variables, command syntax, and output handling between Windows and Linux nodes.
  • Ensure screenshots and walkthroughs show both Windows and Linux pool creation and task execution where applicable.
GitHub Create Pull Request
Batch Monitor Azure Batch ...s/azure-docs/blob/main/articles/batch/monitor-batch.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and patterns, such as the Batch .NET library and Application Insights integration with .NET solutions. There are no Linux-specific examples, nor is there mention of Linux command-line tools or SDKs (e.g., Python, Java) for monitoring Azure Batch. The documentation references Batch Explorer and .NET code samples, but does not provide parity for Linux users or alternative cross-platform approaches.
Recommendations
  • Include examples using cross-platform SDKs such as Python, Java, or Node.js for monitoring Batch resources.
  • Provide sample scripts for accessing diagnostic logs using Linux tools (e.g., Azure CLI, Bash, curl, jq) alongside any PowerShell or .NET examples.
  • Mention and demonstrate how to integrate Application Insights or other monitoring solutions in non-.NET environments (e.g., Python, Java).
  • Clarify Batch Explorer's platform support and offer guidance for Linux users if available.
  • Ensure that references to monitoring tools and libraries are not exclusively Windows/.NET-centric, and provide links to equivalent Linux documentation or samples.
GitHub Create Pull Request
Batch Nodes and pools in Azure Batch ...azure-docs/blob/main/articles/batch/nodes-and-pools.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific tools and patterns (such as .exe, .cmd, .bat, and PowerShell scripts) are listed before Linux equivalents when discussing supported executables. Windows remote access (RDP) is mentioned before Linux (SSH). Container support examples reference Windows Server images first, with no explicit Linux container example. There are no concrete Linux shell script or tool examples, and Linux-specific instructions are generally referenced via links rather than described inline.
Recommendations
  • List Linux script types (e.g., shell scripts, Python) before or alongside Windows types when discussing supported executables.
  • Provide explicit Linux examples (e.g., bash scripts, SSH commands) in relevant sections, not just links.
  • When discussing remote access, mention SSH for Linux first or equally with RDP for Windows.
  • Include Linux container pool creation examples and reference popular Linux container images.
  • Ensure parity in describing both Windows and Linux node setup, configuration, and troubleshooting steps.
  • Where possible, balance references to Windows and Linux tools (e.g., PowerShell vs. bash) and avoid defaulting to Windows-first language.
GitHub Create Pull Request
Batch Quickstart: Use .NET to create a pool and run a job ...zure-docs/blob/main/articles/batch/quick-run-dotnet.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively using Windows Server for compute nodes, Windows command-line tools (cmd, type), and providing examples that only work on Windows. There are no Linux equivalents or examples, and Windows is mentioned first and exclusively in several key steps.
Recommendations
  • Include examples for creating pools with Linux VM images, and explain how to select Linux Marketplace images in the pool configuration.
  • Provide sample task command lines using Linux shell commands (e.g., 'cat' instead of 'type'), and show how to specify them in the .NET API.
  • Clarify that Batch supports both Windows and Linux nodes, and discuss differences in configuration and scripting.
  • Add instructions for building and running the app on Linux (e.g., using dotnet CLI on Linux, or VS Code), and mention cross-platform development explicitly.
  • Where Windows tools or patterns are mentioned, provide Linux equivalents side-by-side.
GitHub Create Pull Request
Batch Batch security and compliance best practices ...cs/blob/main/articles/batch/security-best-practices.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and resources (such as PowerShell and Windows registry settings for TLS) are mentioned before or more prominently than their Linux equivalents. Examples and links for discovering supported images use PowerShell first, with Azure CLI mentioned second. The section on OS-level TLS settings is Windows-centric, with no Linux-specific guidance. There are no explicit Linux command-line examples or references to Linux security configuration patterns, and Windows terminology (RDP, registry) appears more frequently than SSH or Linux equivalents.
Recommendations
  • Provide Linux-first or parallel examples where PowerShell is mentioned, such as showing both Azure CLI and PowerShell commands for listing supported images.
  • Add Linux-specific guidance for OS-level security configuration, such as instructions for configuring TLS/cipher suites on supported Linux distributions.
  • Ensure that references to remote access (RDP/SSH) are balanced, with equal detail for both Windows (RDP) and Linux (SSH) scenarios.
  • Include links to Linux documentation (e.g., OpenSSL, SSH hardening, Linux disk encryption) where Windows-specific resources are provided.
  • Review terminology to ensure Linux and Windows are treated equally throughout, and avoid defaulting to Windows-first phrasing.
GitHub Create Pull Request
Batch Tutorial: Run a parallel workload using the .NET API ...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a strong Windows bias: it exclusively uses Windows VM images for compute pools, references only the Windows build of ffmpeg, and provides command-line examples using Windows syntax (cmd.exe). There are no examples or instructions for using Linux VM images, Linux-compatible ffmpeg builds, or Bash command lines, despite Azure Batch supporting Linux pools and .NET being cross-platform.
Recommendations
  • Add explicit instructions and code samples for creating Linux-based pools, including the use of Ubuntu or other supported Linux images.
  • Provide guidance on downloading and packaging the Linux build of ffmpeg, and reference its usage in the application package step.
  • Include alternative command-line examples using Bash syntax for running ffmpeg on Linux nodes.
  • Mention the differences in environment variables and file paths between Windows and Linux nodes, and how to handle them in cross-platform .NET code.
  • Update screenshots and walkthroughs to show both Windows and Linux pool/job/task creation and monitoring.
  • Clarify that Azure Batch supports both Windows and Linux, and encourage users to select the platform that best fits their workload.
GitHub Create Pull Request
Batch Mount a virtual file system on a pool ...re-docs/blob/main/articles/batch/virtual-file-mount.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is used as the primary scripting language for both Windows and Linux examples, even though Bash is more common for Linux. Windows-specific tools and patterns (e.g., 'cmdkey', 'net use', RDP) are described in detail, often before their Linux equivalents (e.g., 'cifs-utils', SSH). Troubleshooting and manual mounting instructions are more elaborate for Windows, with direct references to Windows tools and workflows. Some Linux-specific details, such as native Bash commands for mounting or troubleshooting, are missing or underrepresented.
Recommendations
  • Provide native Bash examples for Linux, especially for mounting and troubleshooting, rather than relying solely on PowerShell.
  • Present Linux and Windows instructions in parallel, ensuring equal detail and visibility for both platforms.
  • Include Linux-first or Linux-specific troubleshooting steps, such as using 'mount', 'df', 'lsblk', and examining system logs.
  • Reference Linux tools (e.g., 'mount', 'umount', 'journalctl') and workflows as prominently as Windows tools.
  • Clarify when PowerShell is required on Linux, and offer alternative Bash workflows where possible.
  • Ensure external links and references are balanced between Windows and Linux resources.
GitHub Create Pull Request
CDN Get started with the Azure CDN Library for .NET ...s/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is heavily oriented towards Windows development environments. It exclusively references Visual Studio 2015 for project creation and management, assumes use of Windows-specific UI elements and workflows, and provides no guidance or examples for Linux or cross-platform development. The only alternative tool mentioned is PowerShell, which is primarily a Windows technology, and there are no references to Linux equivalents (e.g., VS Code, CLI, or cross-platform .NET workflows). There are no instructions for running the sample on Linux or macOS, nor any mention of .NET Core/SDK usage outside Visual Studio.
Recommendations
  • Add instructions for creating and running the .NET project using the .NET CLI (dotnet new, dotnet run), which works on Linux, macOS, and Windows.
  • Include examples for using VS Code or other cross-platform editors instead of only Visual Studio.
  • Provide guidance for installing required NuGet packages via the CLI (dotnet add package) as an alternative to the Visual Studio UI.
  • Mention how to run the sample on Linux and macOS, including any platform-specific considerations.
  • Reference Azure CLI or REST API alternatives for CDN management, alongside PowerShell.
  • Clarify that the code is compatible with .NET Core/.NET 5+ and not just .NET Framework, if applicable.
GitHub Create Pull Request
CDN Diagnostic logs ...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias through exclusive use of PowerShell for CLI examples, reliance on Microsoft Azure Storage Explorer (a Windows-centric GUI tool), and lack of Linux or cross-platform command-line alternatives. There are no Bash, Azure CLI, or Linux-native instructions for enabling or consuming diagnostic logs. The ordering also presents Windows/PowerShell methods before mentioning any other automation or scripting options.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logs, which are cross-platform and work natively on Linux and macOS.
  • Include Bash or Python sample scripts for downloading and processing logs from Azure Storage, in addition to the PowerShell examples.
  • Mention and provide instructions for using cross-platform tools such as azcopy or the Azure CLI storage commands to access blobs, instead of only referencing Microsoft Azure Storage Explorer.
  • Clearly indicate which tools and scripts are cross-platform, and provide parity in documentation for Linux users.
  • Reorder sections so that cross-platform or platform-neutral options (Azure CLI, REST API) are presented before or alongside PowerShell and Windows GUI tools.
GitHub Create Pull Request
CDN Tutorial: Add a custom domain to your endpoint .../main/articles/cdn/cdn-map-content-to-custom-domain.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides detailed instructions for using the Azure portal and Azure PowerShell to manage custom domains for Azure CDN endpoints. PowerShell examples are given for both adding and removing custom domains, but there are no equivalent examples for Linux-native tools (such as Azure CLI or Bash scripts). The use of PowerShell as the only command-line automation option reflects a Windows bias, and there is no mention of Linux-specific workflows or cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell, including adding and removing custom domains.
  • Explicitly mention that Azure CLI is cross-platform and provide Bash script samples where appropriate.
  • Ensure that command-line instructions are not limited to Windows tools; include Linux and macOS parity in all automation sections.
  • Where PowerShell is referenced, clarify that it is available on Linux and macOS, or provide links to installation instructions for non-Windows platforms.
  • Consider adding a section or tab for 'Azure CLI' alongside 'Azure PowerShell' and 'Azure portal' in all relevant steps.
GitHub Create Pull Request
Communication Services Prerequisites ...des/create-azure-managed-domain-resource-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all resource management tasks. There are no examples or instructions for Linux users, such as using Azure CLI or Bash, nor is there mention of cross-platform alternatives. The documentation implicitly assumes a Windows environment and does not address Linux or macOS workflows.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks (e.g., az communication email-domain create, az communication email-domain update, etc.).
  • Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide installation instructions.
  • Reorder or parallelize examples so that CLI and PowerShell instructions are presented together, or indicate which is recommended for each platform.
  • Include notes or sections for Linux/macOS users, highlighting any differences or requirements.
  • Avoid using Windows-specific paths (e.g., PS C:\>) in prompts; use generic or platform-neutral prompts.
GitHub Create Pull Request
CDN Troubleshooting file compression in Azure Content Delivery Network ...blob/main/articles/cdn/cdn-troubleshoot-compression.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates Windows bias by primarily referencing Windows-centric tools (Fiddler, IIS), providing troubleshooting steps only for Microsoft IIS web servers, and omitting equivalent Linux/Apache/Nginx examples or guidance. No Linux-specific tools or server configuration instructions are given, and Windows solutions are presented first and exclusively.
Recommendations
  • Include troubleshooting steps for popular Linux web servers such as Apache and Nginx, detailing how to handle compression and proxy headers.
  • Mention Linux-compatible tools (e.g., curl, wget, tcpdump, Wireshark) for inspecting HTTP headers and compression.
  • Provide configuration examples for enabling compression and handling proxy headers on Linux servers.
  • Present Windows and Linux solutions side-by-side or in parallel sections to ensure parity and avoid platform-first bias.
GitHub Create Pull Request
Cloud Services Extended Support Available sizes for Azure Cloud Services (extended support) ...les/cloud-services-extended-support/available-sizes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for listing available VM sizes, referencing Windows-centric tools (PowerShell, Visual Studio) in deployment options, and omitting equivalent Linux/CLI examples. The order of deployment options also lists Windows tools before Linux alternatives, reinforcing the bias.
Recommendations
  • Add Azure CLI and/or Bash examples alongside PowerShell for all code snippets, especially for listing available VM sizes.
  • Explicitly mention Linux-compatible deployment tools (e.g., Azure CLI, ARM templates) in the 'Next steps' section and provide links.
  • Reorder deployment options to present cross-platform tools (Azure portal, CLI, templates) before Windows-specific tools (PowerShell, Visual Studio).
  • Include notes or guidance for Linux users where relevant, such as editing service definition files or repackaging services.
GitHub Create Pull Request
Cloud Services Extended Support Guest OS family 1 retirement notice | Microsoft Docs ...-support/cloud-services-guestos-family-1-retirement.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All examples and recommendations focus exclusively on Windows Server OS families, with no mention of Linux-based options. The only script provided is in Azure PowerShell, and there are no equivalent Bash, CLI, or Linux-native instructions. The migration paths and supported OS families are all Windows-centric, and the tools referenced (PowerShell, .NET framework) are Windows-specific.
Recommendations
  • Include information about Linux-based OS families available for Azure Cloud Services, if supported.
  • Provide equivalent examples using Azure CLI or Bash scripts for users on Linux or macOS.
  • Mention migration paths to Linux-based environments or containers where applicable.
  • Clarify whether only Windows OS families are supported, or update documentation to reflect Linux parity if available.
  • Add notes or links for users who manage services from non-Windows platforms, guiding them to relevant resources.
GitHub Create Pull Request
Cloud Services Extended Support Guest OS family 2, 3, and 4 retirement notice | Microsoft Docs ...port/cloud-services-guestos-family-2-3-4-retirement.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows environments, referencing only Windows Server OS families and providing migration guidance exclusively for Windows Server versions. The only script example is in Azure PowerShell, with no equivalent for Linux users (e.g., Azure CLI, Bash). There is no mention of Linux-based guest OS families, nor guidance for users running Linux workloads on Azure Cloud Services.
Recommendations
  • Include examples using Azure CLI and Bash scripts to help Linux users identify affected services.
  • Clarify whether Linux-based guest OS families are impacted, and provide migration guidance for Linux workloads if applicable.
  • Mention Linux tools and patterns where relevant, such as using SSH, Linux configuration files, or Linux-compatible SDKs.
  • Present both Windows and Linux options in parallel when discussing migration paths, tooling, and supported OS families.
  • Add explicit statements about the scope of the retirement (e.g., 'This retirement only affects Windows-based Guest OS families; Linux-based families are not impacted.') if applicable.
GitHub Create Pull Request
CDN Monitoring, metrics, and raw logs for Azure CDN ...cs/blob/main/articles/cdn/monitoring-and-access-log.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias in its configuration and automation sections. All command-line examples are provided exclusively using Azure PowerShell, a tool most commonly used on Windows and not natively available on Linux. There are no examples using Azure CLI, Bash, or other Linux-native tools. The documentation refers to the Azure portal and PowerShell before mentioning any cross-platform alternatives, and does not provide Linux-specific guidance or parity in automation examples.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash scripting examples for automation tasks, especially for enabling diagnostics and configuring log destinations.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, or provide installation instructions for non-Windows platforms.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell examples.
  • Add notes or links to documentation for Linux users, including troubleshooting and environment setup guidance.
  • Ensure screenshots and UI instructions do not assume a Windows environment (e.g., avoid references to Windows-specific UI elements or terminology).
GitHub Create Pull Request
CDN About Azure CDN from Microsoft (classic) to Azure Front Door migration ...cs/azure-docs/blob/main/articles/cdn/tier-migration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Dev-ops' section, where it mentions updating 'Azure PowerShell module' before CLI commands and APIs, suggesting a Windows-first approach. There are no examples or instructions for Linux-specific tools, shell scripts, or cross-platform automation. The page does not provide parity for Linux users in terms of migration scripting or tool usage.
Recommendations
  • Explicitly mention Azure CLI and REST API as cross-platform alternatives alongside PowerShell.
  • Provide example migration scripts for both PowerShell (Windows) and Bash (Linux/macOS) environments.
  • Clarify that all migration steps can be performed using Azure CLI on Linux/macOS, not just PowerShell on Windows.
  • Include links to documentation for Azure CLI and REST API usage in migration scenarios.
  • Avoid listing PowerShell before CLI in instructions to prevent implicit Windows-first bias.
GitHub Create Pull Request
Cloud Services Extended Support Store and use certificates in Azure Cloud Services (extended support) ...ervices-extended-support/certificates-and-key-vault.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as a primary command-line method for creating Key Vaults, requiring certificate files in .PFX format (commonly used in Windows environments), and mentioning Visual Studio as a deployment tool. There are no examples or instructions for Linux users (e.g., using Azure CLI or OpenSSL), nor are Linux-friendly certificate formats (.PEM, .CRT) discussed. The ordering and tool selection suggest a Windows-centric approach.
Recommendations
  • Add Azure CLI examples for creating Key Vaults and uploading certificates, with explicit Linux shell commands.
  • Include instructions for converting certificates from PEM/CRT to PFX using OpenSSL, and clarify cross-platform compatibility.
  • Mention Linux-friendly certificate formats and provide guidance for Linux users on certificate preparation.
  • List deployment options in a neutral order (e.g., Azure portal, Azure CLI, PowerShell, Visual Studio) and ensure parity in example coverage.
  • Reference Linux tools and workflows (e.g., Bash, OpenSSL) alongside Windows tools.
GitHub Create Pull Request
Cloud Services Extended Support What is the Azure Cloud Service (extended support) model and package ...s-extended-support/cloud-services-model-and-package.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. It references Windows-specific tools (Visual Studio, CSPack.exe, Microsoft Azure Command Prompt, Compute Emulator) and provides command-line examples only in Windows CMD syntax. There is no mention of Linux equivalents, cross-platform alternatives, or instructions for packaging/deploying from Linux environments. PowerShell and Visual Studio are suggested as deployment methods before alternatives, and configuration steps reference Windows UI elements (Properties page, Certificates tab) without Linux parity.
Recommendations
  • Include instructions and examples for packaging and deploying cloud services from Linux environments, such as using Azure CLI or cross-platform .NET tools.
  • Clarify whether CSPack and Compute Emulator are available or supported on Linux/macOS, and if not, suggest alternatives.
  • Provide command-line examples using Bash/Azure CLI alongside Windows CMD/PowerShell.
  • Mention cross-platform editors and tools for editing configuration files, not just Visual Studio.
  • Reorder deployment options to present cross-platform methods (Azure CLI, templates) before Windows-specific tools.
  • Explicitly state platform requirements and limitations for each tool or method.
GitHub Create Pull Request
Cloud Services Extended Support Deploy Azure Cloud Services (extended support) - Azure portal ...icles/cloud-services-extended-support/deploy-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page primarily describes deployment using the Azure portal, which is cross-platform. However, in the 'Related content' section, alternative deployment methods are listed as Azure PowerShell, ARM template, and Visual Studio. PowerShell and Visual Studio are Windows-centric tools, and PowerShell is mentioned before ARM templates (which are platform-neutral). There is no mention of Linux-native tools (such as Azure CLI or Bash scripting), nor are Linux-specific examples provided. This ordering and omission suggest a bias towards Windows tooling and workflows.
Recommendations
  • Add references and examples for deploying Cloud Services (extended support) using Azure CLI, which is cross-platform and widely used on Linux.
  • Ensure that Linux-native tools (such as Bash scripts or cloud-init) are mentioned alongside or before Windows-centric tools in alternative deployment methods.
  • Provide explicit examples or links for Linux users, such as how to upload packages from Linux environments or automate deployments using Linux shells.
  • Review the ordering of alternative deployment methods to avoid prioritizing Windows tools unless there is a technical reason.
GitHub Create Pull Request
Cloud Services Extended Support Deploy Azure Cloud Services (extended support) - SDK ...articles/cloud-services-extended-support/deploy-sdk.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell for key vault and certificate management steps, references to Windows-specific tools and patterns (such as RDP and 'Microsoft.Windows.Azure.Extensions'), and the absence of Linux or cross-platform CLI alternatives for these operations. The examples and instructions for resource creation and management are provided only in C# and PowerShell, with no mention of Bash, Azure CLI, or Linux-friendly workflows. This can hinder Linux users or those preferring non-Windows environments.
Recommendations
  • Provide Azure CLI and Bash script examples for key vault and certificate management steps, alongside PowerShell.
  • Mention Linux-compatible tools and workflows for remote access (e.g., SSH extensions) in addition to RDP.
  • Ensure that all resource creation steps (resource group, storage account, network, etc.) include Azure CLI or REST API examples, not just C#.
  • Reference cross-platform SDKs and tools where possible, and clarify which steps are OS-agnostic.
  • Explicitly state platform requirements or limitations for each step, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Cloud Services Extended Support Apply the Key Vault VM extension in Azure Cloud Services (extended support) ...s-extended-support/enable-key-vault-virtual-machine.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page focuses exclusively on the Key Vault VM extension for Windows, mentioning only Windows certificate stores and providing examples and instructions tailored to Windows environments. There are no references to Linux support, Linux certificate stores, or Linux-specific usage patterns, and the extension is described as 'for Windows' throughout. All configuration examples (such as certificateStoreLocation: LocalMachine, certificateStoreName: My) are Windows-centric, and there is no mention of Linux equivalents or cross-platform applicability.
Recommendations
  • Clarify whether the Key Vault VM extension is supported on Linux VMs in Azure Cloud Services (extended support).
  • If Linux is supported, add equivalent instructions and examples for Linux, including certificate store locations and installation steps.
  • If Linux is not supported, explicitly state this limitation early in the documentation to inform users.
  • Provide links or references to Linux-specific certificate management solutions in Azure if available.
  • Consider restructuring the documentation to address both Windows and Linux scenarios, or create a parallel page for Linux if the extension is supported.
GitHub Create Pull Request
Cloud Services Extended Support Configure scaling for Azure Cloud Services (extended support) ...s/cloud-services-extended-support/configure-scaling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (PowerShell, Visual Studio) before any Linux alternatives, and by providing links and examples that are tailored to Windows environments (e.g., environment-variable-windows in queue storage). There are no explicit Linux or cross-platform CLI examples, and the deployment options prioritize Windows-centric workflows.
Recommendations
  • Add Azure CLI examples for scaling and deployment operations, as Azure CLI is cross-platform.
  • Include Linux-specific instructions or screenshots where relevant, especially for environment variable configuration and deployment.
  • Mention Linux-compatible editors (e.g., VS Code) alongside Visual Studio for template editing and deployment.
  • Ensure that referenced quickstarts and guides include Linux tabs or instructions, not just Windows.
  • Reorder deployment options to list cross-platform tools (Azure portal, Azure CLI, ARM templates) before Windows-only tools (PowerShell, Visual Studio).
GitHub Create Pull Request
Cloud Services Extended Support Enable Monitoring in Cloud Services (extended support) using the Azure portal ...icles/cloud-services-extended-support/enable-alerts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page primarily describes enabling monitoring via the Azure portal, which is cross-platform. However, in the 'Next steps' section, deployment options are listed as Azure portal, PowerShell, Template, and Visual Studio. PowerShell and Visual Studio are Windows-centric tools, and PowerShell is mentioned before any Linux-friendly CLI options. There is no mention of Azure CLI or Bash examples, which are more common on Linux/macOS. This ordering and tool selection suggest a Windows-first and PowerShell-heavy bias.
Recommendations
  • Include Azure CLI examples for deployment and monitoring, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • List deployment options in a neutral order, e.g., 'Azure portal, Azure CLI, PowerShell, Template, Visual Studio', to avoid Windows-first bias.
  • Add explicit notes or examples for Linux/macOS users, such as using Bash or Azure CLI.
  • If Visual Studio is mentioned, consider also referencing VS Code, which is cross-platform.
GitHub Create Pull Request
Cloud Services Extended Support Apply the Remote Desktop in Cloud Services (extended support) ...articles/cloud-services-extended-support/enable-rdp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell, a Windows-centric tool, with no mention of Linux equivalents (such as Azure CLI or SSH). The workflow assumes use of RDP, which is primarily a Windows protocol, and does not provide guidance for connecting from Linux or macOS systems. The order of presentation and tooling is Windows-first, with no parity for Linux users.
Recommendations
  • Add Azure CLI examples for enabling, updating, and connecting to Remote Desktop extensions, as Azure CLI is cross-platform.
  • Include instructions for connecting to RDP from Linux and macOS clients, such as using 'xfreerdp', 'remmina', or 'rdesktop'.
  • Mention SSH as an alternative for Linux-based role instances, if supported.
  • Balance the documentation by presenting Linux/macOS methods alongside Windows/PowerShell methods, rather than exclusively or primarily focusing on Windows.
  • Clarify any platform limitations (e.g., if RDP extension is only for Windows roles) and provide guidance for Linux roles if applicable.
GitHub Create Pull Request
Cloud Services Extended Support Extensions for Cloud Services (extended support) ...articles/cloud-services-extended-support/extensions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-specific tools and patterns, such as PowerShell cmdlets and Windows Defender/Antimalware, without mentioning Linux equivalents or providing Linux-specific examples. The extension features and deployment options are described primarily in the context of Windows environments, and Linux support or alternatives are not discussed.
Recommendations
  • Include examples and instructions for configuring extensions on Linux-based cloud service roles, where applicable.
  • Mention Linux-compatible monitoring and security extensions, or clarify if certain extensions are Windows-only.
  • Provide parity in deployment instructions by including CLI (az), Bash, or Linux shell examples alongside PowerShell.
  • Explicitly state platform limitations or support for each extension (e.g., 'This extension is only available for Windows roles').
  • Add documentation links or sections for Linux-specific tools and workflows relevant to cloud service extensions.
GitHub Create Pull Request
Cloud Shell Persist files in Azure Cloud Shell .../main/articles/cloud-shell/persisting-shell-storage.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Cloud Shell storage, with no equivalent Bash or Linux shell commands shown. The 'Use PowerShell commands' section is prominent, and there is no mention of Linux tools or CLI patterns, nor are Linux/Bash equivalents presented alongside or before the Windows/PowerShell examples.
Recommendations
  • Add equivalent Bash or Azure CLI examples for all PowerShell commands shown, such as using 'az storage share show' or 'az cloud-shell' commands.
  • Include a 'Use Bash commands' or 'Use Azure CLI' section parallel to the PowerShell section.
  • Present both Windows/PowerShell and Linux/Bash examples side-by-side, or alternate which platform is presented first.
  • Mention Linux tools and patterns (e.g., shell scripting, use of environment variables) where relevant.
  • Clarify that Cloud Shell supports both Bash and PowerShell, and provide guidance for users of each.
GitHub Create Pull Request
Cloud Services Extended Support Apply the Microsoft Azure diagnostics extension in Cloud Services (extended support) ...articles/cloud-services-extended-support/enable-wad.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and commands for configuring the Azure Diagnostics extension. All CLI instructions use PowerShell, which is natively available only on Windows (though cross-platform PowerShell exists, it's not mentioned). There are no examples using Azure CLI, Bash, or Linux-native tools. The configuration file examples reference Windows-style performance counters and patterns. The ARM template section is platform-neutral, but all procedural guidance is Windows-centric. The 'Next steps' section lists PowerShell and Visual Studio (Windows tools) before mentioning the Azure portal and ARM templates, further reinforcing Windows-first patterns.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to perform the same tasks on Linux or macOS.
  • Explicitly mention cross-platform PowerShell Core if PowerShell is required, and clarify installation steps for non-Windows users.
  • Include Bash script examples for downloading configuration files and interacting with Azure resources.
  • Reference Linux performance counters and monitoring patterns in the configuration file examples, or clarify Windows-specific elements.
  • Reorder 'Next steps' to list platform-neutral options (Azure portal, ARM template) before Windows-specific tools (PowerShell, Visual Studio).
  • Add a section or note describing Linux/macOS support and any limitations for Cloud Services diagnostics extension management.
GitHub Create Pull Request
Cloud Services Extended Support Feature Analysis Cloud Services vs Virtual Machine Scale Sets ...-services-extended-support/feature-support-analysis.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. It references PowerShell as the method for Azure Site Recovery without mentioning Linux alternatives (e.g., Azure CLI, REST API). The 'Mix operating systems' feature highlights Windows limitations first and only later mentions Linux support. There are no explicit Linux-specific examples, tools, or patterns provided, and Windows terminology (e.g., PowerShell, Windows support) is used without Linux parity.
Recommendations
  • Where PowerShell is mentioned (e.g., Azure Site Recovery), also reference Azure CLI and REST API options for Linux users.
  • Provide explicit examples or notes for Linux users, such as bash/CLI commands for common operations.
  • When discussing operating system support, mention Linux and Windows together, or list Linux first in parity-sensitive contexts.
  • Add a section or table row for Linux-specific features or considerations, if any exist.
  • Avoid assuming Windows as the default; clarify cross-platform support wherever relevant.
GitHub Create Pull Request
Cloud Services Extended Support Override SKU information over CSCFG/CSDEF for Azure Cloud Services (extended support) ...ticles/cloud-services-extended-support/override-sku.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell example (which is Windows-centric) and referencing Windows tools and patterns (e.g., PowerShell cmdlets) without offering equivalent Linux/bash/CLI examples. The PowerShell example appears before any mention of cross-platform alternatives, and there is no Azure CLI or bash script example for Linux users. The SDK example is in C#, which is also more common in Windows environments. No Linux-specific guidance or parity is provided.
Recommendations
  • Add Azure CLI examples for setting allowModelOverride, as Azure CLI is cross-platform and preferred by many Linux users.
  • Include bash script samples for deployment scenarios, demonstrating how Linux users can automate these tasks.
  • Explicitly mention cross-platform tools and workflows, and clarify which steps are OS-agnostic.
  • Consider adding Python SDK examples alongside C# to improve language and platform diversity.
  • Reorder examples so that cross-platform solutions (ARM template, Azure CLI) are presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Cloud Services Extended Support About Azure Cloud Services (extended support) ...n/articles/cloud-services-extended-support/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as PowerShell and Visual Studio, when describing deployment and migration options. There are no explicit examples or guidance for Linux users or cross-platform CLI tools (such as Azure CLI), and the documentation does not mention Linux-based alternatives or provide parity in instructions for non-Windows environments.
Recommendations
  • Include Azure CLI examples alongside or before PowerShell examples to ensure cross-platform compatibility.
  • Mention and provide instructions for deploying Cloud Services (extended support) from Linux or macOS environments.
  • Reference cross-platform editors (such as VS Code) in addition to Visual Studio.
  • Ensure that all deployment and migration steps are documented for both Windows and Linux users, including relevant screenshots or terminal commands.
  • Explicitly state when a tool or workflow is Windows-only, and provide Linux equivalents where possible.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) NetworkConfiguration Schema | Microsoft Docs ...-extended-support/schema-cscfg-networkconfiguration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page references PowerShell specifically as a deployment method for reserved IP allocation, without mentioning or providing equivalent Linux CLI (e.g., Azure CLI, Bash) examples. There are no Linux-specific instructions or examples, and Windows-centric tooling (PowerShell) is mentioned as the default approach for certain tasks.
Recommendations
  • Add Azure CLI and Bash examples for reserved IP allocation and other configuration tasks, alongside PowerShell instructions.
  • Explicitly mention Linux-compatible tools and workflows wherever PowerShell is referenced.
  • Ensure that examples and instructions are presented in a cross-platform manner, or provide parallel examples for both Windows and Linux users.
  • Review the documentation for other Windows-centric terminology or assumptions and clarify platform neutrality.
GitHub Create Pull Request
Cloud Services Extended Support Migrate Azure Cloud Services (classic) to Azure Cloud Services (extended support) ...rvices-extended-support/in-place-migration-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a Windows bias by prioritizing PowerShell and Windows-centric tools for deployment and migration examples. PowerShell is the only command-line example shown for resource registration and status checking, and Visual Studio is listed as a deployment tool without mention of cross-platform alternatives. There is no explicit mention or example of Linux shell commands (e.g., Bash), nor are Linux-specific tools or workflows discussed. The ordering of tools and examples tends to favor Windows-first approaches.
Recommendations
  • Provide equivalent Bash/Azure CLI examples alongside PowerShell commands for resource registration and status checks.
  • Mention and document cross-platform deployment tools (e.g., VS Code, Azure CLI) in the deployment section.
  • Ensure that instructions for setting up access, migration, and deployment are platform-neutral and include steps for Linux/macOS users.
  • Add explicit notes or sections highlighting Linux compatibility and best practices for migration using non-Windows environments.
  • Where Visual Studio is referenced, also mention cross-platform IDEs or editors that can be used for Azure development.
GitHub Create Pull Request
Cloud Services Extended Support Technical details and requirements for migrating to Azure Cloud Services (extended support) ...tended-support/in-place-migration-technical-details.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing PowerShell as the primary command-line tool for migration operations and troubleshooting, with no mention of Linux-specific tools or shell commands. Examples and guidance are given for PowerShell and REST API, but there are no CLI examples using Bash, nor is Azure CLI usage highlighted for Linux users. The documentation assumes familiarity with Windows-centric tooling and patterns, potentially making it less accessible for Linux administrators.
Recommendations
  • Add Azure CLI examples for all operations currently described with PowerShell, and ensure these examples are runnable on Linux and macOS.
  • Explicitly mention cross-platform support for migration tooling, including any prerequisites or differences for Linux users.
  • Provide troubleshooting steps and scripts using Bash or Azure CLI, not just PowerShell.
  • Where PowerShell is referenced, also provide equivalent Azure CLI or Bash commands, and clarify which tools are available on which platforms.
  • Review terminology and instructions to avoid assuming a Windows environment; mention Linux and macOS where relevant.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) post-migration changes ...ud-services-extended-support/post-migration-changes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Visual Studio as primary tools for post-migration operations, with examples and links focused on PowerShell and Windows-centric workflows. Linux equivalents (such as Bash, Azure CLI, or cross-platform scripting) are mentioned only briefly or not at all, and there are no explicit Linux/CLI examples for key operations like retrieving deployment files or managing certificates. Visual Studio is referenced as the default IDE for updates, further reinforcing a Windows-centric approach.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all operations, especially for retrieving .csdef and .cscfg files, managing certificates, and updating deployments.
  • Include Bash script samples or references for common automation tasks.
  • Mention and link to cross-platform tools and editors (e.g., VS Code) in addition to Visual Studio.
  • Clarify which steps and tools are available and supported on Linux/macOS environments.
  • Add explicit notes or sections for Linux users, highlighting any differences or additional requirements.
GitHub Create Pull Request
Cloud Shell Azure Cloud Shell release notes ...e-docs/blob/main/articles/cloud-shell/release-notes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell and .NET (Windows-centric tools) are consistently highlighted in release notes, often listed before or alongside Linux tools. The example in November 2025 mentions Windows keyboard shortcuts first and specifically calls out Windows before Linux. There is a lack of explicit Linux shell (bash/zsh) examples or references, and some package/tool updates (e.g., Azure PowerShell, .NET) are more relevant to Windows users. While Linux tools are present (e.g., Inspektor Gadget, Azure Linux base image), the documentation tends to foreground Windows tools and patterns.
Recommendations
  • Include explicit examples and references for Linux shells (bash, zsh) and tools in release notes.
  • When listing tool updates, alternate the order or group by platform relevance (e.g., Azure PowerShell for Windows, bash tools for Linux).
  • Provide parity in shortcut documentation, mentioning Linux and Windows equally and simultaneously.
  • Add more details about Linux-specific changes, tools, and patterns to balance the coverage.
  • Ensure that links and references include Linux-focused documentation where available.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) Def. WebRole Schema | Microsoft Docs ...loud-services-extended-support/schema-csdef-webrole.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Cloud Services (extended support) WebRole schema exhibits a Windows bias. The schema and examples are centered around IIS 7, ASP.NET, and Windows-centric concepts (e.g., certificate stores like 'CurrentUser' and 'LocalMachine', startup tasks using CMD files, and .NET assemblies). There are no Linux equivalents or examples, and the documentation does not mention Linux-based web roles, tools, or patterns. Windows technologies and terminology are used exclusively and presented as the default or only option.
Recommendations
  • Add explicit notes about Linux support or lack thereof for Cloud Services (extended support) web roles.
  • If Linux-based web roles are supported, provide equivalent schema examples and usage patterns for Linux (e.g., using Apache/Nginx, shell scripts for startup tasks, Linux certificate management).
  • Mention Linux alternatives to Windows-specific features (e.g., certificate stores, environment variables, startup scripts).
  • Clarify which elements and attributes are Windows-only and suggest Linux-compatible approaches where possible.
  • Include cross-platform guidance or links to Linux documentation for similar Azure services.
GitHub Create Pull Request
Cloud Shell Azure Cloud Shell Frequently Asked Questions (FAQ) .../blob/main/articles/cloud-shell/faq-troubleshooting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits mild Windows bias. Windows and PowerShell examples are presented before Linux/Bash equivalents in several sections, such as copy/paste shortcuts and personal data management. Troubleshooting steps reference Microsoft Edge and Chrome developer tools before mentioning alternatives. PowerShell-specific features (like the Azure: drive) are described in detail, while Linux/Bash equivalents are less emphasized. There is limited mention of Linux-specific tools or troubleshooting patterns.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell/Windows examples to ensure parity.
  • Include explicit references to Linux troubleshooting tools and browser developer tools (e.g., instructions for Firefox and Safari).
  • Expand explanations of Bash/Linux features (such as file system access, shell behaviors) to match the detail given for PowerShell.
  • Where Windows-specific tools or patterns are mentioned, provide Linux equivalents (e.g., alternatives to PowerShell providers, Linux file system navigation).
  • Ensure that screenshots and step-by-step instructions are available for Linux environments and browsers.
GitHub Create Pull Request
Cloud Services Extended Support Azure Cloud Services (extended support) Def. WorkerRole Schema | Microsoft Docs ...d-services-extended-support/schema-csdef-workerrole.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Cloud Services (extended support) WorkerRole schema exhibits a Windows bias. It references Windows-specific concepts such as certificate stores (CurrentUser, LocalMachine, store names like My, Root, etc.), .NET Framework entry points, CMD/batch files for startup tasks, and environment variables in Windows style (e.g., %ROLEROOT%). There are no examples or guidance for Linux equivalents, and Windows terminology and patterns are presented exclusively and/or first throughout the document.
Recommendations
  • Add explicit guidance and examples for Linux-based WorkerRoles, including how certificate management, environment variables, and startup tasks are handled in Linux environments.
  • Document Linux equivalents for certificate stores, such as file-based PEM storage or OS-specific certificate locations.
  • Include examples of startup tasks using shell scripts (e.g., .sh files) and note differences in encoding and execution context for Linux.
  • Clarify how environment variables and paths (e.g., %ROLEROOT%) are represented in Linux (e.g., $ROLEROOT or other conventions).
  • Provide parity for .NET and non-.NET entry points, including support for Linux-native runtimes and frameworks.
  • Where Windows-specific terminology is used, add Linux alternatives or a cross-platform note.
GitHub Create Pull Request
Cloud Shell Azure Cloud Shell features .../azure-docs/blob/main/articles/cloud-shell/features.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Cloud Shell features demonstrates a moderate Windows bias. PowerShell is frequently highlighted, with features like the Azure drive ('Azure:') described only for PowerShell and not for Bash. Many Microsoft service integrations are listed as PowerShell modules, and examples for listing installed modules are given for PowerShell before Bash. Several tools are Windows-centric (e.g., Exchange Online PowerShell, Office 365 CLI, Microsoft Graph PowerShell, SqlServer PowerShell modules), and there is a lack of equivalent Linux/Bash examples or parity in feature descriptions. The documentation often mentions PowerShell and Windows tools first or exclusively, while Linux/Bash alternatives are less emphasized or missing.
Recommendations
  • Provide equivalent Bash examples for features currently described only for PowerShell, such as Azure resource navigation.
  • List Bash/Linux commands alongside PowerShell commands when describing how to view installed modules and packages.
  • Highlight open source and Linux-native tools with equal prominence as Microsoft/Windows-centric tools.
  • Add examples and documentation for managing Azure resources using Bash and Azure CLI, not just PowerShell.
  • Ensure that feature descriptions do not prioritize Windows/PowerShell tools and modules over Linux/Bash alternatives.
  • Include links to Linux/Bash documentation where relevant, similar to the links provided for PowerShell modules.
GitHub Create Pull Request
Communication Services Enable interoperability in your Teams tenant ...s/includes/enable-interoperability-for-teams-tenant.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on PowerShell commands and Windows-specific tooling (MicrosoftTeams PowerShell module), with no mention of Linux or cross-platform alternatives. All examples and instructions assume use of PowerShell, which is traditionally a Windows tool, and there is no guidance for Linux users or those using other shells. The documentation also introduces Windows-centric steps first and exclusively.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, including how to install and use PowerShell Core (pwsh) on non-Windows platforms.
  • Clarify whether the MicrosoftTeams PowerShell module is supported on PowerShell Core for Linux/macOS, and provide installation steps if so.
  • Offer alternative approaches using Azure CLI, REST APIs, or other cross-platform tools where possible.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • Add troubleshooting notes for common issues encountered on Linux/macOS (e.g., authentication dialogs, module compatibility).
GitHub Create Pull Request
Communication Services Azure logs and metrics for Teams external users ...ervices/concepts/interop/guest/monitor-logs-metrics.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft-centric tools such as Teams Admin Center and Teams Call Quality Dashboard, which are primarily accessed via web interfaces or Windows environments. There are no examples or instructions for accessing logs or metrics using Linux tools, command-line interfaces, or cross-platform methods. The documentation assumes the reader is using Microsoft tools and does not mention alternatives or parity for Linux users.
Recommendations
  • Include instructions or examples for accessing Azure logs and metrics using cross-platform tools such as Azure CLI, which is available on Linux.
  • Provide guidance on downloading or exporting Teams logs for analysis on Linux systems, possibly using REST APIs or PowerShell Core (which is cross-platform).
  • Mention any web-based tools as platform-agnostic, but clarify if any features are limited to Windows environments.
  • Add examples of viewing or processing logs using Linux utilities (e.g., grep, jq) after exporting them from Azure or Teams.
  • Ensure parity by listing both Windows and Linux methods for log access and analysis wherever possible.
GitHub Create Pull Request
Communication Services Teams Phone extensibility FAQ .../concepts/interop/tpe/teams-phone-extensibility-faq.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily by referencing configuration via PowerShell cmdlets and the Teams Admin Center (TAC) portal, both of which are Windows-centric tools. There are no Linux or cross-platform alternatives mentioned for administrative tasks, nor are there examples or guidance for Linux users. This may hinder users on Linux or macOS from fully utilizing or administering Teams Phone extensibility features.
Recommendations
  • Include equivalent instructions for Linux and macOS users, such as using Microsoft Graph API or Azure CLI for configuration tasks.
  • Provide examples of how to manage Teams Phone extensibility features using cross-platform tools.
  • Explicitly mention platform compatibility for administrative interfaces and tools.
  • Add links or references to documentation for Linux/macOS administration of Teams and Azure Communication Services.
  • Clarify whether PowerShell cmdlets can be run on PowerShell Core (cross-platform) and provide installation guidance if so.
GitHub Create Pull Request
Communication Services Enable interoperability with Teams ...ices/concepts/interop/enable-interoperability-teams.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (Set-CsPhoneNumberAssignment) for configuration, mentioning Windows-centric tools and patterns, and omitting any Linux or cross-platform alternatives. No examples or guidance are provided for performing these steps on Linux or macOS, nor is there mention of equivalent CLI or REST API methods.
Recommendations
  • Provide equivalent instructions using Azure CLI, REST API, or other cross-platform tools where possible.
  • Include Linux/macOS-specific examples or note platform limitations explicitly.
  • Clarify whether PowerShell cmdlets can be run on PowerShell Core (cross-platform) or only on Windows.
  • Add links or references to documentation for non-Windows environments.
  • Consider reordering examples to present cross-platform or platform-neutral options first, or side-by-side.
GitHub Create Pull Request
Communication Services Security for communication as Teams external user ...munication-services/concepts/interop/guest/security.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and administration patterns, such as PowerShell and the Microsoft Teams admin center, without mentioning or providing Linux equivalents. All configuration and management examples are described using Windows tools, and there are no examples or guidance for Linux administrators or cross-platform scenarios.
Recommendations
  • Include examples for managing Teams external user policies using cross-platform tools, such as Azure CLI or REST APIs, which are available on Linux.
  • Explicitly mention whether administrative tasks (e.g., policy configuration) can be performed from Linux or macOS environments, and provide relevant instructions.
  • Reference cross-platform documentation and tools alongside Windows-specific ones, ensuring parity in guidance.
  • Add a section or note about Linux support for Azure Communication Services and Microsoft Purview, including any limitations or alternative workflows.
  • Provide sample commands or scripts for Linux environments where applicable, especially for security configuration and management.
GitHub Create Pull Request
Communication Services Calling capabilities for Teams users ...cation-services/concepts/interop/teams-user-calling.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias primarily through the absence of Linux-specific examples and tools. The feature matrix lists 'Windows' as a platform but does not mention Linux desktop explicitly, nor does it provide parity for Linux usage or integration. References to Microsoft Entra and PowerShell modules are present, but there is no mention of Linux command-line tools or configuration patterns. The documentation focuses on Windows, JavaScript, Android, and iOS, omitting Linux desktop as a first-class platform.
Recommendations
  • Explicitly list Linux desktop as a supported platform in feature tables if applicable, or clarify its support status.
  • Provide Linux-specific examples, such as using Bash, CLI tools, or Linux desktop environments for SDK integration.
  • Include references to Linux equivalents for authentication and device management, such as Azure CLI or relevant open-source tools.
  • Ensure parity in documentation by describing any platform-specific limitations or workarounds for Linux users.
  • If Linux is not supported, state this clearly to avoid confusion and help users plan accordingly.
GitHub Create Pull Request
Communication Services Microsoft Teams shared line appearance ...pts/interop/teams-user/teams-shared-line-appearance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Teams PowerShell as a method for assigning delegates, without mentioning Linux or cross-platform alternatives. The prerequisite steps and tooling focus on Microsoft Teams Client and Teams PowerShell, both of which are primarily Windows-centric. There are no examples or instructions for Linux users, nor is there mention of equivalent Linux tools or command-line patterns. The note about platform support lists Windows explicitly but does not clarify Linux support or provide parity.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Microsoft Graph API, which can be used from Linux environments.
  • Explicitly mention whether Linux is supported for relevant SDKs and features, and provide guidance for Linux users where possible.
  • If PowerShell is required, note the availability of PowerShell Core on Linux and provide Linux-specific setup instructions.
  • Add examples using bash or other Linux-native tools where applicable.
  • Clarify platform support in the 'Platform capabilities' section, including Linux and macOS where relevant.
GitHub Create Pull Request
Communication Services Teams Phone extensibility overview ...epts/interop/tpe/teams-phone-extensibility-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as PowerShell cmdlets and the Teams Admin Center (TAC portal), for administrative tasks. There are no examples or mentions of Linux equivalents or cross-platform alternatives for provisioning, policy assignment, or automation. The documentation assumes the use of Windows-based administration and omits guidance for Linux users, such as using Azure CLI, REST APIs, or cross-platform scripting.
Recommendations
  • Provide Linux and cross-platform examples for Teams administration tasks, such as using Azure CLI or REST APIs for provisioning and policy assignment.
  • Include references to cross-platform tools and scripting languages (e.g., bash, Python) alongside PowerShell examples.
  • Explicitly mention platform-agnostic approaches for automation and configuration, ensuring parity for Linux and macOS users.
  • Add notes or sections clarifying which administrative actions can be performed from non-Windows environments and how.
  • Where PowerShell is referenced, provide equivalent commands or workflows using Azure CLI or other supported cross-platform tools.
GitHub Create Pull Request
Communication Services Teams Phone extensibility Troubleshooting ...terop/tpe/teams-phone-extensibility-troubleshooting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias in troubleshooting steps, especially for Microsoft Entra App permission issues. All command-line examples use PowerShell and Microsoft Graph PowerShell modules, with no mention of Linux/macOS equivalents or cross-platform alternatives. The instructions assume the use of Windows tools and environments, and do not provide parity for Linux users.
Recommendations
  • Provide Azure CLI or Microsoft Graph API REST examples alongside PowerShell commands for tenant and service principal management, which are cross-platform.
  • Explicitly mention whether steps can be performed on Linux/macOS, and offer guidance for those platforms.
  • Include notes or links to documentation for performing equivalent actions using Azure Portal or other platform-agnostic tools.
  • Where PowerShell is required, clarify if PowerShell Core (pwsh) on Linux/macOS is supported, and provide installation instructions if so.
  • Review troubleshooting steps to ensure all admin actions can be performed without requiring Windows-specific tools.
GitHub Create Pull Request
Communication Services Pricing for Teams interop scenarios ...ion-services/concepts/pricing/teams-interop-pricing.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as the use of PowerShell cmdlets (Set-CsPhoneNumberAssignment) for configuration, and mentioning the Teams Desktop client without clarifying cross-platform support. Windows/PowerShell tools are referenced exclusively for administrative tasks, with no Linux alternatives or parity. Example scenarios also specify Windows environments (e.g., 'Windows, Chrome browser') while omitting Linux or macOS equivalents.
Recommendations
  • Provide equivalent Linux/macOS administrative instructions (e.g., Azure CLI, REST API) alongside PowerShell examples.
  • Clarify that Teams Desktop client is available for Windows and macOS, and mention web client support for Linux.
  • Include example scenarios using Linux or macOS environments to demonstrate cross-platform usage.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, browser-based management) before or alongside Windows-specific tools.
  • Avoid assuming Windows as the default environment in user stories and technical instructions.
GitHub Create Pull Request
Communication Services Govern Teams meeting experience with Azure Communication Services ...ts/interop/virtual-visits/govern-meeting-experience.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page focuses exclusively on Microsoft 365, Teams, and Azure tools, which are primarily Windows-centric. There are no examples, instructions, or mentions of Linux-specific tools, patterns, or administration methods. All administrative actions and recommendations assume the use of Microsoft-provided tools, which are most commonly used on Windows platforms, and there is no guidance for Linux administrators or cross-platform scenarios.
Recommendations
  • Include examples or instructions for managing Teams policies and meetings using cross-platform tools such as Azure CLI, which is available on Linux.
  • Mention whether administrative actions (such as policy assignment or meeting template configuration) can be performed via REST APIs or other interfaces accessible from Linux environments.
  • Add notes or sections clarifying platform requirements for each tool, and provide Linux-compatible alternatives where possible.
  • Provide parity in documentation by including Linux shell (bash) examples alongside any PowerShell or Windows GUI instructions.
  • Explicitly state any platform limitations or differences in Teams and Azure Communication Services administration.
GitHub Create Pull Request
Communication Services Plan user experience for virtual appointments ...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Teams Admin Center and PowerShell) as the primary means to learn and configure Teams meeting settings. There are no examples or mentions of Linux equivalents or cross-platform alternatives for managing Teams configurations, and the documentation does not provide parity for Linux users in terms of administrative tooling or command-line instructions.
Recommendations
  • Include cross-platform alternatives for managing Teams configurations, such as Azure CLI or REST API examples, which can be used on Linux and macOS.
  • Explicitly mention whether Teams Admin Center and PowerShell are available or supported on non-Windows platforms, and provide guidance for Linux users.
  • Add examples or links for Linux users to perform equivalent administrative tasks, ensuring feature parity and accessibility.
  • Consider reordering references so that cross-platform or platform-neutral tools are mentioned before or alongside Windows-specific tools.
GitHub Create Pull Request
Communication Services SDKs and REST APIs for Azure Communication Services ...rticles/communication-services/concepts/sdk-options.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias, especially in the SDK platform support section. Windows platforms are listed first and in greater detail, with explicit version ranges and server editions. .NET support is described primarily in terms of Windows technologies (UWP, WinUI3, Windows Server, Windows 10/11), while Linux and macOS are mentioned only briefly and generically. There are no Linux-specific examples, tools, or troubleshooting guidance, and no parity in platform-specific details for Linux or macOS. The documentation does not mention Linux package managers or provide Linux-centric usage patterns.
Recommendations
  • Add explicit Linux and macOS platform support details, including supported distributions and versions.
  • Provide Linux-specific examples, troubleshooting steps, and guidance (e.g., using SDKs on Ubuntu, CentOS, etc.).
  • Include parity in platform-specific details, such as installation instructions for Linux (apt, yum, etc.) and macOS (Homebrew, etc.), not just Windows (NuGet, UWP, WinUI3).
  • List Linux and macOS platforms before or alongside Windows in tables and descriptions, rather than after.
  • Reference cross-platform tools and patterns (e.g., CLI, bash scripts) in addition to Windows-centric ones.
  • Ensure that any platform-specific limitations or notes are provided for Linux and macOS, not just Windows.
GitHub Create Pull Request
Communication Services Azure Communication Services Call Automation how-to for adding Microsoft Teams User into an existing call ...w-tos/call-automation/teams-interop-call-automation.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation demonstrates a Windows bias primarily through its reliance on PowerShell cmdlets (Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) for critical administrative steps, without mentioning or providing Linux/macOS alternatives. The prerequisite and authorization steps assume access to Microsoft Teams PowerShell and Skype for Business PowerShell modules, which are Windows-centric tools. There is no guidance for Linux users on how to perform these administrative tasks, nor are cross-platform CLI or REST API alternatives highlighted. The programming examples themselves are cross-platform, but the administrative setup is Windows-first.
Recommendations
  • Provide equivalent instructions using Microsoft Graph API or Azure CLI for tenant-level and user-level configuration, making the process accessible from Linux/macOS.
  • Explicitly mention platform requirements for PowerShell steps and offer alternatives for non-Windows environments.
  • Add notes or links to documentation on how Linux/macOS users can perform Teams/Skype administrative tasks, e.g., via browser-based admin centers or REST APIs.
  • Where possible, prioritize cross-platform tools and document them before or alongside Windows-specific tools.
GitHub Create Pull Request
Communication Services Add a bot to your chat app ...uickstarts/chat/quickstart-botframework-integration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ visual_studio_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits a Windows bias by consistently referencing Visual Studio (a Windows-centric IDE) for development and deployment steps, providing only Windows-oriented instructions and screenshots, and omitting Linux equivalents or alternatives. There are no examples using Linux-friendly tools (such as VS Code, CLI-only workflows, or Linux deployment commands), and all code and deployment instructions assume a Windows environment. Package installation is shown with dotnet and Powershell, but not with Linux shell commands. No mention is made of Linux or cross-platform development environments.
Recommendations
  • Add instructions and screenshots for using VS Code or other cross-platform editors, including CLI-only workflows.
  • Include Linux shell equivalents for commands (e.g., use 'bash' for dotnet commands, show how to install .NET Core on Linux).
  • Provide deployment steps using Azure CLI on Linux, not just Visual Studio publish dialogs.
  • Mention and link to Linux installation guides for prerequisites (e.g., .NET Core, Bot Framework SDK).
  • Clarify that the SDKs and tools are cross-platform, and explicitly state Linux is supported.
  • Add troubleshooting and FAQ sections for common Linux-specific issues (e.g., permissions, environment setup).
GitHub Create Pull Request
Communication Services Tutorial - Integrate Microsoft Teams breakout rooms ...nication-services/how-tos/calling-sdk/breakoutrooms.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias primarily through its reliance on Windows-centric tools and patterns. The prerequisite for assigning Teams meeting policy links directly to a PowerShell module, which is a Windows-specific tool, and does not mention or provide Linux/macOS alternatives (such as Microsoft Graph API or Teams admin center web interface). The documentation references Windows tools first and exclusively, with no parity for Linux users in administrative tasks. There are no Linux-specific examples or guidance for managing Teams policies or breakout rooms.
Recommendations
  • Provide alternative instructions for assigning Teams meeting policies using cross-platform tools such as Microsoft Graph API or the Teams admin center web interface.
  • Include examples or links for managing breakout rooms from non-Windows environments (Linux/macOS).
  • Clarify which steps are platform-agnostic and which require Windows, and offer parity wherever possible.
  • Add explicit notes or sections for Linux/macOS users to ensure they are not excluded from administrative or development workflows.
GitHub Create Pull Request
Communication Services Tutorial - Teams Shared Line Appearance ...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Teams PowerShell as a method for assigning delegates, without mentioning Linux or cross-platform alternatives. Windows tools and patterns (e.g., PowerShell, Teams Client) are mentioned exclusively or first, and there are no examples or guidance for Linux users. The SDK support table lists 'Windows' as a platform, but does not mention Linux or provide parity. No Linux-specific instructions or examples are provided.
Recommendations
  • Include Linux-compatible methods for assigning delegates, such as using Microsoft Graph API or cross-platform CLI tools.
  • Provide explicit Linux examples or instructions alongside PowerShell/Windows steps.
  • Clarify SDK/platform support for Linux and add relevant documentation if available.
  • Avoid referencing Windows tools exclusively; mention alternatives or note platform limitations.
  • Add a section addressing cross-platform usage and considerations for Linux administrators.
GitHub Create Pull Request
Communication Services include file ...tion-services/quickstarts/chat/includes/chat-csharp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Windows tools (Visual Studio) as a prerequisite without mentioning Linux alternatives, using PowerShell for package installation, and referencing Windows console environments (cmd, PowerShell) before Bash. There are no explicit Linux instructions or examples for installing dependencies or running the sample, and the development workflow assumes a Windows-centric environment.
Recommendations
  • Include Linux development environment options in prerequisites, such as VS Code or JetBrains Rider.
  • Provide explicit Bash and Linux shell examples for package installation (e.g., use 'dotnet add package' in Bash, not PowerShell).
  • List Bash and Linux terminal environments before or alongside Windows ones when giving instructions.
  • Clarify that the .NET CLI commands work cross-platform and provide troubleshooting tips for Linux users.
  • Mention Linux-specific requirements or dependencies if any (e.g., mono, .NET SDK installation on Linux).
  • Add links to Linux setup guides for .NET and Azure CLI.
GitHub Create Pull Request
Communication Services Create a Communication Services resource in Azure Communication Services ...-services/quickstarts/create-communication-resource.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific instructions and tools (e.g., PowerShell, setx, app.config/web.config) are presented first or exclusively in several sections. The Azure CLI installation link defaults to Windows, and examples use PowerShell syntax. Linux and macOS instructions are present but are secondary, and some configuration file references (app.config/web.config) are Windows/.NET-centric.
Recommendations
  • Present platform instructions in parallel or randomized order, rather than always listing Windows first.
  • Include Linux/macOS equivalents for all configuration and tooling examples (e.g., mention .env files, systemd environment files, or other common Linux patterns for storing secrets).
  • Provide links to Azure CLI installation for all platforms, not just Windows.
  • Balance SDK examples by including samples for Python, Java, or Node.js, which are popular on Linux/macOS.
  • When referencing configuration files, mention cross-platform alternatives (e.g., .env, environment variables, secrets managers) alongside Windows-specific files.
  • Avoid PowerShell-specific syntax in CLI examples unless explicitly in a PowerShell section; use bash/zsh syntax for Linux/macOS sections.
GitHub Create Pull Request
Communication Services Add custom verified email domains ...vices/quickstarts/email/add-custom-verified-domains.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways. PowerShell is given its own dedicated section, and the only DNS management guide for 'Other (General)' links to a Windows-based DNS guide, with no mention of Linux-based DNS servers (e.g., BIND). There are no explicit Linux command-line examples or references to Linux-native tools for DNS management. The ordering of pivots and examples tends to favor Windows technologies and tools, with Windows/PowerShell options listed before Linux alternatives or not at all.
Recommendations
  • Add explicit Linux/BIND DNS management instructions and links for users managing their own DNS on Linux servers.
  • Include Linux shell (bash) examples for relevant Azure CLI commands, clarifying cross-platform usage.
  • Provide parity in documentation for Linux-native tools (e.g., dig, nsupdate) alongside Windows/PowerShell examples.
  • Ensure that 'Other (General)' DNS instructions include both Windows and Linux server scenarios.
  • Review ordering of pivots and examples to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Communication Services Create and manage Email Communication Service resource in Azure Communication Services ...ickstarts/email/create-email-communication-resource.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a Windows bias by including PowerShell as a primary platform pivot, listing it alongside Azure portal, .NET, and Azure CLI. PowerShell is a Windows-centric tool, and its inclusion as a first-class example suggests prioritization of Windows workflows. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users. The documentation does not clarify cross-platform compatibility for the .NET or Azure CLI instructions, and the ordering of pivots places PowerShell before any Linux-specific alternatives.
Recommendations
  • Add explicit Bash or Linux shell examples where applicable, especially for resource management via Azure CLI.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide platform-specific notes if there are differences.
  • Include instructions or pivots for Linux-native tools or environments, such as Bash scripts or references to Linux package managers.
  • Reorder platform pivots to avoid implicit prioritization of Windows tools (e.g., list Azure CLI before PowerShell).
  • Add a section or note on cross-platform compatibility for all management options, ensuring Linux users are equally supported.
GitHub Create Pull Request
Communication Services Prerequisites ...es/create-custom-managed-domain-resource-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all resource management tasks. There are no examples or instructions for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. The documentation assumes a Windows environment and does not mention alternative tools or workflows available on Linux or macOS.
Recommendations
  • Provide equivalent Azure CLI examples for all resource management operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Add a 'Platform compatibility' note clarifying that PowerShell Core is available on Linux and macOS, but also recommend Azure CLI for non-Windows users.
  • Reorder sections or provide parallel instructions so that Linux/macOS tools (Azure CLI, Bash) are presented alongside or before Windows-specific tools.
  • Include installation instructions for Azure CLI and/or PowerShell Core on Linux/macOS.
  • Explicitly mention that all operations can be performed from any OS using Azure CLI, and link to relevant CLI documentation.
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-smtpclient.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when describing where to run commands. All code examples use C#/.NET, which is cross-platform but traditionally associated with Windows. There are no explicit Linux or macOS-specific instructions, troubleshooting, or examples, and no mention of platform-specific issues or alternatives. The documentation does not provide parity for Linux users in terms of environment setup, command-line usage, or platform-specific notes.
Recommendations
  • List Bash or Linux terminal first or equally when describing where to run commands.
  • Add explicit instructions or troubleshooting notes for Linux/macOS users (e.g., package installation, permissions, firewall settings).
  • Include example commands for Linux/macOS environments, such as using terminal commands to install .NET or run the application.
  • Mention any platform-specific caveats, such as differences in handling SSL certificates or environment variables.
  • Clarify that .NET Core and SmtpClient are cross-platform and provide links to Linux/macOS documentation where relevant.
GitHub Create Pull Request
Communication Services Send an email using SMTP ...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides examples for sending email via SMTP using SmtpClient (typically .NET, often Windows-centric) and Windows PowerShell, but does not include Linux-specific tools or examples (such as using sendmail, mailx, or Python scripts on Linux). The inclusion of 'Windows Powershell' as a dedicated section and the absence of Linux command-line or scripting alternatives demonstrates a bias towards Windows environments.
Recommendations
  • Add examples using common Linux tools (e.g., sendmail, mailx, swaks) for sending email via SMTP.
  • Include a Python example that works cross-platform, with installation instructions for Linux.
  • Provide guidance for configuring SMTP on Linux systems, including authentication and TLS.
  • Ensure that examples and instructions are clearly labeled for both Windows and Linux users.
  • Consider adding a section comparing Windows and Linux approaches, highlighting platform-specific nuances.
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively provides instructions and examples using PowerShell and the Send-MailMessage cmdlet, which are native to Windows. There are no examples or guidance for sending email via SMTP from Linux or macOS environments, nor are cross-platform tools (such as curl, swaks, or Python scripts) mentioned. The documentation assumes the user is on Windows and familiar with Windows-specific tooling.
Recommendations
  • Add equivalent SMTP email sending examples for Linux and macOS, using tools such as swaks, curl, or Python's smtplib.
  • Include instructions for storing credentials securely on non-Windows platforms.
  • Present cross-platform examples side-by-side, or clearly indicate platform-specific sections.
  • Mention alternative tools and approaches for users who do not have access to PowerShell or prefer open-source solutions.
GitHub Create Pull Request
Communication Services Prerequisites ...rts/email/includes/create-email-resource-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively uses PowerShell commands and examples, which are native to Windows. There is no mention of equivalent Azure CLI or Bash commands, nor any guidance for Linux or macOS users. The prerequisites and instructions assume the use of Windows tools and patterns, creating a strong Windows bias.
Recommendations
  • Add Azure CLI examples alongside PowerShell commands for all operations (resource creation, management, deletion).
  • Include installation instructions for Azure CLI and note cross-platform compatibility.
  • Explicitly mention that Azure CLI and Bash can be used on Linux and macOS, and provide sample commands.
  • Reorder sections or add notes to clarify that both PowerShell and CLI approaches are supported and provide parity.
  • Consider adding a table comparing PowerShell and CLI commands for common tasks.
GitHub Create Pull Request
Communication Services Prerequisites ...includes/create-sender-username-resource-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module, which is primarily associated with Windows environments. There are no examples or instructions for Linux users (e.g., Bash, Azure CLI), and Windows-centric tools and patterns are mentioned without Linux equivalents. This creates a bias towards Windows and may hinder Linux users from following the guide.
Recommendations
  • Provide equivalent Azure CLI examples for all operations (login, resource creation, management, deletion).
  • Explicitly mention cross-platform compatibility of Azure PowerShell, or clarify if steps are Windows-only.
  • Add instructions for installing and using Azure CLI on Linux/macOS.
  • Reorder prerequisites and examples to present cross-platform tools (e.g., Azure CLI) before or alongside PowerShell.
  • Include notes or links for Linux/macOS users to ensure parity and accessibility.
GitHub Create Pull Request
Communication Services include file ...uickstarts/email/includes/send-email-async-sync-net.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific console environments (cmd, PowerShell) before mentioning Bash, and by providing only .NET/C# examples and commands. There are no Linux-specific instructions, examples, or troubleshooting notes, and no mention of Linux package managers or shell environments beyond a brief mention of Bash. All code samples and tooling instructions assume a Windows/.NET development environment.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms for .NET Core and Azure Communication Services Email SDK.
  • Provide Linux-specific instructions for installing .NET Core (e.g., using apt, yum, or Homebrew).
  • Include example commands for Bash and other Linux shells, and clarify any differences in environment variable setup or file paths.
  • Add troubleshooting notes for common Linux issues (e.g., permissions, firewall, dependency installation).
  • Reference cross-platform editors (e.g., VS Code) and clarify that the steps work on Linux and macOS as well as Windows.
  • Ensure parity in sample code and instructions for running and building the application on Linux/macOS terminals.
GitHub Create Pull Request
Communication Services include file ...es/quickstarts/email/includes/send-email-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses Azure PowerShell for all examples and instructions, with explicit references to running commands in 'windows PowerShell'. There are no examples or guidance for Linux or cross-platform alternatives (such as Azure CLI or REST API). The installation instructions and code samples are all tailored to Windows/PowerShell users, and there is no mention of Linux-compatible tools or workflows.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, and provide installation instructions for those platforms.
  • Include REST API or SDK (e.g., Python, Node.js) examples for sending emails, to support users on non-Windows platforms.
  • Rephrase instructions to avoid assuming a Windows environment (e.g., say 'in your terminal' instead of 'in a windows PowerShell').
  • Provide guidance on checking module installation and running commands on Linux/macOS terminals.
GitHub Create Pull Request
Communication Services include file ...arts/email/send-email-advanced/includes/prepend-net.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific consoles (cmd, PowerShell) before mentioning Bash, and by not providing any Linux-specific instructions or examples. All command-line instructions use the generic 'dotnet' CLI, but there are no explicit Linux shell or environment setup examples. The Azure portal is referenced for resource management, but no mention is made of CLI alternatives (such as Azure CLI) that are popular on Linux. There are no examples of Linux-specific patterns, nor guidance for Linux users regarding environment variables or file paths.
Recommendations
  • Explicitly mention Linux and macOS support in the prerequisites and instructions.
  • Provide example commands for Linux shells (e.g., Bash, zsh) alongside Windows (cmd, PowerShell).
  • Include guidance for setting environment variables on Linux (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...) and macOS.
  • Reference Azure CLI or other cross-platform tools for resource management as alternatives to the Azure portal.
  • Ensure file paths and editor instructions are platform-neutral or provide platform-specific notes.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, .NET installation differences).
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a bias towards Windows environments and tooling. All code examples and instructions use C#/.NET, with commands such as dotnet new, dotnet build, dotnet add package, and dotnet run. Console references include 'cmd', 'PowerShell', and 'Bash', but no Linux-specific instructions, troubleshooting, or environment setup are provided. There are no Linux or cross-platform code samples, nor are there references to Linux package managers or shell environments beyond generic mentions. The documentation assumes familiarity with Windows development patterns and does not address Linux-specific nuances.
Recommendations
  • Add explicit Linux instructions for installing .NET Core and running the sample, including package manager commands (e.g., apt, yum, zypper).
  • Provide troubleshooting steps for common Linux issues (e.g., permissions, environment variables).
  • Include sample code or terminal output from a Linux shell (e.g., bash/zsh) to demonstrate parity.
  • Mention cross-platform editors (e.g., VS Code, Vim) and how to open/edit Program.cs on Linux.
  • Clarify that the .NET SDK and Azure Communication Services Email client library are cross-platform and provide links to Linux-specific documentation.
  • Add a section on running the sample in containers or on WSL for Windows users who want a Linux-like environment.
GitHub Create Pull Request
Communication Services include file ...ail-advanced/includes/inline-attachments-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page exclusively uses Windows PowerShell for all examples and instructions, including installation and usage of the Azure Communication Services module. There is no mention of Linux, macOS, or cross-platform alternatives such as Azure CLI, Bash, or PowerShell Core. The prerequisite check and module installation steps are Windows/PowerShell-specific, and all code samples use PowerShell syntax. No Linux-specific tools, commands, or instructions are provided.
Recommendations
  • Add equivalent instructions and examples for Linux and macOS users, such as using PowerShell Core (pwsh) or Azure CLI.
  • Clarify that Azure PowerShell can be used cross-platform and provide installation steps for Linux and macOS.
  • Include Bash or Azure CLI examples for sending emails, if supported.
  • Update prerequisite checks to include Linux/macOS environments, e.g., checking module installation in PowerShell Core or Azure CLI.
  • Explicitly mention platform compatibility and provide guidance for non-Windows users.
GitHub Create Pull Request
Communication Services Send email with inline attachments ...d-email-advanced/send-email-with-inline-attachments.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page provides examples for multiple programming languages and tools, including Azure CLI and PowerShell. However, the inclusion of PowerShell as a distinct pivot and the absence of explicit Linux shell (bash) examples or references to Linux-native tools (such as bash scripts or shell commands) indicates a bias towards Windows environments. PowerShell is primarily associated with Windows, and its presence without a corresponding bash or Linux shell example suggests a Windows-first approach. Additionally, there are no troubleshooting or resource management instructions tailored for Linux users.
Recommendations
  • Add explicit bash or Linux shell examples alongside PowerShell, especially for command-line operations.
  • Include troubleshooting steps or resource management instructions relevant to Linux environments.
  • Ensure that references to command-line tools are balanced between Windows and Linux, mentioning both PowerShell and bash where appropriate.
  • Consider adding a 'programming-language-bash' or 'programming-language-linux-shell' pivot for parity.
  • Review and update any instructions or notes that assume a Windows environment to be more platform-neutral.
GitHub Create Pull Request
Communication Services Prerequisites ...vents/includes/create-event-subscription-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exclusively uses Azure PowerShell commands and modules for all examples and instructions, with no mention of Azure CLI, Bash, or Linux-native tools. The prerequisites and step-by-step guides assume PowerShell usage, which is most common on Windows. There are no Linux or cross-platform alternatives provided, and the documentation does not acknowledge non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions).
  • Include installation instructions for Azure CLI and note its cross-platform compatibility.
  • Explicitly mention that PowerShell is available on Linux and macOS, but provide Bash/CLI examples for users who prefer native Linux tools.
  • Reorder or parallelize examples so that Windows and Linux instructions are presented side-by-side or in separate tabs.
  • Reference documentation for both PowerShell and CLI tools in the 'Next steps' section.
GitHub Create Pull Request
Communication Services Subscribe to events ...ion-services/quickstarts/events/subscribe-to-events.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary method for subscribing to events, referencing Windows-centric tools (PowerShell, .NET SDK), and omitting explicit Linux shell examples. The Azure CLI is mentioned, but there is no clear parity in examples or guidance for Linux users, and the .NET SDK reference further reinforces a Windows-centric approach.
Recommendations
  • Add explicit Bash or Linux shell examples alongside PowerShell, especially in code snippets and step-by-step instructions.
  • Mention cross-platform compatibility for Azure CLI and .NET SDK, and provide guidance for using these tools on Linux and macOS.
  • Include references to other SDKs (e.g., Python, JavaScript) that are commonly used on Linux.
  • Reorder sections so that platform-neutral or Linux-friendly tools (like Azure CLI) are presented before Windows-specific tools (like PowerShell).
  • Clarify that PowerShell Core is cross-platform if recommending PowerShell, and provide installation instructions for Linux.
GitHub Create Pull Request
Communication Services Register the Event Grid resource provider ...starts/events/includes/register-provider-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation exclusively provides PowerShell commands for registering the Event Grid resource provider, which are typically used on Windows. There are no examples or instructions for Linux or cross-platform tools such as Azure CLI, and no mention of alternatives for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI commands for registering and checking the status of the Event Grid resource provider, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Include a note clarifying that PowerShell examples are for Windows users and provide guidance for users on other operating systems.
  • Consider reordering examples to present cross-platform tools (e.g., Azure CLI) before platform-specific ones (e.g., PowerShell) to avoid implicit prioritization of Windows.
  • Explicitly mention the availability of Azure CLI and provide installation links for users on Linux and macOS.
GitHub Create Pull Request
Communication Services Prerequisites ...ces/quickstarts/includes/create-resource-powershell.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exclusively uses PowerShell commands and Windows-centric tooling (Az PowerShell Module) for all examples and instructions. There are no Linux or cross-platform CLI examples (such as Azure CLI), nor is there mention of how to perform these tasks on Linux or macOS. The documentation assumes the use of PowerShell and Windows tools, which may not be available or preferred on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include installation instructions for Azure CLI and/or Az PowerShell on Linux and macOS, or link to relevant documentation.
  • Clearly indicate which commands and modules are Windows-specific and suggest alternatives for other platforms.
  • Reorder or balance examples so that Linux/macOS options are presented alongside or before Windows/PowerShell examples.
  • Add a section discussing platform compatibility and best practices for users on non-Windows systems.
GitHub Create Pull Request
Communication Services Set up and obtain access tokens for Microsoft Entra ID users ...ntity/microsoft-entra-id-authentication-integration.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily through its exclusive mention of Windows-centric tools (Azure portal, Microsoft Entra admin center) and patterns. While the Azure CLI is referenced (which is cross-platform), there are no explicit Linux-specific instructions, examples, or screenshots. The documentation assumes use of the Azure portal and admin center, which are web-based but often presented with a Windows-centric UI. There is no mention of Linux shell commands, environment setup, or alternative workflows for Linux users. No PowerShell examples are present, but the overall flow and tooling are Windows-oriented.
Recommendations
  • Add explicit Linux shell examples for relevant CLI commands, including environment setup and authentication.
  • Include notes or screenshots showing the Azure portal and admin center on Linux browsers to clarify cross-platform compatibility.
  • Mention that Azure CLI is cross-platform and provide troubleshooting tips for Linux users (e.g., installation, authentication).
  • If any steps can be performed via REST API or automation, provide curl/bash examples alongside Azure CLI.
  • Clarify that all steps can be performed on Linux and MacOS as well as Windows, and highlight any platform-specific caveats.
GitHub Create Pull Request
Communication Services include file ...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides command-line examples for both Command Prompt and PowerShell, which are Windows-specific shells, but does not provide any explicit Linux or macOS shell examples (e.g., Bash). The order of presentation is Windows-first, and there are no references to Linux tools, shells, or platform-specific instructions for non-Windows users.
Recommendations
  • Add Bash (Linux/macOS) command examples alongside Command Prompt and PowerShell examples for all CLI instructions.
  • Explicitly mention support for Linux/macOS platforms in the prerequisites and setup sections.
  • Include notes or sections on platform differences, such as file paths and shell syntax, where relevant.
  • Ensure parity in troubleshooting and environment setup instructions for Linux/macOS users.
GitHub Create Pull Request
Communication Services Set up and create access tokens for Teams users ...nication-services/quickstarts/manage-teams-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a bias towards Windows environments, particularly in the administrator troubleshooting section. PowerShell is exclusively used for command-line examples, with no mention of Linux or cross-platform alternatives. Instructions for installing and using the Microsoft Graph module are Windows/PowerShell-centric, and there are no Bash, Azure CLI, or Linux-native equivalents provided. The troubleshooting steps and tooling references assume a Windows environment, which may hinder Linux users or those on other platforms.
Recommendations
  • Provide equivalent command-line instructions using Azure CLI and/or Bash for Linux/macOS users.
  • Mention cross-platform alternatives to PowerShell, such as running commands in Bash or using REST APIs directly.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer guidance for non-Windows environments.
  • Include links or references to documentation for Linux/macOS setup of required tools (e.g., Microsoft Graph CLI, Azure CLI).
  • Ensure that all code samples and troubleshooting steps have Linux/macOS parity, or explicitly state platform requirements.
GitHub Create Pull Request
Communication Services References - How to collect verbose log from browsers ...lling/references/how-to-collect-browser-verbose-log.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively provides instructions and examples for collecting verbose logs from browsers on Windows, using Windows file paths, command syntax, and tools. There are no Linux or macOS equivalents, nor any mention of how to perform the same task on those platforms.
Recommendations
  • Add Linux/macOS instructions for launching Edge/Chrome with verbose logging, including example command lines using typical executable paths (e.g., /usr/bin/google-chrome).
  • Specify where logs are saved on Linux/macOS and how to locate them.
  • Mention any platform-specific differences in command-line arguments or log file locations.
  • Present examples for all major platforms, or clearly indicate platform-specific instructions.
GitHub Create Pull Request
Connectors Connect to 3270 apps on IBM mainframes ...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation demonstrates a Windows bias primarily through its reliance on the 3270 Design Tool, which requires Microsoft .NET Framework 4.8—a Windows-only prerequisite. There are no alternative instructions or tools for Linux or macOS users to generate the required HIDX file, nor is there mention of cross-platform compatibility for the design tool. All setup and workflow examples assume use of the Azure Portal (web-based), but the critical metadata generation step is Windows-dependent. Linux/macOS users are left without a clear path to complete the task.
Recommendations
  • Provide information on whether the 3270 Design Tool can run under Wine or Mono on Linux/macOS, or offer a supported cross-platform version.
  • List alternative methods or open-source tools for generating HIDX files on non-Windows platforms, if available.
  • Explicitly state the platform limitations of the 3270 Design Tool and suggest workarounds for Linux/macOS users.
  • Consider adding a note or section for Linux/macOS users outlining the steps required to obtain or generate HIDX files if they do not have access to Windows.
  • If possible, develop and document a web-based or cross-platform tool for HIDX file creation.
GitHub Create Pull Request
Connectors Access CICS Programs from Standard Workflows ...ticles/connectors/integrate-cics-apps-ibm-mainframe.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools (HIS Designer, .NET Framework 4.8) for generating required metadata, with no mention of Linux/macOS alternatives or compatibility. All setup instructions and prerequisites assume a Windows environment, and there are no examples or guidance for Linux or macOS users.
Recommendations
  • Clarify whether HIS Designer and required components (e.g., .NET Framework) are available or supported on Linux/macOS, or provide alternatives if available.
  • If the tools are Windows-only, explicitly state this limitation and suggest possible workarounds (e.g., using a Windows VM, Docker container, or remote desktop).
  • Add examples or notes for Linux/macOS users regarding how to obtain or generate the HIDX file, or how to interact with the Azure portal from non-Windows systems.
  • Consider developing or linking to cross-platform tooling for metadata generation if feasible.
GitHub Create Pull Request
Active Directory B2C Authorization code flow - Azure Active Directory B2C ...ticles/active-directory-b2c/authorization-code-flow.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias. The only tool explicitly recommended for testing HTTP POST requests is Microsoft PowerShell, with no mention of Linux or cross-platform alternatives (e.g., curl, httpie). This reference appears before any mention of Linux tools, and no Linux-specific or cross-platform examples are provided. All other content is platform-neutral, focusing on HTTP requests and protocol details.
Recommendations
  • Include Linux and cross-platform command-line examples, such as curl or httpie, alongside or before PowerShell references.
  • Explicitly mention that any HTTP client can be used, and provide sample commands for both Windows (PowerShell) and Linux/macOS (curl, wget, httpie).
  • Avoid recommending Microsoft-specific tools exclusively; instead, provide a balanced set of options for different operating systems.
  • Add a section or note clarifying cross-platform compatibility and tool choices for developers on Linux, macOS, and Windows.
GitHub Create Pull Request
API Center Import APIs from Azure API Management - Azure API Center ...main/articles/api-center/import-api-management-apis.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell, but consistently presents PowerShell examples immediately after bash, sometimes with explicit formatting notes. There is a recurring emphasis on PowerShell syntax and usage, which may suggest a slight Windows bias. However, Linux/bash examples are present and not omitted.
Recommendations
  • Alternate the order of shell examples, sometimes presenting bash first and sometimes PowerShell, or group them together for parity.
  • Add explicit notes or sections for macOS users if there are any platform-specific considerations.
  • Clarify that all CLI commands are cross-platform and highlight any differences or caveats for Linux/macOS users.
  • Consider providing generic CLI examples without shell-specific formatting where possible, or use tabs/expanders to let users select their shell.
  • Ensure that any referenced tooling, scripts, or file paths use neutral or platform-agnostic conventions.
GitHub Create Pull Request
API Management Set Up Logging for LLM APIs in Azure API Management ...ticles/api-management/api-management-howto-llm-logs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes configuration and log review steps using the Azure Portal GUI, which is most commonly accessed on Windows systems. There are no CLI, PowerShell, or Bash examples, but the workflow implicitly assumes a graphical environment typical of Windows. There is no mention of Linux tools, command-line alternatives, or cross-platform automation methods for enabling logging or exporting data.
Recommendations
  • Add Azure CLI and/or Azure PowerShell examples for enabling diagnostic settings and exporting logs, ensuring commands work on both Windows and Linux.
  • Include instructions for configuring logging using ARM templates or Bicep, which are platform-neutral.
  • Provide sample Kusto queries that can be run from the Azure CLI or Azure Cloud Shell, not just via the portal.
  • Mention and demonstrate how to access and manipulate logs from Linux environments, such as using curl, jq, or az CLI.
  • Clarify that all steps can be performed from any OS, and link to cross-platform tooling documentation.
GitHub Create Pull Request
Active Directory B2C Set up sign-up and sign-in with a Microsoft Account ...e-directory-b2c/identity-provider-microsoft-account.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively references the Azure portal web UI and does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell). There is no mention of Linux-specific tools, nor is there any parity in examples for Linux environments. All instructions are GUI-based and implicitly assume a Windows-centric workflow, as the Azure portal is most commonly used in Windows environments and the documentation does not acknowledge alternative platforms or automation approaches.
Recommendations
  • Add Azure CLI examples for all major steps (e.g., app registration, secret creation, identity provider configuration) to support Linux and cross-platform users.
  • Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide links or instructions for command-line alternatives.
  • Include sample scripts for Bash and PowerShell where relevant, and present them side-by-side to ensure parity.
  • Reference Linux-friendly tools and workflows (e.g., VS Code, Azure CLI, REST API) where possible.
  • Add a note clarifying platform independence for all steps, and avoid implying a Windows-only workflow.
GitHub Create Pull Request
Active Directory B2C Register a Microsoft Graph application ...es/active-directory-b2c/microsoft-graph-get-started.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively describes management tasks using the Azure portal (web UI) and does not provide any command-line examples. There is no mention of platform-specific tools, but all instructions assume use of the Azure portal, which is equally accessible from Windows and Linux. However, there is a subtle Windows bias in the absence of Linux-oriented automation examples (e.g., Bash, CLI, or scripting), and no mention of PowerShell or Windows tools, but also no parity for Linux shell or CLI workflows.
Recommendations
  • Add examples for registering applications and granting permissions using Azure CLI (az), which is cross-platform and widely used on Linux.
  • Include sample scripts for automating these tasks using Bash or other Linux-friendly tools.
  • If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided.
  • Explicitly mention that all steps can be performed from any OS with a web browser, and highlight automation options for both Windows and Linux users.
GitHub Create Pull Request
App Service Quickstart: Use Terraform to configure an Azure App Service Environment v3 ...articles/app-service/environment/creation-terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but Azure PowerShell is given equal prominence as Azure CLI, despite PowerShell being primarily a Windows tool. There are no Linux-specific shell examples (e.g., Bash), and PowerShell usage may be less familiar or available on Linux platforms. The order of presentation (CLI first, then PowerShell) is reasonable, but the inclusion of PowerShell as a primary tab may signal Windows bias.
Recommendations
  • Ensure all command-line examples work seamlessly on Linux/macOS (e.g., Bash shell).
  • Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Consider adding explicit Bash shell examples or notes for Linux users, especially for variable assignment and command syntax.
  • If PowerShell is included, note its cross-platform availability but clarify its historical Windows focus.
  • Review other sections for implicit assumptions about Windows environments (e.g., file paths, tool installation instructions).
GitHub Create Pull Request
App Service [Portal](#tab/azure-portal) ...torial-dotnet-storage-managed-identity/introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is consistently listed before Azure CLI in all code example sections. This ordering may suggest a preference for Windows environments. There are no Linux-specific tools, shell, or OS-specific instructions, and PowerShell is not as commonly used on Linux as on Windows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first, as it is cross-platform and more common on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary Linux-specific notes (e.g., line continuation differences, shell requirements).
  • Where possible, include bash shell examples or highlight any OS-specific considerations.
  • If referencing Visual Studio (a Windows-first IDE), also mention cross-platform alternatives (e.g., VS Code) for Linux users.
GitHub Create Pull Request
Active Directory B2C Twilio Verify App with Azure Active Directory B2C ...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows-first bias by referencing .NET and web.config configuration, which are primarily associated with Windows environments. There are no explicit Linux or cross-platform deployment instructions, nor are there examples for Linux-based hosting or configuration (e.g., appsettings.json, environment variables, or Linux deployment steps). Certificate creation and hosting guidance are linked to Azure App Service, but do not mention Linux alternatives or provide parity for Linux users.
Recommendations
  • Provide equivalent instructions for Linux-based deployments, including configuration using appsettings.json or environment variables.
  • Include examples for hosting the demo application on Linux platforms (e.g., Azure App Service for Linux, Docker, or other Linux-based web servers).
  • Offer guidance for certificate creation and management on Linux (e.g., using OpenSSL).
  • Ensure that all configuration steps (such as updating keys and certificates) have cross-platform examples.
  • Clarify that the .NET app can be run on Linux using .NET Core/6+, and provide relevant commands for Linux environments.
GitHub Create Pull Request
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell-only example for enabling HTTP/2 support on Application Gateway listeners, with no equivalent CLI or Bash example for Linux users. There is no mention of Azure CLI or cross-platform tools, and the only code snippet is Windows-centric. This may hinder Linux and macOS users who do not use PowerShell.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all configuration tasks, especially for enabling HTTP/2 support.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Ensure that all code snippets are available in both PowerShell and CLI/Bash formats, and present them in parallel or with clear tabs.
  • Review other sections for implicit Windows-first patterns and update them to reference cross-platform tools where applicable.
GitHub Create Pull Request
Application Gateway Troubleshoot Application Gateway for Containers ...cation-gateway/for-containers/troubleshooting-guide.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example is presented after the Linux example and uses Windows-specific tools (findstr). There is a slight bias in that Windows command-line tools are explicitly called out, and the documentation uses a '[Linux]' and '[Windows]' tab structure, which can sometimes lead to Windows-first presentation in other contexts. However, most of the core troubleshooting steps use cross-platform tools (kubectl, helm) and Bash syntax, which are more common in Linux environments.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence and clarity.
  • Consider using a neutral tab structure (e.g., 'Linux/macOS' and 'Windows') and avoid implying one platform is primary.
  • Where possible, provide examples for macOS as well, or clarify that Linux commands work on macOS.
  • If using platform-specific tools (e.g., findstr for Windows), briefly explain their purpose and provide links to documentation for users unfamiliar with them.
  • Review the order of examples to avoid unintentional prioritization of Windows commands or tools.
GitHub Create Pull Request
Active Directory B2C Troubleshoot custom policies and user flows in Azure Active Directory B2C ...lob/main/articles/active-directory-b2c/troubleshoot.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a mild Windows bias. Troubleshooting tools and examples mention Windows-centric tools (Fiddler, Edge/Internet Explorer developer tools) and browser extensions for Chrome/Edge/Firefox, but do not mention Linux-native alternatives. When listing SAML debugging tools, Edge/IE developer tools are included alongside browser extensions, and Fiddler is recommended for tracing, both of which are primarily Windows tools. Visual Studio Code is recommended as an editor, which is cross-platform, but all configuration and screenshots are shown in a way that assumes a Windows-like environment (e.g., 'File>Preferences>Settings'). No Linux-specific troubleshooting tools or command-line examples are provided.
Recommendations
  • Include Linux-native alternatives for protocol tracing, such as Wireshark, mitmproxy, or curl for SAML/JWT debugging.
  • When mentioning Fiddler, clarify its availability on Linux (via Fiddler Everywhere) or suggest alternatives.
  • Add explicit instructions or screenshots for Visual Studio Code usage on Linux/macOS, including file navigation and settings.
  • List browser extensions and tools that work across all major platforms, and avoid listing Windows-only developer tools before cross-platform options.
  • Provide command-line examples for troubleshooting (e.g., using curl, jq, or OpenSSL for JWT/SAML inspection) to improve parity for Linux users.
GitHub Create Pull Request
API Center Include file .../includes/configure-managed-identity-kv-secret-user.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are given immediately after Bash, and the variable assignment syntax is labeled 'Formatted for PowerShell' rather than 'Windows'. There is no explicit mention of Linux or macOS, and no examples for those platforms beyond Bash. The portal instructions implicitly assume a Windows environment due to the use of PowerShell and lack of mention of Linux-specific tools or workflows.
Recommendations
  • Explicitly mention that Bash examples are suitable for Linux/macOS and that PowerShell examples are for Windows.
  • Provide clear guidance on which shell to use for each operating system.
  • Include notes or tabs for Linux/macOS users, such as using Bash in WSL or native terminals.
  • Avoid labeling examples as 'Formatted for PowerShell' only; instead, use 'Windows (PowerShell)' and 'Linux/macOS (Bash)'.
  • Consider adding troubleshooting tips for common issues on Linux/macOS (e.g., permissions, path differences).
GitHub Create Pull Request
API Center Enable API Center portal view - Azure API Center - VS Code extension ...i-center/enable-api-center-portal-vs-code-extension.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code and its extensions, which, while cross-platform, are most commonly associated with Windows environments. The instructions and screenshots focus on VS Code usage patterns (e.g., Ctrl+Shift+P shortcut) without mentioning Linux-specific alternatives or keyboard shortcuts. There are no examples or guidance for Linux users, such as using VS Code on Linux, or alternative CLI-based workflows. Additionally, all authentication and troubleshooting steps are described in terms of Azure and Microsoft Entra, with no mention of Linux-specific considerations or potential issues.
Recommendations
  • Add explicit notes confirming that Visual Studio Code and the Azure API Center extension are supported on Linux and macOS, and provide installation instructions for those platforms.
  • Include Linux/macOS keyboard shortcuts (e.g., Cmd+Shift+P for macOS) alongside Windows shortcuts.
  • Provide screenshots from VS Code running on Linux or macOS, or clarify that the UI is identical across platforms.
  • Mention any Linux-specific troubleshooting steps or considerations, such as package dependencies or permissions.
  • If possible, offer CLI-based alternatives for connecting to the API Center, for users who prefer terminal workflows.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using Bicep ...ain/articles/application-gateway/quick-create-bicep.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup tasks. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is mentioned in every example tab. There is no mention of Linux-specific tools or shell patterns (such as Bash), nor are there any explicit Linux VM management or SSH examples. The use of PowerShell may suggest a Windows bias, especially for users who are not on Windows platforms.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Windows, macOS, and Linux.
  • Add explicit Bash shell examples or notes for Linux/macOS users, especially for command-line tasks.
  • Mention SSH as a method to connect to Linux VMs, if relevant to the scenario.
  • If PowerShell is included, consider noting that PowerShell Core is available cross-platform, or provide Bash alternatives.
  • Ensure that any VM configuration steps (such as IIS setup) also mention Linux alternatives (e.g., Apache or Nginx) if the backend could be Linux.
GitHub Create Pull Request
API Center Include file ...ter/includes/configure-managed-identity-apim-reader.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are given immediately after the Bash ones, and use Windows-specific syntax (e.g., backticks for line continuation, .substring method). There is no explicit mention of Linux or macOS environments, nor any guidance for users on non-Windows platforms. The portal instructions are generic, but the CLI section leans toward Windows by including PowerShell-formatted code for each step.
Recommendations
  • Explicitly state that Bash examples are for Linux/macOS and PowerShell examples are for Windows, helping users identify which to use.
  • Provide clear guidance or a note at the start of the CLI section about which shell/environment each example is intended for.
  • Consider listing Bash (Linux/macOS) examples first to avoid implicit Windows-first bias.
  • Add troubleshooting tips or links for common issues encountered on Linux/macOS (e.g., Azure CLI installation, shell compatibility).
  • Ensure parity in explanations and code comments for both Bash and PowerShell, and avoid assuming PowerShell as the default for CLI usage.
GitHub Create Pull Request
API Center Include file ...enter/includes/quickstart-template-review-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation mentions Azure PowerShell as a tool for listing deployed resources alongside Azure CLI, but does not provide explicit Linux-specific examples or mention Linux shell tools. The ordering of 'Azure CLI or Azure PowerShell' may suggest a slight Windows-first bias, and the lack of Linux-specific guidance or examples further reinforces this.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux (bash).
  • Include Linux shell examples (e.g., bash) for listing resources using Azure CLI.
  • Clarify that Azure PowerShell is primarily a Windows tool, and suggest alternatives for Linux users.
  • Consider reordering to mention Azure CLI before Azure PowerShell, as CLI is more universally available.
GitHub Create Pull Request
API Center Quickstart - Create Your Azure API Center - Bicep ...ob/main/articles/api-center/set-up-api-center-bicep.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the Bicep file, but PowerShell is featured equally alongside CLI, and there is no mention of Linux-specific tools or shell environments (e.g., Bash). The prerequisites and deployment instructions do not clarify cross-platform usage, and PowerShell (traditionally Windows-centric) is presented without noting its availability on Linux. No Linux-specific examples, troubleshooting, or guidance are provided.
Recommendations
  • Explicitly mention that Azure CLI and PowerShell are cross-platform, and clarify installation steps for Linux and macOS users.
  • Include Bash shell examples or instructions for Linux users, especially for file handling (e.g., copying/uploading Bicep files).
  • Add troubleshooting notes or tips for common Linux issues (e.g., file permissions, path formats).
  • Ensure that any referenced tools or commands (such as PowerShell) are clearly marked as available on Linux, or provide alternative commands where appropriate.
  • Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
API Management Azure API Management - Overview and Key Concepts ...articles/api-management/api-management-key-concepts.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias in its discussion of management tools. It lists Azure portal, Azure PowerShell, Azure CLI, Visual Studio Code extension, and REST API as management interfaces, with PowerShell (a Windows-centric tool) mentioned before CLI and Linux-native options. No explicit Linux or Bash examples are provided, and there is no mention of Linux-specific tooling or workflows for management tasks. However, the self-hosted gateway is described as Linux-based and Docker/Kubernetes-focused, which is positive for Linux parity.
Recommendations
  • Explicitly mention Bash, shell, or Linux-native workflows alongside PowerShell when listing management tools.
  • Provide example commands for both PowerShell and Bash/Azure CLI where relevant.
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux/macOS.
  • Consider listing Azure CLI before PowerShell to avoid Windows-first ordering.
  • Add references or links to Linux-specific documentation or quickstarts for API Management.
GitHub Create Pull Request
API Management Subscriptions in Azure API Management | Microsoft Docs ...rticles/api-management/api-management-subscriptions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation mentions Azure PowerShell as a tool for automating subscription key lifecycle management but does not mention Linux-friendly alternatives (such as Azure CLI or REST API usage from Bash). No examples or instructions are provided for Linux users, and the only tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Mention Azure CLI as an alternative to Azure PowerShell for managing subscription keys, and provide example commands.
  • Include REST API examples using curl or similar tools commonly available on Linux systems.
  • When referencing automation tools, list both Azure PowerShell and Azure CLI, and avoid implying PowerShell is the default or only option.
  • Add explicit Linux/Bash examples alongside any PowerShell or Windows-centric instructions.
  • Review other documentation pages linked from this one to ensure Linux parity is maintained throughout related content.
GitHub Create Pull Request
API Management Versions in Azure API Management | Microsoft Docs ...ain/articles/api-management/api-management-versions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page references Azure PowerShell and the Azure portal as primary management tools, listing them before Azure CLI and Resource Manager templates. There is no mention of Linux-specific tools or command-line patterns, and examples do not demonstrate parity between Windows and Linux environments. The order and emphasis suggest a Windows-centric approach.
Recommendations
  • Ensure Azure CLI examples are provided alongside or before Azure PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI and Resource Manager templates are fully supported on Linux and macOS, not just Windows.
  • Include command-line examples for common version management tasks using Azure CLI, highlighting their use on Linux.
  • Avoid listing Windows-specific tools (Azure PowerShell, Azure portal) before cross-platform alternatives unless contextually necessary.
  • Add a section or note about managing API versions from Linux environments, referencing relevant tools and documentation.
GitHub Create Pull Request
API Management Add a GraphQL API to Azure API Management | Microsoft Docs ...-docs/blob/main/articles/api-management/graphql-api.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a GraphQL API, but PowerShell is given equal prominence and is mentioned in the prerequisites alongside Azure CLI. There is no explicit mention of Linux-specific tools or shell environments, nor are there any examples using Bash or other Linux-native tools. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not clarify cross-platform usage for CLI or PowerShell commands.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Provide Bash shell examples for Linux users, especially for environment variable setting and command usage.
  • Clarify that PowerShell Core is available on Linux and macOS, or link to instructions for installing PowerShell on non-Windows platforms.
  • Add notes or sections highlighting any platform-specific differences or requirements for CLI and PowerShell usage.
  • Consider listing Azure CLI examples before PowerShell to emphasize cross-platform parity.
GitHub Create Pull Request
API Management Deploy self-hosted gateway to Kubernetes with OpenTelemetry integration ...to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-centric tools (Azure PowerShell) before Linux alternatives (Azure CLI) when describing how to create an Azure Kubernetes cluster. The use of backslash in the Helm install command for the configuration file path ('.\opentelemetry-collector-config.yml') also reflects a Windows file path convention, which may confuse Linux/macOS users. However, the majority of the commands and examples are platform-neutral (Helm, kubectl, curl), and there are no PowerShell-heavy or exclusively Windows-only examples.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting cross-platform options, or present both equally.
  • Use forward slashes ('./opentelemetry-collector-config.yml') for file paths in example commands to match Linux/macOS conventions, or note both formats.
  • Explicitly mention that all commands work on Linux, macOS, and Windows, and provide platform-specific notes where necessary.
  • Where Azure PowerShell is mentioned, also provide equivalent Azure CLI commands for Linux/macOS users.
GitHub Create Pull Request
API Management Deploy a Self-Hosted Gateway to Azure Kubernetes Service ...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation lists Windows-centric tools (Azure PowerShell and Azure portal) before Linux-native options (Azure CLI) when describing how to create an Azure Kubernetes cluster. There is a slight ordering bias toward Windows tools, and PowerShell is mentioned as an equal alternative to CLI, which may not reflect the typical Linux user workflow. However, the main deployment instructions use cross-platform tools (kubectl) and do not show exclusive Windows or PowerShell examples.
Recommendations
  • List Azure CLI (Linux-native and cross-platform) before Azure PowerShell and Azure portal when describing cluster creation, or group them without implied priority.
  • Explicitly mention that Azure CLI and kubectl are cross-platform and provide links or notes for Linux users where appropriate.
  • If PowerShell is mentioned, clarify its cross-platform availability or provide Linux shell equivalents if any commands differ.
  • Review related content and ensure parity in examples and tool recommendations for both Linux and Windows users.
GitHub Create Pull Request
API Management Deploy a Self-Hosted Gateway to Azure Container Apps - Azure API Management ...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but consistently lists PowerShell examples immediately after Bash, and uses explicit PowerShell syntax in every command block. There is no mention of Linux-specific tools, patterns, or troubleshooting, and the only shell environments referenced are Bash and PowerShell, with PowerShell given equal prominence to Bash throughout. No Linux-specific guidance or parity checks are present, and Windows/PowerShell users are directly accommodated, while Linux users are assumed to use Bash.
Recommendations
  • Explicitly mention Linux as a supported platform in the prerequisites and environment setup sections.
  • Add a note clarifying that Bash examples are applicable to Linux and macOS users, and PowerShell examples are for Windows users.
  • Include troubleshooting tips or environment setup instructions specific to Linux (e.g., package dependencies, permissions, CLI installation steps).
  • Where PowerShell syntax is shown, consider also providing generic shell syntax (sh/zsh) or highlighting any platform-specific differences.
  • Reference Linux-native tools or patterns where relevant (e.g., systemd for service management, Linux file paths, etc.).
  • Ensure parity in example ordering: alternate which shell is presented first, or clarify that Bash is the default for cross-platform use.
GitHub Create Pull Request
API Management Import an Azure web app to Azure API Management | Microsoft Docs ...n/articles/api-management/import-app-service-as-api.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric development patterns (such as ASP.NET Core and Visual Studio Code) and omitting Linux-specific examples or instructions. There are no mentions of Linux tools, shell commands, or cross-platform CLI usage. The guidance assumes familiarity with Windows-based workflows and does not provide parity for Linux users.
Recommendations
  • Include examples for creating and publishing web APIs using Linux-based frameworks and tools (e.g., Node.js/Express, Python/Flask, Java/Spring Boot).
  • Provide instructions for deploying web apps to Azure App Service from Linux environments, including CLI commands and shell scripts.
  • Reference cross-platform tools (such as Azure CLI) and show usage on both Windows and Linux terminals.
  • Add links to documentation for developing and publishing APIs from Linux and macOS systems.
  • Ensure that screenshots and step-by-step instructions are not specific to Windows-only tools (e.g., Visual Studio Code) and mention alternatives where appropriate.
GitHub Create Pull Request
API Management Quickstart - Create Azure API Management Instance - ARM Template ...ain/articles/api-management/quickstart-arm-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page consistently references the Azure portal for deployment and management tasks, and mentions Azure PowerShell and Azure CLI only in passing, without providing any command-line examples. There are no explicit Linux-specific instructions or examples, and the order of mention (portal, PowerShell, CLI, REST) places Windows-centric tools first. The absence of Linux shell (bash) or CLI walkthroughs, and the lack of parity in example coverage, indicate a Windows-first and missing Linux example bias.
Recommendations
  • Add explicit step-by-step examples for deploying the ARM template using Azure CLI (az deployment) in bash or shell environments.
  • Include Linux-specific instructions or screenshots where relevant, especially for command-line operations.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Mention cross-platform compatibility of Azure CLI and provide guidance for both Windows and Linux users.
  • Clarify that the Azure portal is accessible from any OS, but highlight automation and scripting options for Linux users.
GitHub Create Pull Request
App Service Configure Premium V3 Tier ...s/app-service/app-service-configure-premium-v3-tier.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium V3 tier configuration, but PowerShell (a Windows-centric tool) is given its own dedicated section after the CLI. There are no Linux shell-specific examples (e.g., Bash scripts), and the portal instructions do not mention platform differences. The CLI examples do distinguish between Windows and Linux SKUs, but overall, Windows tools (PowerShell) are highlighted, and Linux-native scripting is absent.
Recommendations
  • Add Bash shell script examples for Linux users alongside Azure CLI and PowerShell.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Include notes or sections for Linux-specific automation patterns (e.g., using shell scripts, cron jobs).
  • Ensure that PowerShell is not presented as the only or primary automation tool, and balance with Linux-native approaches.
  • Explicitly mention platform parity in portal instructions if any differences exist.
GitHub Create Pull Request
App Service Set Up Access Restrictions ...in/articles/app-service/app-service-ip-restrictions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell examples are given equal or greater prominence, including in advanced scenarios and custom rule creation. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may suggest a slight Windows bias. No Linux-specific shell (e.g., bash) or scripting examples are provided, and PowerShell examples are sometimes shown before or in parallel with CLI, reinforcing the Windows-first approach. There are no references to Windows-only tools or patterns, but the lack of Linux shell examples and the heavy use of PowerShell may disadvantage Linux users.
Recommendations
  • Add bash/sh scripting examples for common scenarios, especially for advanced rule creation and multi-source rules.
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Where PowerShell examples are given, ensure Azure CLI examples are shown first or in parallel, and clarify platform compatibility.
  • Consider including automation examples using Python SDK or REST API for users who prefer non-Windows environments.
  • Review screenshots and UI references to ensure they do not assume Windows-specific conventions.
GitHub Create Pull Request
App Service Use Key Vault References as App Settings ...ticles/app-service/app-service-key-vault-references.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuration tasks, but consistently lists the PowerShell examples after the CLI, and does not provide any Linux shell-specific examples (such as Bash scripts or Linux-native tools). The use of PowerShell, which is more familiar to Windows users, may disadvantage Linux users, especially since PowerShell is not the default shell on most Linux distributions. There are no explicit Linux-only instructions or examples, and the troubleshooting and portal navigation sections do not mention any OS-specific considerations.
Recommendations
  • Add explicit Bash or shell script examples alongside Azure CLI and PowerShell, especially for Linux users.
  • Clarify that Azure CLI commands are cross-platform and can be run in Bash, Cloud Shell, or other Linux environments.
  • Where PowerShell is used, note that PowerShell Core is available cross-platform, but provide equivalent Bash or shell-native alternatives where possible.
  • Include notes or sections that address any Linux-specific behaviors or troubleshooting steps, particularly for networking and identity configuration.
  • Ensure that any references to tools or commands are not Windows-centric by default, and that Linux-first or Linux-equal examples are provided.
GitHub Create Pull Request
App Service Configure continuous deployment ...n/articles/app-service/deploy-continuous-deployment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by referencing 'Windows apps' specifically in the 'External Git' section and not mentioning Linux apps or providing Linux-specific guidance. There are no explicit Linux examples, nor is there mention of Linux-specific deployment patterns or tools. The documentation assumes parity but does not confirm or illustrate it, and Windows terminology appears first or exclusively in some places.
Recommendations
  • Explicitly mention Linux app support wherever 'Windows apps' are referenced, or clarify if steps differ for Linux.
  • Provide examples or notes for deploying to Linux-based App Service apps, especially in sections like 'External Git' and authentication.
  • Include references to Linux-specific deployment patterns or troubleshooting, if applicable.
  • Review screenshots and UI instructions to ensure they are not Windows-centric and clarify when steps apply to both OS types.
  • Add a parity statement confirming that all steps apply equally to Linux and Windows, or highlight differences where they exist.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-curl-commands.md ...includes/quickstart-python/deploy-zip-curl-commands.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Bash and PowerShell examples for deploying via Kudu, but the introductory instructions focus on navigating the Azure portal, which is more familiar to Windows users. The PowerShell example includes a specific note about quoting, giving extra attention to Windows/PowerShell usage. There is no mention of Linux-specific tools or navigation patterns, and the Bash example is presented after the general instructions, not as a primary workflow.
Recommendations
  • Add explicit instructions for Linux users, such as how to access Kudu from Linux environments or via CLI.
  • Include references to Linux-native tools (e.g., wget, scp) where appropriate.
  • Present Bash and PowerShell examples in parallel, or alternate which is shown first.
  • Clarify that the instructions apply equally to Linux and Windows users, and note any platform-specific differences.
  • Consider adding a section on using Azure CLI for deployment, which is cross-platform.
GitHub Create Pull Request
App Service Securely connect .NET apps to resources using the Entra agent identity platform ...b/main/articles/app-service/overview-agent-identity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure App Service and Azure Functions, which are traditionally associated with Windows environments, and by providing only .NET/C# code examples. There are no Linux-specific instructions, examples, or references to Linux-native tools, nor is there any mention of deploying or configuring agent identity scenarios in Linux environments (such as Azure App Service for Linux, Azure Functions on Linux, or container-based deployments). The documentation also omits any discussion of cross-platform considerations, shell differences, or Linux-specific environment variable configuration.
Recommendations
  • Add explicit instructions and examples for deploying .NET agent apps on Azure App Service for Linux and Azure Functions on Linux.
  • Include Linux shell (bash/zsh) environment variable configuration examples alongside any Windows/PowerShell equivalents.
  • Mention cross-platform deployment considerations, such as differences in managed identity assignment and authentication between Windows and Linux hosting plans.
  • Provide sample code or references for running the agent identity scenarios in containerized environments (Docker), which are common in Linux-based deployments.
  • Clarify that the steps and code are applicable to both Windows and Linux environments, and highlight any platform-specific caveats.
  • Add links to documentation for Linux-based Azure App Service and Azure Functions, and ensure parity in guidance.
GitHub Create Pull Request
App Service Migration Checklist - Azure App Service on Arc-enabled Kubernetes to Azure Container Apps on Arc-enabled Kubernetes ...b/main/articles/app-service/migrate-app-service-arc.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource queries, but PowerShell is given equal prominence and is listed immediately after CLI in every case. There are no Linux shell-specific examples (e.g., Bash scripts, shell pipelines), nor is there mention of Linux-native tools. The documentation does not acknowledge platform-specific differences in running CLI commands (e.g., shell quoting, environment setup), and PowerShell—a Windows-centric tool—is featured as a primary option.
Recommendations
  • Add explicit Bash shell examples for all CLI commands, including Linux-specific syntax and usage notes.
  • Clarify that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide guidance for Linux users (e.g., installation, environment setup).
  • If PowerShell is included, note its cross-platform availability but avoid implying it is the default or preferred option for all users.
  • Consider listing Bash/Linux examples before PowerShell, or provide tabs for Bash, PowerShell, and CLI to ensure parity.
  • Mention any platform-specific caveats (such as quoting differences) when presenting CLI commands.
GitHub Create Pull Request
App Service Monitor Azure App Service .../blob/main/articles/app-service/monitor-app-service.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page shows mild Windows bias, primarily through the mention of Visual Studio integration for Application Insights and listing PowerShell as a query method for Azure activity logs before CLI or REST API. There are no explicit Linux or Bash examples, nor are Linux-specific tools or patterns mentioned. The documentation does not provide parity in examples or tool references for Linux users.
Recommendations
  • Add explicit examples using Azure CLI and Bash scripts alongside PowerShell where applicable, especially in sections discussing querying logs or automating monitoring tasks.
  • Mention Linux-friendly development tools (such as VS Code, JetBrains IDEs) in addition to Visual Studio when discussing Application Insights integration.
  • Ensure that references to command-line tools (PowerShell, CLI) are presented in a neutral order or grouped together, rather than listing Windows tools first.
  • Include troubleshooting and monitoring scenarios relevant to Linux-hosted App Service apps, such as integration with syslog or Linux-native logging formats.
  • Provide links or references to Linux documentation and best practices for monitoring Azure App Service.
GitHub Create Pull Request
App Service Authentication and Authorization ...s/app-service/overview-authentication-authorization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page presents the Windows (IIS module) architecture before the Linux/container equivalent and references Windows-specific technologies (IIS modules) without providing equal detail or examples for Linux. There are no explicit PowerShell-heavy examples or missing Linux examples, but the ordering and terminology favor Windows environments.
Recommendations
  • Present Linux/container architecture before or alongside Windows architecture to avoid implicit prioritization.
  • Provide equivalent technical detail for Linux/container deployments, including references to relevant Linux technologies (e.g., ambassador pattern, container orchestration).
  • Include examples or links for configuring authentication and authorization on Linux/container environments, not just Windows/IIS.
  • Clarify any differences in configuration or troubleshooting between Windows and Linux/container environments.
  • Avoid using Windows-specific terminology (e.g., IIS module) without explaining or paralleling the Linux/container approach.
GitHub Create Pull Request
App Testing Quickstart: Automate load tests with CI/CD ...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses exclusively on Azure Pipelines and the Azure DevOps portal, with all examples and screenshots based on the web UI and Azure-specific workflows. There is no mention of Linux-specific tools, command-line interfaces, or alternative CI/CD systems (other than a brief link to GitHub Actions). No examples are provided for configuring pipelines using Linux-native tools or shell scripts, and the documentation assumes use of the Azure portal and Azure DevOps, which are more commonly used in Windows environments.
Recommendations
  • Include examples for configuring CI/CD pipelines using Linux command-line tools (e.g., Azure CLI, Bash scripts) and show how to automate load tests without relying on the Azure portal UI.
  • Provide parity by adding step-by-step instructions for setting up load tests in popular Linux-based CI/CD systems (e.g., Jenkins, GitLab CI) alongside Azure Pipelines.
  • Add sample YAML pipeline definitions that can be used in cross-platform environments, highlighting any OS-specific considerations.
  • Explicitly mention that the process works on both Windows and Linux agents, and clarify any differences in setup or execution.
  • Include screenshots or terminal output from Linux environments to balance the visual representation.
GitHub Create Pull Request
App Testing Manage workspace access ...laywright-workspaces/how-to-manage-workspace-access.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes managing workspace access using the Azure portal UI, which is primarily accessed via a web browser on Windows. There are no examples or instructions for command-line or automation approaches, such as using Azure CLI, PowerShell, or REST API, which are cross-platform and commonly used on Linux. The absence of Linux-specific or CLI-based instructions may disadvantage users who prefer or require non-Windows environments or automation.
Recommendations
  • Add instructions and examples for managing workspace access using Azure CLI, which is available on Linux, macOS, and Windows.
  • Include REST API examples for role assignment and revocation, enabling automation and cross-platform usage.
  • If PowerShell examples are added, ensure Azure CLI equivalents are provided and presented with equal prominence.
  • Explicitly mention that all management operations can be performed from Linux, macOS, and Windows using CLI or API tools.
  • Add troubleshooting and prerequisite notes for CLI/API usage, such as authentication setup on Linux.
GitHub Create Pull Request
Application Gateway Container networking with Azure Application Gateway for Containers ...ication-gateway/for-containers/container-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where the link to 'Deploy ALB Controller' defaults to Windows instructions (install-helm-windows tab) and does not mention Linux or cross-platform alternatives. There are no explicit Linux or bash examples, and Windows tooling is implicitly prioritized by the tab default.
Recommendations
  • Provide equal visibility and instructions for Linux/macOS environments alongside Windows, especially in quickstart and deployment guides.
  • Ensure links to installation guides default to a cross-platform or neutral tab, or clearly offer both Windows and Linux/macOS tabs.
  • Include bash or Linux CLI examples where relevant, not just Windows/PowerShell.
  • Review all referenced quickstart and deployment documentation to ensure Linux parity in examples and tooling.
GitHub Create Pull Request
Application Gateway Azure Application Gateway configuration overview ...articles/application-gateway/configuration-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page lists PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. While Azure CLI is mentioned, there are no explicit Linux-specific examples or references, and PowerShell is given prominence, which may indicate a bias toward Windows users.
Recommendations
  • List Azure CLI before PowerShell in 'Next steps', as CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
  • Provide examples or links for configuring Application Gateway using Linux-native tools or environments.
  • Add a note clarifying platform compatibility for each tool (PowerShell vs Azure CLI).
  • Consider including walkthroughs or screenshots from Linux environments where relevant.
GitHub Create Pull Request
Application Gateway Azure Application Gateway request routing rules configuration ...ication-gateway/configuration-request-routing-rules.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell-based instructions and links before their Azure CLI equivalents in several places. PowerShell is primarily a Windows tool, while Azure CLI is cross-platform. There are no Linux-specific examples or tools mentioned, and no explicit parity between Windows and Linux workflows is established.
Recommendations
  • Present Azure CLI and PowerShell instructions side-by-side, or list CLI first to emphasize cross-platform support.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide examples for Linux shell usage where relevant.
  • Add a section or callout for Linux users, highlighting any platform-specific considerations or best practices.
  • Ensure that all referenced guides (e.g., redirect guides) include both PowerShell and CLI examples, and avoid implying PowerShell is the default or preferred method.
GitHub Create Pull Request
Application Gateway Configure Azure Monitor alerts for Application Gateway ...application-gateway/configure-alerts-with-templates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by exclusively referencing the Azure Portal and linking to procedures that prioritize CLI, PowerShell, and ARM template usage without mentioning Linux-specific tools or workflows. There are no examples or guidance for Linux users (e.g., Azure CLI on bash, shell scripting, or cross-platform deployment methods). The 'Deploy to Azure' button links directly to the Azure Portal, which is platform-agnostic but often associated with Windows workflows, and the referenced procedure page lists PowerShell before CLI, reinforcing a Windows-first pattern.
Recommendations
  • Add explicit examples using Azure CLI on Linux (bash) for deploying ARM templates and configuring alerts.
  • Include instructions or links for using cross-platform tools (e.g., Azure CLI, REST API) to create and manage alert rules.
  • Ensure referenced procedures present CLI and PowerShell options side-by-side, or lead with CLI for platform neutrality.
  • Clarify that the Azure Portal and ARM templates are accessible from any OS, and mention Linux compatibility where relevant.
GitHub Create Pull Request
Application Gateway Quickstart: Create Application Gateway for Containers managed by ALB Controller ...ation-gateway-for-containers-managed-by-alb-controller.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides command-line examples exclusively using Azure CLI and kubectl, which are cross-platform tools. However, there is implicit Windows bias in the variable assignment syntax and command formatting (e.g., use of single quotes, reliance on bash-style variable expansion, and lack of explicit mention of Linux or macOS environments). There are no PowerShell or Windows-specific tools, but the examples do not clarify compatibility or provide parallel instructions for Linux/macOS users, nor do they address common issues such as line endings or shell differences.
Recommendations
  • Explicitly state that the Azure CLI and kubectl commands work on Linux, macOS, and Windows (with WSL or bash).
  • Provide notes or examples for running commands in PowerShell, CMD, and bash, especially for variable assignment and multi-line commands.
  • Clarify any platform-specific requirements (e.g., use of tr -d '\r' for line endings in Windows).
  • Add troubleshooting tips for common cross-platform issues, such as differences in quoting, environment variable syntax, and command chaining.
  • Consider adding a 'Platform compatibility' section to highlight any differences or requirements for Linux, macOS, and Windows users.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller ...ploy-application-gateway-for-containers-alb-controller.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides installation instructions for Helm on both Windows and Linux, but the Windows instructions (using winget) are presented first, and the Windows-specific tool (winget) is mentioned explicitly. The Linux instructions are present and functional, but Windows is given priority in ordering and tool mention. No PowerShell-heavy bias or missing Linux examples are found, as most commands are cross-platform Azure CLI and Bash. However, the documentation could improve parity by balancing the order and detail of platform-specific instructions.
Recommendations
  • Present Windows and Linux installation instructions for Helm in parallel, or alternate which platform is listed first.
  • Mention Linux package managers (e.g., apt, yum, dnf) as alternatives for Helm installation, not just the curl script.
  • Provide explicit guidance for running Azure CLI commands on Linux (e.g., ensure az CLI is installed and available in PATH).
  • Avoid implying Windows as the default by listing it first; use neutral phrasing or alphabetical order.
  • Include a note that all Azure CLI and Helm commands are cross-platform unless otherwise specified.
GitHub Create Pull Request
Application Gateway Application Gateway Ingress Controller troubleshooting ...application-gateway/ingress-controller-troubleshoot.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page consistently recommends Azure Cloud Shell as the primary troubleshooting environment and provides all command-line examples using Bash. While Bash is cross-platform, the documentation does not mention or provide guidance for running commands on native Linux or macOS terminals, nor does it address differences in local environments versus Cloud Shell. There are no references to Windows-specific tools (e.g., PowerShell), but the documentation assumes the use of Azure Cloud Shell, which is more commonly used by Windows users and may not be the default for Linux administrators. There is a lack of explicit Linux parity, as the instructions do not discuss how to perform troubleshooting steps outside of Cloud Shell or on Linux systems.
Recommendations
  • Add explicit instructions for running troubleshooting commands on native Linux and macOS terminals, including any prerequisites (such as installing kubectl, Azure CLI, etc.).
  • Clarify that Bash commands provided can be run on any Bash-compatible shell, not just Azure Cloud Shell.
  • Include a section comparing troubleshooting in Azure Cloud Shell versus local Linux/macOS environments, highlighting any differences or additional steps required.
  • If relevant, mention how to perform troubleshooting using PowerShell for Windows users to ensure parity for all platforms.
  • Avoid language that implies Azure Cloud Shell is the only or preferred method, and instead present it as one of several options.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway ...ocs/blob/main/articles/application-gateway/overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents Azure PowerShell as a primary method for creating an Application Gateway, listing it before Azure CLI in the 'Next steps' section. This ordering, along with explicit mention of PowerShell, subtly prioritizes Windows-centric tooling and patterns. While Azure CLI is included (which is cross-platform), the emphasis and ordering suggest a Windows-first approach. There are no Linux-specific examples or references to Linux-native tools or shell environments.
Recommendations
  • List Azure CLI before PowerShell in example and quickstart links to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and Windows, and provide shell/bash examples where appropriate.
  • Add a note or section highlighting Linux/macOS usage, including any relevant differences or tips for those platforms.
  • Ensure future tutorials and quickstarts provide equal coverage and visibility for Linux users, possibly including screenshots or walkthroughs using Linux environments.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Python ...docs/blob/main/articles/automanage/quick-python-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by linking exclusively to the Windows VM quick-create guide in the prerequisites section and not mentioning or providing examples for Linux virtual machines. There are no Linux-specific instructions, nor is there parity in references or examples for Linux users.
Recommendations
  • Include links to both Windows and Linux VM quick-create guides in the prerequisites.
  • Explicitly state that the process applies to both Windows and Linux VMs, if applicable.
  • Provide example resource links or code snippets for Linux VM scenarios.
  • Clarify any differences in Automanage support or configuration between Windows and Linux VMs.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for JavaScript .../blob/main/articles/automanage/quick-javascript-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by linking only to the Windows virtual machine quick-create guide in the prerequisites and not mentioning or providing equivalent Linux VM documentation or examples. There are no Linux-specific instructions, examples, or references, and the only VM link is for Windows, suggesting a Windows-first approach.
Recommendations
  • Add links to both Windows and Linux VM quick-create guides in the prerequisites section.
  • Explicitly state that the SDK and Automanage features work for both Windows and Linux VMs, if applicable.
  • Provide example resource names and configuration profile assignments for both Windows and Linux VMs.
  • Include notes or examples highlighting any differences in Automanage usage or best practices between Windows and Linux VMs.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Java ...e-docs/blob/main/articles/automanage/quick-java-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing only the Windows VM creation guide in the prerequisites and omitting any mention of Linux virtual machines or their documentation. There are no examples or instructions specific to Linux VMs, nor is there parity in guidance for Linux users.
Recommendations
  • Include links to both Windows and Linux VM creation guides in the prerequisites section.
  • Explicitly state that Automanage supports both Windows and Linux VMs, if applicable.
  • Provide examples or notes on any differences when enabling Automanage for Linux VMs.
  • Ensure that terminology and instructions are platform-neutral unless a step is specific to Windows or Linux.
GitHub Create Pull Request
Automation Azure Automation extension for Visual Studio Code ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page for the Azure Automation extension for Visual Studio Code shows a bias towards Windows environments by referencing PowerShell modules as a prerequisite and not providing equivalent Linux or cross-platform guidance. There are no examples or instructions for Linux-specific tools, shell environments, or package management, and the documentation assumes PowerShell is the default scripting language and runtime for local testing, which is more common on Windows.
Recommendations
  • Include explicit instructions for installing and using the extension on Linux and macOS, such as verifying compatibility and any required dependencies.
  • Add examples for using Python runbooks, including guidance on installing Python and required packages on Linux/macOS.
  • Clarify whether Bash or other shell scripts are supported and provide examples if so.
  • Mention cross-platform PowerShell (PowerShell Core) and provide installation steps for Linux/macOS.
  • List any platform-specific limitations or differences in the extension's behavior.
  • Ensure screenshots and UI references are not Windows-specific, or provide alternatives for other platforms.
GitHub Create Pull Request
Azure App Configuration Export settings from App Configuration with Azure Pipelines .../azure-app-configuration/azure-pipeline-export-task.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides only a PowerShell example for consuming exported key-values, with no equivalent example for Linux shell environments (e.g., Bash). This may make it less accessible for users running pipelines on Linux agents or those more familiar with Bash scripting.
Recommendations
  • Add Bash (Linux shell) examples alongside PowerShell examples to demonstrate how to consume pipeline variables in cross-platform scenarios.
  • Explicitly mention that environment variables are accessible in both Windows and Linux agents, and provide syntax for both.
  • Review other sections for implicit Windows-first language or screenshots, and ensure parity in instructions for Linux users where relevant.
GitHub Create Pull Request
Automanage Automanage Configuration profiles ...articles/automanage/overview-configuration-profiles.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page discusses Automanage configuration profiles in a general manner, but it lacks concrete examples or instructions for either Windows or Linux. However, the only explicit mention of OS-specific documentation is in the 'Next steps' section, where 'Automanage for Linux' is listed after 'Automanage for Windows Server', suggesting a subtle 'windows_first' ordering. There are no PowerShell-heavy examples or exclusive references to Windows tools, but the absence of any Linux-specific examples or patterns in the main content constitutes a 'missing_linux_example' bias.
Recommendations
  • Provide parallel examples for both Windows and Linux throughout the documentation, not just as links.
  • When listing OS-specific resources, alternate the order or list Linux first in some cases to avoid implicit prioritization.
  • Include explicit Linux configuration scenarios or references in the main body, not just in linked documents.
  • Ensure that any tools or commands mentioned are available or have equivalents on both platforms, and document both.
GitHub Create Pull Request
Automanage About Azure Automanage Machine Best Practices ...e-docs/blob/main/articles/automanage/overview-about.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references both Windows and Linux support, but examples, links, and explanations tend to mention Windows first or exclusively. There are no concrete Linux-specific examples, commands, or walkthroughs provided on this page, and Windows Server is often listed before Linux distros. The prerequisites section links to Windows Server versions before Linux distributions, and there are no Linux command-line or tool references.
Recommendations
  • Provide Linux-specific onboarding examples and walkthroughs directly on this page, not just via links.
  • Ensure Linux distros are mentioned with equal prominence and ordering as Windows Server.
  • Include example commands or configuration steps for both Windows (e.g., PowerShell) and Linux (e.g., Bash, CLI).
  • Reference Linux tools and patterns (such as cloud-init, systemd, or package managers) where relevant.
  • Add a table or section comparing Windows and Linux support, prerequisites, and differences for clarity.
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with Go web applications ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and gives detailed Windows-specific commands (setx, PowerShell) alongside bash equivalents. There is a slight preference for Windows in ordering and detail, but Linux/macOS instructions are present and correct.
Recommendations
  • Present Linux/macOS instructions before Windows instructions, or in parallel, to avoid implicit prioritization.
  • Add notes about differences in environment variable persistence (e.g., setx vs export) and session scope for all platforms.
  • Ensure parity in troubleshooting and tips for both Windows and Linux/macOS users.
  • Consider grouping platform-specific instructions in tabs or collapsible sections for clarity and equal prominence.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with .NET | Microsoft Docs .../azure-app-configuration/quickstart-dotnet-core-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows command prompt and PowerShell before mentioning macOS/Linux equivalents. Windows-specific tools (setx, PowerShell) are described in detail, with Linux/macOS commands listed last. However, the .NET CLI is emphasized as cross-platform, and most code examples are platform-neutral.
Recommendations
  • Present environment variable instructions for all platforms in parallel, or list Linux/macOS first in some sections.
  • Explicitly state that all CLI commands work on Windows, macOS, and Linux.
  • Provide brief context for each platform's command, avoiding implicit prioritization of Windows.
  • Consider grouping platform instructions in tabs or side-by-side tables for parity.
  • Mention Linux/macOS terminal options (e.g., bash, zsh) alongside Windows shells.
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to Spring Boot with Azure App Configuration ...p-configuration/quickstart-feature-flag-spring-boot.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell examples. While Linux/macOS commands are present, Windows instructions are listed first, which may subtly prioritize Windows users. No Linux-specific tools or patterns are missing, but the ordering and inclusion of PowerShell examples indicate a mild Windows bias.
Recommendations
  • Present Linux/macOS (bash) commands before Windows commands, or group them equally under OS-specific tabs.
  • Ensure parity in command examples for all platforms, including zsh or other common Linux shells if relevant.
  • Add a note clarifying that all platforms are supported equally.
  • Consider using tabbed code blocks for OS-specific instructions to avoid implicit prioritization.
  • Review other sections for subtle prioritization (e.g., screenshots, tool recommendations) and ensure balanced representation.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Go ...ure-docs/blob/main/articles/automanage/quick-go-sdk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by linking only to the Windows VM quick-create guide in the prerequisites, without mentioning or providing a Linux VM equivalent. There are no Linux-specific instructions or examples, and the documentation implicitly assumes the use of Windows virtual machines.
Recommendations
  • Include links to both Windows and Linux VM quick-create guides in the prerequisites section.
  • Clarify that Automanage can be used with both Windows and Linux VMs, if applicable.
  • Provide examples or notes for Linux VM scenarios where relevant.
  • Ensure terminology and instructions are platform-neutral unless a feature is Windows-specific.
GitHub Create Pull Request
Automanage Azure Automanage Machine Best Practices ...articles/automanage/virtual-machines-best-practices.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias, particularly in the 'Guest configuration' section, where only Windows security baselines are mentioned. There are no explicit Linux examples or references to Linux-specific best practices, tools, or configuration baselines. The documentation assumes a Windows-centric approach, omitting equivalent Linux guidance.
Recommendations
  • Include information about Linux security baselines or compliance profiles supported by Automanage, such as CIS or OS-specific baselines.
  • Explicitly mention Linux support in each service description where applicable, and provide links to Linux documentation.
  • Add examples or references for both Windows and Linux environments, ensuring parity in guidance and resources.
  • Clarify any differences in onboarding, configuration, or monitoring for Linux VMs compared to Windows VMs.
GitHub Create Pull Request
Azure Functions Task hubs in Durable Functions - Azure ...azure-functions/durable/durable-functions-task-hubs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides code examples for multiple languages, including PowerShell, which is primarily a Windows-centric shell. PowerShell examples are given equal prominence alongside other languages, but there are no explicit Linux shell (e.g., Bash) examples. Additionally, tooling references (such as Azure Storage Explorer) are Windows-friendly, and there is no mention of Linux-specific tools or patterns for inspecting storage. The documentation does not discuss Linux-specific deployment or management considerations, nor does it provide parity for Linux-native scripting or command-line usage.
Recommendations
  • Add Bash or Linux shell script examples where PowerShell is shown, or clarify PowerShell usage on Linux.
  • Mention cross-platform tools for inspecting Azure Storage (e.g., az CLI, cross-platform Azure Storage Explorer, or alternatives like 'azure-storage' Python SDK).
  • Discuss any Linux-specific deployment, configuration, or troubleshooting considerations for Durable Functions.
  • Clarify that PowerShell examples can be run on Linux (if true), or provide alternative Linux-native scripting examples.
  • Ensure that references to tools and patterns are not Windows-centric, or provide Linux equivalents in parallel.
GitHub Create Pull Request
Azure Functions Durable Functions packages .../azure-functions/durable/durable-functions-packages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents .NET (in-process and isolated) package information first and in greatest detail, which are traditionally Windows-centric runtimes. PowerShell is explicitly called out as a supported language and receives a dedicated note about SDK migration, while Linux-specific tools, patterns, or examples are not mentioned. There are no explicit Linux examples, nor is there mention of Linux package management or shell usage.
Recommendations
  • Add explicit examples or instructions for Linux environments, such as referencing package installation via bash or Linux-native tools.
  • Include notes on cross-platform compatibility for .NET and PowerShell, clarifying support for Linux and macOS.
  • Balance language-specific notes by providing similar migration or usage guidance for Node.js, Python, and Java users.
  • Mention any Linux-specific considerations for storage providers, SDK installation, or runtime configuration.
  • Ensure that non-Windows runtimes (Node.js, Python, Java) receive equal detail and visibility in the documentation structure.
GitHub Create Pull Request
Azure Functions Azure OpenAI assistant post input binding for Azure Functions ...tions/functions-bindings-openai-assistantpost-input.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides a dedicated section for PowerShell examples and configuration, including explicit references to function.json and run.ps1 files. This focus on PowerShell, a Windows-centric scripting language, is not matched by equivalent coverage for Linux shell scripting (e.g., Bash). No Linux-specific tools or shell examples are provided, and the only scripting example outside of programming languages is PowerShell, suggesting a Windows bias in the scripting and configuration guidance.
Recommendations
  • Add equivalent Bash or shell script examples for Linux users alongside PowerShell examples.
  • Include guidance for configuring and running Azure Functions using Linux-native tools and environments.
  • Clarify cross-platform compatibility for configuration files and scripting, noting any differences for Linux users.
  • Ensure that scripting and automation examples are provided for both Windows and Linux environments to improve parity.
GitHub Create Pull Request
Azure Functions IP addresses in Azure Functions ...ocs/blob/main/articles/azure-functions/ip-addresses.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides command-line examples for Azure CLI, Azure PowerShell, and portal-based workflows. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments and is presented alongside CLI examples. There is no explicit mention of Linux-specific tools or shell commands (e.g., curl, dig), and the use of PowerShell is given equal prominence to CLI, which may suggest a Windows bias. Additionally, the documentation does not provide Linux shell alternatives for tasks like querying outbound IP addresses or checking resource properties.
Recommendations
  • Include Linux shell command examples (e.g., using curl, dig, jq) for tasks such as DNS lookup and querying Azure resources via REST API.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and consider providing sample shell syntax for Bash/zsh.
  • Where PowerShell is shown, offer equivalent Bash or shell script examples for Linux users.
  • Explicitly mention cross-platform compatibility for each tool and avoid assuming PowerShell as the default scripting environment.
  • Add notes or tabs for Linux/macOS users where workflows or commands may differ.
GitHub Create Pull Request
Automation Azure Automation FAQ ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page generally maintains cross-platform awareness, mentioning both Windows and Linux Hybrid Runbook Workers. However, in the section describing how a Hybrid Runbook Worker selects the Python interpreter, only Windows-specific environment variables and paths (e.g., C:\Python2\python.exe) are described in detail, with no equivalent Linux example or explanation. This prioritizes Windows usage and omits Linux-specific guidance, which may hinder Linux users.
Recommendations
  • Add explicit Linux examples for environment variable configuration and Python interpreter path resolution (e.g., describe use of /usr/bin/python3 and relevant environment variables on Linux).
  • Include Linux-specific troubleshooting steps or notes where Windows-specific instructions are given.
  • Ensure that all platform-specific instructions are presented in parallel, with equal detail for both Windows and Linux.
  • Review other sections for subtle Windows-first phrasing and update to present both platforms with parity.
GitHub Create Pull Request
Automation Forward Azure Automation job data to Azure Monitor logs ...mation/automation-manage-send-joblogs-log-analytics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias. It references PowerShell as the tool for viewing individual job logs and mentions PowerShell error streams when discussing job errors. There are no explicit Linux or cross-platform CLI examples, nor is there mention of Linux-specific tools or shell environments. The documentation assumes familiarity with PowerShell concepts and does not provide parity for Linux users (e.g., Bash, CLI, or cross-platform scripting).
Recommendations
  • Add explicit references to cross-platform tools such as Azure CLI and Bash where applicable, especially for querying or automating tasks.
  • Provide examples for viewing job logs and streams using Azure CLI or REST API, not just PowerShell.
  • Clarify that Azure Automation and Azure Monitor log querying is platform-agnostic and can be performed from any OS using supported tools.
  • When discussing error streams, mention how non-terminating errors are handled in Bash or other Linux scripting environments, if relevant.
  • Ensure that introductory sections do not imply PowerShell is the only or primary method for interacting with Azure Automation logs.
GitHub Create Pull Request
Automation Enforce job execution on Azure Automation Hybrid Runbook Worker ...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell examples are presented with equal prominence and detail as CLI, and PowerShell is mentioned first in the introductory text. There are no Linux-specific shell examples (e.g., Bash) or references to Linux-native tooling, and the documentation does not clarify cross-platform usage of Azure CLI or PowerShell. The examples and instructions assume familiarity with PowerShell, which is traditionally Windows-centric, and do not address Linux-specific considerations for Hybrid Runbook Workers.
Recommendations
  • Explicitly state that Azure CLI and Azure PowerShell are cross-platform and provide guidance for running commands on Linux, macOS, and Windows.
  • Add Bash shell examples for Azure CLI usage to demonstrate Linux-native workflows.
  • Clarify any platform-specific prerequisites or differences for Hybrid Runbook Worker configuration and policy assignment.
  • Ensure that introductory text and example ordering do not prioritize Windows/PowerShell over Linux/Bash; alternate the order or provide a neutral introduction.
  • Mention that Azure PowerShell can be installed and used on Linux and macOS, and provide installation links or references.
GitHub Create Pull Request
Automation Manage Python 2 packages in Azure Automation ...-docs/blob/main/articles/automation/python-packages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by providing package download instructions exclusively for Windows (using a Windows 64-bit machine and referencing C:\Python27\Scripts), with no equivalent guidance for Linux or macOS users. There are no Linux-specific examples, commands, or tools mentioned, and Windows is presented as the default platform for offline package management.
Recommendations
  • Add equivalent instructions for downloading Python 2 packages and dependencies on Linux and macOS, using standard Python and pip commands.
  • Provide example commands for Linux (e.g., using 'pip download' in a bash shell) alongside Windows examples.
  • Clarify that the process is cross-platform and specify any platform-specific considerations.
  • Include screenshots or terminal outputs from Linux environments where appropriate.
  • Avoid presenting Windows as the default or only supported platform for package management tasks.
GitHub Create Pull Request
Automation Archive for What's new in Azure Automation ...ocs/blob/main/articles/automation/whats-new-archive.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page generally maintains cross-platform parity, mentioning both Windows and Linux support for Azure Automation features. However, there are subtle signs of Windows bias: Windows-specific tools and scripts (e.g., PowerShell Gallery, Az modules, Windows HybridWorker) are referenced by name, sometimes before or more prominently than their Linux equivalents. Windows operating system support is called out in dedicated sections, while Linux support is often grouped or referenced as an afterthought. The onboarding script update and runbook examples tend to highlight Windows/PowerShell tools first.
Recommendations
  • Ensure Linux examples and tools are mentioned with equal prominence and detail as Windows equivalents.
  • When referencing scripts or onboarding processes, present both Windows and Linux options side-by-side, rather than listing Windows first.
  • Include explicit Linux command-line examples (e.g., bash, shell scripts) where PowerShell or Windows tools are mentioned.
  • Highlight Linux-specific features, troubleshooting, and best practices in dedicated sections, not just as grouped mentions.
  • Review headings and ordering to avoid consistently listing Windows before Linux.
GitHub Create Pull Request
Avere Vfxt Access the Avere vFXT control panel - Azure ...lob/main/articles/avere-vfxt/avere-vfxt-cluster-gui.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation mentions both Windows and Linux clients, but provides only generic SSH command-line instructions without platform-specific examples. The SSH keys documentation links present 'Windows' before 'Linux', and there are no Linux-specific tool or pattern examples (e.g., using OpenSSH, PuTTY, or native Linux terminal commands). There is no mention of Linux graphical SSH tunnel tools or browser caveats specific to Linux environments.
Recommendations
  • Provide explicit Linux examples, such as using native OpenSSH in the terminal, and mention Linux-specific SSH tunnel commands.
  • Include references to common Linux SSH tunnel tools (e.g., ssh, autossh) and graphical clients (e.g., GNOME Terminal, KDE Konsole).
  • Balance the order of platform references (e.g., mention Linux before or alongside Windows when listing SSH key documentation).
  • Add troubleshooting notes or browser caveats relevant to Linux users (e.g., certificate warnings in Firefox on Linux).
  • Consider including a brief example for macOS users, as they often use similar commands to Linux.
GitHub Create Pull Request
Avere Vfxt Avere vFXT prerequisites - Azure ...cs/blob/main/articles/avere-vfxt/avere-vfxt-prereqs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples using the Azure Portal (a web GUI commonly associated with Windows workflows) and Azure CLI commands, without offering Linux-specific guidance or parity for command-line operations outside Azure CLI. There are no examples using Linux shell tools, nor is there mention of Linux-specific considerations or alternative workflows. The documentation assumes the use of the Azure Portal and Azure CLI, which are cross-platform, but does not explicitly address Linux environments or provide examples tailored for Linux users.
Recommendations
  • Add explicit instructions for performing prerequisite tasks using Linux shell commands where applicable (e.g., using Bash scripts for Azure CLI).
  • Include screenshots or terminal examples from Linux environments to demonstrate parity.
  • Mention any Linux-specific considerations, such as differences in authentication, environment setup, or file paths.
  • Clarify that Azure CLI is cross-platform and provide installation instructions for Linux users.
  • If PowerShell is referenced elsewhere, ensure Bash or Linux shell equivalents are also provided.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration dynamic configuration in an Azure Functions app ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and references Visual Studio and Windows-specific tooling (e.g., setx, F5, firewall exceptions) as the default workflow for local testing. Linux/macOS instructions are present but appear after Windows examples, and there is no mention of Linux-native editors or CLI workflows.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel, or alternate which platform is shown first.
  • Include examples for Linux-native development environments (e.g., VS Code, Azure Functions Core Tools CLI) and workflows.
  • Mention cross-platform tools and clarify that Azure Functions development and testing can be performed on Linux/macOS as well as Windows.
  • Avoid assuming Visual Studio as the default IDE; provide CLI-based testing instructions for parity.
  • Add notes about firewall exceptions and tool installation for Linux/macOS where relevant.
GitHub Create Pull Request
Azure App Configuration .NET Framework: dynamic configuration in App Configuration ...p-configuration/enable-dynamic-configuration-dotnet.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits a mild Windows bias. Windows tools (Visual Studio, Command Prompt, PowerShell) are mentioned first and in more detail, especially in the prerequisites and environment variable setup sections. PowerShell and Windows Command Prompt commands are given before Linux/macOS equivalents. The workflow assumes Visual Studio, which is primarily a Windows tool, and instructs users to restart Visual Studio after setting environment variables, which is not relevant for Linux users. However, Linux/macOS commands are present and not omitted.
Recommendations
  • Present environment variable setup instructions for Windows, Linux, and macOS in parallel, rather than listing Windows first.
  • Include instructions for building and running the app using cross-platform .NET CLI (dotnet build/run) in addition to Visual Studio.
  • Clarify that Visual Studio is optional and suggest alternatives for Linux/macOS users, such as VS Code or JetBrains Rider.
  • Avoid instructions that are only relevant for Windows (e.g., restarting Visual Studio) or provide Linux/macOS alternatives.
  • Add screenshots or terminal output examples for Linux/macOS environments alongside Windows examples.
GitHub Create Pull Request
Azure App Configuration Configuration Provider Overview ...e-app-configuration/configuration-provider-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows/.NET-first bias by listing .NET-based providers and samples before those for other platforms and languages. All sample links for .NET providers point to Windows-centric examples (e.g., DotNetCore, DotNetFramework/WebDemo), with no explicit mention or examples for Linux environments or Linux-specific usage patterns. There is no reference to Linux tools, shell commands, or cross-platform configuration scenarios. The documentation implicitly assumes a Windows development environment, especially in the .NET sections.
Recommendations
  • Add explicit Linux usage examples for .NET providers, such as running .NET Core applications on Linux, using Linux shell commands for configuration, and deploying to Linux containers.
  • Include cross-platform sample projects and instructions, highlighting both Windows and Linux environments.
  • Mention Linux equivalents (e.g., bash, systemd, environment variables) where Windows-specific tools or patterns are referenced.
  • Ensure that documentation for all languages/platforms includes parity in sample environments, not just Windows-centric ones.
  • Consider reordering the provider list or grouping by language rather than platform to avoid implicit prioritization of Windows/.NET.
GitHub Create Pull Request
Azure App Configuration Use dynamic configuration using push refresh - Java Spring ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes both Windows command prompt and PowerShell commands explicitly, with Linux/macOS instructions coming last. All platforms are covered, but the ordering and explicit mention of Windows tools first indicate a subtle Windows-first bias. There are no missing Linux examples or exclusive use of Windows tools, but the pattern prioritizes Windows users.
Recommendations
  • Present environment variable setup instructions in a platform-neutral order, or alternate the order between sections to avoid always listing Windows first.
  • Group platform-specific instructions in a tabbed or clearly separated format (e.g., tabs for Windows CMD, PowerShell, Linux/macOS Bash) to give equal prominence.
  • Explicitly state that all commands are cross-platform where possible, and avoid implying Windows is the default or primary platform.
  • Consider including screenshots or examples from Linux/macOS environments as well, not just Windows.
  • Review other sections for subtle prioritization of Windows tools or patterns and adjust for parity.
GitHub Create Pull Request
Azure App Configuration Enable telemetry for feature flags in a Node.js application .../azure-app-configuration/howto-telemetry-javascript.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides instructions for setting environment variables in Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. Windows commands are listed first, and PowerShell is given its own example, which may suggest a bias towards Windows users. However, Linux/macOS instructions are present and correct.
Recommendations
  • Present environment variable instructions for all platforms together, or start with a neutral cross-platform approach (e.g., show Linux/macOS and Windows side by side).
  • Consider using a table or code tabs to allow users to select their OS, improving parity and discoverability.
  • Avoid listing Windows commands first by default; alternate the order or use alphabetical order.
  • Ensure that any platform-specific instructions are equally detailed and prominent for Linux/macOS.
GitHub Create Pull Request
Azure App Configuration Roll out features to targeted audiences in a Python app ...re-app-configuration/how-to-targeting-filter-python.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. Windows-specific tools (setx, PowerShell syntax) are described in detail, while Linux/macOS is only briefly covered. The order and detail of examples favor Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel, or start with Linux/macOS examples to balance audience expectations.
  • Provide equal detail for Linux/macOS commands (e.g., explain persistence of environment variables, mention .bashrc/.zshrc for permanent changes).
  • Avoid Windows-first ordering; consider grouping OS-specific instructions under clear subheadings.
  • Include troubleshooting notes for common issues on Linux/macOS (e.g., shell differences, permissions).
  • Ensure that all code and command examples are tested and validated on both platforms.
GitHub Create Pull Request
Azure App Configuration Enable telemetry for feature flags in a Python application ...cles/azure-app-configuration/howto-telemetry-python.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides instructions for setting environment variables on Windows using Command Prompt and PowerShell before mentioning the equivalent Linux/macOS command. This ordering prioritizes Windows users and may give the impression that Windows is the primary or preferred platform. Additionally, both Windows Command Prompt and PowerShell examples are included, while only a single Linux/macOS example is given.
Recommendations
  • Present platform instructions in parallel (side-by-side or in a table) rather than listing Windows first.
  • Provide equal detail and visibility for Linux/macOS commands and workflows.
  • Explicitly state cross-platform compatibility and mention that all examples work on Linux/macOS unless otherwise noted.
  • Consider including Linux/macOS-specific troubleshooting tips or notes if relevant.
  • Avoid listing multiple Windows shell examples unless also providing equivalent alternatives for Linux/macOS (e.g., bash, zsh).
GitHub Create Pull Request
Azure App Configuration Use variant feature flags in a Node.js application ...onfiguration/howto-variant-feature-flags-javascript.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a Windows bias in the section on setting environment variables: Windows Command Prompt and PowerShell instructions are listed before Linux/macOS, and both Windows shells are given explicit commands. While Linux/macOS instructions are present, Windows approaches are prioritized and described in more detail.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Use a tabbed or side-by-side format for environment variable setup, so users can easily find instructions for their OS.
  • Provide equal detail for Linux/macOS commands (e.g., mention shell persistence, profile files if relevant).
  • Consider referencing cross-platform tools (like dotenv or npm scripts) for environment variable management.
  • Avoid language that implies Windows is the default or primary platform.
GitHub Create Pull Request
Azure App Configuration Create an Azure App Configuration store using Bicep ...n/articles/azure-app-configuration/quickstart-bicep.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is presented in parallel tabs throughout. There is no explicit mention of Linux or macOS environments, nor are there any platform-specific notes or troubleshooting for non-Windows users. The use of PowerShell may implicitly favor Windows users, as PowerShell is natively available on Windows and less commonly used on Linux/macOS. No Linux-specific tools or shell examples (e.g., Bash) are provided.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Windows, Linux, and macOS, and are recommended for cross-platform usage.
  • Consider listing Azure CLI examples before PowerShell examples, as CLI is more universally available.
  • Include troubleshooting or installation guidance for Azure CLI and PowerShell on Linux/macOS.
  • Add Bash shell examples for common tasks, or clarify that CLI commands can be run in Bash, zsh, etc.
  • Where PowerShell is mentioned, note that PowerShell Core is available cross-platform, but CLI is generally simpler for Linux/macOS users.
GitHub Create Pull Request
Azure App Configuration Quickstart for using chat completion configuration in a Go app ...ure-app-configuration/quickstart-chat-completion-go.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. Windows-specific tools (setx, PowerShell) are described first, with Linux/macOS only mentioned afterward. There is no exclusive use of Windows tools, but the ordering and detail favor Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or in a neutral order (e.g., Linux/macOS first, or side-by-side).
  • Provide equal detail for Linux/macOS commands and troubleshooting steps.
  • Avoid implying Windows is the default or primary platform by listing all OS options together.
  • Consider using cross-platform environment variable setting instructions (e.g., via .env files or Go code) where possible.
GitHub Create Pull Request
Azure App Configuration Integrate Azure App Configuration with Kubernetes Deployment using Helm ...-configuration/integrate-kubernetes-deployment-helm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides a PowerShell example for passing secrets to Helm, without a corresponding Linux/bash example. The use of PowerShell syntax and cmdlets (e.g., ConvertFrom-Json, foreach) is Windows-centric and may not be directly usable by Linux or macOS users. This PowerShell example appears before any Linux alternative, and no bash or shell script equivalent is provided.
Recommendations
  • Add a bash/Linux shell example for the 'helm upgrade --set' workflow, using jq or similar tools to process JSON output from Azure CLI.
  • Explicitly mention cross-platform compatibility for CLI commands and provide alternatives for both Windows and Linux/macOS users.
  • Where PowerShell is used, provide a side-by-side bash equivalent to ensure parity.
  • Review other sections for subtle Windows-first language or tool recommendations and ensure Linux tools are equally represented.
GitHub Create Pull Request
Azure App Configuration Quickstart for using chat completion configuration in a .NET app ...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates minor Windows bias in the section on setting environment variables: Windows Command Prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell is given a dedicated example, while the Linux/macOS example is brief and lacks detail. The rest of the documentation is platform-neutral, focusing on .NET CLI and C# code, which is cross-platform.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Provide more detailed Linux/macOS instructions, including troubleshooting tips (e.g., how to persist environment variables across sessions).
  • Include a note clarifying that all .NET CLI commands and code samples work identically on Linux, macOS, and Windows.
  • Consider grouping environment variable instructions by platform in a table or side-by-side format for parity.
  • Add links to official documentation for setting environment variables on Linux/macOS.
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with JavaScript apps ...re-app-configuration/quickstart-javascript-provider.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. Windows-specific tools (setx, PowerShell) are mentioned explicitly, while Linux/macOS instructions are grouped together and provided after the Windows examples. The Node.js installation guidance also references Windows and WSL before other platforms.
Recommendations
  • Present platform instructions in parallel tabs or in a consistent order (e.g., alphabetical: Linux/macOS, PowerShell, Windows CMD) to avoid prioritizing Windows.
  • Explicitly mention Linux and macOS tools and patterns where relevant, and ensure parity in detail and clarity.
  • In prerequisite sections, provide installation instructions for Node.js on Linux/macOS with equal prominence as Windows.
  • Consider using generic cross-platform instructions first, or highlight that all platforms are equally supported.
  • Review for any other subtle prioritization of Windows terminology or tooling, and balance with Linux/macOS equivalents.
GitHub Create Pull Request
Azure App Configuration Using Azure App Configuration in Python apps with the Azure SDK for Python .../articles/azure-app-configuration/quickstart-python.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page exhibits mild Windows bias in the 'Prerequisites' and environment variable setup sections. The Python installation guidance links only to Windows documentation, and instructions for setting environment variables list Windows Command Prompt and PowerShell before macOS/Linux, with more detailed steps for Windows (e.g., restart prompt for setx). No Linux-specific installation or troubleshooting guidance is provided.
Recommendations
  • In the prerequisites, add links to Python installation guides for Linux and macOS alongside the Windows documentation.
  • When describing environment variable setup, present all platforms in parallel (e.g., a table or side-by-side tabs) or alternate the order to avoid always listing Windows first.
  • Include any platform-specific notes for Linux/macOS users, such as common locations for Python installations, shell differences, or troubleshooting tips.
  • Ensure parity in detail and clarity for Linux/macOS instructions, matching the specificity given to Windows users (e.g., mention shell session persistence for export commands).
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to JavaScript apps ...pp-configuration/quickstart-feature-flag-javascript.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a Windows-first bias, especially in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell and Windows-specific tools (setx) are given prominent placement, while Linux/macOS instructions are listed last. The prerequisite section also references Windows and WSL before Linux. All code samples themselves are cross-platform, but the environment setup guidance prioritizes Windows users.
Recommendations
  • Present environment variable instructions for Linux/macOS first, or in parallel with Windows, to avoid implying Windows is the default platform.
  • In the prerequisites, provide direct links or instructions for installing Node.js on Linux/macOS, not just Windows/WSL.
  • Use tabbed or side-by-side formatting for platform-specific commands to emphasize parity.
  • Explicitly state that all code samples are cross-platform and runnable on Linux/macOS as well as Windows.
  • Consider including a note about differences in environment variable persistence between platforms (e.g., setx vs. export).
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with Go applications ...s/azure-app-configuration/quickstart-go-console-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes explicit PowerShell examples. While Linux/macOS instructions are present, Windows tools and patterns are mentioned first and in more detail, 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.
  • Avoid giving Windows-specific tools (e.g., setx, PowerShell) precedence; consider grouping all OS instructions equally.
  • Add clarifying notes about differences in environment variable persistence (e.g., setx vs export), especially for Linux users.
  • Consider providing a cross-platform script or guidance for setting environment variables, or refer to OS documentation for details.
  • Explicitly mention that all Go code and Azure CLI commands are cross-platform, and highlight any OS-specific caveats.
GitHub Create Pull Request
Azure App Configuration Using Azure App Configuration in JavaScript apps with the Azure SDK for JavaScript | Microsoft Docs ...icles/azure-app-configuration/quickstart-javascript.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a mild Windows bias, particularly in the 'Configure an environment variable' section. Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents, and PowerShell is given its own example. The Node.js installation instructions reference Windows and WSL before Linux, and links for getting started with Node.js are Windows-centric. However, Linux/macOS commands are present and correct, and most code samples are platform-agnostic.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Provide links for installing Node.js on Linux/macOS, not just Windows.
  • Avoid giving Windows-specific tools (PowerShell, setx) precedence over cross-platform or Linux-native methods.
  • Consider grouping environment variable instructions by platform, or using tabs for Windows, macOS, and Linux equally.
  • Explicitly state that all code samples work on Linux/macOS as well as Windows.
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with Python apps | Microsoft Learn .../azure-app-configuration/quickstart-python-provider.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation displays a mild Windows bias in the 'Prerequisites' and 'Run the application' sections. Windows-specific instructions (Windows command prompt and PowerShell) are listed before Linux/macOS equivalents, and the only link for Python setup is for Windows. However, Linux/macOS commands are present and correct, and code samples are platform-neutral.
Recommendations
  • Provide links for Python installation on Linux and macOS alongside the Windows documentation link in the prerequisites.
  • List environment variable commands for Linux/macOS before or alongside Windows/PowerShell, or present all platforms in a tabbed or side-by-side format for parity.
  • Explicitly state that the instructions and code samples work equally well on Linux/macOS, not just Windows.
  • Consider adding troubleshooting notes or tips for Linux/macOS users, if there are platform-specific caveats.
GitHub Create Pull Request
Azure Cache For Redis Best practices for memory management ...he-for-redis/cache-best-practices-memory-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation references Azure PowerShell as a primary tool for programmatic cache scaling, listing it before Azure CLI and REST API. This ordering and inclusion of PowerShell (a Windows-centric tool) may suggest a Windows-first perspective and a slight bias toward Windows tooling. However, Linux-compatible tools (Azure CLI, REST API) are also mentioned, and there are no exclusive Windows-only examples or commands.
Recommendations
  • List Azure CLI before PowerShell when mentioning cross-platform tools, as CLI is natively supported on both Windows and Linux.
  • Provide explicit examples for both Azure CLI and PowerShell when describing programmatic operations, ensuring parity.
  • Add a note clarifying that all mentioned tools (PowerShell, CLI, REST API) are available on multiple platforms, and link to installation guides for both Windows and Linux.
  • Avoid implying PowerShell is the default or preferred tool for automation unless there is a technical reason.
GitHub Create Pull Request
Azure Cache For Redis Azure Cache for Redis Event Grid Overview ...ain/articles/azure-cache-for-redis/cache-event-grid.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page lists PowerShell as a primary tool for quickstarts and next steps, placing it before Azure CLI in some sections. PowerShell is strongly associated with Windows, and its prominence may suggest a Windows-centric approach. While Azure CLI (cross-platform) is included, there are no explicit Linux-specific examples or mentions of Linux tools, and the ordering tends to favor Windows/PowerShell over CLI.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI is available and supported on Linux and macOS, not just Windows.
  • Add Linux-specific instructions or examples (e.g., using Bash scripts, curl, or other native Linux tools) for subscribing to and handling events.
  • Consider including a table or section that highlights platform compatibility for each tool.
  • Avoid defaulting to PowerShell as the primary automation example; provide equal coverage for Bash/CLI workflows.
GitHub Create Pull Request
Azure Cache For Redis Scale an Azure Cache for Redis instance ...n/articles/azure-cache-for-redis/cache-how-to-scale.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a mild Windows bias. PowerShell examples are provided before Azure CLI examples in all relevant sections, and PowerShell is mentioned as a primary tool for scaling operations. There are no Linux-specific shell examples (e.g., Bash) or explicit references to Linux environments. However, Azure CLI is cross-platform and included throughout, which helps mitigate the bias. No Windows-only tools or patterns are used, and the portal instructions are platform-neutral.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash invocation where appropriate.
  • Add a short note or section for Linux users, confirming that all CLI operations are supported on Linux and macOS, and referencing installation instructions for Azure CLI on those platforms.
  • If possible, include example scripts or automation patterns using Bash or other common Linux shells.
  • Avoid implying PowerShell is the default or preferred automation tool; clarify that both PowerShell and Azure CLI are supported equally.
GitHub Create Pull Request
Azure Functions Durable entities - Azure Functions .../azure-functions/durable/durable-functions-entities.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Durable Entities in Azure Functions does not show explicit Windows bias in terms of examples using Windows-specific tools (e.g., PowerShell) or referencing Windows-only patterns. However, there is a subtle 'windows_first' bias in the ordering and depth of .NET (C#) examples, which are presented first and in greater detail than JavaScript or Python. There are no explicit Linux-specific examples, nor is there discussion of Linux tooling or platform differences. The documentation assumes parity across platforms but does not demonstrate it with equivalent Linux-oriented content.
Recommendations
  • Add explicit notes or examples for Linux environments, such as running Azure Functions on Linux hosts, including any differences in deployment, configuration, or runtime behavior.
  • Include references to Linux-native tools or workflows (e.g., Bash scripts, CLI usage on Linux) where relevant, especially in sections about accessing or deploying entities.
  • Ensure that code samples and walkthroughs for JavaScript and Python are as detailed and comprehensive as those for .NET, including advanced scenarios (e.g., entity coordination, locking).
  • If there are platform-specific limitations or behaviors (e.g., file system, environment variables, authentication), document these clearly for both Windows and Linux.
  • Consider adding a section or sidebar comparing Windows and Linux hosting for Durable Entities, highlighting any differences or best practices.
GitHub Create Pull Request
Azure Functions Event-driven Scaling in Azure Functions .../main/articles/azure-functions/event-driven-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. In the section on limiting scale-out for Consumption/Premium plans, both Azure CLI and Azure PowerShell examples are provided, but PowerShell is given a dedicated tab and example, while no Linux-specific shell (e.g., Bash) or cross-platform alternatives (e.g., REST API, ARM template) are shown. Additionally, scale-in behavior is described specifically for 'apps running on Windows in a Consumption plan,' with no mention of Linux or cross-platform differences. No explicit Linux examples, tools, or parity notes are present.
Recommendations
  • Add explicit Bash examples alongside PowerShell for configuration commands.
  • Clarify whether scale-in behaviors and drain mode apply similarly to Linux-hosted apps, or document any differences.
  • Include notes or examples for Linux users, such as using the Azure CLI in Bash or referencing REST API/ARM template alternatives.
  • Avoid phrasing that singles out Windows unless there is a technical reason; provide parity information for Linux where applicable.
GitHub Create Pull Request
Azure Functions Apache Kafka output binding for Azure Functions ...les/azure-functions/functions-bindings-kafka-output.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides code samples for multiple languages, including C#, JavaScript, Python, Java, and PowerShell. However, the inclusion of PowerShell examples and configuration implies a Windows-centric approach, as PowerShell is primarily a Windows shell (though now cross-platform). The presence of PowerShell examples alongside other languages, and the lack of explicit Linux shell (e.g., Bash) or Linux-specific guidance, suggests a subtle Windows bias. There are no explicit references to Windows-only tools or patterns, but the prioritization of PowerShell as a top-level language option is a sign of Windows-first thinking.
Recommendations
  • Add Bash or Linux shell examples for scripting scenarios, especially for automation or deployment tasks.
  • Explicitly mention cross-platform compatibility for PowerShell examples, or provide equivalent Bash scripts where applicable.
  • Include guidance or troubleshooting notes for Linux environments, such as file path conventions, permissions, or common Kafka deployment patterns on Linux.
  • Ensure that any references to tools, configuration, or environment setup are not Windows-specific, or provide Linux alternatives in parallel.
  • Consider reordering language pivots so that PowerShell is not featured before more cross-platform languages (e.g., Python, JavaScript).
GitHub Create Pull Request
Azure Functions Model context protocol bindings for Azure Functions ...ain/articles/azure-functions/functions-bindings-mcp.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page shows a Windows bias by providing only Azure CLI examples for retrieving function keys, with no mention of Linux-specific commands or parity for Linux users. The page references Azure Functions Core Tools for local development but does not clarify cross-platform usage or provide Linux-specific installation or usage guidance. There are no PowerShell-specific examples, but the absence of Linux shell (bash) or cross-platform examples and the general assumption of Windows-centric tools and workflows indicate a subtle Windows-first bias.
Recommendations
  • Add explicit Linux (bash) command examples for key retrieval, such as using curl or az CLI in bash.
  • Clarify that Azure Functions Core Tools are cross-platform and provide installation instructions for Linux and macOS.
  • Include notes or examples for Linux users regarding environment setup, file paths, and shell usage.
  • Ensure that all CLI examples work identically on Linux, and mention any platform-specific caveats.
  • Add a section or callout highlighting cross-platform compatibility and best practices for Linux users.
GitHub Create Pull Request
Azure Functions Azure OpenAI embeddings input binding for Azure Functions ...unctions/functions-bindings-openai-embeddings-input.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides dedicated code examples and configuration details for PowerShell, which is a Windows-centric scripting language. There are no equivalent examples for Bash or other Linux-native shells. The presence of PowerShell-specific instructions and absence of Linux shell alternatives indicates a bias toward Windows environments.
Recommendations
  • Add Bash or shell script examples alongside PowerShell to support Linux users.
  • Include instructions for configuring and running Azure Functions bindings in Linux environments.
  • Ensure that any references to configuration files or environment variables are platform-neutral and provide examples for both Windows and Linux shells.
  • Where PowerShell is used, offer equivalent Bash commands or scripts for parity.
GitHub Create Pull Request
Azure Functions Azure OpenAI Semantic Search Input Binding for Azure Functions ...ions/functions-bindings-openai-semanticsearch-input.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides code examples for multiple languages, including C#, Java, JavaScript, TypeScript, Python, and PowerShell. However, the PowerShell example is the only shell scripting example provided, with no equivalent Bash or Linux shell example. PowerShell is primarily a Windows tool, and its inclusion without a Linux shell counterpart suggests a Windows bias. There are no references to Linux-specific tools, nor are there examples for Bash or other common Linux shells. The configuration and usage sections do not mention platform-specific considerations, but the presence of PowerShell as the sole shell scripting example is notable.
Recommendations
  • Add equivalent Bash or Linux shell examples alongside PowerShell to ensure Linux parity.
  • Explicitly mention platform compatibility for shell scripting examples (e.g., note if PowerShell Core is supported on Linux).
  • Include guidance or links for Linux users on how to run or adapt the examples.
  • Consider providing cross-platform instructions for configuration and environment variable setup.
GitHub Create Pull Request
Azure Functions Azure Blob storage trigger and bindings for Azure Functions ...les/azure-functions/functions-bindings-storage-blob.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific namespaces (e.g., Microsoft.WindowsAzure.Storage) and tools (NuGet, .NET CLI) throughout, and the historical context and migration guides focus on Windows-centric SDKs. There is no explicit mention of Linux equivalents or cross-platform CLI usage (e.g., dotnet CLI on Linux), and the examples and instructions are presented in a way that assumes a Windows development environment. However, there are no PowerShell-heavy examples, and the page does not completely exclude Linux usage.
Recommendations
  • Explicitly mention that .NET CLI and NuGet commands work cross-platform, including on Linux and macOS.
  • Add notes or examples for installing and using the SDKs and extensions on Linux (e.g., using dotnet CLI on Ubuntu).
  • Avoid referring to deprecated Windows-centric namespaces as the default or primary option; clarify their legacy status and highlight cross-platform alternatives.
  • Where possible, provide parity in instructions for Linux users, such as mentioning package managers or shell commands relevant to Linux.
  • Ensure that migration guides and references do not assume a Windows environment by default.
GitHub Create Pull Request
Azure Functions Enable private site access to Azure Functions ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively guiding users to create a Windows Server VM and providing screenshots and instructions tailored to Windows. There are no instructions or examples for creating or using a Linux VM, nor is there mention of Linux-specific tools or workflows. The quickstart links for creating functions do include command line and Maven options, but the core networking and VM setup is Windows-centric.
Recommendations
  • Add parallel instructions and screenshots for creating a Linux VM (e.g., Ubuntu) in Azure.
  • Explicitly mention that either Windows or Linux VMs can be used for this scenario, and discuss any differences in setup or access.
  • Provide examples of accessing the function app from a Linux VM, including using SSH via Azure Bastion.
  • Ensure that command line instructions (e.g., Azure CLI) are presented for both Windows and Linux environments where relevant.
  • Balance references to Windows tools (e.g., RDP) with Linux equivalents (e.g., SSH), and clarify when each is applicable.
GitHub Create Pull Request
Azure Functions Manually run a non HTTP-triggered Azure Functions ...les/azure-functions/functions-manually-run-non-http.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing the Azure portal and Visual Studio Code (both commonly used on Windows) as primary tools for running and testing Azure Functions. The examples and instructions do not mention or provide Linux-specific alternatives, nor do they reference Linux-native tools or workflows. There are no explicit PowerShell or Windows-only command examples, but the lack of Linux parity and the ordering of instructions favor Windows-centric approaches.
Recommendations
  • Include explicit examples using Linux-native HTTP test tools, such as curl or httpie, with sample commands.
  • Mention and provide steps for accessing the Azure portal and running functions from Linux environments.
  • Add guidance for using the Azure CLI on Linux, including installation and usage notes specific to Linux.
  • Reference cross-platform editors and tools (e.g., VS Code on Linux, or alternatives like Vim, Emacs) where appropriate.
  • Ensure that screenshots and instructions do not assume a Windows environment, and clarify platform-agnostic steps.
GitHub Create Pull Request
Azure Functions Azure Functions runtime versions overview ...ob/main/articles/azure-functions/functions-versions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a mild Windows bias by mentioning Windows and Windows-based tools (Visual Studio, .csproj, .NET Framework) before Linux alternatives, and by omitting explicit Linux-specific examples or instructions. The guidance for pinning to a minor version refers to differences between Windows and Linux but does not provide Linux-specific steps or examples. Most tooling examples (Visual Studio, .csproj) are Windows-centric, with limited coverage of Linux workflows or parity in example depth.
Recommendations
  • Provide explicit Linux examples and instructions wherever Windows-specific guidance is given, especially for runtime pinning and local development workflows.
  • Include parity in tooling coverage by detailing workflows for Linux-based development environments (e.g., VS Code on Linux, CLI usage on Linux, .NET SDK installation on Linux).
  • When mentioning platform-specific differences (e.g., pinning runtime versions), offer side-by-side examples for both Windows and Linux.
  • Expand documentation to include Linux-native tools and patterns (e.g., bash scripts, Linux file paths, package managers) where relevant.
  • Avoid assuming Visual Studio or .csproj as the default; mention alternatives like VS Code, JetBrains Rider, or CLI-based workflows for cross-platform development.
GitHub Create Pull Request
Azure Functions Manage connections in Azure Functions ...ob/main/articles/azure-functions/manage-connections.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples and guidance primarily for C#/.NET and JavaScript, with a strong focus on .NET libraries and patterns (e.g., HttpClient, SqlClient, Entity Framework). There is no mention of Linux-specific tools, connection management patterns, or examples for languages/environments commonly used on Linux (such as Python, Java, or Bash). Configuration instructions reference Windows-centric concepts (e.g., Application settings, local.settings.json) without discussing Linux deployment nuances. The order of presentation and the depth of .NET examples suggest a Windows-first bias, and there are no Linux-specific troubleshooting or connection management tips.
Recommendations
  • Add examples for other languages commonly used on Linux, such as Python (requests, Azure SDK), Java, or Bash scripts.
  • Include guidance on connection management for Linux-native tools and environments, such as environment variable configuration, systemd service settings, or Linux-specific networking limits.
  • Discuss deployment and configuration differences between Windows and Linux function apps, including file paths, environment variable management, and troubleshooting techniques.
  • Provide parity in troubleshooting steps and references to Linux monitoring tools (e.g., using Azure Monitor on Linux, inspecting /proc/net/tcp for connection counts).
  • Explicitly mention that the guidance applies to both Windows and Linux hosting environments, and clarify any platform-specific caveats.
GitHub Create Pull Request
Azure Functions Memory profiling of Python apps in Azure Functions ...es/azure-functions/python-memory-profiler-reference.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a Windows bias in the local development setup instructions. Windows PowerShell is mentioned first, and Windows-specific commands (such as 'py -m venv .venv' and '.venv\Scripts\Activate.ps1') are listed before their Linux equivalents. The phrase 'Open a Windows PowerShell or any Linux shell as you prefer' also places Windows first, subtly prioritizing it. However, Linux equivalents are present, and most code examples are OS-agnostic Python.
Recommendations
  • Present Linux and Windows instructions side-by-side or in separate tabs, rather than listing Windows first.
  • Use neutral phrasing such as 'Open a terminal (Windows PowerShell or Linux shell)' or 'Open your preferred shell.'
  • List Linux commands before or alongside Windows commands to avoid implicit prioritization.
  • Ensure parity in troubleshooting and environment setup guidance for both platforms.
  • Consider adding explicit macOS instructions where relevant.
GitHub Create Pull Request
Azure Government Azure support for export controls ...e-government/documentation-government-overview-itar.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is generally platform-neutral, with most guidance focused on Azure features and compliance requirements. However, there is a subtle Windows bias in the 'FIPS 140 validated cryptography' section, where Windows-specific FIPS validation is referenced before Linux, and links are provided to Windows FIPS validation documentation. The mention of 'commercially available operating systems (Linux and Windows), and Azure-specific version of Windows' does acknowledge Linux, but the validation details and supporting links are Windows-centric. No PowerShell-heavy examples, missing Linux examples, or exclusive use of Windows tools/patterns are present, but Windows is prioritized in cryptography validation references.
Recommendations
  • Provide equal detail and reference links for Linux FIPS 140 validation, including documentation on how Azure's Linux-based services meet FIPS 140 requirements.
  • Clarify that both Linux and Windows operating systems in Azure use FIPS 140 validated cryptographic modules, and link to relevant Linux validation documentation or standards.
  • Include examples or references for managing encryption and compliance on Linux-based Azure services, not just Windows.
  • Review other sections for subtle prioritization of Windows tools or documentation and ensure Linux parity in technical references.
GitHub Create Pull Request
Azure Government Azure support for public safety and justice ...re-government/documentation-government-overview-jps.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates a moderate Windows bias, especially in sections discussing cryptography and authentication. Windows-specific tools and validation programs (such as Windows FIPS validation and Windows Hello for Business) are mentioned explicitly and sometimes before Linux equivalents. References to cryptographic modules and authentication verifiers focus on Windows implementations, with little mention of Linux-specific guidance or parity.
Recommendations
  • Include explicit references to Linux cryptographic modules and their FIPS validation status in Azure environments.
  • Provide examples or guidance for configuring Azure security features (such as Key Vault, encryption, and authentication) on Linux systems, not just Windows.
  • Mention Linux-compatible authentication solutions (such as FIDO2 security keys and smartcards) and how they integrate with Azure and Microsoft Entra ID.
  • Ensure that documentation about cryptography, authentication, and compliance highlights cross-platform support and does not imply Windows as the default or preferred environment.
  • Add links or sections for Linux-specific best practices in Azure for public safety and justice workloads.
GitHub Create Pull Request
Azure Netapp Files Understand Azure NetApp Files control plane security .../articles/azure-netapp-files/control-plane-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently references Azure management interfaces as 'APIs, PowerShell, CLI, or the Azure portal', listing PowerShell (a Windows-centric tool) before CLI and omitting explicit mention of Linux-native tools or shell scripting. No Linux-specific examples, commands, or patterns are provided, and there is no discussion of Bash, Azure CLI usage on Linux, or cross-platform scripting. The documentation implicitly prioritizes Windows/PowerShell by order and omission.
Recommendations
  • Explicitly mention Azure CLI and Bash scripting as first-class management options alongside PowerShell.
  • Provide example commands for both PowerShell and Azure CLI (with Bash syntax) for common control plane operations.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Include links to Azure CLI documentation and Linux setup guides.
  • Avoid listing PowerShell before CLI unless contextually justified; consider 'CLI, PowerShell, APIs, or the Azure portal' or 'Azure CLI (cross-platform), PowerShell (Windows), APIs, or the Azure portal'.
GitHub Create Pull Request
Azure Netapp Files azure-netapp-files/create-active-directory-connections.md ...les/azure-netapp-files/includes/netlogon-april-2023.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation focuses exclusively on the impact of a Windows Update (April 2023) and Netlogon Secure Channel changes, with no mention of Linux or cross-platform considerations. Only Windows-specific terminology and update references are provided, and there are no examples or guidance for Linux environments.
Recommendations
  • Include information about how (or if) Linux-based clients or Samba implementations are affected by the Netlogon protocol changes.
  • Provide equivalent guidance or examples for managing Active Directory connections from Linux systems.
  • Clarify whether the update has any impact on non-Windows environments and, if not, explicitly state this for transparency.
  • Add links or references to Linux/Samba documentation where relevant.
GitHub Create Pull Request
Azure Netapp Files Requirements and considerations for Azure NetApp Files large volumes ...app-files/large-volumes-requirements-considerations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell commands first and in detail for feature registration and status checking, with Azure CLI commands mentioned only as alternatives and without explicit examples. No Linux-specific tools or shell commands are provided, and the command-line instructions are primarily tailored to Windows/PowerShell users.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell, not just references.
  • Include Linux shell (bash) usage patterns for feature registration and status checking.
  • Ensure command-line instructions are presented in a platform-neutral manner or alternate between Windows and Linux examples.
  • Add notes or sections for Linux users, clarifying any differences in procedure or environment.
  • Review other configuration steps for implicit Windows assumptions and offer Linux equivalents.
GitHub Create Pull Request
Azure Netapp Files Integration FAQs for Azure NetApp Files ...ob/main/articles/azure-netapp-files/faq-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. In the section about mounting Azure NetApp Files volumes on AVS VMs, Windows is mentioned first for both NFS and SMB, and only Windows VMs are referenced for SMB shares. There are no explicit Linux examples for SMB, and Linux is only mentioned in passing for NFS mounts, with no details or parity in instructions/examples.
Recommendations
  • Provide explicit examples or instructions for mounting Azure NetApp Files SMB shares on Linux VMs, if supported.
  • Ensure that Linux is mentioned equally and not only after Windows, especially in lists or examples.
  • Where possible, offer parallel instructions for both Windows and Linux environments for common integration scenarios.
  • Clarify any limitations or differences in support between Windows and Linux for NFS and SMB mounts.
GitHub Create Pull Request
Azure Maps Create your Azure Maps account using an Azure Resource Manager template in Azure Maps ...lob/main/articles/azure-maps/how-to-create-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation primarily describes deploying Azure Maps accounts using the Azure Portal, which is platform-neutral, but when mentioning alternative deployment methods, it lists Azure PowerShell first, followed by Azure CLI and REST API. There are no explicit PowerShell examples, but the CLI examples provided use Azure CLI, which is cross-platform. However, there is no mention of Linux-specific tools, shell scripts, or guidance for Linux users, and the linked 'Deploy templates' page refers to PowerShell before CLI. This ordering and lack of Linux-specific context indicate a subtle Windows-first bias and missing Linux parity.
Recommendations
  • Ensure that deployment method lists alternate between PowerShell and CLI, or list CLI first to reflect cross-platform parity.
  • Provide explicit examples for both Azure PowerShell and Azure CLI, and clarify that CLI commands work on Windows, Linux, and macOS.
  • Include references to Linux shell scripting or automation where appropriate.
  • Add notes or sections for Linux/macOS users, such as prerequisites for installing Azure CLI on those platforms.
  • Review linked pages to ensure Linux parity and avoid PowerShell-first ordering.
GitHub Create Pull Request
Azure Resource Manager Bicep functions - string ...azure-resource-manager/bicep/bicep-functions-string.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
This documentation page is largely platform-neutral in its technical content and code examples, which are all written in Bicep and do not reference any OS-specific tools or patterns. However, there is evidence of Windows bias in the 'Next steps' section, where the only deployment guide linked is for Azure PowerShell, a Windows-centric tool, with no mention of Linux-friendly alternatives such as Azure CLI or Bash scripting. Additionally, references to .NET APIs (e.g., System.String.Format, Guid structure) may be more familiar to Windows/.NET users, though these are relevant to Bicep's implementation and not strictly platform bias.
Recommendations
  • Add links to deployment guides using Azure CLI and Bash for Linux/macOS users in the 'Next steps' section.
  • Where .NET APIs are referenced, briefly note that Bicep is cross-platform and these APIs are used internally, so users on Linux/macOS need not worry about .NET prerequisites.
  • Ensure future documentation consistently provides parity between Windows (PowerShell) and Linux/macOS (CLI/Bash) tooling in examples and guidance.
GitHub Create Pull Request
Azure Maps Drawing tools module ...s/blob/main/articles/azure-maps/set-drawing-options.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell example for installing npm packages ("npm install --save-dev style-loader css-loader") and referencing PowerShell syntax in the context of JavaScript development. There are no Linux or macOS shell equivalents (e.g., bash) shown, and the installation command is presented in PowerShell format without alternatives. This may cause confusion for developers on non-Windows platforms and suggests a Windows-first approach.
Recommendations
  • Provide equivalent installation commands using bash/sh (e.g., `npm install --save-dev style-loader css-loader`) without the PowerShell prompt, or clarify that the command works cross-platform.
  • Avoid using platform-specific prompts (e.g., `powershell`) unless necessary, and if used, always provide alternatives for Linux/macOS users.
  • Add notes or examples that explicitly mention cross-platform compatibility for all commands and tooling.
  • Where tooling (like webpack) is discussed, ensure instructions are not tailored to Windows environments only.
GitHub Create Pull Request
Azure Resource Manager Create multiple resource instances in Bicep ...icles/azure-resource-manager/bicep/quickstart-loops.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for deployment and cleanup, but PowerShell is mentioned as a primary tool in the prerequisites and is given equal prominence in all code tabs. Visual Studio Code is recommended as the editor, which is cross-platform, but the overall pattern leans toward Windows-centric tools and workflows, with no explicit mention of Linux-specific alternatives or shell environments (e.g., Bash). There are no Linux-specific examples, nor is there guidance for Linux users regarding shell syntax or environment setup.
Recommendations
  • Explicitly mention that Azure CLI commands work in Bash and other Linux shells, and provide example commands using Bash syntax (e.g., export instead of variable assignment with =).
  • Add a note in the prerequisites about using Bicep and Azure CLI on Linux and macOS, with links to installation guides for those platforms.
  • Consider including a Linux shell tab alongside CLI and PowerShell, showing Bash-style variable assignment and command usage.
  • Clarify that Visual Studio Code and the Bicep extension are available on Linux and macOS, and mention alternative editors if relevant.
  • Ensure that references to PowerShell do not imply it is the default or preferred method, and balance with Linux-native tooling.
GitHub Create Pull Request
Azure Netapp Files Release Notes for Azure Application Consistent Snapshot tool for Azure NetApp Files | Microsoft Docs .../articles/azure-netapp-files/azacsnap-release-notes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides download links and release notes for both Linux and Windows versions of AzAcSnap, but there is a noticeable Windows-first bias in feature announcements and examples. Features for Microsoft SQL Server on Windows are highlighted before Linux equivalents, and some features are described as 'only available for Microsoft SQL Server', implicitly Windows-centric. There are no explicit Linux-specific examples, nor are Linux tools or patterns mentioned. While binaries for both platforms are provided, the documentation lacks parity in example usage and feature coverage for Linux environments.
Recommendations
  • Include explicit Linux usage examples and configuration patterns alongside Windows examples.
  • When announcing features, clarify platform parity and availability (e.g., 'available for both Linux and Windows' or note any differences).
  • Provide examples for Linux-specific database platforms (e.g., Oracle, SAP HANA) where relevant.
  • Mention Linux tools, commands, or troubleshooting steps where appropriate.
  • Ensure feature announcements do not prioritize Windows unless there is a technical reason, and always note Linux support status.
GitHub Create Pull Request
Azure Netapp Files Configure NFSv4.1 ID domain for Azure NetApp Files ...pp-files/azure-netapp-files-configure-nfsv41-domain.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias by presenting Azure PowerShell commands for feature registration before mentioning Azure CLI alternatives, and by referencing Windows in cross-platform mounting instructions. However, the core configuration steps and examples are focused on Linux NFS clients, with no exclusive use of Windows tools or missing Linux examples.
Recommendations
  • Present Azure CLI commands alongside or before Azure PowerShell commands for feature registration, as CLI is cross-platform and more commonly used on Linux.
  • Clarify that all configuration examples are for Linux clients, and provide explicit instructions for any Windows-based NFS client scenarios if relevant.
  • In cross-platform references (e.g., mounting volumes), ensure Linux instructions are given equal prominence and detail as Windows instructions.
  • Avoid using terms like 'Mount a volume for Windows or Linux VMs' without providing both sets of instructions or linking directly to Linux-specific guidance.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager resource group and resource deletion ...e-resource-manager/management/delete-resource-group.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents PowerShell examples and tabs before Azure CLI and other cross-platform options, suggesting a Windows-first approach. PowerShell is a Windows-centric tool, and its prominence may signal bias toward Windows users. However, Azure CLI and Python examples are also provided, which are cross-platform. No Linux-specific shell examples (e.g., Bash) or explicit Linux tool references are present.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used outside Windows.
  • Include explicit Bash or shell script examples for Linux users.
  • Clarify that Azure CLI and Python examples work on Linux, macOS, and Windows.
  • Add notes or sections highlighting Linux usage patterns, such as running commands in Bash or using Linux authentication methods.
  • Avoid implying PowerShell is the default or preferred method unless justified by user data.
GitHub Create Pull Request
Azure Resource Manager Move guidance for classic deployment model resources ...ent/move-limitations/classic-model-move-limitations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation refers to Azure PowerShell and the portal before mentioning Azure CLI or REST API, which may suggest a Windows-first approach. There are no explicit Linux-specific examples or guidance, and command-line instructions are generic (REST/HTTP), lacking parity for Linux users who may prefer Bash or CLI workflows.
Recommendations
  • Present Azure CLI examples alongside or before PowerShell examples to ensure Linux parity.
  • Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash/CLI).
  • Avoid listing Windows-centric tools (PowerShell, portal) before cross-platform alternatives unless contextually necessary.
  • Add a section or note for Linux users, clarifying any differences or additional steps relevant to their environment.
GitHub Create Pull Request
Azure Resource Manager What is Azure Resource Manager? ...articles/azure-resource-manager/management/overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell before Azure CLI in instructions for creating resource groups and referencing PowerShell as a primary management tool. No Linux-specific tools or examples are mentioned, and the ordering of tools favors Windows-centric patterns. However, Azure CLI is mentioned, and there are no exclusive Windows-only instructions.
Recommendations
  • Alternate the order of tool references (e.g., mention Azure CLI before PowerShell in some sections).
  • Explicitly state that Azure CLI is cross-platform and provide parity in examples and links.
  • Add Linux-specific usage notes or examples where appropriate, especially for command-line operations.
  • Include references to Bash scripting or other Linux-native automation approaches alongside PowerShell.
  • Clarify that ARM templates and Bicep files can be deployed from any OS, and provide links to Linux setup guides for Azure CLI.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of an output value ...icles/azure-resource-manager/templates/copy-outputs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a subtle Windows bias by listing Azure PowerShell before Azure CLI when discussing supported versions for zero-count copy loops, and by linking only to a PowerShell deployment guide in the 'Next steps' section. There are no Linux-specific examples, and the CLI is mentioned but not given equal prominence or example coverage.
Recommendations
  • List Azure CLI before or alongside Azure PowerShell when mentioning supported tools and versions.
  • Include links to both Azure CLI and PowerShell deployment guides in the 'Next steps' section.
  • Provide example commands for both Azure CLI and PowerShell when discussing deployment scenarios.
  • Explicitly mention Linux support and parity where relevant, especially in tool/version compatibility notes.
GitHub Create Pull Request
Azure Resource Manager View deployment history with Azure Resource Manager ...azure-resource-manager/templates/deployment-history.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for Azure Portal, PowerShell, Azure CLI, and REST API. PowerShell is given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool, and its examples are presented before Azure CLI in every section. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or patterns. The documentation assumes PowerShell is universally available, which may not be the case for Linux users. The use of PowerShell as a primary scripting example introduces a subtle Windows bias.
Recommendations
  • Add bash/sh scripting examples alongside PowerShell, especially for scenarios where scripting is needed.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and highlight its parity.
  • Consider presenting Azure CLI examples before PowerShell, or at least alternating their order.
  • Include notes or links for installing PowerShell on Linux if PowerShell examples are retained.
  • Where possible, reference Linux-native tools or patterns (e.g., jq for JSON parsing) in CLI examples.
  • Clarify that PowerShell is not required for Linux users and that all operations can be performed with Azure CLI or REST API.
GitHub Create Pull Request
Azure Resource Manager Template functions - resources ...ource-manager/templates/template-functions-resource.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias in the section describing how to discover available 'list*' functions for resource types. The PowerShell example (Get-AzProviderOperation) is presented before the Azure CLI equivalent, and only Windows/PowerShell tooling is mentioned by name in the narrative. There are no Linux-specific examples or references to Bash, and the CLI example is not as prominently described. The rest of the page is platform-neutral, focusing on ARM template syntax and JSON examples.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side, or list Azure CLI first to avoid implicit Windows-first ordering.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide Bash or shell script examples where appropriate.
  • Add a note or tip for Linux/macOS users, referencing the Azure CLI as the preferred tool for non-Windows environments.
  • Ensure that any tooling references (e.g., 'Get-AzProviderOperation') are balanced with equivalent Linux-friendly commands.
  • Review other documentation links (such as 'Deploy resources with ARM templates and Azure PowerShell') to ensure parity with Azure CLI deployment guides.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Add outputs to your Azure Resource Manager template ...rce-manager/templates/template-tutorial-add-outputs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell deployment instructions before Azure CLI, and by referencing PowerShell as a primary tool in the prerequisites. There are no explicit Linux-only examples, nor is there mention of Linux-specific tools or shell patterns. The CLI example is present and correct, but the ordering and language favor Windows/PowerShell users.
Recommendations
  • Alternate the order of PowerShell and CLI instructions in tutorials, or present them side-by-side to avoid implicit prioritization.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide shell-specific notes if needed.
  • Include brief instructions or links for running Azure CLI commands in Bash or other Linux shells.
  • In prerequisites, clarify that both Azure PowerShell and Azure CLI are available on all major platforms, and link to installation guides for Linux/macOS as well as Windows.
  • Consider adding a note or section for users working in Linux environments, highlighting any differences or tips.
GitHub Create Pull Request
Azure Resource Manager Scope on extension resource types ...esource-manager/templates/scope-extension-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being cross-platform. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented as a primary method, which may reinforce a Windows-centric workflow for users. No explicit Linux tools or patterns are mentioned.
Recommendations
  • Prioritize Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux and macOS.
  • Add Bash shell script examples for ARM template deployments to demonstrate Linux-native workflows.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation links for non-Windows platforms.
  • Consider referencing Linux-native editors or tools (e.g., VS Code on Linux, nano, vim) for editing ARM templates.
  • If PowerShell is included, clarify that PowerShell Core is available on Linux, but emphasize CLI as the default for cross-platform scenarios.
GitHub Create Pull Request
Azure Netapp Files Configure a cache volume for Azure NetApp Files ...articles/azure-netapp-files/configure-cache-volumes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a mild Windows bias by presenting Azure PowerShell commands first and in detail for feature registration, with Azure CLI commands mentioned only as an alternative in a single sentence. There are no Linux-specific shell examples (e.g., Bash), and the registration steps are shown interactively for PowerShell only. The rest of the documentation is platform-neutral, focusing on REST API calls and ONTAP commands, which are not OS-specific.
Recommendations
  • Provide explicit Azure CLI (Bash) command examples alongside PowerShell for feature registration and status checking, with equal prominence and detail.
  • Add notes or examples for Linux/macOS users, such as how to install and use Azure CLI, and clarify that all REST API calls can be executed from any OS.
  • Ensure that command-line examples are presented in parallel tabs or sections for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) users.
  • Review other sections for subtle Windows-centric language or assumptions, and clarify cross-platform compatibility where relevant.
GitHub Create Pull Request
Azure Netapp Files Configure customer-managed keys for Azure NetApp Files volume encryption .../azure-netapp-files/configure-customer-managed-keys.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides step-by-step instructions for configuring customer-managed keys for Azure NetApp Files using the Azure Portal, Azure CLI, and Azure PowerShell. The CLI instructions are cross-platform, but the PowerShell instructions are Windows-centric and are presented as a full, separate section. There is no mention of Linux-specific tools or shell environments (e.g., Bash, zsh), nor are there any examples using Linux-native scripting or automation approaches. The ordering of examples places Azure PowerShell (a Windows-first tool) on equal footing with Azure CLI, and the documentation metadata explicitly tracks Azure PowerShell. No Linux-specific guidance, troubleshooting, or considerations are provided.
Recommendations
  • Explicitly state that Azure CLI commands work on both Windows and Linux, and provide example shell environments (e.g., Bash, zsh) for Linux users.
  • Add troubleshooting notes or tips for Linux users, such as handling environment variables, file paths, or authentication differences.
  • Consider including examples using Bash scripts for automation, especially for steps involving multiple CLI commands.
  • Clarify that Azure PowerShell is primarily for Windows and provide guidance for Linux users who may wish to use PowerShell Core.
  • Review documentation metadata and ensure Linux parity is tracked (e.g., devx-track-bash or devx-track-linux).
  • If relevant, mention Linux-specific tools or patterns (e.g., jq for JSON parsing, curl for REST calls) alongside CLI examples.
GitHub Create Pull Request
Azure Netapp Files Manage cross-zone-region replication for Azure NetApp Files ...etapp-files/cross-zone-region-replication-configure.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates a Windows bias by providing Azure PowerShell examples for feature registration and status checking, with Azure CLI commands mentioned only as an aside. The PowerShell examples are presented first and in detail, while Linux-friendly CLI commands are referenced briefly and without example syntax. No Linux-specific tools or workflows are described.
Recommendations
  • Provide full Azure CLI command examples alongside PowerShell examples for all operations, not just as a mention.
  • Present CLI and PowerShell examples in parallel, or alternate which is shown first, to avoid Windows-first ordering.
  • Explicitly state that both Windows and Linux users can perform these operations, and clarify any platform-specific prerequisites.
  • Include screenshots or walkthroughs using Azure CLI on Linux or macOS where applicable.
  • Review other sections for similar bias and ensure parity in tooling and instructions.
GitHub Create Pull Request
Azure Netapp Files Manage default and individual user and group quotas for Azure NetApp Files volumes ...p-files/manage-default-individual-user-group-quotas.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by providing detailed quota target formats for SMB (Windows) and dual-protocol volumes with explicit SID patterns, while NFS (Linux/Unix) quota targets are mentioned briefly and generically. There are no concrete Linux/NFS command-line examples, nor are Linux tools or workflows referenced. Windows-specific patterns (SID) are described before NFS equivalents in dual-protocol sections, and no parity is offered for Linux administrators in terms of practical examples or tool references.
Recommendations
  • Provide explicit Linux/NFS examples for quota management, such as command-line workflows or integration with Linux identity management.
  • Reference Linux tools or utilities (e.g., getent, id, or nfs client commands) for identifying user/group IDs for quota targets.
  • Ensure that NFS (Linux/Unix) instructions are presented with equal detail and order as SMB (Windows) instructions, especially in dual-protocol sections.
  • Include screenshots or step-by-step guides for Linux/NFS environments where applicable.
  • Clarify how Linux administrators can map users/groups to quota targets, and provide troubleshooting tips relevant to Linux.
GitHub Create Pull Request
Azure Netapp Files Mount SMB volumes for Windows VMs ...n/articles/azure-netapp-files/mount-volumes-vms-smb.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes mounting SMB volumes for Windows virtual machines, providing instructions only for Windows clients. There are no examples, instructions, or references for mounting SMB volumes on Linux clients, nor is there mention of Linux tools or commands. The focus is solely on Windows, indicating a Windows-first and missing Linux example bias.
Recommendations
  • Add a section detailing how to mount SMB volumes on Linux clients, including example commands (e.g., using 'mount -t cifs', 'smbclient', or relevant Linux tools).
  • Provide parity in screenshots and step-by-step instructions for both Windows and Linux environments.
  • Mention any differences or prerequisites for mounting SMB volumes on Linux, such as required packages or authentication methods.
  • Ensure that both Windows and Linux mounting procedures are presented with equal prominence and clarity.
GitHub Create Pull Request
Azure Netapp Files Benefits of using Azure NetApp Files for SQL Server deployment ...es/solutions-benefits-azure-netapp-files-sql-server.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses exclusively on SQL Server deployment, which is traditionally a Windows-centric workload. All examples, benchmarks, and tooling references are for SQL Server, with no mention of Linux-based alternatives (such as running SQL Server on Linux or using other database engines). There are no Linux-specific deployment patterns, performance metrics, or cost analyses. The documentation implicitly assumes a Windows environment and does not address Linux parity.
Recommendations
  • Include examples and benchmarks for SQL Server running on Linux VMs in Azure, comparing performance and cost with Azure NetApp Files.
  • Mention and link to documentation for deploying SQL Server on Linux with Azure NetApp Files.
  • Discuss any differences or considerations when using Azure NetApp Files with SQL Server on Linux (e.g., supported features, SMB/NFS support, tooling).
  • Provide parity in tooling references (e.g., mention Linux equivalents to perfmon, such as sar, iostat, or atop, for performance metrics).
  • Add a section or note clarifying support for both Windows and Linux SQL Server deployments, and highlight any platform-specific guidance.
GitHub Create Pull Request
Azure Netapp Files Troubleshoot user access on LDAP volumes in Azure NetApp Files ...es/azure-netapp-files/troubleshoot-user-access-ldap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation focuses exclusively on troubleshooting LDAP user access using the Azure portal GUI, without providing any command-line examples or alternative methods. There is no mention of Linux tools (such as getent, id, or ldapsearch) that are commonly used to validate LDAP group memberships, nor are there any PowerShell or Windows command-line examples. However, the lack of Linux-specific troubleshooting steps or parity is notable, especially given the POSIX/LDAP context.
Recommendations
  • Add Linux command-line examples for validating LDAP group memberships (e.g., using 'id username', 'getent group', or 'ldapsearch').
  • Include troubleshooting steps that can be performed from a Linux client, as many Azure NetApp Files users may mount volumes on Linux systems.
  • If Windows tools (such as PowerShell or Active Directory Users and Computers) are relevant, provide equivalent Linux instructions and present both platforms equally.
  • Clarify whether the portal-based troubleshooting is platform-agnostic, and explicitly mention how users on Linux or Windows can validate group memberships outside the portal.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes creating a .NET Framework console application using Visual Studio, a Windows-centric IDE, and provides only Windows-oriented instructions (e.g., right-clicking in Visual Studio, using .NET Framework). There are no examples or guidance for Linux users, such as using .NET Core/SDK CLI, cross-platform editors, or Linux-specific setup steps.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
  • Mention cross-platform IDEs/editors such as VS Code and how to install the NuGet package via CLI ('dotnet add package Microsoft.Azure.Relay').
  • Clarify that the code works with .NET Core/.NET 5+ and is not limited to .NET Framework/Visual Studio.
  • Provide explicit Linux setup steps, including prerequisites and environment notes.
  • Ensure all code and package instructions are platform-neutral or provide alternatives for non-Windows platforms.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-server.md ...id-connections-http-requests-dotnet-get-started-server.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes creating a console application using Visual Studio and .NET Framework, both of which are Windows-centric tools and patterns. There are no instructions or examples for Linux users, such as using .NET Core/SDK CLI, VS Code, or cross-platform NuGet installation. The guidance assumes a Windows development environment and omits Linux equivalents.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (dotnet new console) to support Linux and macOS users.
  • Mention and provide examples for using VS Code or other cross-platform editors, not just Visual Studio.
  • Include steps for installing the NuGet package via the CLI (dotnet add package Microsoft.Azure.Relay) as an alternative to the Visual Studio GUI.
  • Clarify that the code works on .NET Core/.NET 5+ and is cross-platform, or note any platform-specific limitations.
  • Explicitly state platform requirements and provide parity in examples for both Windows and Linux environments.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes creating a .NET Framework console application in Visual Studio, a Windows-centric IDE, and provides instructions using Windows GUI patterns (right-click, Manage NuGet Packages). There are no examples or guidance for Linux users, such as using .NET Core/SDK CLI tools, cross-platform editors, or alternative package management approaches.
Recommendations
  • Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
  • Include guidance for installing the Relay NuGet package via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Mention cross-platform editors such as VS Code, and provide steps for users who do not use Visual Studio.
  • Clarify that the code sample works with .NET Core/.NET 5+ and is not limited to .NET Framework.
  • Add explicit notes or sections for Linux/macOS users, including any platform-specific considerations.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md ...id-connections-http-requests-dotnet-get-started-client.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes creating a .NET Framework console application using Visual Studio, a Windows-centric IDE, and provides step-by-step instructions tailored to Windows workflows. There are no examples or guidance for Linux users, such as using .NET Core/.NET 6+ (cross-platform), alternative editors (VS Code, JetBrains Rider), or command-line approaches for package management and project creation.
Recommendations
  • Add instructions for creating a .NET Core/.NET 6+ console application using the dotnet CLI, which works on Linux, macOS, and Windows.
  • Include examples for installing NuGet packages via the command line (dotnet add package Microsoft.Azure.Relay) instead of only through Visual Studio.
  • Mention and provide steps for using cross-platform editors like Visual Studio Code or JetBrains Rider.
  • Clarify that the code sample works on Linux and macOS as well, and provide any necessary platform-specific notes (e.g., prerequisites for .NET SDK installation).
  • Reorder or parallelize instructions so that Windows and Linux/macOS approaches are presented together, avoiding Windows-first bias.
GitHub Create Pull Request
Azure Relay Hybrid Connections - HTTP requests in .NET ...ay-hybrid-connections-http-requests-dotnet-get-started.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) and providing instructions that assume a Windows environment. There are no examples or guidance for Linux users, such as using cross-platform .NET development tools (e.g., VS Code, CLI) or running the applications on Linux. The tutorial does not mention Linux equivalents or provide parity for non-Windows platforms.
Recommendations
  • Include instructions for setting up the development environment on Linux, such as using .NET Core SDK and Visual Studio Code.
  • Provide examples for running the applications using the .NET CLI (dotnet run) instead of only referencing Visual Studio.
  • Clarify that the sample applications can be developed and executed on Linux and macOS, not just Windows.
  • Add troubleshooting or notes for platform-specific differences, if any.
  • Mention alternative editors (e.g., VS Code, JetBrains Rider) that are available cross-platform.
GitHub Create Pull Request
Azure Resource Manager Quickstart: Integrate Bicep with Azure Pipelines ...ource-manager/bicep/add-template-to-azure-pipelines.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for resource cleanup, but lists Azure CLI first. The pipeline YAML examples use 'ubuntu-latest' as the build agent, indicating Linux parity in CI/CD steps. However, in the Azure CLI YAML example, the inline script uses backticks (`) for line continuation, which is a PowerShell/Windows convention, not valid in bash (Linux). This may confuse Linux users and suggests a subtle Windows bias in scripting patterns.
Recommendations
  • Ensure all bash script examples use correct Linux line continuation (backslash \) instead of backtick (`).
  • Explicitly mention that Azure CLI commands are cross-platform and clarify which shell syntax is being used.
  • Provide clear separation or tabs for Windows (PowerShell) and Linux/macOS (bash) examples where applicable.
  • Review all inline script examples for shell-specific syntax and adjust to match the specified scriptType.
  • Continue listing Azure CLI examples first, but ensure parity and correctness for Linux users.
GitHub Create Pull Request
Azure Resource Manager Bicep functions - resources ...ure-resource-manager/bicep/bicep-functions-resource.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page provides both PowerShell and Azure CLI examples for discovering resource provider operations, but PowerShell is presented first and in greater detail. The only explicit command-line example for listing resource provider operations is a PowerShell cmdlet, with the Azure CLI example following. There are no Linux-specific tools or shell patterns shown, and no mention of Linux environments or considerations. The documentation does not provide parity in example ordering or depth between Windows/PowerShell and Linux/Azure CLI, which may subtly reinforce a Windows-centric workflow.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
  • Expand Azure CLI examples to match the detail and explanation given for PowerShell, including output formatting and filtering.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, include Bash or shell scripting examples for common resource queries.
  • Review other sections for implicit Windows-first language or assumptions and ensure Linux parity in all code samples and tool references.
GitHub Create Pull Request
Azure Resource Manager Data types in Bicep ...in/articles/azure-resource-manager/bicep/data-types.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page displays mild Windows bias by referencing PowerShell as the example CLI for Bicep deployments and describing its integer range limitations before mentioning alternatives. No Linux-specific examples or tools are referenced, and the only CLI mentioned is PowerShell, which is Windows-centric. There are no explicit Linux examples, nor is cross-platform parity addressed.
Recommendations
  • Include examples and notes for Linux/macOS users, such as using Azure CLI or Bash for deployments.
  • Mention cross-platform CLI tools (e.g., Azure CLI) alongside PowerShell when discussing deployment limitations.
  • Clarify that Bicep is supported on multiple platforms and provide links or instructions for Linux/macOS installation and usage.
  • If platform-specific limitations exist (e.g., integer range), provide equivalent details for Linux/macOS tools.
  • Add a section or callout highlighting cross-platform compatibility and best practices.
GitHub Create Pull Request
Azure Resource Manager Use Bicep to create a new resource group .../azure-resource-manager/bicep/create-resource-group.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files, but PowerShell (a Windows-centric tool) is always presented immediately after Azure CLI and with equal prominence. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or patterns. The documentation implicitly assumes PowerShell is a primary alternative to Azure CLI, which may not reflect the experience of Linux users.
Recommendations
  • Explicitly note that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux users.
  • Add Bash-specific examples or clarify that the Azure CLI examples are suitable for Bash and other Unix shells.
  • De-emphasize PowerShell as the only alternative to Azure CLI; mention that PowerShell is primarily used on Windows, while Azure CLI is more universal.
  • If PowerShell is included, consider placing Azure CLI examples first, and PowerShell second, or clarify their platform relevance.
  • Add a brief section or note about running Bicep deployments on Linux, including prerequisites and shell compatibility.
GitHub Create Pull Request
Azure Resource Manager Deploy Bicep files by using GitHub Actions .../azure-resource-manager/bicep/deploy-github-actions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for resource group creation and deletion, but consistently lists PowerShell as a primary tab alongside CLI, rather than Bash or Linux shell alternatives. No explicit Linux shell or Bash examples are given, and PowerShell (a Windows-centric tool) is presented as the only alternative to Azure CLI, which is cross-platform. There is no mention of Linux-specific tools or workflows, nor any guidance for Linux users beyond the use of Azure CLI. The workflow examples use 'ubuntu-latest' runners, which is positive for Linux parity, but the command-line instructions show a subtle Windows bias.
Recommendations
  • Add Bash examples for resource group creation and deletion, especially since Azure CLI is cross-platform and commonly used on Linux.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide explicit instructions for Linux users where appropriate.
  • Consider including a note or tab for Bash or Linux shell users, not just PowerShell and CLI.
  • Where PowerShell is mentioned, clarify its cross-platform availability, but avoid implying it is the default alternative to CLI for all users.
  • Review reusable content includes to ensure they do not assume Windows or PowerShell usage.
GitHub Create Pull Request
Azure Resource Manager Bicep modules .../main/articles/azure-resource-manager/bicep/modules.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias by referencing Azure PowerShell and the Azure portal as deployment tools before mentioning the Azure CLI and API. Additionally, it discusses embedding PowerShell scripts in Bicep modules, but does not mention Linux shell scripts or provide parity for Linux-specific tooling. There are no explicit Linux examples or references to Linux-native tools, and the only mention of path separators is to enforce cross-platform compatibility rather than to highlight Linux usage.
Recommendations
  • When listing deployment tools, mention Azure CLI before or alongside Azure PowerShell and the Azure portal to avoid Windows-first bias.
  • Explicitly mention support for embedding Linux shell scripts (e.g., Bash) in Bicep modules when discussing artifact embedding.
  • Provide examples or references for deploying Bicep modules using Linux environments and tools, such as Bash scripts or the Azure CLI on Linux.
  • Add a note or example demonstrating how Bicep works seamlessly on Linux, including integration with popular Linux editors and shells.
  • Ensure that documentation for file paths and tooling includes Linux-specific considerations and examples, not just cross-platform notes.
GitHub Create Pull Request
Azure Resource Manager Bicep logical operators ...cles/azure-resource-manager/bicep/operators-logical.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page shows a Windows bias by mentioning Azure PowerShell before Azure CLI when describing how to run Bicep examples. The initial instructions suggest using Azure CLI or Azure PowerShell, which are both available cross-platform, but PowerShell is traditionally associated with Windows. There are no explicit Linux-specific instructions, nor is there mention of Linux-native tools or shell patterns (e.g., Bash). No Linux-specific examples or parity checks are present.
Recommendations
  • Mention Azure CLI first, as it is more commonly used cross-platform, including on Linux and macOS.
  • Explicitly state that all examples can be run on Linux, macOS, and Windows using Azure CLI.
  • Include example commands for deploying Bicep files using Bash (Linux/macOS) and PowerShell (Windows), showing parity.
  • Add a note or section clarifying platform compatibility and providing links to installation instructions for Azure CLI and PowerShell on all major operating systems.
  • Avoid implying PowerShell is the default or preferred option unless justified by technical reasons.
GitHub Create Pull Request
Azure Resource Manager Use Bicep linter ...b/main/articles/azure-resource-manager/bicep/linter.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias by referencing Visual Studio Code (a tool most commonly associated with Windows, though cross-platform) and including a linter rule specifically for 'use-recent-az-powershell-version', which is a Windows-centric tool. There are no explicit Linux examples, nor are Linux-specific tools or shell commands mentioned. The CLI usage section is generic, but the absence of Linux shell examples or references to Bash/Zsh is notable.
Recommendations
  • Add explicit examples of using Bicep CLI and linter in Linux environments, such as Bash or Zsh command lines.
  • Mention cross-platform compatibility of Visual Studio Code and Bicep CLI, and provide instructions for installation and usage on Linux and macOS.
  • Balance references to PowerShell with equivalent Bash or shell scripting examples for common tasks.
  • Clarify that the linter and Bicep CLI work identically on Windows, Linux, and macOS, and provide troubleshooting tips for non-Windows platforms if relevant.
GitHub Create Pull Request
Azure Resource Manager Create Bicep files - Visual Studio ...ger/bicep/quickstart-create-bicep-use-visual-studio.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias by focusing exclusively on Visual Studio (a Windows-centric IDE) for Bicep authoring, listing Visual Studio as the primary tool in prerequisites and instructions, and providing PowerShell examples alongside Azure CLI. Although Azure CLI (cross-platform) is included for deployment and cleanup, the authoring workflow is centered on Visual Studio, which is not natively available on Linux. The mention of Visual Studio Code as an alternative is brief and relegated to a 'Next steps' section, rather than being presented as an equal option throughout the guide.
Recommendations
  • Present Visual Studio Code as a first-class option for Bicep authoring, including direct links and instructions in the main workflow, not just as a next step.
  • Add explicit Linux/macOS parity notes in the prerequisites, clarifying that Visual Studio is Windows-only and recommending VS Code for non-Windows users.
  • Ensure all command-line examples (Azure CLI and PowerShell) are presented with equal prominence, possibly defaulting to Azure CLI (cross-platform) and listing PowerShell as an alternative.
  • Consider a dedicated section or parallel instructions for Linux/macOS users, highlighting cross-platform tools and workflows.
  • Avoid language that implies Visual Studio is the default or preferred environment for Bicep development; instead, present both VS and VS Code as valid choices.
GitHub Create Pull Request
Azure Resource Manager Create Bicep files with Visual Studio Code ...les/azure-resource-manager/bicep/visual-studio-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias by mentioning Azure PowerShell alongside Azure CLI in environment setup and providing both Azure CLI and Azure PowerShell examples for resource ID retrieval, with PowerShell examples presented immediately after CLI. There is no explicit Linux example or mention of Linux-specific tools, and Windows keyboard shortcuts are referenced before Mac equivalents. However, most instructions are cross-platform due to Visual Studio Code's nature, and Azure CLI is included, which is platform-neutral.
Recommendations
  • Ensure that Linux and macOS are explicitly mentioned as supported platforms for Visual Studio Code and Bicep extension.
  • Provide Linux/macOS-specific instructions or screenshots where relevant (e.g., keyboard shortcuts, installation steps).
  • When listing command-line examples, alternate the order or present Azure CLI (platform-neutral) before PowerShell (Windows-centric), or clarify that both are available on all platforms.
  • Include troubleshooting tips or notes for Linux/macOS users, such as file permissions or common issues.
  • Reference Linux tools or shell environments (e.g., Bash) where appropriate, and avoid implying PowerShell is the default or preferred option.
GitHub Create Pull Request
Azure Resource Manager Create and publish Azure Managed Application in service catalog ...er/managed-applications/publish-service-catalog-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents both Azure PowerShell and Azure CLI examples for all command-line steps, but consistently lists PowerShell (a Windows-centric tool) before CLI (cross-platform). It also refers to opening a 'PowerShell terminal' in Visual Studio Code, which is a Windows-specific pattern, while the CLI instructions mention Bash more generically. There are no Linux-specific tools or shell patterns (e.g., zsh, Linux file utilities) mentioned, and the use of PowerShell splatting is explained in detail, while Bash line continuation is only briefly noted. No steps are missing for Linux users, but the ordering and depth of explanation favor Windows/PowerShell.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to reflect cross-platform parity.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and suggest Bash or other shells for Linux/macOS users.
  • Provide equivalent explanations for Bash scripting features (e.g., variable assignment, line continuation) as is done for PowerShell splatting.
  • Include notes or tips for Linux/macOS users, such as using native zip utilities or shell commands.
  • Clarify that Visual Studio Code is cross-platform and that terminals can be Bash, zsh, or PowerShell depending on OS.
GitHub Create Pull Request
Azure Resource Manager Move Microsoft.Resources resources to new region ...manager/management/microsoft-resources-move-regions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently uses Windows-style file paths (e.g., c:\export) in both Azure PowerShell and Azure CLI examples, and does not provide Linux/macOS equivalents. This may confuse or hinder users on non-Windows platforms. Additionally, references to deployment steps and exported templates link to PowerShell-specific instructions, with no mention of Bash, Linux, or cross-platform alternatives.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/export) alongside Windows paths in all CLI and PowerShell commands.
  • Explicitly state that Azure CLI is cross-platform and provide Bash shell examples where appropriate.
  • Add links to documentation for deploying templates using Bash or Azure CLI on Linux/macOS, not just PowerShell.
  • Where file paths are referenced, clarify platform differences and provide guidance for users on non-Windows systems.
GitHub Create Pull Request
Azure Resource Manager Manage Azure resources by using Azure CLI ...re-resource-manager/management/manage-resources-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
While the main Azure CLI examples use bash-like syntax compatible with both Windows and Linux, there is a notable Windows bias in the documentation. The only linked template authoring tutorial is 'Quickstart: Create ARM templates with Visual Studio Code', which explicitly references PowerShell tabs and does not mention Linux or bash alternatives. No Linux-specific tools or editors (such as VS Code on Linux, nano, vim, or bash scripting) are mentioned, and the documentation does not clarify cross-platform compatibility for the examples. The documentation assumes familiarity with Windows-first patterns and does not provide parity for Linux users in referenced tutorials.
Recommendations
  • Add explicit notes clarifying that Azure CLI examples work on both Windows (PowerShell, CMD) and Linux (bash, zsh).
  • Provide links to Linux/bash-specific tutorials for ARM template authoring and deployment.
  • Ensure referenced tutorials (such as the Quickstart) include Linux/bash tabs or examples, not just PowerShell.
  • Mention cross-platform editors (e.g., VS Code on Linux, nano, vim) when discussing template authoring.
  • Where PowerShell is referenced, provide equivalent bash or shell examples and links.
  • Review all external links to ensure Linux parity in guidance and examples.
GitHub Create Pull Request
Azure Resource Manager Set up preview features in Azure subscription .../azure-resource-manager/management/preview-features.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion alongside CLI in every example can suggest a Windows bias. Additionally, the ordering of examples consistently places Azure PowerShell immediately after Azure CLI, and the documentation metadata includes 'devx-track-azurepowershell' before 'devx-track-azurecli', indicating a possible preference for Windows-centric tools. There are no explicit Linux-only examples, nor are Linux-specific patterns or shell commands (e.g., Bash, zsh) mentioned. REST API is referenced only in 'Next steps', not in the main workflow.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for common tasks like listing, registering, and unregistering features.
  • Clarify that Azure CLI commands work identically across Windows, Linux, and macOS, and highlight this cross-platform compatibility.
  • Consider reordering examples to present Azure CLI before Azure PowerShell, or group cross-platform tools together, to avoid implicit Windows-first bias.
  • Include REST API examples in the main workflow, not just in 'Next steps', to provide parity for users who prefer direct API calls.
  • Add notes or links for installing and using Azure CLI and PowerShell on Linux and macOS, ensuring users know these tools are available cross-platform.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid custom topics to another region ...ment/relocation/relocation-event-grid-custom-topics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses the Azure portal (GUI) for all steps and does not provide any command-line examples. There is no mention of PowerShell or Windows-specific tools, but the absence of CLI instructions (such as Azure CLI or Bash scripts) means Linux users are not given parity. The documentation implicitly favors Windows users by relying solely on GUI workflows, which are more commonly used on Windows, and does not address Linux or cross-platform command-line usage.
Recommendations
  • Add Azure CLI examples for all major steps (exporting templates, deploying resources, deleting topics/resource groups) alongside portal instructions.
  • Explicitly mention that all steps can be performed using CLI tools on Linux, macOS, and Windows.
  • Provide sample Bash scripts for automation of the relocation process.
  • Include links to relevant Azure CLI documentation for Event Grid resource management.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., file paths, editors).
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid system topics to another region ...ment/relocation/relocation-event-grid-system-topics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses the Azure portal UI for all instructions and screenshots, which is most commonly accessed from Windows environments. There are no examples or instructions for performing these operations using cross-platform command-line tools such as Azure CLI, PowerShell, or ARM templates via command line. No Linux-specific guidance or parity is provided, and all steps assume a graphical interface, which may not be available or preferred in Linux environments.
Recommendations
  • Add step-by-step instructions for relocating Event Grid system topics using Azure CLI, which is cross-platform and widely used on Linux.
  • Include equivalent examples using PowerShell for users who prefer scripting, but ensure Azure CLI examples are presented first or alongside.
  • Provide guidance for editing and deploying ARM templates from the command line (e.g., using az deployment group create) rather than relying solely on the portal.
  • Mention that all operations can be performed from Linux, macOS, or Windows, and clarify any platform-specific prerequisites.
  • Include screenshots or terminal output examples from Linux environments to demonstrate parity.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Event Grid domains to another region ...management/relocation/relocation-event-grid-domains.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses the Azure portal UI for all steps, which is most commonly accessed from Windows environments. There are no CLI, PowerShell, or Bash examples provided, and no mention of Linux-specific tools or workflows. The lack of command-line instructions or cross-platform tooling (such as Azure CLI or ARM templates via Bash) means Linux users are not given parity in guidance.
Recommendations
  • Add Azure CLI examples for exporting, editing, and deploying ARM templates, covering all major steps.
  • Include Bash shell commands for file operations (e.g., unzipping, editing JSON) alongside generic editor instructions.
  • Explicitly mention that the Azure portal is accessible from any OS, and provide links to CLI documentation for cross-platform users.
  • Provide PowerShell examples only if paired with equivalent Bash/Azure CLI instructions.
  • Add a section comparing portal, CLI, and PowerShell workflows, highlighting cross-platform options.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Virtual Machine Scale Sets to another region ...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently references the Azure portal and PowerShell as primary methods for exporting and deploying templates, with no explicit mention or examples for Linux-specific tools or workflows. There are no CLI (bash) or Linux-native instructions, and the use of screenshots and step-by-step guides are tailored to the Azure portal, which is more commonly used on Windows. The mention of PowerShell as an IAC tool is not balanced by Linux shell or scripting alternatives.
Recommendations
  • Add explicit Azure CLI (bash) examples for each step where PowerShell or portal instructions are given.
  • Include screenshots or instructions for using the Azure CLI on Linux/macOS, not just the portal.
  • Mention Linux-native tools (such as bash scripting, jq, etc.) where template editing or resource validation is discussed.
  • Ensure that all automation steps (export, edit, deploy) have both PowerShell and Azure CLI (bash) equivalents.
  • Clarify that all steps can be performed on Linux, and provide links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Azure Resource Manager Manage personal data associated with Azure Resource Manager ...e-manager/management/resource-manager-personal-data.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation consistently lists Windows PowerShell commands before cross-platform Azure CLI equivalents in each section, and explicitly references PowerShell modules. This ordering and emphasis may suggest a Windows-centric approach, potentially making Linux users feel secondary or less supported.
Recommendations
  • Alternate the order of examples, listing Azure CLI commands before PowerShell commands in some sections.
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide example command blocks for both Azure CLI and PowerShell, clarifying platform applicability.
  • Include brief notes or links for Linux/macOS users on installing and using Azure CLI.
  • Avoid implying PowerShell is the primary or default tool for resource management.
GitHub Create Pull Request
Azure Resource Manager Label mission-critical workloads ...ce-manager/management/tag-mission-critical-workload.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation lists Azure PowerShell before Azure CLI in the 'How to apply Azure tags' section, which may suggest a Windows-first approach. PowerShell is a Windows-native tool, while CLI is cross-platform and more common on Linux. No explicit Linux examples or Linux-specific tools are provided, and the ordering may reinforce a Windows-centric workflow.
Recommendations
  • List Azure CLI before Azure PowerShell to reflect cross-platform parity and the prevalence of CLI usage on Linux.
  • Include explicit examples for both Azure CLI and PowerShell, clarifying their cross-platform compatibility.
  • Add a note highlighting that Azure CLI is available and commonly used on Linux and macOS, not just Windows.
  • Consider providing shell script examples (bash/zsh) for Linux users where automation is discussed.
  • Review other sections for implicit Windows-centric language or assumptions, and ensure equal coverage for Linux environments.
GitHub Create Pull Request
Azure Resource Manager Best practices for templates ...les/azure-resource-manager/templates/best-practices.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits Windows bias primarily in the section discussing parameter naming conflicts, where only PowerShell (Windows-centric) deployment commands and cmdlets are referenced. Additionally, in the resources section, Windows VM connection methods are listed before Linux equivalents, and more links are provided for Windows-specific connection scenarios. No Linux shell (bash/CLI) deployment examples or references to Linux-native tooling are present.
Recommendations
  • Include Azure CLI (bash) examples alongside or before PowerShell examples when discussing deployment commands and parameter naming conflicts.
  • Reference Linux-native tools and workflows (e.g., Azure CLI, bash scripts) in addition to Windows/PowerShell tools.
  • Ensure that connection instructions for Linux VMs are given equal prominence and detail as those for Windows VMs.
  • Where possible, provide cross-platform guidance and examples, making it clear how best practices apply regardless of OS or tool preference.
GitHub Create Pull Request
Azure Resource Manager Deploy templates with Cloud Shell ...azure-resource-manager/templates/deploy-cloud-shell.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples for deploying ARM templates in Cloud Shell, but PowerShell is given equal or slightly more prominence than Bash. The 'Next steps' section lists PowerShell resources after CLI, but the overall structure and screenshots frequently mention switching between Bash and PowerShell, which may imply parity but also reinforces PowerShell as a first-class option. There are no Linux-specific tools or patterns mentioned, and the examples do not address Linux-specific nuances or alternatives beyond Bash/CLI.
Recommendations
  • Explicitly mention that Azure CLI works seamlessly in both Bash (Linux) and PowerShell environments, and clarify any differences if they exist.
  • Add notes or examples for Linux users who may want to use native shell scripting or other Linux tools in conjunction with Azure CLI.
  • Include links to Linux-specific documentation or troubleshooting guides for Cloud Shell.
  • Ensure that Bash/Azure CLI examples are presented first, or alternate the order to avoid implicit prioritization of PowerShell.
  • Highlight any platform-specific considerations (e.g., file paths, permissions) that may affect Linux users.
GitHub Create Pull Request
Azure Resource Manager Deploy resources to subscription ...e-resource-manager/templates/deploy-to-subscription.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment commands, but consistently lists PowerShell examples immediately after CLI, and references PowerShell-specific modules and aliases. There is no explicit mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments (such as shell scripting or environment differences). The documentation assumes parity between CLI and PowerShell, but PowerShell is a Windows-centric tool, and its prominence may suggest a Windows bias.
Recommendations
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS), and provide Bash-specific examples or notes where relevant.
  • Clarify that PowerShell examples are for both Windows PowerShell and PowerShell Core (which runs on Linux/macOS), or provide Bash equivalents for common tasks.
  • Where scripting is shown (e.g., variable assignment), provide both Bash and PowerShell syntax to ensure Linux users are equally supported.
  • Add a short section or note about using Azure CLI in Bash/Linux environments, including tips for handling parameters, quoting, and environment variables.
  • Consider listing CLI (Bash) examples before PowerShell to avoid implicit Windows-first ordering.
GitHub Create Pull Request
Azure Resource Manager Use Azure Resource Manager templates to deploy resources to resource groups ...resource-manager/templates/deploy-to-resource-group.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment operations. However, PowerShell examples are presented before CLI examples in several sections, and PowerShell is given its own dedicated tab, which can be perceived as a Windows-first approach. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux users (such as shell scripting or use of native Linux tools). The CLI examples are generic and do not reference Bash or Linux-specific conventions. There is also no mention of cross-platform compatibility or guidance for Linux users.
Recommendations
  • Alternate the order of Azure CLI and PowerShell examples so that CLI (cross-platform) is shown first in some sections.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide Bash-specific examples where appropriate.
  • Add notes or examples for running deployments from Bash scripts or Linux environments, highlighting any differences or considerations.
  • Include references to Linux-native tools or environments (such as Bash, zsh, or Cloud Shell on Linux) where relevant.
  • Ensure that documentation language is inclusive of all platforms, not assuming PowerShell as the default or primary method.
GitHub Create Pull Request
Azure Resource Manager Deploy resources to tenant ...s/azure-resource-manager/templates/deploy-to-tenant.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias. In the 'Required access' section, the PowerShell example (New-AzRoleAssignment) is presented before the Azure CLI example, which may subtly prioritize Windows tooling. The page also includes dedicated tabs for both Azure CLI and PowerShell deployment commands, but does not provide explicit Linux shell (bash) or cross-platform scripting examples, nor does it mention platform-specific considerations for Linux users. There are no references to Linux-native tools or patterns, and no explicit mention of running these commands from Linux environments.
Recommendations
  • Ensure that Azure CLI examples (which are cross-platform) are presented before PowerShell examples, or in parallel, to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample bash scripts or usage from Linux terminals where appropriate.
  • Add notes or examples for running deployments from Linux environments, such as using bash or zsh, and clarify any platform-specific differences (if any).
  • Consider including a section or tip highlighting cross-platform compatibility and recommending Azure CLI for users on Linux or macOS.
  • Avoid using PowerShell-specific syntax (such as backticks for line continuation) in examples unless also providing bash equivalents.
GitHub Create Pull Request
Azure Resource Manager Outputs in ARM templates ...n/articles/azure-resource-manager/templates/outputs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for retrieving output values, but PowerShell is presented first, which may suggest a Windows-first bias. There are no Linux-specific tools or shell examples (e.g., Bash), nor is there mention of Linux environments or patterns. The examples and instructions are otherwise platform-neutral, focusing on ARM template syntax.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more commonly used in Linux environments.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily used on Windows (though available on Linux).
  • Add Bash shell examples for parsing output values, demonstrating usage in a native Linux environment.
  • Include a note or section on how to retrieve output values using REST API or SDKs, which are platform-agnostic.
  • Ensure parity in troubleshooting or advanced usage examples for both Windows and Linux users.
GitHub Create Pull Request
Azure Resource Manager Use linked and nested templates to deploy Azure resources ...s/azure-resource-manager/templates/linked-templates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias. PowerShell examples are consistently presented before Azure CLI (Bash/Linux) equivalents, and PowerShell is referenced in metadata and tutorial links. There are no Linux-specific tools or patterns, but the ordering and prominence of Windows/PowerShell may suggest a preference for Windows users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first in some sections.
  • Add explicit notes that both Azure CLI and PowerShell are cross-platform and available on Windows, Linux, and macOS.
  • Include Bash-specific tips or troubleshooting where relevant, especially for file paths, permissions, or shell scripting.
  • Review metadata and tutorial links to ensure equal visibility for Azure CLI and Bash workflows.
  • Consider adding a short section or callout for deploying from Linux environments, highlighting any differences or best practices.
GitHub Create Pull Request
Azure Resource Manager Set resource location in ARM template .../azure-resource-manager/templates/resource-location.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for querying resource locations, but PowerShell is presented first, which may subtly prioritize Windows users. There is no explicit mention of Linux-specific tools or shell environments, and the CLI example is generic, not tailored to Linux shells. No Linux-exclusive example or guidance is given.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit Windows prioritization.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific guidance if needed (e.g., bash syntax).
  • Include example output or troubleshooting notes for common Linux shell environments.
  • Reference Linux-specific tools or workflows where relevant, such as using jq for JSON parsing in bash.
  • Ensure parity in documentation language, avoiding terms or patterns that are Windows-centric unless necessary.
GitHub Create Pull Request
Azure Resource Manager Understand the structure and syntax of ARM templates ...in/articles/azure-resource-manager/templates/syntax.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-centric tools and workflows before their Linux equivalents, and omitting explicit Linux examples. Specifically, Visual Studio and Visual Studio Code are mentioned as editors for ARM templates, with no mention of Linux-native editors. Additionally, deployment instructions reference Azure PowerShell and Azure CLI, but do not provide Linux-specific command-line examples or mention Bash/Shell usage. There are no explicit examples or guidance tailored for Linux users.
Recommendations
  • Include references to Linux-native editors (e.g., Vim, Emacs, nano) and provide guidance on configuring them for ARM template development.
  • Provide explicit Bash/Shell examples for deploying ARM templates using Azure CLI, including command syntax and file handling on Linux.
  • Mention cross-platform compatibility for tools like Visual Studio Code, and clarify that instructions apply equally to Linux, macOS, and Windows.
  • Add notes or examples for handling JSONC files and comments in editors commonly used on Linux.
  • Ensure that deployment instructions and troubleshooting tips address both Windows and Linux environments, including file path conventions and permission issues.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Add template functions to your Azure Resource Manager template ...e-manager/templates/template-tutorial-add-functions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell deployment instructions before Azure CLI instructions, and by referencing Azure PowerShell prominently in the prerequisites. Although both PowerShell and CLI examples are provided, there is no explicit mention of Linux or macOS environments, nor are there any Linux-specific patterns or shell examples (e.g., Bash). The use of Visual Studio Code is cross-platform, but the overall flow assumes familiarity with Windows-centric tools and ordering.
Recommendations
  • Explicitly mention Linux/macOS compatibility for both Azure CLI and Visual Studio Code.
  • Provide Bash shell examples for Azure CLI commands, including variable assignment and file paths.
  • Alternate the order of PowerShell and CLI instructions, or present CLI first to avoid implicit Windows-first bias.
  • Add a note clarifying that Azure CLI works natively on Linux/macOS and show how to install it on those platforms.
  • Reference Linux-native editors (e.g., Vim, nano) as alternatives to Visual Studio Code for template editing.
GitHub Create Pull Request
Azure Resource Manager Create multiple resource instances ...mplates/template-tutorial-create-multiple-instances.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is listed as the sole prerequisite, which is cross-platform but often associated with Windows. In deployment instructions, PowerShell is mentioned before Bash/CLI, and PowerShell examples are presented alongside CLI examples, but the tab order and narrative often lead with PowerShell. The Azure portal instructions use Windows-style UI terms (e.g., 'File > Open File'), and the clean-up steps are portal-centric, which is platform-neutral but may feel more familiar to Windows users.
Recommendations
  • Explicitly mention that Visual Studio Code is available on Linux and macOS, or list alternative editors (e.g., Vim, nano) for Linux users.
  • Alternate the order of CLI and PowerShell tabs/examples, or default to CLI (which is more platform-agnostic) in the narrative.
  • Include Linux-specific instructions for file operations (e.g., using nano, vim, or command-line tools to open and edit files).
  • Clarify that the Azure portal and Cloud Shell are accessible from any OS, and highlight that Bash/CLI is available for Linux/macOS users.
  • Add a note that all steps can be performed on Linux, macOS, or Windows, and provide links to Linux/macOS setup guides if relevant.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Add variables to your Azure Resource Manager template ...e-manager/templates/template-tutorial-add-variables.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI instructions in the deployment section. PowerShell is a Windows-centric tool, and its placement before the cross-platform Azure CLI may signal a preference for Windows users. While both PowerShell and CLI examples are provided, there is no explicit mention of Linux or macOS environments, nor are there any Linux-specific instructions or screenshots.
Recommendations
  • Alternate the order of deployment instructions, sometimes presenting Azure CLI before PowerShell to avoid implicit prioritization.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation links for all platforms.
  • Include notes or screenshots showing deployment from a Linux or macOS terminal.
  • Reference Linux-native editors (such as Vim, Nano) alongside Visual Studio Code, or clarify that VS Code is cross-platform.
  • Add troubleshooting tips or command-line differences for Linux/macOS users where relevant.
GitHub Create Pull Request
Azure Resource Manager Request disallowed by policy error ...ubleshooting/error-policy-requestdisallowedbypolicy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for troubleshooting the 'RequestDisallowedByPolicy' error, but the PowerShell section is given equal prominence and detail, despite PowerShell being primarily a Windows-centric tool. There is no mention of Linux-specific shell patterns (e.g., Bash), nor are there examples tailored for Linux users. The CLI examples are generic, but the PowerShell examples are more elaborate and include advanced usage (e.g., ConvertTo-Json), which may reinforce a Windows bias.
Recommendations
  • Add Bash-specific examples or notes for Linux users, especially for parsing JSON output from Azure CLI.
  • Clarify that Azure CLI commands work cross-platform and highlight any differences in output formatting or usage on Linux/macOS.
  • Reduce the emphasis on PowerShell-specific advanced features unless a Linux shell equivalent is also provided.
  • Consider adding troubleshooting steps or examples using common Linux tools (e.g., jq for JSON parsing) to improve parity.
GitHub Create Pull Request
Azure Vmware Integrate Microsoft Defender for Cloud with Azure VMware Solution ...in/articles/azure-vmware/azure-security-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing a security rule example and tip that specifically targets Windows server sign-in failures, without offering equivalent examples for Linux systems. There are no Linux-specific queries, scenarios, or instructions, and the only explicit operating system reference is to Windows. This suggests an assumption that users are primarily managing Windows VMs, despite Azure VMware Solution supporting both Windows and Linux guests.
Recommendations
  • Include Linux-specific security rule examples, such as detecting failed SSH login attempts or monitoring Linux audit logs.
  • Provide sample queries for common Linux security events (e.g., authentication failures, sudo usage, file integrity changes).
  • Add guidance or tips for both Windows and Linux VMs when describing analytics rules and incident response.
  • Explicitly mention Linux support in steps where operating system selection is required, and clarify any differences in script execution or agent installation.
  • Balance examples and screenshots to represent both Windows and Linux environments.
GitHub Create Pull Request
Azure Vmware Move Azure VMware Solution subscription to another subscription ...ain/articles/azure-vmware/move-ea-csp-subscriptions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides a single command-line example ('ping') and refers to 'command prompt' without specifying platform. The screenshots and instructions implicitly assume Windows usage, as 'command prompt' is a Windows term and no Linux or cross-platform alternatives (e.g., Bash, Terminal) are mentioned. No PowerShell-specific commands or Windows-only tools are referenced, but the lack of Linux parity is evident.
Recommendations
  • Explicitly mention that 'ping' can be run from Windows Command Prompt, PowerShell, or Linux/macOS Terminal.
  • Provide screenshots or instructions for running 'ping' on Linux/macOS (e.g., using Terminal).
  • Use platform-neutral language such as 'open a terminal' instead of 'command prompt'.
  • If scripts or tools are referenced, clarify their cross-platform compatibility or provide equivalents for Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Resource provider registration errors ...er/troubleshooting/error-register-resource-provider.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides full example parity between Azure CLI and Azure PowerShell for resource provider registration tasks. However, the PowerShell section is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows-centric tool (though cross-platform now, it is still more common on Windows). There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native patterns or tools. The ordering places Azure CLI first, which is more cross-platform, but the inclusion and detail of PowerShell examples may signal a slight Windows bias.
Recommendations
  • Add explicit Bash shell examples using Azure CLI to demonstrate usage in native Linux environments.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and can be run from Bash, PowerShell, or CMD.
  • Consider mentioning that PowerShell Core is available cross-platform, but that Bash is the default shell on most Linux systems.
  • Include troubleshooting steps or notes relevant to Linux users, such as installation instructions for Azure CLI on Linux.
  • If possible, provide a short section or note on how to perform these tasks using REST API calls or SDKs, which are platform-agnostic.
GitHub Create Pull Request
Azure Signalr Authorize requests to Azure SignalR Service resources with Microsoft Entra managed identities ...re-signalr/signalr-howto-authorize-managed-identity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides configuration and code examples for Azure SignalR Service authorization using managed identities, but it implicitly favors Windows environments. Application settings examples reference the Azure portal (Windows-centric) and local development via Visual Studio, Azure CLI, and Azure PowerShell, with no explicit Linux shell or tool examples. There are no Linux-specific instructions or parity for configuring managed identities or accessing environment variables, and the order of examples and tool mentions (Visual Studio, Azure CLI, Azure PowerShell) suggests a Windows-first approach.
Recommendations
  • Add explicit Linux shell examples for configuring environment variables and application settings, such as using bash or zsh.
  • Include instructions for using Linux-native tools (e.g., vim, nano, or code editors) to edit local.settings.json.
  • Mention Linux equivalents for Azure CLI usage and clarify cross-platform compatibility.
  • Provide parity in examples for both Windows and Linux environments, including authentication flows and troubleshooting steps.
  • Explicitly state that the instructions apply to both Windows and Linux, and highlight any platform-specific differences.
GitHub Create Pull Request
Azure Signalr Quickstart: Create an Azure SignalR Service - Bicep ...nalr/signalr-quickstart-azure-signalr-service-bicep.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured equally alongside CLI, and there is no explicit mention of Linux-specific tools or patterns. The use of PowerShell (which is traditionally associated with Windows) and the lack of Linux-specific shell examples (such as Bash) or explicit Linux instructions may indicate a mild Windows bias, especially for users unfamiliar with PowerShell or working primarily on Linux systems.
Recommendations
  • Add explicit Bash shell examples for all CLI commands to demonstrate usage on Linux and macOS.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and provide guidance for running them in Bash or other Linux shells.
  • Mention installation and usage of Azure CLI on Linux systems in the prerequisites.
  • Consider including screenshots or instructions for Linux terminal environments where relevant.
  • If PowerShell is included, note that PowerShell Core is cross-platform, but clarify differences if any exist for Linux users.
GitHub Create Pull Request
Azure Vmware Enable guest management and install extensions on Arc-enabled VMs ...n/articles/azure-vmware/arc-enable-guest-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing VMware Tools (which is most commonly associated with Windows VM management), and does not provide any Linux-specific guidance or examples. There are no Linux command-line examples, nor is there mention of Linux tools or patterns for enabling guest management or installing extensions. The steps and prerequisites are generic but implicitly assume Windows environments, especially in the context of administrator credentials and VMware Tools.
Recommendations
  • Explicitly mention support for Linux VMs and clarify any differences in guest management enablement for Linux operating systems.
  • Provide Linux-specific examples, such as using SSH for authentication or managing extensions on Linux VMs.
  • Reference Linux equivalents to VMware Tools (e.g., open-vm-tools) and include installation or verification steps for Linux guests.
  • Include command-line examples for Linux environments, such as Bash scripts or Linux CLI usage, alongside Azure CLI commands.
  • Clarify any OS-specific requirements or troubleshooting steps for Linux VMs in the prerequisites and enablement sections.
GitHub Create Pull Request
Azure Vmware Architecture - Integrate an Azure VMware Solution deployment in a hub and spoke architecture ...in/articles/azure-vmware/architecture-hub-and-spoke.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-based jump boxes (Windows 10 or Windows Server) for accessing Azure VMware Solution environments, without mentioning Linux alternatives. There are no examples or guidance for deploying or using Linux VMs as jump boxes, nor is there mention of Linux tools or SSH-based workflows for management. The documentation also refers to Active Directory domain controllers for identity and DNS, which are typically Windows-based, and does not discuss Linux-based identity solutions.
Recommendations
  • Include examples and guidance for deploying Linux-based jump boxes (e.g., Ubuntu or CentOS VMs) in the shared service subnet, and describe how to access Azure VMware Solution using SSH.
  • Mention Linux-based DNS and identity solutions (such as Samba/Bind for DNS and identity) as alternatives or supplements to Windows Active Directory.
  • Provide parity in instructions for both RDP (Windows) and SSH (Linux) access methods when describing connectivity and security practices.
  • Explicitly state that both Windows and Linux VMs can be used as jump boxes, and provide configuration steps for each.
  • Reference Linux tools and patterns (such as OpenSSH, iptables, etc.) where relevant in network and security considerations.
GitHub Create Pull Request
Azure Vmware Deploy Bitnami virtual appliances ...articles/azure-vmware/bitnami-appliances-deployment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates Windows bias by providing instructions for connecting to the VM via RDP and linking only to Windows VM connection documentation, without mentioning Linux alternatives (e.g., SSH). The initial access pattern assumes a Windows environment and does not offer parity for Linux users. Subsequent steps for configuring the appliance use Linux commands, but the initial VM access is Windows-centric.
Recommendations
  • Include instructions for connecting to the VM using SSH from Linux/macOS clients, alongside the RDP/Windows method.
  • Link to Azure documentation for connecting to Linux VMs, not just Windows VMs.
  • When referencing VM connection, mention both RDP (for Windows) and SSH (for Linux/macOS) options.
  • Ensure that prerequisites and steps do not assume a Windows-only environment, and clarify cross-platform compatibility.
GitHub Create Pull Request
Backup Back Up Azure VMs with the Enhanced Policy ...in/articles/backup/backup-azure-vms-enhanced-policy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides detailed PowerShell examples and step-by-step instructions before presenting Azure CLI commands. PowerShell, which is primarily a Windows-centric tool, is given more coverage, with multiple code blocks and explanations. The CLI section is shorter and lacks the depth and context provided in the PowerShell section. There are no Linux-specific shell examples (e.g., bash), and no mention of Linux tools or patterns. The documentation implicitly assumes familiarity with PowerShell, which may disadvantage Linux users.
Recommendations
  • Provide bash-specific examples for Azure CLI commands, including variable usage and output parsing, to help Linux users.
  • Balance the depth of explanation between PowerShell and CLI sections, ensuring CLI instructions are as detailed as PowerShell ones.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide tips for Linux environments (e.g., jq for JSON parsing, use of environment variables).
  • Add a section or notes on how to perform backup policy management using REST API with curl, which is common on Linux.
  • Avoid assuming PowerShell as the default scripting environment; clarify tool parity and platform support in introductory notes.
GitHub Create Pull Request
Backup Tutorial - Configure vaulted backup for Azure Blobs using Azure Backup ...main/articles/backup/blob-backup-configure-tutorial.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell as the first method for restoring Azure Blobs, ahead of Azure CLI and REST API. This ordering may suggest a preference for Windows-centric tooling. There are no explicit Linux examples, nor is there mention of Linux-specific tools or shell commands, but Azure CLI is referenced, which is cross-platform.
Recommendations
  • Reorder related content to list Azure CLI before Azure PowerShell, or present both equally to avoid perceived prioritization.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Provide example commands for both Azure PowerShell and Azure CLI in the main tutorial, highlighting cross-platform usage.
  • Add a note clarifying that all operations can be performed from Linux environments using Azure CLI or REST API.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure Backup ...ob/main/articles/backup/blob-backup-configure-quick.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a restore method before Azure CLI and REST API, and by referencing PowerShell-specific instructions. There is no explicit mention of Linux-specific tools or parity in command-line examples, and PowerShell (primarily a Windows tool) is highlighted before CLI (cross-platform).
Recommendations
  • List Azure CLI before Azure PowerShell in all instructions and links, as CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI instructions are suitable for Linux and macOS users.
  • Provide example commands for both Azure CLI and PowerShell side-by-side where applicable.
  • Add a note clarifying platform compatibility for each tool (e.g., PowerShell is available on Linux, but CLI is preferred for Linux users).
  • Ensure that any referenced scripts or automation examples include both PowerShell and Bash/CLI versions.
GitHub Create Pull Request
Bastion VNet peering and Azure Bastion architecture .../azure-docs/blob/main/articles/bastion/vnet-peering.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows virtual machine creation first and exclusively in the deployment overview, and by linking only to Windows-specific VM creation instructions. There are no Linux VM examples or links to Linux VM documentation, which may make it less accessible for users working with Linux-based environments.
Recommendations
  • Include parallel instructions and links for creating Linux virtual machines alongside Windows VM instructions.
  • Reference both Windows and Linux VM connection guides when describing how to connect via Azure Bastion.
  • Ensure examples and walkthroughs mention both operating systems to provide parity and inclusivity for cross-platform users.
GitHub Create Pull Request
Bastion Choose the right Azure Bastion SKU to meet your needs ...s/blob/main/articles/bastion/bastion-sku-comparison.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation presents VM connectivity features with Windows RDP listed before Linux SSH, and Windows RDP/SSH before Linux RDP/SSH. There are no platform-specific usage examples, but the feature tables and capacity metrics consistently mention Windows (RDP) before Linux (SSH), and do not provide parity in example detail or ordering. There is no mention of Linux-specific tools or workflows, and Linux RDP connectivity is only available in higher SKUs, while Windows RDP is available in all SKUs.
Recommendations
  • Present Linux and Windows features in parallel, alternating order or grouping by protocol rather than OS.
  • Provide explicit Linux usage examples (e.g., SSH, RDP from Linux clients) alongside Windows examples.
  • Mention Linux-native tools and workflows (such as using Azure CLI from Linux, or Linux RDP clients) where relevant.
  • Clarify feature availability for Linux and Windows equally, and explain any differences in support (e.g., why Linux RDP is only available in Standard/Premium SKUs).
  • Ensure that documentation links and next steps include Linux-specific guides or tutorials.
GitHub Create Pull Request
Bastion Enable remote work by using Azure Bastion ...cs/blob/main/articles/bastion/work-remotely-support.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as a primary configuration method before Azure CLI, and by not providing explicit Linux-centric examples or mentioning Linux tools. The focus on RDP (a Windows protocol) in the context of remote access also subtly prioritizes Windows scenarios, even though SSH (used for Linux) is mentioned. There are no explicit Linux command-line examples or references to Linux remote management tools.
Recommendations
  • Add explicit Linux-centric examples, such as using SSH from a Linux terminal to connect via Azure Bastion.
  • Mention Linux remote management tools (e.g., OpenSSH, native terminal commands) alongside PowerShell.
  • Ensure that Azure CLI (which is cross-platform) is listed before or alongside PowerShell in configuration instructions.
  • Include screenshots or walkthroughs for both Windows and Linux users in the portal and command-line sections.
  • Clarify that Azure Bastion supports both RDP (Windows) and SSH (Linux) equally, with examples for each.
GitHub Create Pull Request
Bastion Troubleshoot Azure Bastion .../azure-docs/blob/main/articles/bastion/troubleshoot.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides a specific troubleshooting section for Windows domain-joined VMs, but does not offer equivalent guidance for Linux VMs (e.g., troubleshooting SSH sign-in issues, domain integration, or file transfer specifics for Linux). The file transfer section mentions PowerShell and the Azure portal, but does not discuss Linux command-line tools or workflows. Windows scenarios are prioritized or exclusively addressed in some sections.
Recommendations
  • Add troubleshooting guidance for Linux VMs, such as common SSH authentication issues, domain integration (e.g., with LDAP or Kerberos), and file transfer using Linux-native tools.
  • Provide Linux-specific examples and command-line workflows alongside Windows instructions, especially in sections discussing sign-in and file transfer.
  • Ensure parity in troubleshooting steps for both Windows and Linux environments, including error messages, credential formats, and client tool usage.
  • Mention Linux equivalents (e.g., scp, sftp, rsync) when discussing file transfer, and clarify any platform-specific limitations or requirements.
GitHub Create Pull Request
Bastion What's new in Azure Bastion? ...ocs/azure-docs/blob/main/articles/bastion/whats-new.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page lists recent Azure Bastion features and updates, with a notable tendency to mention Windows/RDP-related features before Linux/SSH equivalents. For example, 'Microsoft Entra ID support for portal (RDP)' is listed before 'Microsoft Entra ID support for portal (SSH)', and the RDP feature is described as being in preview while the SSH feature is already generally available. There are no explicit Linux-specific examples, tools, or usage patterns highlighted, and the terminology (RDP, graphical session recording) is more closely associated with Windows environments.
Recommendations
  • Ensure Linux/SSH features are given equal prominence and ordering as Windows/RDP features in release tables and documentation.
  • Provide explicit examples and links for Linux usage (e.g., SSH tunneling, Linux client configuration) alongside Windows examples.
  • Include references to Linux tools and patterns (such as OpenSSH, xterm, etc.) where relevant.
  • Balance terminology so that both Windows and Linux remote access scenarios are described with equal detail and clarity.
GitHub Create Pull Request
Bastion Configure Bastion for native client connections ...azure-docs/blob/main/articles/bastion/native-client.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Windows native client connection instructions and examples before Linux equivalents in both the main connection table and the 'Next steps' section. There is also a lack of detailed Linux-specific examples or screenshots, with Windows-centric instructions and visuals being more prominent.
Recommendations
  • Present Linux and Windows instructions/examples in parallel or alternate order to avoid prioritizing Windows.
  • Include Linux-specific screenshots and step-by-step instructions for configuring and connecting via native client.
  • Expand the 'Next steps' section to explicitly link to Linux connection guides before or alongside Windows guides.
  • Ensure parity in feature explanation and troubleshooting for both Windows and Linux clients.
GitHub Create Pull Request
Bastion Record Bastion sessions ...e-docs/blob/main/articles/bastion/session-recording.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates bias by omitting any OS-specific examples or guidance, but implicitly assumes a Windows-centric workflow by referencing RDP sessions and not mentioning SSH or Linux session types. There are no examples or instructions tailored for Linux users or SSH session recording, and the terminology and steps are oriented toward Windows/Azure Portal patterns, with no parity for Linux command-line or tooling.
Recommendations
  • Include explicit instructions and examples for recording SSH sessions (common for Linux VMs) in addition to RDP.
  • Add command-line examples using Azure CLI, Bash, or PowerShell for both Windows and Linux environments.
  • Clarify whether session recording supports both RDP and SSH, and if there are differences in configuration or playback.
  • Provide parity in screenshots and walkthroughs for Linux-based workflows (e.g., using Azure CLI on Linux to configure Bastion session recording).
  • Mention any limitations or considerations specific to Linux/SSH sessions, if applicable.
GitHub Create Pull Request
Azure Vmware Configure VMware Cloud Director Service in Azure VMware Solution ...re-vmware-cloud-director-service-azure-vmware-solution.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently references the Azure portal and VMware management tools, which are typically accessed via web interfaces or Windows environments. There are no examples or instructions for Linux users, such as using Linux CLI tools, SCP for OVA transfer, or Linux-based credential management. All steps assume access to Windows-centric GUIs and workflows, and there is no mention of Linux alternatives or parity in procedures.
Recommendations
  • Include Linux-specific instructions for tasks such as transferring OVA files (e.g., using SCP, rsync, or curl from Linux terminals).
  • Provide CLI examples for Linux users to interact with vCenter, NSX Manager, or Azure (e.g., using Azure CLI, PowerShell Core on Linux, or REST APIs).
  • Clarify that the procedures can be performed from Linux environments where applicable, and note any platform-specific limitations.
  • Add screenshots or terminal outputs from Linux systems where GUI steps are not required.
  • Explicitly mention cross-platform compatibility for credential management and remote access (e.g., SSH from Linux, using open-source tools).
GitHub Create Pull Request
Azure Vmware Enable VMware Cloud Director service with Azure VMware Solution .../articles/azure-vmware/enable-vmware-cds-with-azure.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently references Azure VMs and configuration steps via the Azure portal, implicitly assuming Windows-based workloads and administrative patterns. All VM examples use Azure VM names (e.g., JSVM1, JSVM2) without specifying OS, but the context and lack of Linux-specific instructions or CLI examples suggest a Windows-first approach. There are no Linux-specific configuration steps, tools, or troubleshooting guidance, nor are there examples using Linux VMs or command-line tools like Azure CLI, PowerShell, or SSH.
Recommendations
  • Include explicit examples for both Windows and Linux VMs when describing test scenarios and connectivity verification (e.g., show how to ping from a Linux VM).
  • Provide instructions for configuring VPN and firewall rules using Azure CLI and PowerShell, as well as Linux-native tools (e.g., strongSwan, iptables) for users who may be managing Linux-based workloads.
  • Add troubleshooting steps and verification commands for Linux environments, such as using SSH, netcat, or tcpdump.
  • Clarify that the guidance applies to both Windows and Linux workloads, and specify any OS-specific considerations where relevant.
  • Reference Linux-based Azure VM images and provide parity in example VM naming and configuration.
GitHub Create Pull Request
Azure Vmware Manage Arc-enabled Azure VMware private cloud ...ure-vmware/manage-arc-enabled-azure-vmware-solution.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides command examples for both Windows and Linux-based management VMs, but the Windows example is listed first and is slightly more explicit. There is a lack of parity in example formatting and detail, and some steps (such as directory navigation) are not clearly described for Linux. No Linux-specific tools or patterns are mentioned, and the documentation generally assumes a Windows-first workflow.
Recommendations
  • Present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first.
  • Ensure equal detail and clarity for both Linux and Windows instructions, including explicit directory navigation and activation commands.
  • Include Linux-specific notes or troubleshooting tips where appropriate.
  • Review all command examples to ensure they are tested and accurate for both platforms.
  • Consider adding a table or toggle for platform-specific instructions to improve usability for Linux users.
GitHub Create Pull Request
Azure Vmware Send VMware syslogs to log management server using Azure Logic Apps .../blob/main/articles/azure-vmware/logs-via-logic-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates subtle Windows bias by referencing the 'default Windows plan' (Workflow Standard WS1) as the primary hosting option for Logic Apps and mentioning Windows-centric resource specifications (ACU, memory, vCPU) without clarifying Linux alternatives. There are no explicit PowerShell examples or Windows-only tools, but the documentation does not mention Linux-based hosting plans or provide parity for Linux environments. The workflow and certificate instructions are platform-neutral, but the overall framing and defaults assume a Windows-centric deployment.
Recommendations
  • Explicitly mention Linux-based hosting plans for Logic Apps if available, and provide guidance for selecting them.
  • Clarify whether the Workflow Standard WS1 plan is Windows-only or if equivalent Linux plans exist, and list their specifications.
  • Add notes or examples for deploying and managing Logic Apps in Linux environments, including certificate management and environment variable configuration.
  • Ensure that any references to default plans or resource specifications include both Windows and Linux options where applicable.
  • Review screenshots and UI instructions to confirm they are applicable to both Windows and Linux hosting scenarios, or provide separate guidance if differences exist.
GitHub Create Pull Request
Azure Vmware Attach Azure NetApp Files to Azure VMware Solution VMs ...zure-vmware/netapp-files-with-azure-vmware-solution.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation mentions both Linux and Windows VMs as prerequisites and acknowledges support for both SMB (Windows) and NFS (Linux) protocols. However, the SMB/Windows mapping process is described first and in more detail, while Linux/NFS mounting is referenced only briefly, with no concrete Linux command-line examples or step-by-step instructions. There are no PowerShell-heavy sections, but the lack of Linux-specific examples and the ordering of Windows/SMB information before Linux/NFS indicate a subtle Windows-first bias.
Recommendations
  • Provide explicit Linux mounting instructions, including sample mount commands and /etc/fstab configuration for NFS volumes.
  • Include step-by-step examples for both Windows (SMB) and Linux (NFS) share mapping, ensuring parity in detail and clarity.
  • Consider presenting Linux/NFS and Windows/SMB procedures in parallel or alternating order, rather than consistently listing Windows/SMB first.
  • Add troubleshooting tips for both Linux and Windows clients to ensure comprehensive cross-platform support.
GitHub Create Pull Request
Azure Web Pubsub How to collect a network trace ...s/azure-web-pubsub/howto-troubleshoot-network-trace.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page exhibits mild Windows bias. Fiddler, a tool with historical Windows roots, is presented first and in most detail, despite being cross-platform. The browser section lists Microsoft Edge (Chromium) first, and instructions often mention Windows shortcuts before Linux/macOS equivalents. There is no mention of Linux-native GUI tools (e.g., Wireshark) for network tracing, and tcpdump is only briefly covered for Linux/macOS, with no Windows equivalent (e.g., Wireshark or Windows packet capture tools).
Recommendations
  • Add examples and instructions for Linux-native GUI tools such as Wireshark, including installation and usage steps.
  • Include Windows equivalents for tcpdump (e.g., mention Wireshark or Microsoft Message Analyzer) and clarify cross-platform options.
  • Balance ordering in browser sections by rotating which browser is presented first, or group by OS rather than browser vendor.
  • When listing keyboard shortcuts, present all platforms equally (e.g., Windows, Linux, macOS) rather than Windows first.
  • Expand the tcpdump section to include more detailed usage examples and troubleshooting tips for Linux users.
  • Consider adding a summary table comparing tools available on Windows, Linux, and macOS for network tracing.
GitHub Create Pull Request
Azure Web Pubsub Create an Azure Web PubSub resource ...cles/azure-web-pubsub/howto-develop-create-instance.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing resources, but PowerShell is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. In deployment and resource review/cleanup sections, PowerShell examples are presented alongside CLI, which may suggest a Windows-centric approach. There is no explicit mention of Linux-specific tools or shell environments, nor are there notes about running Azure CLI on Linux or macOS. The documentation does not provide Linux-specific guidance or highlight cross-platform usage beyond Azure CLI.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Note that PowerShell examples are primarily for Windows users, and suggest Bash or other shell environments for Linux/macOS users.
  • Provide explicit Bash shell examples for Linux/macOS users where appropriate, especially in sections currently showing only Azure CLI and PowerShell.
  • Add a brief section or note about installing and using Azure CLI on Linux/macOS.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples to avoid implicit Windows-first bias.
GitHub Create Pull Request
Azure Web Pubsub include file ...web-pubsub/includes/web-pubsub-add-role-assignments.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily describes role assignment using the Azure portal, which is a GUI-centric approach more commonly used on Windows. In the 'Learn more' section, Azure PowerShell is listed before Azure CLI, which is the preferred cross-platform command-line tool for Linux users. There are no explicit Linux-specific examples or references to Linux tools or workflows.
Recommendations
  • Add explicit Linux CLI examples for role assignment, using Azure CLI commands.
  • Ensure Azure CLI is mentioned before Azure PowerShell in lists, as it is cross-platform.
  • Include screenshots or instructions for using the Azure CLI in Linux environments.
  • Clarify that the Azure portal is accessible from any OS/browser, and mention alternatives for users who prefer command-line workflows.
  • Consider adding a section comparing PowerShell and CLI usage for role assignment, highlighting cross-platform compatibility.
GitHub Create Pull Request
Azure Web Pubsub Integrate - Build a real-time collaborative whiteboard using Web PubSub for Socket.IO and deploy it to Azure App Service .../azure-web-pubsub/socket-io-howto-integrate-web-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for compressing the application into a zip file, but Bash is presented first and PowerShell is included as an alternative. No Linux-specific tools or patterns are missing, and Azure CLI is cross-platform. However, the explicit inclusion of PowerShell commands and references may indicate a slight Windows bias, especially since PowerShell is not the default shell on Linux systems.
Recommendations
  • Clarify that Bash commands are for Linux/macOS and PowerShell commands are for Windows, to help users quickly identify which instructions apply to their environment.
  • Consider providing Linux-specific notes where relevant (e.g., mention that zip is pre-installed on most Linux distributions, but may require installation on Windows).
  • If possible, add a table or section summarizing commands for different platforms (Windows, Linux, macOS) for common tasks like compression.
  • Ensure that all examples and instructions are equally clear and accessible for both Windows and Linux users, and avoid assuming PowerShell usage unless necessary.
GitHub Create Pull Request
Backup Support matrix for Azure Elastic SAN Backup (preview) ...cles/backup/azure-elastic-san-backup-support-matrix.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively references the Azure portal for configuration, restore, and management steps, without mentioning or providing examples for command-line interfaces such as Azure CLI, Bash, or PowerShell. There is no explicit mention of Windows-specific tools, but the absence of Linux-oriented instructions or parity in examples (e.g., CLI commands) suggests a subtle Windows-first bias, as Azure portal usage is often associated with Windows environments and administrative patterns.
Recommendations
  • Add examples for configuring, restoring, and managing Elastic SAN backup using Azure CLI and/or Bash scripts.
  • Include references to cross-platform tools and workflows, ensuring that Linux users can follow equivalent steps.
  • Explicitly mention that all operations can be performed from any OS, and provide links to documentation for CLI-based management.
  • If PowerShell is supported, provide parity by including Bash or Azure CLI equivalents for each operation.
GitHub Create Pull Request
Backup Troubleshoot Azure Kubernetes Service backup ...backup/azure-kubernetes-service-backup-troubleshoot.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows/Azure portal bias by consistently presenting troubleshooting steps and configuration instructions using the Azure portal UI, with no mention of Linux-native or cross-platform alternatives (e.g., bash scripts, Linux desktop tools, or non-portal workflows). All CLI examples use Azure CLI and kubectl, which are cross-platform, but the portal instructions and screenshots are Windows-centric. There are no references to Linux-specific tools, nor are Linux workflows or desktop environments acknowledged. This may disadvantage Linux users who prefer command-line or automation-first approaches.
Recommendations
  • Provide equivalent command-line instructions for all portal-based steps, especially for resource scaling and extension configuration (e.g., using az CLI and kubectl YAML patches).
  • Include explicit notes that Azure CLI and kubectl commands work on Linux, macOS, and Windows, and show example shell commands for Linux environments.
  • Add references or links to Linux desktop tools or automation scripts where relevant.
  • Balance screenshots and UI walkthroughs with CLI and YAML-based workflows to support Linux-first and automation-centric users.
  • Where possible, mention OS-agnostic troubleshooting patterns and avoid assuming use of Windows/Azure portal as the primary interface.
GitHub Create Pull Request
Backup Restore Azure VMs using REST API .../backup/backup-azure-arm-userestapi-restoreazurevms.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias. While the REST API examples themselves are platform-neutral, several example responses and request bodies (especially in the Cross Region Restore section) repeatedly use 'osType': 'Windows' and Windows VM names. There are no explicit Linux VM examples, nor is there any mention of restoring Linux VMs or handling Linux-specific scenarios. This may lead Linux users to feel underrepresented or uncertain about Linux support.
Recommendations
  • Include example responses and request bodies that feature Linux VMs (e.g., set 'osType': 'Linux', use Linux VM names).
  • Explicitly state that the REST API supports both Windows and Linux VMs, and note any differences in restore operations or metadata.
  • Add a section or note addressing Linux-specific considerations, such as file system consistency, encryption, or agent requirements.
  • Ensure parity in documentation by alternating or combining Windows and Linux examples throughout, especially in sample JSON and response bodies.
  • Where possible, clarify that all steps and APIs apply equally to Linux VMs, and link to Linux-specific troubleshooting or best practices.
GitHub Create Pull Request
Backup Replace your tape infrastructure by using Azure Backup ...n/articles/backup/backup-azure-backup-cloud-as-tape.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing System Center Data Protection Manager (DPM), a Windows-only tool, and by providing links and examples that focus on Windows backup scenarios (e.g., 'backup-windows-with-mars-agent.md'). There are no Linux-specific examples, tools, or guidance, and Linux backup workflows are not mentioned or illustrated.
Recommendations
  • Include Linux backup examples and workflows, such as using Azure Backup with Linux VMs or workloads.
  • Reference Linux-compatible backup tools (e.g., Azure Backup for Linux, Azure CLI, or third-party solutions) alongside or before Windows tools.
  • Provide parity in screenshots and sample policies for Linux environments.
  • Add links to Linux-specific documentation, such as 'backup-linux-with-azure-agent.md' if available.
  • Clarify that Azure Backup supports both Windows and Linux, and outline any platform-specific considerations.
GitHub Create Pull Request
Backup Create backup policies for Azure database for PostgreSQL - Flexible server using data protection REST API in Azure Backup ...base-postgresql-flex-use-rest-api-create-update-policy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page contains a reference to the 'default PowerShell object' for PostgreSQL Flexible servers, implying a Windows-centric approach to backup policy creation and scheduling. There are no Linux-specific examples, nor are alternative Linux-native tools or command-line patterns mentioned. The only tooling reference is PowerShell, which is traditionally associated with Windows, and it is mentioned before any cross-platform or Linux alternatives.
Recommendations
  • Replace or supplement references to 'PowerShell object' with cross-platform alternatives, such as Azure CLI or Bash scripts.
  • Provide explicit examples for Linux users, including how to perform the same REST API operations using curl, wget, or Azure CLI.
  • Clarify that PowerShell is available cross-platform, or avoid implying that it is the default or only option.
  • Add a section or note describing how Linux administrators can automate or schedule these backups using cron jobs or other Linux-native tools.
  • Ensure that all examples and tooling references are presented in a platform-neutral way, or provide parallel examples for both Windows and Linux environments.
GitHub Create Pull Request
Backup Back up Azure Disks using Azure Data Protection REST API. ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates subtle Windows bias. In the 'Next steps' section, the order of restore instructions lists 'Azure PowerShell' before 'Azure CLI', which is commonly associated with Linux/macOS. Additionally, the only explicit link to permissions assignment refers to a PowerShell-based page (backup-managed-disks-ps.md), with no mention of Linux/CLI alternatives in the main flow. There are no direct Linux/CLI examples or references in the main backup workflow, and no Bash or shell scripting examples are provided.
Recommendations
  • Ensure parity by providing explicit Azure CLI examples alongside PowerShell, especially for permissions assignment and backup configuration.
  • When linking to further instructions, list Azure CLI and PowerShell together or alternate their order to avoid implicit prioritization.
  • Include Bash/shell scripting examples for REST API calls to demonstrate Linux compatibility.
  • Reference both PowerShell and CLI documentation in prerequisite and workflow steps, not just in 'Next steps'.
  • Add a note clarifying that all REST API operations can be performed from any OS, and provide sample commands for both Windows and Linux environments.
GitHub Create Pull Request
Backup Integrate Microsoft Defender's ransomware alerts to protect Azure Backup recovery points ...up-azure-integrate-microsoft-defender-using-logic-apps.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses exclusively on Azure Virtual Machines and Microsoft Defender integration, but all examples, terminology, and workflows implicitly assume Windows environments. There are no references to Linux VMs, Linux-specific backup considerations, or examples of how ransomware detection and backup protection would work for Linux workloads. All instructions, screenshots, and role assignments are generic but do not mention Linux or cross-platform scenarios, which may lead Linux users to feel unsupported or unclear about applicability.
Recommendations
  • Explicitly mention support for Linux VMs in the scope and prerequisites, or clarify limitations if Linux is not supported.
  • Provide examples or workflows that demonstrate how the integration works for Linux-based Azure VMs, including any differences in alerting or backup retention.
  • Include screenshots or step-by-step instructions that reference Linux VM resources where applicable.
  • Discuss any Linux-specific considerations for ransomware detection, backup retention, or logic app deployment.
  • If Microsoft Defender for Cloud or Azure Backup features differ for Linux, document those differences and provide guidance for Linux administrators.
GitHub Create Pull Request
Backup Supported VM SKUs for Azure Policy .../articles/backup/backup-azure-policy-supported-skus.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_heavy
Summary
The documentation page lists supported VM SKUs for Azure Backup policies, and the table of supported images is heavily weighted toward Windows-based SKUs. Windows SKUs are listed first and in much greater detail, with many variants and specialized options, while Linux distributions are listed later and with less granularity. There are no examples or guidance specific to Linux backup scenarios, and the documentation does not mention Linux-specific considerations or tools.
Recommendations
  • Provide equal detail for Linux SKUs, including variants and specialized options (e.g., server core, containers, BYOS, etc.) where applicable.
  • Add Linux-specific notes or examples, such as considerations for backup on different Linux distributions, or guidance for custom images.
  • Clarify any differences in backup features or limitations between Windows and Linux VMs.
  • Consider listing Linux SKUs first or interleaving them with Windows SKUs to avoid perceived prioritization.
  • Include links to Linux backup documentation or troubleshooting guides.
GitHub Create Pull Request
Backup Manage SQL server databases in Azure VMs using Azure Backup via CLI ...ob/main/articles/backup/backup-azure-sql-manage-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation focuses exclusively on managing SQL Server databases in Azure VMs using Azure CLI, but all examples and terminology assume a Windows environment (SQL Server, Windows-style resource/container naming, no mention of Linux SQL Server or cross-platform differences). There are no references to Linux-based SQL Server VMs, nor any examples or notes for Linux-specific considerations, despite SQL Server being supported on Linux. The documentation implicitly assumes the reader is using Windows VMs.
Recommendations
  • Add explicit notes clarifying that SQL Server on Linux VMs is supported and highlight any differences in backup/restore operations or prerequisites.
  • Provide example commands and outputs for Linux-based SQL Server VMs, including any differences in resource/container naming conventions or required permissions.
  • Include troubleshooting or FAQ sections for common Linux-specific issues (e.g., permissions, file system paths, service management).
  • Where relevant, mention OS-specific requirements for Azure Backup agent installation/configuration on Linux SQL Server VMs.
  • Ensure terminology and instructions are inclusive of both Windows and Linux SQL Server deployments.
GitHub Create Pull Request
Backup Back Up an Azure Virtual Machine with Azure Extended Zones Portal ...ain/articles/backup/backup-azure-vms-extended-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page generally uses the Azure Portal UI for backup configuration, which is cross-platform. However, in the 'Install the VM agent' section, instructions for Windows appear first, with explicit download links and file paths, while Linux instructions are less detailed and refer users to distribution repositories. The Windows agent installation is described with more step-by-step guidance and tool references (MSI installer, file paths), whereas the Linux section is more generic and lacks equivalent detail or troubleshooting steps.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and troubleshooting guidance.
  • Include explicit Linux agent installation commands (e.g., apt, yum, zypper) and verification steps, similar to the Windows example.
  • Provide direct links to documentation for both Windows and Linux agent installation and updates.
  • Avoid listing Windows instructions before Linux; consider using tabs or side-by-side formatting.
  • Mention Linux-specific considerations (e.g., SELinux, systemd service status) where relevant.
GitHub Create Pull Request
Backup Perform actions using Backup center in Azure Backup ...ocs/blob/main/articles/backup/backup-center-actions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently focusing on Azure Virtual Machines (VMs) as the primary backup and restore example, with references to SQL and SAP HANA in Azure VMs, which are commonly Windows workloads. There is a lack of explicit Linux VM examples, Linux-specific backup/restore scenarios, or mention of Linux tools/commands. The documentation does not provide parity for Linux users, as it omits guidance for Linux VM backup/restore or any Linux-specific considerations, and always uses VM examples generically without clarifying Windows vs. Linux applicability.
Recommendations
  • Add explicit examples and instructions for backing up and restoring Linux VMs, including screenshots and step-by-step guidance.
  • Clarify whether the procedures for Azure VMs apply equally to both Windows and Linux, and note any differences or prerequisites for Linux workloads.
  • Include references to Linux-specific backup scenarios (e.g., file-level restore, application-consistent backups for Linux workloads).
  • Where SQL in Azure VM is mentioned, also mention open-source database workloads commonly run on Linux (e.g., MySQL, MongoDB) if supported.
  • Ensure that any command-line or automation examples (if present) include both PowerShell and Bash/Azure CLI equivalents.
GitHub Create Pull Request
Backup Support matrix for Backup center for Azure Backup ...b/main/articles/backup/backup-center-support-matrix.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. Windows-centric workloads (such as SQL in Azure VM, SAP HANA in Azure VM, System Center Data Protection Manager, Azure Backup Agent (MARS), and Azure Backup Server (MABS)) are listed before Linux workloads or Linux-native equivalents. Windows backup tools (MARS, MABS, DPM) are mentioned explicitly, while Linux backup agents or tools are not referenced. There are no explicit Linux examples, and the documentation does not clarify support for Linux VMs or Linux-specific backup scenarios.
Recommendations
  • Explicitly mention Linux VM backup support and provide parity in listing Linux workloads alongside Windows workloads.
  • Include references to Linux-native backup agents or tools if available, or clarify that Azure Backup supports Linux VMs.
  • Provide examples or documentation links for Linux backup scenarios, such as restoring or backing up Linux VMs.
  • Avoid listing Windows workloads and tools before Linux equivalents; use neutral or alphabetical ordering.
  • Clarify any differences or limitations for Linux workloads in the support matrix.
GitHub Create Pull Request
Backup Encryption in Azure Backup ...re-docs/blob/main/articles/backup/backup-encryption.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by mentioning BitLocker (a Windows encryption tool) before DM-Crypt (the Linux equivalent) in the context of Azure Disk Encryption for VM backups. The explanation of in-guest encryption lists BitLocker for Windows VMs first, and DM-Crypt for Linux VMs second. Additionally, the section on TDE-enabled database backup restoration refers only to SQL Server (a Microsoft/Windows-centric product) without mentioning Linux-based database restoration scenarios or tools.
Recommendations
  • Present Linux and Windows tools in parallel, or alternate the order to avoid consistently listing Windows tools first.
  • Include explicit examples or references for Linux-based backup and restoration processes, such as restoring TDE-enabled databases on Linux SQL Server instances.
  • Expand documentation to mention Linux-native tools and patterns where relevant, ensuring parity in guidance for both platforms.
  • Add links or references to DM-Crypt documentation and Linux database backup/restore procedures, similar to those provided for BitLocker and SQL Server.
GitHub Create Pull Request
Backup Back up Azure Managed Disks using Azure CLI .../blob/main/articles/backup/backup-managed-disks-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is largely cross-platform, focusing on Azure CLI commands, which are available on both Windows and Linux. However, there are subtle signs of Windows bias: (1) Variable assignment examples use PowerShell syntax (e.g., $DiskId = ...), which is not valid in Bash or other Linux shells; (2) The 'Next steps' section lists 'Azure portal', 'Azure PowerShell', and 'Azure CLI' in that order, putting PowerShell before CLI, which can imply a Windows-first mindset. There are no Linux-specific examples or notes, and the documentation does not explicitly show Bash-compatible variable usage or mention Linux shell environments.
Recommendations
  • Provide variable assignment examples in both PowerShell and Bash syntax, or use Bash syntax by default for cross-platform parity (e.g., DiskId="..." instead of $DiskId = ...).
  • Add a note clarifying that Azure CLI commands work identically on Windows, Linux, and macOS, and provide shell-agnostic examples where possible.
  • In the 'Next steps' section, list Azure CLI before PowerShell, or group them together without implying an order of preference.
  • Explicitly mention that the instructions are valid for both Windows and Linux, and consider adding a short section or callout for Linux/macOS users if there are any environment-specific considerations.
GitHub Create Pull Request
Backup Azure Resource Manager and Bicep files ...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by providing a template specifically for deploying a Windows Server VM with backup enabled, while lacking equivalent examples for Linux VMs. There are no Linux-specific backup scenarios or templates mentioned, and Windows is the only OS highlighted in the VM deployment section. No PowerShell or Windows-only tools are referenced directly, but the absence of Linux parity in examples is notable.
Recommendations
  • Add templates and examples for deploying and backing up Linux VMs (e.g., Ubuntu, CentOS) with Recovery Services vaults.
  • Include documentation or links for Linux-specific backup scenarios, such as backing up Linux workloads or configuring backup policies for Linux VMs.
  • Ensure that examples for VM backup and deployment cover both Windows and Linux operating systems equally.
  • Explicitly mention cross-platform compatibility where applicable, and provide guidance for Linux administrators alongside Windows instructions.
GitHub Create Pull Request
Backup Manage Azure Files backups with the Azure CLI ...ocs/blob/main/articles/backup/manage-afs-backup-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is generally cross-platform, focusing on Azure CLI commands that work on both Windows and Linux. However, there is evidence of Windows bias: (1) The output example for creating a backup policy includes a Windows file path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>), which is unnecessary and may confuse Linux users. (2) The instructions for exporting policies use the '>' operator, which works on both platforms, but the output example is Windows-specific. (3) No Linux-specific shell examples (e.g., bash, file paths, or environment setup) are provided, and Windows-centric patterns (e.g., file locations) appear first or exclusively.
Recommendations
  • Remove or supplement Windows-specific output examples with Linux equivalents (e.g., show both C:\... and ~/... paths).
  • Explicitly mention that all CLI commands work on both Windows and Linux, and provide notes about any platform-specific differences.
  • Include Linux shell examples (e.g., using bash, showing output redirection with '>', and file paths like ~/vaultdemopol.json).
  • Avoid referencing Windows file paths or environments unless also providing Linux alternatives.
  • Add a short section on preparing the environment for Linux users, if relevant.
GitHub Create Pull Request
Backup Manage and monitor SQL Server DBs on an Azure VM .../articles/backup/manage-monitor-sql-database-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses exclusively on managing and monitoring SQL Server databases on Azure VMs, implicitly assuming a Windows environment. There are no examples, instructions, or references for Linux-based SQL Server VMs, nor any mention of Linux-specific tools, commands, or UI differences. All screenshots and workflows are generic to the Azure portal, but the absence of Linux parity is notable given SQL Server's support on Linux.
Recommendations
  • Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify any differences.
  • Add examples or notes for managing SQL Server on Linux VMs, including any differences in backup agent installation, extension management, or troubleshooting.
  • Include references to Linux-specific documentation or CLI commands where applicable.
  • If certain features are Windows-only, clearly highlight this and provide Linux alternatives or workarounds.
  • Add screenshots or walkthroughs for Linux SQL Server VM scenarios to ensure parity.
GitHub Create Pull Request
Backup Update the existing VM backup policy using CLI ...docs/blob/main/articles/backup/modify-vm-policy-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides CLI instructions for updating a VM backup policy, but file path examples (e.g., C:\temp2\Policy.json) use Windows conventions exclusively. There are no Linux/macOS path examples or notes on cross-platform usage, which may confuse or exclude non-Windows users.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Policy.json) alongside Windows examples.
  • Add a note clarifying that file paths should be adapted to the user's operating system.
  • Where possible, use platform-neutral examples or show both Windows and Linux/macOS variants for commands involving file paths.
  • Explicitly mention that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
GitHub Create Pull Request
Backup Quickstart - Back up a VM with the Azure portal by using Azure Backup ...cs/blob/main/articles/backup/quick-backup-vm-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page exhibits Windows bias primarily in the 'Install the VM agent' section, where Windows instructions are listed before Linux instructions and provide more detail (including download links, file paths, and verification steps). The Linux instructions are less detailed and lack direct package commands or verification steps. Additionally, the initial VM creation link points to a Windows VM creation guide, with no mention of a Linux equivalent.
Recommendations
  • Provide Linux VM creation instructions or link to the Linux VM creation quickstart alongside the Windows link.
  • In the 'Install the VM agent' section, present Linux and Windows instructions with equal detail, including explicit package installation commands (e.g., apt, yum) and verification steps for Linux.
  • Alternate the order of Windows and Linux instructions, or present them in parallel, to avoid implicit prioritization.
  • Include screenshots or examples for Linux where relevant, matching the level of detail given for Windows.
GitHub Create Pull Request
Backup Troubleshoot SAP HANA databases instance backup errors ...cles/backup/sap-hana-database-instance-troubleshoot.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation refers exclusively to 'Azure VM' without specifying or providing examples for Linux-based VMs, which are the typical platform for SAP HANA. There are no Linux-specific troubleshooting steps, commands, or references to Linux tools (such as shell commands or Linux file system management). The guidance and terminology are generic but implicitly Windows-centric by omitting Linux context, despite SAP HANA's primary deployment on Linux.
Recommendations
  • Explicitly mention Linux VM scenarios and clarify that SAP HANA is generally deployed on Linux VMs.
  • Provide Linux-specific troubleshooting steps, including relevant shell commands (e.g., for mounting disks, checking file systems, moving data between volumes).
  • Reference Linux file system types and tools (e.g., ext3, xfs, mount, lsblk, fdisk) in error resolutions where appropriate.
  • Include example commands for assigning roles and permissions using Azure CLI or shell scripts, not just PowerShell or portal instructions.
  • Add notes or sections highlighting differences or additional steps for Linux VMs versus Windows VMs, if any.
GitHub Create Pull Request
Backup Script Sample - Disable Soft delete for File Share using ARM API .../backup/scripts/disable-soft-delete-for-file-shares.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by using Windows-style file paths (e.g., .\rqbody-disableSoftDelete.json) in all command examples and omitting any Linux/macOS equivalents. There are no bash or shell examples, and the documentation does not mention how to run armclient or manage JSON files on Linux systems.
Recommendations
  • Provide Linux/macOS command examples using forward slashes (e.g., ./rqbody-disableSoftDelete.json) and appropriate shell syntax.
  • Clarify that armclient is cross-platform and provide installation and usage instructions for Linux/macOS.
  • Add notes or sections highlighting differences in file path conventions and shell usage between Windows and Linux.
  • Ensure parity in documentation by including both Windows and Linux/macOS examples for all commands and file operations.
GitHub Create Pull Request
Backup Tutorial - Restore a VM with Azure CLI ...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_reference ⚠ī¸ windows_first
Summary
The documentation is largely cross-platform and focused on Azure CLI, which is inherently cross-platform and works on both Windows and Linux. However, there are subtle signs of Windows bias: (1) The only cross-link to alternative tooling is for PowerShell, with no mention of Bash or Linux-native scripting; (2) In the cross-zonal restore section, the link to 'Azure zone pinned VMs' points to a Windows-specific page; (3) There is no explicit mention or example for restoring Windows VMs, but the only alternative tool mentioned is PowerShell, which is most commonly used on Windows. The CLI examples themselves are platform-neutral.
Recommendations
  • Include a cross-link to Bash or Linux shell scripting guides for users who may prefer those over PowerShell.
  • When referencing 'zone pinned VMs', link to both Windows and Linux VM documentation, or to a neutral overview page.
  • Explicitly state that all CLI commands apply equally to both Windows and Linux VMs, and provide examples or notes where behavior may differ.
  • If mentioning PowerShell as an alternative, also mention Bash or other Linux-native automation options for parity.
  • Ensure that any referenced documentation or examples do not default to Windows unless there is a technical reason.
GitHub Create Pull Request
Baremetal Infrastructure Connect BareMetal Infrastructure instances in Azure ...tal-infrastructure/connect-baremetal-infrastructure.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently presents Azure portal (GUI) and Azure CLI examples for managing BareMetal Infrastructure instances, but does not provide any Linux-specific command-line examples or mention Linux tools. The CLI instructions are platform-neutral but lack explicit guidance for Linux users (e.g., shell environment setup, authentication differences). The portal instructions assume a graphical environment, which is more common on Windows. There is no mention of PowerShell, but the absence of Linux-specific context or examples indicates a subtle Windows bias.
Recommendations
  • Add explicit instructions for Linux users, such as how to install and authenticate with Azure CLI on Linux.
  • Include example CLI commands run in a Bash shell, and clarify any differences in command syntax or environment variables between Windows and Linux.
  • Mention Linux desktop environments or alternatives for accessing the Azure portal, or provide guidance for users working in headless/server environments.
  • If relevant, provide examples using native Linux tools (e.g., curl, jq) for interacting with Azure REST APIs.
  • Ensure screenshots and step-by-step instructions are not exclusively tailored to Windows UI conventions.
GitHub Create Pull Request
Baremetal Infrastructure Architecture of BareMetal Infrastructure for NC2 on Azure ...-infrastructure/workloads/nc2-on-azure/architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently references Azure management via the portal, CLI, or PowerShell, but does not mention Linux-native tools or provide Linux-specific examples. There is an implicit Windows-first bias, as PowerShell is highlighted and no Linux command-line equivalents (such as Bash or Azure CLI usage on Linux) are shown. No Linux-specific deployment or management patterns are discussed.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide examples of managing NC2 on Azure from Linux environments using Bash and Azure CLI.
  • Include Linux-specific instructions or examples for common management tasks, such as cluster deployment, monitoring, and connectivity setup.
  • Clarify that PowerShell is available on Linux, but also show parity by providing Bash or shell script examples.
  • Reference Linux tools and patterns (e.g., SSH, scp, Linux-based automation) where relevant, especially for on-premises connectivity and VM management.
  • Ensure that diagrams and workflow descriptions do not assume a Windows-centric environment.
GitHub Create Pull Request
Bastion Copy and paste to and from a Windows virtual machine: Azure ...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is exclusively focused on Windows virtual machines, with all instructions, prerequisites, and examples referring only to Windows. There is no mention of Linux VMs, nor are there any Linux-specific examples or considerations provided. This creates a Windows-first bias and omits guidance for users working with Linux VMs.
Recommendations
  • Add equivalent instructions and examples for Linux virtual machines, including any differences in clipboard behavior or limitations.
  • Update the prerequisites section to mention both Windows and Linux VM scenarios.
  • Clarify whether the Bastion clipboard feature works identically for Linux VMs, and provide troubleshooting steps or notes for common Linux desktop environments (e.g., GNOME, KDE).
  • Include screenshots or step-by-step guides for Linux VM sessions where applicable.
  • Ensure parity in documentation structure and detail between Windows and Linux VM sections.
GitHub Create Pull Request
Bastion Connect to a Linux VM using RDP .../main/articles/bastion/bastion-connect-vm-linux-rdp.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page describes connecting to a Linux VM using RDP via Azure Bastion, but it demonstrates bias by focusing on RDP—a protocol and workflow historically associated with Windows. The page requires installation of xrdp (a Linux implementation of RDP) but does not mention or provide examples for native Linux remote access tools (such as SSH or VNC), nor does it provide Linux-specific client usage instructions. There are no examples of connecting from a Linux client, and the documentation does not address Linux-centric remote management patterns.
Recommendations
  • Include examples and guidance for connecting to Linux VMs using SSH via Azure Bastion, which is the native and most common method for Linux remote management.
  • Provide instructions for connecting from Linux client machines, including use of RDP clients available on Linux (e.g., Remmina, rdesktop, FreeRDP) and SSH clients.
  • Mention and compare alternative remote desktop solutions for Linux (such as VNC, X2Go), and clarify when RDP/xrdp is preferable.
  • Ensure parity in documentation by presenting Linux-native patterns and tools before or alongside Windows-centric ones.
  • Add troubleshooting steps and configuration examples specific to Linux environments, including firewall and authentication considerations.
GitHub Create Pull Request
Bastion Quickstart: Deploy Azure Bastion to a virtual network using an ARM template .../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where only Windows virtual machine creation and Windows RDP connection guides are linked. There are no examples or links for Linux VM creation or SSH connection via Bastion, and no Linux-specific tooling or patterns are mentioned throughout the page.
Recommendations
  • Add links to Linux VM quickstart guides alongside the Windows VM links in the 'Next steps' section.
  • Include instructions or examples for connecting to Linux VMs via Bastion (e.g., SSH) in the relevant sections.
  • Ensure parity by mentioning both Windows and Linux scenarios when discussing Bastion usage.
  • Where possible, provide screenshots or examples that reference Linux environments as well as Windows.
GitHub Create Pull Request
Bastion Secure Your Azure Bastion Deployment ...zure-docs/blob/main/articles/bastion/secure-bastion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by mentioning RDP (Windows) connectivity and features (such as Kerberos authentication for domain-joined Windows VMs) before or more prominently than SSH/Linux equivalents. While there are references to connecting to Linux VMs and storing SSH keys, the examples and guidance are generally Windows-centric, with Windows-specific features (Kerberos, RDP, domain-joined VMs) described in detail and linked before Linux alternatives. There are no explicit Linux command-line or tool examples, and Linux security patterns are not discussed with the same depth as Windows ones.
Recommendations
  • Provide Linux-specific examples and guidance alongside Windows instructions, such as SSH configuration, Linux authentication methods, and Linux VM security best practices.
  • Include links to documentation for connecting to Linux VMs and securing Linux environments with Azure Bastion in sections where Windows features are described.
  • Balance the coverage of Windows and Linux tools and patterns, ensuring that Linux equivalents (e.g., SSH key management, Linux session recording, Linux authentication) are given equal prominence and detail.
  • Add explicit Linux command-line examples (e.g., using SSH from Linux/macOS terminals) and reference Linux-native security tools where relevant.
  • Where features are Windows-only (e.g., Kerberos for domain-joined VMs), clearly indicate this and provide Linux alternatives or note the absence of equivalent features.
GitHub Create Pull Request
Bastion Quickstart: Use Terraform to deploy Azure Bastion ...b/main/articles/bastion/quickstart-deploy-terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell example is given equal prominence and detail as the CLI example. This can be interpreted as a subtle Windows bias, as PowerShell is primarily a Windows tool, and no Linux-specific shell (e.g., Bash) or OS-specific instructions are mentioned. The order of tabs places Azure CLI first, which is cross-platform, but the inclusion of PowerShell as a primary alternative may reinforce a Windows-centric approach.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash commands where appropriate.
  • Clarify that PowerShell Core is available cross-platform, or note that the PowerShell example is primarily for Windows users.
  • Consider adding a note or tab for Linux/macOS users, highlighting any OS-specific steps or differences.
  • Ensure that all tooling and instructions are presented in a way that does not assume a Windows environment by default.
GitHub Create Pull Request
Bastion About VM connections and features ...Docs/azure-docs/blob/main/articles/bastion/vm-about.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features and examples before Linux equivalents, and by omitting explicit Linux instructions or links in key sections. For example, the 'Copy and paste' section only links to Windows VM instructions, and there is no mention of Linux VMs or their workflows in the main feature descriptions.
Recommendations
  • Add equivalent Linux VM documentation links and examples alongside Windows instructions, especially for features like copy/paste and file transfer.
  • Explicitly mention Linux support and workflows in each feature section, clarifying any differences or limitations.
  • Ensure that feature descriptions and quickstart guides provide parity for both Windows and Linux users, including references to SSH and Linux-native tools where appropriate.
GitHub Create Pull Request
Batch Move an Azure Batch account to another region ...cs/azure-docs/blob/main/articles/batch/account-move.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes moving an Azure Batch account using the Azure portal, with all instructions and examples focused on GUI interactions. There are no command-line examples, and no mention of cross-platform tools such as Azure CLI or PowerShell. The workflow implicitly assumes a Windows environment, as the Azure portal is most commonly accessed from Windows, and there is no guidance for Linux users or those preferring automation via CLI tools.
Recommendations
  • Add equivalent instructions for moving a Batch account using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for users who prefer scripting, but ensure Azure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that the Azure portal is accessible from any OS, and provide links or notes for Linux/macOS users.
  • Provide sample scripts for exporting, modifying, and deploying ARM templates using Azure CLI and/or PowerShell.
  • Clarify any OS-specific steps (e.g., unzipping files) and offer alternatives for Linux/macOS.
GitHub Create Pull Request
Batch Migrate Batch account certificates to Azure Key Vault ...in/articles/batch/batch-certificate-migration-guide.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page generally covers both Windows and Linux Batch pools, but there is a subtle Windows bias: in the FAQ section, the link to Windows documentation is listed before the Linux equivalent, and there are no concrete Linux-specific command examples or step-by-step instructions, especially for certificate handling. Linux users are told to 'run such commands' without examples, while Windows users are implicitly prioritized in documentation references.
Recommendations
  • Provide explicit Linux command-line examples (e.g., bash scripts, chmod usage) for certificate installation and access.
  • Ensure Linux documentation links are presented alongside or before Windows links when discussing cross-platform support.
  • Include step-by-step instructions for Linux users on how to handle certificate permissions and access, not just general guidance.
  • Add sample start task/job prep scripts for Linux environments.
  • Review and balance the order of platform references throughout the documentation to avoid implicit prioritization.
GitHub Create Pull Request
Batch Configure node endpoints in Azure Batch pool ...lob/main/articles/batch/pool-endpoint-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation alternates Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples first in each section. The introductory text also mentions RDP before SSH. The C# code samples for Windows pools use RDP and the Python samples for Linux pools use SSH, but there is no explicit parity in tool or scripting language recommendations (e.g., PowerShell vs Bash). The documentation does not provide command-line examples for either OS, but the ordering and emphasis slightly favor Windows.
Recommendations
  • Alternate the order of Windows and Linux examples in each section, or present them side-by-side to avoid implicit prioritization.
  • Explicitly mention both RDP (Windows) and SSH (Linux) together in introductory and summary sections.
  • Provide equivalent command-line examples for both Windows (PowerShell) and Linux (Bash), if relevant to the audience.
  • Ensure that tooling and terminology for both OSes are introduced with equal prominence.
  • Consider adding a table or summary comparing endpoint configuration for Windows and Linux pools to reinforce parity.
GitHub Create Pull Request
Batch Use the Batch Management .NET library to manage account resources ...cs/blob/main/articles/batch/batch-management-dotnet.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exclusively provides .NET (C#) code samples and instructions, which are most commonly used on Windows platforms. There are no Linux-specific examples, alternative tools, or cross-platform guidance. The documentation implicitly assumes a Windows development environment, with no mention of how to perform these tasks on Linux or using Linux-friendly tools (e.g., CLI, Bash, Python).
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash scripts to demonstrate how to manage Batch accounts and quotas on Linux.
  • Include Python SDK examples, as Python is widely used on Linux and is mentioned in the 'Next steps' section.
  • Explicitly state cross-platform compatibility of the .NET SDK and provide guidance for Linux/Mac users (e.g., using .NET Core/.NET 6+ on Linux).
  • Reference Linux-friendly authentication methods and environment setup steps.
  • Balance the order of examples so that Windows and Linux approaches are presented equally, or clarify that the .NET SDK is cross-platform.
GitHub Create Pull Request
Batch Azure Batch pool create event ...cs/blob/main/articles/batch/batch-pool-create-event.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Windows VM sizes and OS families before Linux equivalents, and by providing detailed configuration options for Windows (e.g., windowsConfiguration) without corresponding Linux configuration examples or details. There are no Linux-specific configuration examples or references to Linux tools or patterns.
Recommendations
  • Add explicit Linux configuration examples, such as a linuxConfiguration section analogous to windowsConfiguration, with details on settings relevant to Linux pools.
  • Ensure Linux VM sizes and configuration options are presented with equal prominence and detail as Windows options.
  • Provide links to Linux-specific documentation (e.g., Azure Linux VM images, configuration best practices) alongside Windows links.
  • Include example pool create event bodies for both Windows and Linux pools to illustrate parity.
  • Clarify in notes and tables which options are applicable to Linux, and provide guidance for Linux users where options differ.
GitHub Create Pull Request
CDN Quickstart - Create an Azure Content Delivery Network profile and endpoint ...docs/blob/main/articles/cdn/cdn-create-new-endpoint.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and does not provide any command-line examples. While this avoids explicit Windows-only tools like PowerShell, it implicitly favors Windows users by omitting Linux-friendly CLI instructions (such as Azure CLI or Bash). There are no examples or references to Linux-specific workflows, and no parity for users who prefer or require command-line automation, which is common in Linux environments.
Recommendations
  • Add Azure CLI examples for all major steps (creating CDN profile, endpoint, and resource cleanup), with sample commands that work on Linux, macOS, and Windows.
  • Explicitly mention that the Azure CLI can be used from any platform and provide links to installation instructions for Linux.
  • Where possible, provide Bash script snippets for automation, and clarify cross-platform compatibility.
  • Ensure that any references to deleting resources or managing them include both portal and CLI options.
GitHub Create Pull Request
Batch Migrate Azure Batch pools to the simplified compute node communication model ...ified-compute-node-communication-model-migration-guide.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific tools (RDP) before Linux equivalents (SSH) and does not provide any OS-specific examples or guidance for either platform. The mention of agent binaries distinguishes between Windows (.exe) and Linux, but does not provide parity in examples or troubleshooting steps for Linux users. There is a subtle Windows-first ordering in connectivity instructions and tool naming.
Recommendations
  • Provide explicit examples for both Windows and Linux environments when discussing connectivity (e.g., show both RDP and SSH commands or configuration steps).
  • When mentioning agent binaries, clarify usage or troubleshooting for both platforms, not just naming conventions.
  • Ensure that Linux tools and patterns (such as SSH, Linux agent management, firewall configuration) are mentioned with equal prominence and detail as Windows equivalents.
  • Consider adding a dedicated section for platform-specific migration steps or FAQs, addressing common Linux scenarios.
GitHub Create Pull Request
Communication Services Teams Phone extensibility provisioning .../interop/tpe/teams-phone-extensibility-provisioning.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses on Teams Phone extensibility provisioning and authorization, but all procedural references (such as cmdlets and admin roles) assume a Windows-centric environment. There are no examples or guidance for Linux or cross-platform administration, and Windows terminology (cmdlet, Teams Admin) is used exclusively. No Linux shell, CLI, or cross-platform tool examples are provided.
Recommendations
  • Include equivalent Linux shell (bash) or Azure CLI examples for provisioning and authorization steps.
  • Clarify whether the described cmdlets and admin tools are available cross-platform, and provide links or instructions for Linux/macOS users.
  • Mention and document any cross-platform tools (e.g., Azure CLI, Microsoft Graph API via REST) that can be used for these tasks.
  • Avoid using Windows-specific terminology (such as 'cmdlet') without also referencing cross-platform alternatives.
  • Add a section explicitly addressing cross-platform support and any limitations for Linux or macOS administrators.
GitHub Create Pull Request
Batch Migrate low-priority VMs to spot VMs in Batch ...s/batch/low-priority-vms-retirement-migration-guide.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Azure CLI and PowerShell methods for migrating Batch pools, but PowerShell (a Windows-centric tool) is given as the only alternative automation method after CLI, with no mention of Bash, Linux shell scripting, or cross-platform SDKs. PowerShell examples are provided in detail, while Linux-specific automation (e.g., Bash scripts) is absent. The CLI examples use Ubuntu images, but the automation tooling guidance is Windows-first, and PowerShell is highlighted before any Linux-native alternatives.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for automation tasks.
  • Mention cross-platform SDKs (e.g., Python, .NET, Java) as automation alternatives alongside PowerShell.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • If PowerShell is presented, also provide equivalent Bash or shell script snippets for parity.
  • Add troubleshooting and validation steps using Linux-native tools (e.g., jq, curl) where appropriate.
GitHub Create Pull Request
Batch Associate Azure Batch accounts with network security perimeter ...blob/main/articles/batch/network-security-perimeter.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as a primary automation option before Azure CLI, and by providing detailed PowerShell examples alongside Azure CLI. There are no explicit Linux shell (bash) examples, nor are Linux-specific patterns or tools mentioned. The use of PowerShell may implicitly favor Windows users, as PowerShell is the default shell on Windows, while bash is more common on Linux. The Azure portal instructions are platform-neutral, but the scripting examples do not address Linux users directly.
Recommendations
  • Add bash shell examples for all CLI commands, showing usage in a typical Linux environment.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any platform-specific notes if needed.
  • Where PowerShell is used, clarify that PowerShell Core is cross-platform, or provide equivalent bash scripts for Linux users.
  • Consider listing Azure CLI (bash) instructions before PowerShell, or present both side-by-side to avoid implicit prioritization.
  • Include troubleshooting or environment setup notes for Linux users, such as installing Azure CLI or configuring authentication.
GitHub Create Pull Request
Batch Configure managed identities in Batch pools ...ocs/blob/main/articles/batch/managed-identity-pools.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias. In the section on retrieving managed identity tokens within Batch nodes, the Windows/PowerShell example is presented before the Linux/Bash equivalent. Additionally, PowerShell is mentioned explicitly as the scripting tool for Windows, while Bash is used for Linux. However, both examples are present, and the rest of the documentation generally maintains cross-platform parity, including references to both Windows and Linux in pool creation and configuration steps.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • Explicitly mention that both Windows and Linux nodes are supported throughout the documentation, especially in code and script examples.
  • Where possible, provide examples using cross-platform tools (e.g., Azure CLI) before platform-specific tools like PowerShell.
  • Include a table or section summarizing equivalent commands for both Windows and Linux to improve clarity for all users.
GitHub Create Pull Request
Batch Quickstart: Create an Azure Batch account using Terraform ...ocs/blob/main/articles/batch/quick-create-terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell examples are given equal prominence and use Windows-specific syntax (e.g., `$variable=$(...)`), which is not portable to Linux/macOS. There is no explicit mention of Linux shell alternatives for PowerShell commands, and PowerShell is a Windows-centric tool. The documentation does not clarify which commands are cross-platform or provide bash/zsh equivalents for PowerShell-specific steps.
Recommendations
  • Clearly indicate which commands are cross-platform and which are Windows-specific.
  • For every PowerShell example, provide an equivalent bash/zsh (Linux/macOS) command if possible.
  • Note that Azure CLI is available on all platforms and recommend it as the default for cross-platform usage.
  • If PowerShell is mentioned, clarify that it is available on Linux/macOS, but provide bash syntax for variable assignment and command execution.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Batch Create a simplified node communication pool without public IP addresses ...tch/simplified-node-communication-pool-no-public-ip.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides troubleshooting commands for both Windows and Linux, but the Windows PowerShell example (Test-NetConnection) is listed first, and the command is more detailed. The Linux example (nc) is present but less emphasized. There are no other explicit Windows-only tools or patterns, and the rest of the documentation is platform-neutral, focusing on REST API, ARM templates, and Azure portal workflows.
Recommendations
  • Present Linux and Windows troubleshooting commands with equal detail and prominence, possibly side-by-side.
  • Expand Linux examples to match the verbosity and explanation given to Windows commands (e.g., explain nc output, add options for more detailed diagnostics).
  • Where possible, provide Bash/CLI equivalents for any PowerShell scripts or commands.
  • Consider listing Linux commands first or in parallel to avoid implicit prioritization of Windows.
  • Explicitly mention that all steps (portal, REST API, ARM templates) are cross-platform unless otherwise noted.
GitHub Create Pull Request
Business Process Tracking Create Pipelines for Infrastructure, CI, and CD ...s-tracking/set-up-continuous-integration-deployment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently references Visual Studio Code and Azure DevOps, but all local development and command-line instructions assume a Windows environment. There is no mention of Linux or macOS equivalents, nor are there examples or guidance for users on those platforms. The use of terms like 'command prompt' and screenshots showing Windows UI elements further reinforce a Windows-centric approach. No PowerShell-specific commands are present, but the lack of Linux shell (bash) or cross-platform terminal instructions is notable.
Recommendations
  • Explicitly mention that Visual Studio Code and Azure DevOps are cross-platform and can be used on Windows, Linux, and macOS.
  • Replace 'command prompt' with 'terminal' and clarify that the steps apply to any OS with Git and VS Code installed.
  • Provide screenshots or instructions for Linux/macOS environments where UI or file paths differ.
  • Include bash/zsh command examples alongside the current instructions, especially for Git operations.
  • Add a note about installing prerequisites (VS Code, Git, Azure CLI) on Linux/macOS.
  • Ensure that all tooling and extensions referenced are available and supported on Linux/macOS, and link to relevant installation guides.
GitHub Create Pull Request
CDN Get started with the Azure CDN SDK for Node.js .../azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. Visual Studio Code is mentioned as the preferred editor, and the only debugger setup example is for VS Code (which is most popular on Windows, though cross-platform). The 'Next Steps' section highlights PowerShell for further CDN management, with no mention of Linux-native tools (such as Bash, CLI, or shell scripting). No explicit Linux examples or references to Linux-specific workflows are provided.
Recommendations
  • Include examples of running the Node.js application from Linux/macOS terminals, such as Bash or zsh.
  • Mention and provide guidance for using other editors and debuggers common on Linux (e.g., Vim, Emacs, JetBrains IDEs).
  • Add instructions for passing command-line arguments in debuggers/editors on Linux/macOS.
  • In the 'Next Steps' section, provide links to Azure CLI or Bash scripting documentation for CDN management, alongside PowerShell.
  • Clarify that all steps are cross-platform and explicitly state compatibility with Linux/macOS environments.
GitHub Create Pull Request
CDN Quickstart: Create a profile and endpoint - Resource Manager template .../main/articles/cdn/create-profile-endpoint-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides deployment instructions using Azure CLI, PowerShell, and Portal. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its inclusion as a primary method (with full example) may indicate a mild Windows bias. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The order of examples (CLI, then PowerShell, then Portal) is reasonable, but the PowerShell example could be perceived as Windows-centric, especially since no bash-specific guidance is given.
Recommendations
  • Add explicit bash shell examples for Linux users, demonstrating equivalent commands and environment setup.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary notes about platform differences.
  • If PowerShell is included, consider mentioning PowerShell Core (cross-platform) or clarifying its usage on Linux/macOS.
  • Review the documentation for any assumptions about the user's operating system and ensure parity for Linux users in instructions and troubleshooting.
GitHub Create Pull Request
CDN Quickstart: Create an Azure CDN profile and endpoint using Terraform ...main/articles/cdn/create-profile-endpoint-terraform.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is presented as a primary tab alongside CLI, suggesting parity. However, there is a subtle Windows bias: PowerShell is a Windows-centric tool, and its inclusion as a top-level tab (rather than, for example, Bash or Linux shell) may imply preference for Windows users. No explicit Linux shell or Bash examples are given, and the CLI examples use variable assignment syntax compatible with Bash but do not clarify Linux usage. There are no references to Linux-specific tools or workflows.
Recommendations
  • Add explicit Bash/Linux shell examples for verification steps, clarifying compatibility with Linux environments.
  • Include notes or tabs for Mac/Linux users, specifying any differences in command syntax or environment setup.
  • Consider reordering tabs so that Azure CLI (cross-platform) appears first, or add Bash as a separate tab to emphasize Linux parity.
  • Mention that Azure CLI is available on Windows, Linux, and macOS, and provide installation links for all platforms.
  • If PowerShell is included, clarify that PowerShell Core is cross-platform, or provide examples using native Linux tools where appropriate.
GitHub Create Pull Request
Cloud Shell Get started with Azure Cloud Shell .../blob/main/articles/cloud-shell/get-started/classic.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides examples for both Azure CLI (Bash) and Azure PowerShell, but PowerShell is consistently presented alongside or immediately after CLI, and some advanced examples (such as navigating the Azure drive and using Get-AzCommand) are only shown for PowerShell. The 'Next steps' section lists PowerShell before CLI, suggesting a slight preference for Windows/PowerShell users. There are no Linux-specific tools, patterns, or troubleshooting tips, and the document does not mention platform-specific differences or considerations for Linux users.
Recommendations
  • Ensure parity by providing advanced Azure CLI examples similar to those given for PowerShell (e.g., context-specific command discovery).
  • Alternate the order of CLI and PowerShell examples or present them in parallel tabs to avoid implicit prioritization.
  • Add notes or tips for Linux users, such as file path conventions, shell environment differences, or troubleshooting steps.
  • Include links to Linux-specific documentation or resources in the 'Next steps' section.
  • Explicitly state that both Bash and PowerShell are fully supported and highlight any differences in usage or capabilities.
GitHub Create Pull Request
Cloud Shell Get started with Azure Cloud Shell using persistent storage ...b/main/articles/cloud-shell/get-started/new-storage.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Bash (Linux) and PowerShell (Windows) options for Azure Cloud Shell, but PowerShell is mentioned equally or slightly more prominently. Examples and tips are provided for both Azure CLI (Bash) and Azure PowerShell, but PowerShell-specific features (such as the Azure drive and context-specific commands) are described in more detail. The 'Next steps' section lists Azure PowerShell before Azure CLI, suggesting a subtle Windows-first ordering.
Recommendations
  • Ensure equal depth and detail for both Bash/Azure CLI and PowerShell examples, including advanced Bash usage where applicable.
  • Alternate the order of presenting Bash/Azure CLI and PowerShell examples to avoid implicit prioritization.
  • Highlight Linux/Bash-specific features or tips, such as file system navigation, scripting, or integration with other Linux tools.
  • In the 'Next steps' section, list Azure CLI and Azure PowerShell in alphabetical order or alternate their order across documentation pages.
  • Where PowerShell-specific features (e.g., Azure drive) are mentioned, consider providing Bash/Linux equivalents or explicitly noting their absence.
GitHub Create Pull Request
Cloud Shell What is Azure Cloud Shell? .../azure-docs/blob/main/articles/cloud-shell/overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation mentions both Bash and PowerShell as available shell experiences in Azure Cloud Shell, but PowerShell and Azure PowerShell cmdlets are referenced before Bash and Azure CLI in several places. The access points list puts Azure PowerShell documentation before Azure CLI documentation, and deployment examples mention Azure PowerShell before Azure CLI. This ordering subtly prioritizes Windows-centric tools and workflows, which may imply a bias toward Windows users.
Recommendations
  • Alternate the order of Bash/Azure CLI and PowerShell references to avoid implying priority.
  • Ensure examples and documentation links for both Bash/Azure CLI and PowerShell are provided equally and in parallel.
  • Explicitly mention Linux-friendly workflows and tools (e.g., scripting with Bash, using Linux utilities) alongside PowerShell examples.
  • In lists, avoid consistently listing Windows/PowerShell tools before Linux/Bash equivalents.
  • Highlight that Cloud Shell runs on a Linux host and that Bash is a first-class experience.
GitHub Create Pull Request
Communication Services Enable Closed captions with Teams Interoperability ...on-services/concepts/interop/enable-closed-captions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation references Teams policies with links to PowerShell modules (Set-CsTeamsMeetingPolicy, Set-CsTeamsCallingPolicy), which are primarily managed via Windows-centric tools. There is no mention of Linux equivalents or cross-platform management options for these policies. Additionally, the supported SDKs list 'Windows' before other platforms, and there are no Linux-specific examples or guidance provided.
Recommendations
  • Include information about managing Teams policies via cross-platform tools (e.g., Microsoft Graph API) alongside or instead of PowerShell references.
  • Add explicit mention of Linux support for Azure Communication Services SDKs, if available, and provide Linux-specific usage examples.
  • Ensure that platform lists (e.g., supported SDKs) do not prioritize Windows unless there is a technical reason, and clarify parity across platforms.
  • Where PowerShell or Windows tools are referenced, provide alternatives or note limitations for non-Windows users.
GitHub Create Pull Request
Communication Services Messaging Connect overview ...mmunication-services/concepts/sms/messaging-connect.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a subtle Windows bias by exclusively referencing the Azure portal (a web UI most commonly used on Windows) for provisioning and management steps, and by omitting any Linux-specific or cross-platform command-line examples (such as Azure CLI, Bash, or PowerShell). All SDK code samples are in C# and JavaScript, with no mention of Linux-friendly languages or tools (e.g., Python, Bash, Azure CLI). There is no guidance for Linux users on how to perform provisioning or management tasks outside the portal, nor are there any examples using Linux-native tools.
Recommendations
  • Add Azure CLI and/or Bash examples for provisioning Messaging Connect numbers and sending SMS, alongside or before portal instructions.
  • Include Python SDK examples once available, and mention their roadmap.
  • Explicitly state that all steps can be performed from any OS, and provide parity for Linux/macOS users in instructions and screenshots.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) in the developer experience section, not just the portal.
  • Add troubleshooting and configuration notes relevant to Linux environments (e.g., environment variables, authentication setup).
GitHub Create Pull Request
Communication Services Subscribe to events in Job Router ...cation-services/how-tos/router-sdk/subscribe-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias in its quick-start instructions. When instructing users to create a new C# application, it lists 'cmd, PowerShell, or Bash' as possible console windows, but the order places Windows tools first. More importantly, all code and command-line examples use .NET (dotnet CLI) and C#, which are cross-platform but are more familiar to Windows users. There are no Linux- or macOS-specific instructions, nor are there any examples using Linux-native tools or scripting languages (e.g., Python, Bash scripts) for subscribing to or consuming events. The documentation does not mention or demonstrate Linux-specific patterns or troubleshooting.
Recommendations
  • Explicitly state that all dotnet CLI commands and C# code are fully cross-platform and supported on Linux and macOS as well as Windows.
  • When listing console options, rotate or randomize the order, or explicitly say 'cmd, PowerShell (Windows), or Bash (Linux/macOS)'.
  • Provide at least one example using a Linux-native scripting language (e.g., Python) to consume messages from Azure Storage Queue, or link to such examples.
  • Include troubleshooting notes or tips for Linux users (e.g., installing dotnet SDK on Linux, permissions for Bash, etc.).
  • Consider adding a section or callout highlighting parity and support for Linux and macOS environments.
GitHub Create Pull Request
Communication Services include file ...s/quickstarts/router/includes/router-quickstart-net.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows console environments (cmd, PowerShell) before Bash when describing where to run commands. All command-line instructions use the 'dotnet' CLI, which is cross-platform, but there are no Linux-specific examples, troubleshooting notes, or references to Linux package managers. The documentation does not mention Linux-specific considerations or provide parity for Linux users beyond the generic mention of Bash.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console environments.
  • Add explicit instructions or troubleshooting notes for Linux users, such as permissions, environment setup, or common issues.
  • Include references to Linux package managers (e.g., apt, yum) for installing .NET, or link to official .NET installation guides for Linux.
  • Provide sample output screenshots or terminal commands from a Linux environment to demonstrate parity.
  • Clarify that the instructions are cross-platform and highlight any platform-specific differences where relevant.
GitHub Create Pull Request
Communication Services include file ...ices/quickstarts/includes/manage-teams-identity-net.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation refers to 'console window (such as cmd, PowerShell, or Bash)', listing Windows shells first and omitting Linux-specific examples or instructions. All command-line examples use generic 'dotnet' commands, but there is no mention of Linux-specific tools, shells, or environment setup. There are no examples of how to run or configure the application on Linux, nor any troubleshooting or notes for Linux users.
Recommendations
  • Explicitly mention Linux shells (e.g., Bash, Zsh) first or equally alongside Windows shells.
  • Provide Linux-specific instructions or notes, such as how to set environment variables in Bash (e.g., export AAD_CLIENT_ID=...) and how to run the application on Linux.
  • Include troubleshooting tips for common Linux issues (e.g., permissions, .NET SDK installation).
  • Add a section or note on cross-platform compatibility, clarifying that the instructions work on both Windows and Linux, and highlight any platform-specific differences.
GitHub Create Pull Request
Communication Services Send email with SMTP and XOAuth2 using .NET ...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias by listing Windows-specific console environments ('cmd', 'PowerShell') before Linux equivalents ('Bash') and not providing any Linux-specific instructions or examples. All code and tooling references are platform-neutral (.NET Core, MailKit), but the guidance and examples do not address Linux-specific setup, troubleshooting, or alternative workflows.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms in prerequisites and instructions.
  • Provide Linux/macOS-specific terminal commands and environment setup steps alongside Windows examples.
  • Include troubleshooting notes or tips for common Linux issues (e.g., permissions, package installation).
  • List Bash (or other Linux shells) first or equally when referencing console windows.
  • Clarify that .NET Core and MailKit are cross-platform and provide links to Linux/macOS installation guides.
GitHub Create Pull Request
Communication Services include file ...entity/includes/entra-id/support-entra-id-users-net.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash, and does not provide any Linux-specific instructions or examples for environment variable setup, text editor usage, or running the application. All examples and tooling are generic to .NET, but the workflow assumes familiarity with Windows environments.
Recommendations
  • Explicitly mention Linux and macOS consoles (e.g., Terminal, zsh, bash) alongside Windows ones.
  • Provide examples of setting environment variables in Linux/macOS (e.g., export ENTRA_CLIENT_ID=...) as well as Windows (set ENTRA_CLIENT_ID=...).
  • Suggest cross-platform text editors (e.g., nano, vim, VS Code) for editing Program.cs.
  • Clarify that all dotnet CLI commands work on Linux/macOS and Windows.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, SDK installation).
GitHub Create Pull Request
Communication Services Additional Prerequisites ...ity/includes/active-directory/service-principal-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page consistently references Windows-specific resources and examples, particularly in the section about enabling managed identities for Azure resources. All linked quickstart articles are for Windows VMs, and there are no equivalent Linux VM examples or instructions. The guidance for setting environment variables is generic, but the overall setup flow and linked resources prioritize Windows environments, omitting Linux-specific instructions and parity.
Recommendations
  • Include links to equivalent quickstart guides for Linux VMs for managed identity configuration using Azure portal, PowerShell, CLI, ARM templates, and SDKs.
  • Add explicit examples or notes for setting environment variables in Linux shells (e.g., export commands for Bash/Zsh).
  • Ensure that all instructions and references are platform-neutral or provide parallel steps for both Windows and Linux environments.
  • Mention Linux development environments (e.g., VS Code on Linux, JetBrains IDEs) alongside Windows-specific tools like Visual Studio.
GitHub Create Pull Request
Communication Services Overview ...ity/includes/active-directory/service-principal-net.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows terminals (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. There are no explicit Linux-specific instructions, troubleshooting, or examples, and no mention of Linux package managers or environment setup. All commands are cross-platform (dotnet CLI), but the documentation does not provide parity for Linux users beyond mentioning Bash in passing.
Recommendations
  • List Bash (or Linux terminal) first when mentioning terminal options, or present all platforms equally.
  • Add explicit instructions for Linux users, such as verifying .NET SDK installation via package managers (e.g., apt, yum) and environment setup.
  • Include troubleshooting steps for common Linux issues (e.g., permissions, environment variables).
  • Clarify that all commands are cross-platform and provide links to .NET installation guides for Linux.
  • Consider adding a note or section on running the sample in Linux environments, including any OS-specific caveats.
GitHub Create Pull Request
Communication Services include file ...ces/quickstarts/includes/telemetry-app-insights-net.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation refers to 'cmd, PowerShell, or Bash' as possible console windows, but lists Windows shells first and does not provide any Linux-specific instructions, examples, or troubleshooting. All command-line examples use generic 'dotnet' commands without platform-specific notes, and there is no mention of Linux tools, editors, or environment setup. The guidance assumes parity but does not demonstrate it.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms in prerequisites and setup steps.
  • Provide Linux/macOS-specific instructions or notes where relevant (e.g., environment variable setup, file permissions, common editors like nano/vim).
  • Include troubleshooting tips for common Linux issues (e.g., SDK installation, PATH configuration).
  • List Bash before or alongside Windows shells to avoid Windows-first ordering.
  • Add example commands for setting environment variables in Bash/zsh (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...) and running the app.
  • Reference cross-platform editors (VS Code, nano, vim) when suggesting how to edit Program.cs.
GitHub Create Pull Request
Communication Services Answer Teams Phone calls from Call Automation ...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a notable Windows bias. Key setup steps, such as creating a Teams resource account and associating it with Azure Communication Services, rely exclusively on PowerShell commands and reference PowerShell modules. The DevTunnel setup is shown only with PowerShell commands, with no mention of Linux/macOS alternatives or CLI parity. There are no Linux/macOS-specific instructions or examples, and Windows tooling is presented first and exclusively.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as Azure CLI or Bash commands where possible.
  • Reference cross-platform tools for DevTunnel setup, or clarify if the PowerShell commands work on Linux/macOS (e.g., via PowerShell Core).
  • Offer guidance for creating and managing Teams resource accounts via REST API or other cross-platform methods if available.
  • Explicitly state platform requirements and limitations for each step.
  • Add Linux/macOS examples alongside Windows/PowerShell ones, or at least link to platform-specific guides.
GitHub Create Pull Request
Communication Services Quickstart - How to call to Teams user from an Android app ...ideo-calling/includes/teams-user/teams-user-android.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation references enabling Teams Phone features via PowerShell and links to Windows-centric Teams deployment guides, without mentioning Linux/macOS alternatives or parity. No Linux/macOS-specific instructions or examples are provided for Teams administration tasks, which may create friction for non-Windows users.
Recommendations
  • Include instructions or links for managing Teams users and licenses via cross-platform tools (e.g., Microsoft 365 admin center web UI) or clarify PowerShell Core support on Linux/macOS.
  • Explicitly state whether Teams Phone license and Enterprise Voice enabling can be performed from non-Windows platforms, and provide relevant guidance.
  • Add notes or sections for Linux/macOS users on how to complete prerequisite steps, especially where PowerShell or Windows-only tools are referenced.
GitHub Create Pull Request
Communication Services Teams Phone Extensibility ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits a notable Windows bias, primarily through exclusive use of PowerShell cmdlets and references to Windows-centric tools (e.g., Teams PowerShell, Azure PowerShell modules, Teams Admin Center). All administrative and provisioning examples are given using PowerShell commands, with no mention of Linux/macOS equivalents or cross-platform alternatives. The Azure CLI is referenced, but only in the context of installing PowerShell modules. There are no bash, shell, or Linux-native command examples, and no guidance for non-Windows users on how to perform these tasks.
Recommendations
  • Provide equivalent examples using Azure CLI and Microsoft Graph API for provisioning and managing Teams Resource Accounts, as these are cross-platform.
  • Explicitly state platform requirements for PowerShell-based steps, and offer alternatives for Linux/macOS users (e.g., using Graph API, Azure CLI, or REST calls).
  • Include bash or shell script examples where possible, especially for steps that can be accomplished via REST or CLI.
  • Clarify which steps require Windows-only tools and suggest workarounds or alternative workflows for non-Windows environments.
  • Add a section or callout for Linux/macOS users, describing how to complete key tasks without relying on Windows tools.
GitHub Create Pull Request
Communication Services Quickstart - Make a call to Teams user from an iOS app ...ce-video-calling/includes/teams-user/teams-user-ios.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where enabling Teams Phone features for users is described only via a PowerShell-based process, with no mention of Linux/macOS-compatible alternatives. The Teams deployment link also points to a Windows-centric installation guide. However, the remainder of the quickstart is focused on iOS development and does not reference Windows-specific tools or workflows.
Recommendations
  • Provide Linux/macOS-compatible instructions for enabling Teams Phone features, or clarify if these steps can only be performed on Windows.
  • Include links to cross-platform or web-based administration tools (e.g., Microsoft 365 Admin Center) for managing Teams users and licenses.
  • Explicitly state platform requirements for administrative steps, so Linux/macOS users are aware of any limitations.
  • If PowerShell is required, suggest alternatives such as running PowerShell Core on Linux/macOS, or using remote administration.
GitHub Create Pull Request
Container Apps Code to cloud options in Azure Container Apps .../main/articles/container-apps/code-to-cloud-options.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio and Visual Studio Code (both Microsoft products, with Visual Studio being Windows-only) are emphasized as primary code editor options for deploying to Azure Container Apps. The CLI section mentions both PowerShell and Bash, but PowerShell is listed first, and there are no explicit Linux/macOS-specific examples or tool recommendations. No Linux-first editors (e.g., JetBrains IDEs, Vim, Emacs) or Linux/macOS deployment workflows are mentioned. The resources and next steps sections also prioritize Visual Studio and Visual Studio Code, reinforcing a Windows-centric workflow.
Recommendations
  • Add explicit examples and guidance for Linux/macOS users, including using Bash and other shell environments.
  • Include alternative code editors popular on Linux/macOS (e.g., JetBrains IDEs, Vim, Emacs) in the 'Code editor' section.
  • Provide parity in CLI instructions, showing both PowerShell and Bash commands side-by-side.
  • Mention Docker and container tooling installation steps for Linux/macOS platforms.
  • Balance resource links to include Linux/macOS-focused tutorials and workflows.
GitHub Create Pull Request
Communication Services References - How to collect diagnostic audio recordings ...ferences/how-to-collect-diagnostic-audio-recordings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively providing build instructions for the unpack_aecdump tool using Windows-specific prerequisites (Visual Studio 2022, Windows depot_tools instructions) and referencing the output as a Windows executable (.exe). No Linux or macOS build instructions, prerequisites, or usage examples are provided, which may hinder non-Windows users from completing the task.
Recommendations
  • Add Linux/macOS build instructions for unpack_aecdump, including required packages and toolchains (e.g., GCC/Clang, Python, depot_tools setup for Unix).
  • Reference the output binary as platform-agnostic (e.g., unpack_aecdump or unpack_aecdump.exe/unpack_aecdump depending on OS).
  • Include example commands for running unpack_aecdump on Linux/macOS.
  • Mention any platform-specific caveats or dependencies for non-Windows users.
  • Reorder or parallelize instructions so that Windows and Linux/macOS users see relevant information simultaneously.
GitHub Create Pull Request
Communication Services Detect sensitive data using Azure AI ...ion-services/samples/email-detect-sensitive-content.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns first (e.g., 'cmd', 'PowerShell', registry queries), and omits Linux/macOS equivalents for key setup steps. The initial prerequisite check uses a Windows registry command to verify .NET installation, with no mention of how to perform this check on Linux or macOS. Console examples list Windows shells before Bash, and all code samples are in C#/.NET, which is cross-platform but the setup instructions assume a Windows environment.
Recommendations
  • Provide Linux/macOS equivalents for .NET installation checks (e.g., 'dotnet --info' or package manager commands).
  • List Bash or Linux/macOS terminal options alongside or before Windows shells when referencing console windows.
  • Include notes or examples for Linux/macOS users in all setup and environment variable instructions.
  • Clarify that the C#/.NET code is cross-platform and provide links or brief instructions for running on Linux/macOS.
  • Avoid Windows registry commands unless alternatives are given for other platforms.
GitHub Create Pull Request
Communication Services Automate email resource management ...nication-services/samples/email-resource-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias by prioritizing PowerShell examples and commands, which are native to Windows. The clean-up instructions provide PowerShell commands for deleting Email Communication Services and Domain resources, but do not offer equivalent Azure CLI or bash examples for Linux/macOS users. The structure and ordering also place PowerShell and Windows-centric tooling before cross-platform alternatives.
Recommendations
  • Provide Azure CLI or bash equivalents for all resource deletion commands currently shown only in PowerShell.
  • Ensure that Linux/macOS-friendly instructions are included and clearly labeled alongside Windows/PowerShell examples.
  • Consider reordering examples so that cross-platform tools (Azure CLI, Python) are presented first or in parallel with PowerShell.
  • Explicitly state platform compatibility for each command or script.
GitHub Create Pull Request
Communication Services include file ...ludes/email-resource-management-azurecli-powershell.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily biased towards Windows and PowerShell. All code samples are written in PowerShell syntax, and the workflow is presented as a PowerShell script. Prerequisite checks and installation links are Windows-centric, with no mention of Linux/macOS equivalents or Bash scripting. There are no examples or guidance for running these automation steps on Linux or macOS, despite Azure CLI being cross-platform.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, especially for Azure CLI commands.
  • Include installation instructions and prerequisite checks for Azure CLI and Azure PowerShell on Linux and macOS.
  • Clarify which steps are PowerShell-specific and which can be run in any shell, and offer alternatives where possible.
  • Reorder or balance examples so that Linux/macOS workflows are presented alongside or before Windows/PowerShell ones.
  • Use generic Azure CLI examples where possible, since CLI is cross-platform.
GitHub Create Pull Request
Cost Management Billing Software costs not included in Azure savings plans ...nt-billing/savings-plan/software-costs-not-included.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses almost exclusively on Windows VM software costs and related meters, with no mention of Linux VM software costs or examples. The content assumes the reader is using Windows, omitting any discussion of Linux or open-source software licensing in the context of Azure savings plans.
Recommendations
  • Add a section explicitly addressing Linux VM software costs, even if to clarify that Linux VMs typically do not incur additional software charges beyond infrastructure.
  • Include examples or tables for Linux VM meters if applicable, or state clearly that Linux VMs are not affected by the listed software meters.
  • Provide parity in documentation by mentioning both Windows and Linux scenarios when discussing savings plans and software costs.
  • Consider adding a brief comparison table showing differences in software cost treatment between Windows and Linux VMs under Azure savings plans.
GitHub Create Pull Request
Communication Services Include file ...es/samples/includes/call-automation-azure-openai-js.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation frequently references Windows-specific tools and workflows, such as PowerShell and Windows terminal, and lists them before mentioning generic or Linux/macOS equivalents. The instructions for running commands and opening terminals are Windows-centric, with no explicit Linux/macOS examples or terminal references.
Recommendations
  • Explicitly mention Linux/macOS terminal usage alongside PowerShell and Windows terminal.
  • Provide example commands for bash/zsh where relevant, especially for steps like opening the terminal and running npm scripts.
  • Clarify that all commands (git, npm, devtunnel) work in Linux/macOS terminals and provide any necessary platform-specific notes.
  • Add screenshots or terminal prompts for Linux/macOS users to improve parity.
  • Avoid listing Windows tools first; use neutral language like 'Open a terminal (PowerShell, Command Prompt, Terminal, etc.)'.
GitHub Create Pull Request
Communication Services include file ...mples/includes/email-resource-management-powershell.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and syntax. The prerequisite check and installation instructions reference PowerShell and Windows-specific guidance, with no mention of Bash, Azure CLI, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the documentation implicitly assumes the user is running Windows or PowerShell Core.
Recommendations
  • Provide equivalent Azure CLI examples for all major steps (resource creation, DNS management, domain verification, linking).
  • Clarify that Azure PowerShell can run on Linux/macOS via PowerShell Core, and provide installation instructions for those platforms.
  • Include a section comparing PowerShell and Azure CLI, helping users choose the best tool for their OS.
  • Add explicit Bash/Azure CLI scripts for Linux/macOS users, or at least note how to adapt the PowerShell scripts for cross-platform use.
  • Update prerequisite checks to include Linux/macOS environments and instructions for verifying PowerShell Core or Azure CLI installation.
GitHub Create Pull Request
Communication Services Tutorial - Prepare a web app for Azure Communication Services (Node.js) ...communication-services/tutorials/building-app-start.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation exhibits Windows bias in several areas: installation instructions for Node.js, nvm, and npm are Windows-specific and link only to Windows setup guides; PowerShell commands are provided for nvm usage without any equivalent bash/zsh instructions for Linux/macOS; file path examples use Windows conventions; and screenshots and workflow descriptions assume Windows environments. There are no explicit instructions or examples for Linux or macOS users, which may cause confusion or friction for those on non-Windows platforms.
Recommendations
  • Provide parallel instructions and examples for Linux and macOS, including links to official Node.js/nvm/npm setup guides for those platforms.
  • Include bash/zsh command examples for nvm usage alongside PowerShell commands.
  • Use platform-agnostic or dual file path examples (e.g., C:\... and ~/...) where appropriate.
  • Add notes or callouts clarifying any platform-specific steps, and ensure screenshots or UI references are relevant for all supported platforms.
  • Explicitly state that the tutorial is cross-platform and provide troubleshooting tips for common Linux/macOS issues.
GitHub Create Pull Request
Confidential Computing Secure Key Release with Azure Key Vault and application on Confidential VMs with AMD SEV-SNP ...idential-computing/skr-flow-confidential-vm-sev-snp.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. While both Linux and Windows are mentioned for the guest attestation client, scripting examples for performing the key release operation are provided only in PowerShell, which is primarily a Windows tool (though available on Linux, it's less common in Linux workflows). The instructions for obtaining managed identity object IDs mention PowerShell first, and the main example for the key release operation is a PowerShell script, with no equivalent Bash, Python, or Linux-native example. Windows-specific tools (e.g., VC_redist.x64.exe) are referenced in the Windows section, and Windows instructions are often presented before or more prominently than Linux equivalents.
Recommendations
  • Provide a Bash or Python example for the key release operation, demonstrating how to perform the HTTP request and handle JWTs on Linux.
  • When listing ways to retrieve managed identity object IDs, mention Azure CLI and Linux-native tools before or alongside PowerShell.
  • Ensure that instructions and examples for both Windows and Linux are presented with equal prominence and in parallel tabs/sections.
  • Clarify that PowerShell Core is cross-platform, but also offer alternatives more familiar to Linux users.
  • Include troubleshooting steps and package installation instructions for Linux environments where PowerShell is not available.
GitHub Create Pull Request
Connectors Integrate and manage security operations & Microsoft Graph Security ...ecurity-operations-create-api-microsoft-graph-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently references the Azure portal and Logic App Designer, which are primarily accessed via web browsers and are platform-agnostic. However, all step-by-step instructions and examples assume use of the Azure portal, with no mention of Linux/macOS-specific tooling, CLI, or automation options. There are no examples using Azure CLI, Bash, or other Linux-native tools, nor are alternatives to the portal (such as az logicapp commands) discussed. Windows-centric terms (e.g., Outlook connector, Power Automate, Power Apps) are mentioned before any Linux alternatives, and no Linux/macOS-specific guidance is provided.
Recommendations
  • Add examples using Azure CLI (az logicapp ...) for creating and managing Logic Apps and Microsoft Graph Security connections.
  • Include instructions for performing key tasks (e.g., authentication, connector setup) via command line or automation scripts suitable for Linux/macOS users.
  • Mention cross-platform alternatives to Outlook connector (e.g., SMTP, SendGrid) for sending alerts.
  • Explicitly state that all steps can be performed from any OS via browser, and clarify any OS-specific requirements if present.
  • Provide parity in examples, showing both portal and CLI/script approaches side by side.
GitHub Create Pull Request
Communication Services Migrating from Twilio Conversations Chat to Azure Communication Services Chat C# ...orials/includes/twilio-to-acs-chat-android-tutorial.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas: Visual Studio is listed as the only required IDE, and the only package installation example uses PowerShell syntax ('dotnet add package'), which is most commonly associated with Windows environments. There is no mention of Linux/macOS alternatives for development environments or package installation, nor are cross-platform CLI instructions (e.g., bash, zsh) provided. The Azure CLI example is cross-platform, but the overall setup and examples assume a Windows-first workflow.
Recommendations
  • Explicitly mention that .NET and Azure Communication Services SDKs are cross-platform, and can be used on Linux/macOS as well as Windows.
  • Provide alternative instructions for installing the SDK using bash/zsh (e.g., 'dotnet add package' in a Linux/macOS terminal).
  • List VS Code or JetBrains Rider as alternative IDEs for Linux/macOS users, or clarify that Visual Studio is optional.
  • Add a note that the Azure CLI works on all major platforms.
  • Ensure that all code snippets and setup steps are platform-agnostic or provide platform-specific variants.
GitHub Create Pull Request
Connectors Enable stateful mode for stateless built-in connectors ...ectors/enable-stateful-affinity-built-in-connectors.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell examples for command-line configuration, referencing Windows-centric tools, and omitting equivalent instructions for Linux/macOS users (such as Azure CLI or REST API via curl). The troubleshooting section also relies solely on PowerShell. While the Azure portal and REST API are cross-platform, command-line automation is presented only for Windows environments.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users have parity.
  • Include REST API usage examples with curl or similar cross-platform tools.
  • Present command-line examples in parallel (PowerShell and CLI), or show CLI first to avoid Windows-first ordering.
  • Clarify that Azure CLI and REST API methods work on all platforms, and link to relevant documentation.
  • Provide troubleshooting steps using CLI or REST API, not just PowerShell.
GitHub Create Pull Request
Cost Management Billing Assign permissions to Cost Management APIs ...nt-billing/automate/cost-management-api-permissions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell as the only command-line method for assigning roles to service principals, without mentioning or providing examples for Linux/macOS-friendly alternatives such as Azure CLI. The portal-based instructions are platform-neutral, but the only automation example is PowerShell, which is most commonly used on Windows. There are no Linux/macOS-specific examples or explicit mention of cross-platform tools.
Recommendations
  • Add Azure CLI examples for assigning roles to service principals, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used for role assignments, and link to relevant CLI documentation.
  • Where automation is discussed, provide parallel instructions for both PowerShell and CLI to ensure parity.
  • Consider adding a note clarifying that all portal instructions are platform-neutral.
GitHub Create Pull Request
Cost Management Billing Link a partner ID to your account that’s used to manage customers ...cles/cost-management-billing/manage/link-partner-id.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a Windows bias by presenting all command-line examples with Windows-style prompts (C:\>), referencing PowerShell modules and commands extensively, and listing Windows-centric instructions before Linux/macOS alternatives. The Azure CLI section also uses Windows paths and prompts, and does not mention Linux/macOS installation or usage specifics. There are no explicit Linux/macOS examples, nor are platform differences discussed.
Recommendations
  • Provide command-line examples using both Windows (PowerShell, CMD) and Linux/macOS (bash/zsh) syntax and prompts.
  • Remove Windows-specific prompts (C:\>) from Azure CLI examples, or show equivalent Linux/macOS shell usage (e.g., $ az ...).
  • Add installation instructions for Azure CLI and PowerShell modules on Linux/macOS, including package manager commands (apt, yum, brew, etc.).
  • Clarify that Azure CLI and PowerShell are cross-platform, and provide notes or links to platform-specific documentation.
  • Ensure screenshots and UI instructions are not Windows-specific, or provide alternatives for other platforms if relevant.
GitHub Create Pull Request
Cyclecloud Images ...ocs/azure-docs/blob/main/articles/cyclecloud/images.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides configuration examples exclusively for Windows images (e.g., 'cycle.image.win2022', 'MicrosoftWindowsServer:WindowsServer:2022-datacenter-g2:latest'), with no equivalent examples for Linux images. Although the list of supported images includes several Linux distributions, the practical usage examples and instructions focus solely on Windows, making it less clear for Linux users how to specify their images.
Recommendations
  • Add configuration examples for Linux images (e.g., Ubuntu, AlmaLinux, SLES) alongside Windows examples.
  • Present both Windows and Linux examples in parallel or alternate their order to avoid Windows-first bias.
  • Clarify that the same configuration patterns apply to Linux images and provide explicit sample values for Linux.
  • Include notes or sections addressing any Linux-specific considerations (e.g., Jetpack usage, image labels).
GitHub Create Pull Request
Cost Management Billing Copy billing roles from one MCA to another MCA across tenants with a script ...s/cost-management-billing/manage/mca-role-migration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation exclusively provides a PowerShell script for automating billing role migration and instructs users to select PowerShell in Azure Cloud Shell, with no mention of Bash or Linux/macOS alternatives. All scripting and execution steps assume PowerShell usage, which is native to Windows and only more recently available on Linux/macOS. There are no Bash, CLI, or cross-platform script examples, nor guidance for Linux/macOS users.
Recommendations
  • Provide equivalent Bash or Azure CLI script examples for Linux/macOS users.
  • Clarify that PowerShell Core is available cross-platform and provide installation instructions for Linux/macOS.
  • Explicitly mention how Linux/macOS users can run the script (e.g., via PowerShell Core or Azure Cloud Shell).
  • Offer guidance on using Bash in Azure Cloud Shell where possible, or note any limitations.
  • Present examples for both PowerShell and Bash/Azure CLI, or at least acknowledge the Windows-centric approach and alternatives.
GitHub Create Pull Request
Cost Management Billing Set up billing for Microsoft Customer Agreement - Azure ...es/cost-management-billing/manage/mca-setup-account.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation exclusively references the Azure portal for all setup, validation, and management steps, with no mention of cross-platform CLI tools (such as Azure CLI or Bash scripts) or Linux/macOS-specific workflows. All example links, instructions, and screenshots are based on the web portal, which is most commonly accessed via Windows. There are no PowerShell-specific instructions, but there is a lack of parity for Linux users who may prefer command-line or automation approaches. Additionally, where automation is mentioned (e.g., recreating export jobs), PowerShell is referenced before alternatives, and no Bash or Linux-native examples are provided.
Recommendations
  • Add Azure CLI examples for key tasks (e.g., transitioning enrollments, managing billing roles, validating setup) alongside portal instructions.
  • Include Bash script snippets for common automation scenarios, especially for Linux/macOS users.
  • Reference cross-platform tools (Azure CLI, REST API) equally or before Windows-specific tools like PowerShell.
  • Clarify that all portal-based steps are accessible from any OS/browser, and provide links to CLI documentation for users who prefer command-line interfaces.
  • Where automation is discussed, provide both PowerShell and Bash/Linux script examples.
GitHub Create Pull Request
Cost Management Billing Programmatically create Azure subscriptions with legacy APIs ...manage/programmatically-create-subscription-preview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides REST, PowerShell, and Azure CLI examples for EA subscription creation, but PowerShell is presented before Azure CLI and is explicitly called out to be run in Azure Cloud Shell with PowerShell selected, which is a Windows-centric tool. There are no Linux/macOS-specific shell or scripting examples, and PowerShell is referenced as a primary method. For MCA and MPA accounts, only REST API examples are provided, but the EA section's ordering and tooling favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, or alternate the order to avoid implicit prioritization.
  • Explicitly mention that Azure CLI works cross-platform and can be run on Linux/macOS, and provide instructions for installing and running CLI on those platforms.
  • Add Bash shell script examples for REST API calls (e.g., using curl or httpie) to demonstrate Linux/macOS workflows.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Avoid language like 'select PowerShell' without also mentioning Bash as an option.
  • For PowerShell examples, note that PowerShell Core is available cross-platform, or provide equivalent Bash/CLI commands.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exclusively provides examples using armclient with PowerShell syntax and does not mention or provide equivalent Linux/macOS command-line instructions. The use of PowerShell and armclient (which is most commonly used on Windows) suggests a Windows-centric approach, and no alternative tools or shell examples for Linux/macOS are offered. All example code blocks are tagged as 'azurepowershell-interactive', reinforcing the Windows-first bias.
Recommendations
  • Provide equivalent examples using bash/curl for REST API calls, which are natively available on Linux/macOS.
  • Clarify whether armclient is cross-platform and, if so, provide installation and usage instructions for Linux/macOS.
  • Include explicit instructions or code samples for Linux/macOS users, such as using curl or httpie.
  • Avoid tagging all code blocks as 'azurepowershell-interactive' if the commands are not PowerShell-specific.
  • Add a section noting cross-platform compatibility and any differences in tooling or syntax.
GitHub Create Pull Request
Cost Management Billing Manage Azure Reservations ...nt-billing/reservations/manage-reserved-vm-instance.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for managing Azure Reservations demonstrates a Windows bias, especially in the section on splitting reservations, where only PowerShell commands are provided. There are no CLI (az) or REST API examples for Linux/macOS users, and PowerShell is presented as the primary method for scripting these operations. Throughout the page, graphical instructions reference the Azure portal, which is cross-platform, but command-line automation is Windows-centric.
Recommendations
  • Add equivalent Azure CLI (az) examples for splitting reservations and updating scopes, as the Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Include REST API sample calls for reservation management tasks, with curl or HTTP request examples.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or clarify any limitations if only Windows PowerShell is supported.
  • Where command-line examples are given, present Azure CLI first or side-by-side with PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Cost Management Billing Get started with your updated Azure billing account ...ent-billing/understand/mosp-new-customer-experience.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page references PowerShell as a primary automation and scripting tool for billing and subscription operations, both in the API support section and when describing automation options. There are no explicit Linux/macOS CLI examples, nor is the Azure CLI mentioned as an alternative to PowerShell for cross-platform users. This creates a subtle bias toward Windows users and may cause friction for those on Linux or macOS.
Recommendations
  • Include Azure CLI examples alongside or instead of PowerShell for automation and scripting tasks, as Azure CLI is cross-platform.
  • Explicitly mention that APIs and SDKs can be used from any OS, and provide sample commands for Linux/macOS environments.
  • Add notes or sections clarifying parity between PowerShell and Azure CLI, and link to relevant Azure CLI documentation.
  • Ensure screenshots and instructions in the portal are OS-agnostic or clarify that the portal is accessible from any modern browser.
GitHub Create Pull Request
Active Directory B2C Manage user data in Azure Active Directory B2C ...main/articles/active-directory-b2c/manage-user-data.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not include any command-line examples (Windows or Linux). However, there is a lack of parity in that no Linux (bash/curl) or Windows (PowerShell) examples are given for interacting with the Microsoft Graph API, which could be seen as a missed opportunity to ensure cross-platform inclusivity.
Recommendations
  • Add explicit examples for both Windows (using PowerShell) and Linux/macOS (using bash and curl) to demonstrate how to call the Microsoft Graph API for deleting and exporting user data.
  • When providing sample scripts or command-line instructions, ensure both PowerShell and bash/curl examples are included side by side.
  • Mention cross-platform tools (such as Azure CLI, Microsoft Graph CLI, or REST API via curl) and clarify their availability on different operating systems.
  • Explicitly state that the operations can be performed from any OS, and provide links or references to platform-agnostic tools.
GitHub Create Pull Request
Application Gateway Listener TLS certificate management in Application Gateway ...cles/application-gateway/ssl-certificate-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page demonstrates a mild Windows bias by mentioning the PowerShell command for listing SSL certificates before the Azure CLI equivalent. No Linux-specific tools or examples are provided, but the CLI command is present, which is cross-platform. There are no exclusive references to Windows-only tools or patterns, and the rest of the documentation is platform-neutral.
Recommendations
  • List Azure CLI commands before PowerShell commands to avoid implicit prioritization of Windows tooling.
  • Explicitly state that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider including Linux-native certificate management commands or references (e.g., OpenSSL usage for preparing PFX files) where relevant.
  • Add a brief note or section highlighting parity between Windows and Linux management options for Application Gateway certificates.
GitHub Create Pull Request
Application Gateway URL Redirect for Azure Application Gateway for Containers - Gateway API ...eway/for-containers/how-to-url-redirect-gateway-api.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_tools
Summary
The documentation is largely cross-platform, using Kubernetes (kubectl), YAML, and curl commands that work on both Linux and Windows. However, there is a minor Windows bias in the BYO deployment section, where the Azure CLI (az) is used to retrieve resource IDs. While az is available on Linux, the pattern of using environment variables and command substitution (e.g., $(...)) is more common in Linux shells (bash) than in Windows PowerShell or Command Prompt, but no PowerShell-specific or Windows-only commands are shown. There are no explicit Linux-only or Windows-only examples, and no PowerShell-heavy or Windows-first patterns. All examples are generic and suitable for Linux, macOS, and Windows (with WSL or appropriate tools installed).
Recommendations
  • Explicitly mention that all CLI examples (kubectl, az, curl, dig) work on Linux, macOS, and Windows (with WSL or Azure CLI installed).
  • Provide PowerShell equivalents for environment variable assignment and command substitution, or clarify how to run these commands in Windows environments.
  • Add a note about installing required tools (kubectl, az, curl, dig) on both Linux and Windows, including links to installation guides.
  • If possible, include example commands for both bash (Linux/macOS) and PowerShell (Windows) for resource ID retrieval and variable assignment.
GitHub Create Pull Request
Azure Functions Azure Functions Scenarios ...b/main/articles/azure-functions/functions-scenarios.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ powershell_heavy
Summary
The documentation provides parity across multiple programming languages, including C#, Python, JavaScript, TypeScript, Java, and PowerShell. While PowerShell is included as a first-class language pivot throughout, there is no evidence of Windows-specific tools, Windows-only examples, or Windows-first ordering. No Windows-exclusive patterns or missing Linux examples are present. The only mild bias is the inclusion of PowerShell as a language pivot, which may be perceived as Windows-centric, but all examples are cross-platform and do not rely on Windows-specific tooling.
Recommendations
  • Clarify that PowerShell examples are cross-platform and can run on Linux hosts.
  • Where relevant, mention that all Azure Functions features and triggers are supported on both Windows and Linux hosting plans.
  • If any example or tutorial relies on Windows-only tooling (such as Visual Studio), provide equivalent instructions for Linux (such as VS Code or CLI).
  • Explicitly state platform compatibility in introductory sections to reassure Linux users.
GitHub Create Pull Request
Avere Vfxt Deploy Avere vFXT for Azure ...ocs/blob/main/articles/avere-vfxt/avere-vfxt-deploy.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation does not exhibit overt Windows bias in terms of command-line examples, tools, or patterns. However, in the authentication section, the only link provided for SSH key creation is to a Windows-specific guide ('How to create and use SSH keys' for Linux VMs from Windows), with no equivalent Linux or macOS instructions. There are no explicit PowerShell or Windows tool references, but the lack of Linux parity in the SSH key guidance is a subtle bias.
Recommendations
  • Provide links to SSH key creation guides for Linux and macOS users alongside the Windows-specific link.
  • Explicitly mention that the deployment process is platform-agnostic and can be performed from any OS with Azure Portal access.
  • If any command-line or scripting examples are added in the future, ensure both Windows (PowerShell/CMD) and Linux (bash) equivalents are provided.
  • Consider a short section or note clarifying that SSH key generation and Azure portal usage are supported from all major operating systems.
GitHub Create Pull Request
Azure App Configuration Roll out features to targeted audiences in a Node.js app ...-app-configuration/howto-targetingfilter-javascript.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the Linux/macOS method. Windows methods are listed first and in greater detail, which may suggest a slight Windows-first bias. However, Linux/macOS instructions are present and correct, and the rest of the tutorial is platform-neutral (Node.js/Express).
Recommendations
  • Present environment variable instructions in a platform-neutral or parallel format (e.g., a table or side-by-side code blocks for Windows and Linux/macOS).
  • Avoid listing Windows commands before Linux/macOS commands; consider alphabetical or usage-based ordering.
  • Explicitly state that all steps work on Linux/macOS unless otherwise noted.
  • Add a note clarifying that the Node.js/Express code is cross-platform and works on Windows, Linux, and macOS.
GitHub Create Pull Request
Azure Functions Apache Kafka trigger for Azure Functions ...es/azure-functions/functions-bindings-kafka-trigger.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ powershell_heavy
Summary
The documentation provides examples for multiple languages, including PowerShell, which is primarily a Windows-centric shell. However, there is no evidence of Windows bias in terms of exclusive use of Windows tools, Windows-first ordering, or missing Linux examples. All examples are provided for C#, JavaScript, Python, Java, and PowerShell, and the content is cross-platform in nature. There are no references to Windows-only tools, nor is PowerShell given priority over other languages. However, the inclusion of PowerShell examples may be interpreted as a mild bias towards Windows environments, since PowerShell is most commonly used on Windows, though it is available on Linux and macOS as well.
Recommendations
  • Clarify that PowerShell examples are cross-platform and can be run on Linux/macOS with PowerShell Core.
  • Consider adding Bash or other Linux-native shell examples if relevant for scripting scenarios.
  • Explicitly mention platform compatibility for all code samples, especially for PowerShell, to reinforce Linux parity.
  • Ensure that any references to file paths, certificates, or environment variables use platform-neutral syntax or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Azure Functions Azure Functions Web PubSub output binding ...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation provides code samples for C# and JavaScript, but omits complete examples for Python and PowerShell, and states that Java is not supported. There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the lack of Linux-oriented examples (e.g., bash, Linux shell, or explicit Linux instructions) and the absence of parity for Python and PowerShell may disadvantage Linux users.
Recommendations
  • Add complete Python examples, ensuring they are runnable on Linux environments.
  • If PowerShell examples are provided, also offer bash or shell script equivalents for Linux users.
  • Explicitly mention cross-platform compatibility in setup/configuration instructions.
  • Include troubleshooting steps or logging instructions relevant to Linux (e.g., using tail, journalctl, or bash commands).
  • Clarify any platform-specific requirements or differences, if applicable.
GitHub Create Pull Request
Azure Resource Manager Bicep numeric operators ...cles/azure-resource-manager/bicep/operators-numeric.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions 'Azure CLI or Azure PowerShell' as ways to deploy Bicep files, listing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, but does not provide explicit Linux shell examples or clarify cross-platform usage. No PowerShell-specific examples are present, but the mention of PowerShell before Linux-native alternatives may suggest a subtle Windows-first bias.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Provide example deployment commands for both Azure CLI (bash/zsh syntax) and Azure PowerShell, clarifying which platforms they run on.
  • Avoid listing Windows-centric tools before cross-platform alternatives unless contextually appropriate.
  • Add a note or section on deploying Bicep files from Linux/macOS terminals, including sample commands.
  • Ensure parity in guidance for both Windows and Linux users throughout the documentation.
GitHub Create Pull Request
Azure Resource Manager Resource declaration in Bicep ...s/azure-resource-manager/bicep/resource-declaration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for querying supported resource locations, but presents the PowerShell example first. This ordering may subtly prioritize Windows tooling, as PowerShell is most commonly used on Windows, while Azure CLI is cross-platform and preferred by many Linux users. No other Windows-specific tools or patterns are present, and Linux parity is generally maintained in examples and instructions.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
  • Explicitly state that both Azure CLI and PowerShell are available on Windows, macOS, and Linux, to avoid implying platform exclusivity.
  • Where possible, include Bash shell examples for common resource management tasks, especially in sections where scripting is discussed.
  • Audit other documentation pages for similar ordering or tool selection biases to ensure consistent cross-platform parity.
GitHub Create Pull Request
Azure Resource Manager Move Azure resources across resource groups, subscriptions, or regions ...resource-manager/management/move-resources-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Azure PowerShell and Azure CLI as methods for moving resources, listing PowerShell (a Windows-centric tool) before CLI (which is cross-platform). No explicit Linux examples, tools, or patterns are provided, and there is no mention of Bash or Linux-specific guidance. However, the bias is mild, as Azure CLI is cross-platform and is mentioned alongside PowerShell.
Recommendations
  • List Azure CLI before Azure PowerShell when enumerating command-line options, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide links to installation guides for each platform.
  • Include example commands for both Azure PowerShell and Azure CLI, ideally with Bash syntax for CLI to demonstrate Linux usage.
  • Add a note that REST API and Azure portal are platform-agnostic.
  • Where possible, provide links to Linux-specific documentation or troubleshooting guides.
GitHub Create Pull Request
Azure Resource Manager Deploy multiple instances of resources ...les/azure-resource-manager/templates/copy-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Azure PowerShell before Azure CLI when listing supported tools for zero-count deployments, which may suggest a subtle Windows-first bias. However, both PowerShell and CLI are referenced, and no examples or instructions are given that are exclusive to Windows or PowerShell. There are no command-line examples, and no Windows-only tools or patterns are described. Linux parity is generally maintained, but the order of tool presentation could be improved.
Recommendations
  • List Azure CLI before Azure PowerShell when describing supported tools, as CLI is cross-platform and commonly used on Linux.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to reinforce cross-platform support.
  • If command-line examples are added in the future, ensure both CLI and PowerShell examples are provided, or default to CLI for cross-platform parity.
GitHub Create Pull Request
Azure Resource Manager Azure resource types for move operations ...-resource-manager/management/move-support-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ powershell_heavy
Summary
The documentation page is largely platform-neutral, presenting Azure resource move capabilities in tabular format without explicit command-line examples. However, the only script reference for region moves (Azure Automation account) specifically mentions a 'PowerShell script', with no mention of Bash, Azure CLI, or Linux alternatives. There are no Linux-specific tools, examples, or parity guidance, and the only explicit scripting guidance is Windows-centric.
Recommendations
  • Where scripting is referenced (e.g., for Azure Automation account region moves), provide equivalent Azure CLI or Bash script examples alongside PowerShell.
  • Explicitly mention that move operations can be performed from Linux/macOS using Azure CLI, not just PowerShell.
  • For any linked guidance pages (e.g., move guidance for App Service, SQL, etc.), ensure that both PowerShell and Azure CLI/Bash examples are present and equally discoverable.
  • Add a general note in the 'Next steps' section clarifying that all move operations can be performed from any OS using Azure CLI, PowerShell, or REST API.
  • Audit linked articles for similar bias and update them to include Linux-friendly instructions where missing.
GitHub Create Pull Request
Azure Resource Manager Template functions - deployment ...rce-manager/templates/template-functions-deployment.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is generally neutral and platform-agnostic, focusing on ARM template JSON syntax. However, in the 'environment' function section, when suggesting how to list registered Azure environments, the documentation mentions the Windows PowerShell cmdlet 'Get-AzEnvironment' after the cross-platform 'az cloud list' CLI command. While both tools are referenced, the PowerShell cmdlet is mentioned second, which is a positive sign, but its inclusion without a corresponding Linux shell example (such as Bash) or clarification that 'az' is cross-platform could be improved.
Recommendations
  • Clarify that the 'az' CLI is cross-platform and works on Windows, Linux, and macOS.
  • When referencing PowerShell cmdlets, also mention that they are available on PowerShell Core, which is cross-platform, or clarify if they are Windows-only.
  • Consider providing example commands for both Bash (Linux/macOS) and PowerShell (Windows), or explicitly state that the 'az' CLI example is suitable for all platforms.
  • Continue to avoid Windows-specific tooling or patterns unless there is a clear cross-platform equivalent, and always present cross-platform options first.
GitHub Create Pull Request
Azure Resource Manager Template functions - string ...esource-manager/templates/template-functions-string.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page does not provide explicit Windows or PowerShell-specific examples, nor does it mention Windows tools or patterns directly. However, in the 'Next steps' section, the only deployment guide referenced is 'Deploy resources with ARM templates and Azure PowerShell', which prioritizes the Windows/PowerShell deployment method and omits Linux or cross-platform CLI alternatives. This constitutes a 'windows_first' bias by suggesting PowerShell as the primary or sole deployment approach.
Recommendations
  • In the 'Next steps' section, add links to deployment guides for Azure CLI and/or Bash, which are cross-platform and commonly used on Linux and macOS.
  • Ensure that deployment instructions and examples are available for both PowerShell and Azure CLI, and present them with equal prominence.
  • Consider adding a note that ARM templates can be deployed from any platform, and reference documentation for Linux/macOS users.
  • Review other related documentation pages to ensure Linux parity in deployment and usage examples.
GitHub Create Pull Request
Azure Vmware Configure AVS Identities Role Assignments Manually ...b/main/articles/azure-vmware/native-role-assignment.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation provides only portal-based, GUI instructions for configuring role assignments in Azure VMware Solution Gen 2. There are no examples or references to command-line methods, such as Azure CLI or PowerShell, which could be used on both Windows and Linux platforms. This omission may disadvantage Linux users who prefer or require CLI-based workflows.
Recommendations
  • Add Azure CLI examples for each role assignment step, as Azure CLI is cross-platform and works on both Windows and Linux.
  • If relevant, include PowerShell examples but ensure they are presented after or alongside Azure CLI instructions.
  • Explicitly mention that all steps can be performed using CLI tools on Linux, macOS, or Windows, and link to official documentation for CLI usage.
  • Consider providing a table or section comparing portal, Azure CLI, and PowerShell approaches for parity.
GitHub Create Pull Request
Azure Vmware Connect to on-premises environment ...in/articles/azure-vmware/native-connect-on-premises.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it omits details about connecting from Linux environments. There are no references to Windows-specific tools or patterns, nor are PowerShell commands or Windows-first instructions present. However, the lack of Linux-specific guidance or parity in examples constitutes a subtle bias by omission.
Recommendations
  • Add explicit instructions or examples for connecting from Linux-based on-premises environments.
  • Include references to Linux networking tools (e.g., strongSwan, OpenVPN, ipsec) for Site-to-Site VPN setup.
  • Clarify any platform-specific requirements or differences for both Windows and Linux environments.
  • Provide links to Azure documentation that covers Linux-based connectivity scenarios.
GitHub Create Pull Request
Backup Restore Azure Managed Disks ...ocs/blob/main/articles/backup/restore-managed-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides instructions for restoring Azure Managed Disks and includes guidance for both Windows and Linux virtual machines when attaching or swapping disks. However, the instructions for Windows VMs are consistently presented before those for Linux VMs, indicating a 'windows_first' bias. No PowerShell-heavy examples or exclusive mention of Windows tools are present, and Linux instructions are included, though always after Windows.
Recommendations
  • Present instructions for Windows and Linux VMs in parallel or alternate the order to avoid implicit prioritization.
  • Explicitly state that the process applies equally to both Windows and Linux VMs at the beginning of relevant sections.
  • Where possible, provide combined or side-by-side examples for both platforms to reinforce parity.
  • Review linked resources to ensure Linux documentation is as comprehensive and up-to-date as Windows documentation.
GitHub Create Pull Request
Bastion Deploy private-only Bastion .../blob/main/articles/bastion/private-only-deployment.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation provides only Azure Portal (GUI) instructions for deploying Bastion in a private-only scenario and does not include any command-line examples. There is no mention of Windows-specific tools (e.g., PowerShell, CMD), but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash) instructions are provided. This omission can disadvantage users who prefer or require automation or command-line deployment, especially on Linux.
Recommendations
  • Add Azure CLI examples for all deployment steps, showing how to create the virtual network, subnet, and Bastion host in private-only mode.
  • Explicitly mention that the Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • If relevant, provide PowerShell examples as well, but ensure that CLI/Bash instructions are given equal prominence.
  • Include a section comparing portal-based and command-line deployment, highlighting automation benefits for Linux users.
GitHub Create Pull Request
Azure Vmware Support for Azure VMware Solution deployment or provisioning failure .../main/articles/azure-vmware/fix-deployment-failures.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation exclusively describes how to gather information and file a support request using the Azure portal's graphical interface, with no mention of command-line alternatives such as Azure CLI, PowerShell, or REST API. There are no examples or instructions for users on Linux or macOS platforms, nor are there any references to cross-platform tools. This may disadvantage users who prefer or require non-Windows environments or automation.
Recommendations
  • Add instructions and examples for obtaining correlation IDs, error messages, and ExpressRoute IDs using Azure CLI (az) commands, which are cross-platform.
  • If relevant, include PowerShell examples, but always provide Azure CLI or REST API equivalents and present them first or side-by-side.
  • Mention that all steps can be performed from any OS using the Azure portal, but highlight automation or scripting options for Linux/macOS users.
  • Provide links to Azure CLI and REST API documentation for advanced or automated workflows.
  • Explicitly state that the process is not limited to Windows and that Linux/macOS users have full parity via CLI or portal.
GitHub Create Pull Request
Azure Vmware Internet connectivity options for Azure VMware Solution Generation 2 private clouds ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/native-internet-connectivity-design-considerations.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ missing_linux_example
Summary
The documentation does not display overt Windows bias in terms of mentioning Windows-specific tools, PowerShell, or Windows-first patterns. However, it lacks any OS-specific command-line or configuration examples, and does not provide parity examples for either Windows or Linux. This absence of examples, especially Linux-focused ones, constitutes a 'missing_linux_example' bias, as Linux is commonly used for network administration.
Recommendations
  • Add step-by-step command-line examples for configuring Azure Firewall and route tables using both Azure CLI (cross-platform, Linux-friendly) and PowerShell (for Windows users).
  • Include sample configuration snippets for common Linux-based NVAs (e.g., how to configure routing/firewall rules on a Linux VM acting as an NVA).
  • Explicitly mention that the steps are OS-agnostic, or provide links to both Windows and Linux documentation for related Azure networking tasks.
  • If referencing Azure CLI, ensure Linux installation and usage instructions are included or linked.
GitHub Create Pull Request
Backup Restore Azure Files with REST API ...n/articles/backup/restore-azure-file-share-rest-api.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Azure portal, Azure PowerShell, and Azure CLI as alternative methods for restoring Azure Files, listing PowerShell (a Windows-centric tool) before CLI (cross-platform). However, all technical examples and REST API usage are platform-neutral, with no explicit PowerShell or Windows-only commands, nor any OS-specific tooling. There are no Linux-specific examples or references, but also no Windows-specific examples beyond the ordering in the introductory and summary sections.
Recommendations
  • List Azure CLI before Azure PowerShell when mentioning alternative tools, as CLI is cross-platform and more accessible to Linux users.
  • Explicitly mention that all REST API examples are platform-agnostic and can be executed from any OS, including Linux, macOS, and Windows.
  • Provide example commands using curl or httpie (common Linux tools) to demonstrate REST API calls from Linux environments.
  • Add a short section or note on authentication and environment setup for Linux users (e.g., using Azure CLI or environment variables for access tokens).
  • Ensure parity in references to management tools by including links to Linux-specific guides or CLI usage where relevant.
GitHub Create Pull Request
Bastion Tutorial: Deploy Azure Bastion using specified settings: Azure portal ...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page presents both Windows and Linux VM options, but consistently lists Windows VM creation and RDP port configuration before Linux equivalents. The Windows VM quickstart is mentioned first, and port requirements for Windows (RDP) precede those for Linux (SSH). No PowerShell or Windows-specific tool bias is present, and Linux parity is generally maintained, but ordering suggests a subtle preference for Windows scenarios.
Recommendations
  • Alternate the order of Windows and Linux instructions/examples throughout the documentation, or list Linux first in some sections.
  • Explicitly state that all steps apply equally to both Windows and Linux VMs, and provide parallel examples where relevant.
  • Ensure that any referenced quickstart or connection articles for Linux are as prominent and detailed as those for Windows.
  • Consider adding a note on cross-platform parity to reinforce that Bastion supports both OS types equally.
GitHub Create Pull Request
Cloud Shell Using the Azure Cloud Shell window ...ob/main/articles/cloud-shell/using-the-shell-window.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation generally maintains cross-platform neutrality, but in the 'Copy and paste' section, Windows instructions are presented first, followed by macOS and Linux. There are no exclusive Windows/Powershell examples or tools, and both Bash and PowerShell environments are mentioned equally. However, the ordering of platforms in the keyboard shortcut instructions reflects a subtle 'windows_first' bias.
Recommendations
  • Present platform-specific instructions in alphabetical order (Linux, macOS, Windows) or group them in a way that does not always prioritize Windows.
  • Where possible, provide parallel examples or notes for both Bash and PowerShell environments, especially if there are environment-specific behaviors.
  • Explicitly mention Linux and macOS support in introductory sections to reinforce parity.
  • Review other sections for subtle ordering or phrasing that may unintentionally prioritize Windows.
GitHub Create Pull Request
Cloud Shell How to use the new user interface for Azure Cloud Shell .../blob/main/articles/cloud-shell/new-ui-shell-window.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation generally maintains parity between Bash and PowerShell environments and provides platform-specific instructions for copy/paste operations. However, in the 'Copy and paste' section, Windows instructions are presented first, followed by macOS and Linux, which may suggest a subtle Windows-first bias. No PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples were found.
Recommendations
  • Present platform instructions in alphabetical order (e.g., Linux, macOS, Windows) or group them together to avoid implicit prioritization.
  • Ensure that examples and instructions for Bash and PowerShell are given equal prominence throughout the documentation.
  • Explicitly mention Linux-specific behaviors or shortcuts where relevant, especially in sections discussing terminal interactions.
  • Review other sections for subtle ordering biases and consider rotating or randomizing the order in which platforms are presented.
GitHub Create Pull Request
Communication Services include file ...ces/quickstarts/rooms/includes/rooms-quickstart-net.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is largely cross-platform, but there is a subtle Windows bias in the order of examples: when suggesting console environments, 'cmd' and 'PowerShell' are mentioned before 'Bash'. No Linux-specific tools or instructions are missing, but the ordering may suggest a Windows-first perspective.
Recommendations
  • List Bash (or 'terminal') before or alongside cmd and PowerShell when mentioning console environments, e.g., 'in a console window (such as Bash, cmd, or PowerShell)'.
  • Explicitly state that all commands work on Windows, Linux, and macOS to reinforce cross-platform compatibility.
  • If there are any OS-specific steps (e.g., environment variable setup, file paths), provide both Windows and Linux/macOS examples.
  • Consider including a short note or table summarizing supported platforms and any platform-specific considerations.
GitHub Create Pull Request
Communication Services include file .../quickstarts/router/includes/router-quickstart-java.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run Maven commands, which may suggest a Windows-first perspective. However, all commands and instructions are cross-platform and do not rely on Windows-specific tools or patterns. No PowerShell-specific examples or Windows-only tools are present, and Linux users are not excluded from any steps.
Recommendations
  • List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when describing command-line usage, or mention all platforms equally (e.g., 'in a terminal such as Bash, cmd, or PowerShell').
  • Explicitly state that all commands work on Windows, Linux, and macOS, to reassure non-Windows users.
  • If platform-specific steps ever arise (e.g., environment variables, file paths), provide examples for both Windows and Linux/macOS.
GitHub Create Pull Request
Communication Services include file ...es/quickstarts/rooms/includes/rooms-quickstart-java.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run Maven commands, which is a subtle form of Windows-first bias. However, all code and tooling instructions are platform-neutral (Java, Maven), and there are no PowerShell-specific commands, Windows-only tools, or missing Linux examples.
Recommendations
  • List Bash before cmd/PowerShell when referencing console windows, or use 'terminal (such as Bash, cmd, or PowerShell)' to avoid platform prioritization.
  • Explicitly state that all commands work on Linux, macOS, and Windows, and provide any necessary notes for cross-platform usage.
  • If there are platform-specific considerations (e.g., environment variables, file paths), include examples for both Windows and Linux/macOS.
GitHub Create Pull Request
Communication Services include file ...ts/identity/includes/access-tokens/access-token-net.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page demonstrates a slight Windows bias by listing Windows command-line tools (cmd, PowerShell) before Bash when describing how to run commands. However, all commands shown are cross-platform (dotnet CLI), and there are no PowerShell-specific examples, Windows-only tools, or missing Linux equivalents. The documentation does not provide Linux-specific environment variable setup instructions or mention Linux text editors, but the core instructions are generally platform-agnostic.
Recommendations
  • List Bash first or equally alongside cmd and PowerShell when mentioning command-line tools.
  • Explicitly mention that all dotnet CLI commands work on Linux, macOS, and Windows.
  • Provide examples for setting environment variables on Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...).
  • Suggest common Linux/macOS text editors (e.g., nano, vim, VS Code) when instructing users to edit Program.cs.
  • Add a note confirming that the quickstart works on all major platforms and link to platform-specific setup guides if available.
GitHub Create Pull Request
Communication Services Quickstart - Teams interop calls on Azure Communication Services ...video-calling/get-started-teams-interop-group-calls.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation exhibits mild Windows bias by referencing Windows-centric deployment and configuration steps, such as linking to Teams installation instructions that are primarily Windows-focused and requiring Teams Phone license enablement via PowerShell (a Windows tool). However, the main code samples and application instructions are cross-platform (JavaScript, web-based), and there are no critical steps that are Windows-only.
Recommendations
  • Provide explicit Linux/macOS alternatives or notes for Teams deployment and configuration steps, especially where PowerShell is referenced.
  • Clarify if Teams Phone license enablement can be performed via Microsoft 365 admin portal or Graph API, and link to those methods.
  • Add a note or section on running the sample on Linux/macOS, including any platform-specific caveats for device access (camera, microphone) and browser compatibility.
  • Ensure links to prerequisites (Teams deployment, enabling users) include Linux/macOS instructions where available.
GitHub Create Pull Request
Communication Services Quickstart - Make a call to Teams user from a web app ...o-calling/includes/teams-user/teams-user-javascript.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where enabling Teams Phone features for users is referenced with a link to a PowerShell-based guide, and no Linux/macOS alternatives or parity are mentioned. The rest of the tutorial is cross-platform JavaScript and web-based, with no further Windows-specific instructions or tools.
Recommendations
  • Add explicit notes or links for Linux/macOS users on how to enable Teams Phone features, including whether PowerShell Core on non-Windows platforms is supported, or provide Azure Portal GUI instructions if available.
  • Clarify whether all prerequisite steps (such as enabling Enterprise Voice) can be completed on Linux/macOS, and if not, document any required workarounds or limitations.
  • Where PowerShell is referenced, mention cross-platform compatibility or alternatives.
GitHub Create Pull Request
Communication Services Prerequisites ...es/quickstarts/telephony/includes/phone-numbers-net.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash when describing where to run commands. However, all commands and code samples use cross-platform .NET CLI and C#, which work on Windows, Linux, and macOS. No Windows-only tools or patterns are present, and Linux/macOS users can follow the instructions without issue.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
  • Explicitly state that all commands work on Linux/macOS terminals as well as Windows.
  • Consider adding a brief note or example showing the same commands run in a Linux/macOS terminal to reinforce cross-platform support.
GitHub Create Pull Request
Communication Services Quickstart - Manage a room call ...cation-services/quickstarts/rooms/manage-rooms-call.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page demonstrates a subtle Windows bias by linking to quickstarts and conceptual documentation with Windows-specific tabs or pivots first (e.g., 'tabs=windows' in URLs), and by not providing any explicit Linux or cross-platform command-line examples or instructions. All code samples are SDK-based and platform-neutral, but supporting links and references prioritize Windows. There are no PowerShell-heavy examples or exclusive mentions of Windows tools, but Linux parity is not addressed.
Recommendations
  • Ensure that all referenced quickstarts and conceptual documentation include Linux tabs or pivots alongside Windows, and avoid defaulting to Windows in URLs (e.g., use 'tabs=linux' or provide both).
  • Add explicit notes or sections clarifying cross-platform compatibility of SDKs and APIs, including any OS-specific caveats for Linux users.
  • Where relevant, provide Linux-specific setup or usage examples (e.g., CLI commands, environment configuration) in addition to Windows instructions.
  • Audit all linked documentation for similar bias and update to ensure Linux parity in examples, instructions, and screenshots.
GitHub Create Pull Request
Communication Services include file ...tion-services/quickstarts/sms/includes/send-sms-net.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation demonstrates minor Windows bias by listing Windows terminals (cmd, PowerShell) before Bash when instructing users to run commands. However, all commands and instructions are cross-platform, and no Windows-specific tools or patterns are used. Linux/macOS users can follow the guide without friction.
Recommendations
  • List Bash (or 'terminal') before Windows-specific shells (cmd, PowerShell) to avoid implying Windows primacy.
  • Explicitly state that all commands work on Windows, Linux, and macOS.
  • Add a note clarifying that the instructions are platform-agnostic and provide troubleshooting tips for common Linux/macOS issues (e.g., environment variable setup).
GitHub Create Pull Request
Communication Services include file ...kstarts/telephony/includes/voice-routing-sdk-csharp.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Windows-specific console environments (Command Prompt, PowerShell) before Bash, suggesting a Windows-first perspective. However, all command-line instructions use cross-platform .NET CLI commands, and there are no Windows-only tools or examples. No Linux/macOS-specific instructions or troubleshooting are provided.
Recommendations
  • List Bash (Linux/macOS) before or alongside Windows consoles to signal equal support.
  • Explicitly state that all CLI commands work on Linux/macOS terminals.
  • Add a note or troubleshooting section for Linux/macOS users (e.g., .NET installation, file paths).
  • Include a screenshot or example of running the commands in a Linux/macOS terminal.
GitHub Create Pull Request
Communication Services Access a user's Teams Phone separate from their Teams client ...ts/tpe/teams-phone-extensibility-access-teams-phone.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a mild Windows bias. The only platform-specific tool mentioned is the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance) for retrieving the ObjectId, with no Linux/macOS alternative or cross-platform guidance. The user enablement instructions reference the Microsoft 365 admin center UI, which is web-based and not platform-specific, but the PowerShell reference is Windows-centric. No Linux or macOS command-line equivalents (such as Azure CLI, Graph API, or bash scripts) are provided for key steps, and the PowerShell method is mentioned before any REST or programmatic alternatives.
Recommendations
  • Provide Linux/macOS-friendly alternatives for retrieving ObjectId, such as using Azure CLI or direct Graph API calls.
  • Explicitly mention that REST API operations can be performed from any OS, and provide example commands using curl or similar cross-platform tools.
  • Where PowerShell is referenced, add equivalent instructions for bash or other common Linux/macOS shells.
  • Clarify that the Microsoft 365 admin center is accessible via browser on any OS.
GitHub Create Pull Request
Cost Management Billing View and download Azure usage and charges ...ement-billing/understand/download-azure-daily-usage.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation primarily describes how to view and download Azure usage and charges via the Azure portal, which is web-based and cross-platform. However, there is a subtle Windows bias in the ordering and presentation: all screenshots and step-by-step instructions reference the Azure portal UI, which is most commonly accessed from Windows environments, and there is no mention of Linux/macOS-specific considerations or alternative tools. The only command-line example provided uses Azure CLI, which is cross-platform, but there are no explicit Linux/macOS shell examples (e.g., bash, curl, etc.), nor are there any notes about platform-specific differences or issues. There is no evidence of PowerShell-heavy or Windows-only tools, but the documentation does not actively ensure Linux parity in its examples.
Recommendations
  • Add explicit notes confirming that all portal instructions apply equally to Linux/macOS users.
  • Include at least one example of downloading usage data using bash/curl or other Linux-native tools, especially for the Azure CLI section.
  • If there are platform-specific considerations (e.g., file formats, browser compatibility), mention them.
  • Provide screenshots or instructions for accessing the Azure portal from Linux/macOS browsers, if relevant.
GitHub Create Pull Request
Communication Services Chat Hero Sample ...les/communication-services/samples/chat-hero-sample.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation shows a minor Windows bias by listing Windows-specific shells (PowerShell, Windows Terminal, Command Prompt) first when instructing users to open a terminal for cloning the repository. The phrase 'or equivalent' does acknowledge other platforms, but no explicit mention of Linux/macOS terminals (e.g., Bash, Terminal.app) is made. All other instructions and tooling (Node.js, npm, VS Code, Azure CLI) are cross-platform and do not exhibit Windows bias.
Recommendations
  • Explicitly mention Linux/macOS terminal options (e.g., Bash, Terminal.app, iTerm) alongside Windows shells.
  • Provide a brief note confirming that all commands work on Linux/macOS terminals.
  • Consider listing terminal options in a platform-neutral order or grouping (e.g., 'Open a terminal (PowerShell, Command Prompt, Bash, Terminal.app, etc.)').
GitHub Create Pull Request
Communication Services Include file ...ices/samples/includes/call-automation-ai-javascript.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias by instructing users to open a PowerShell window to run the application, without mentioning Linux/macOS terminal usage or providing equivalent instructions. Additionally, some prerequisite links default to Windows tabs, suggesting Windows-first orientation.
Recommendations
  • Update the 'Run the application' section to mention using a terminal or command prompt on Linux/macOS, not just PowerShell.
  • Provide explicit instructions or notes for Linux/macOS users, e.g., 'Open a terminal window (PowerShell on Windows, Terminal on Linux/macOS)'.
  • Ensure prerequisite links and resource setup instructions do not default to Windows tabs, or provide clear parity for Linux/macOS.
  • Add a note clarifying that the sample works cross-platform and that commands are the same on Linux/macOS.
GitHub Create Pull Request
Communication Services Include file ...services/samples/includes/call-automation-ai-python.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation shows mild Windows bias by linking to resource creation instructions with a 'tabs=windows' parameter and mentioning PowerShell and command prompt before Unix terminal when describing how to run the Python application. However, most instructions and examples are cross-platform, and Linux/macOS users can follow along without significant friction.
Recommendations
  • Update resource creation links to default to a neutral or Linux tab, or provide explicit instructions for Linux/macOS users.
  • When listing command-line options, alternate or equally mention Unix terminal and PowerShell/command prompt.
  • Add explicit notes or examples for Linux/macOS users where platform-specific differences may exist.
GitHub Create Pull Request
Communication Services Using ACS UI library JavaScript bundles with Teams Call Queues and Auto Attendants ...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation shows a minor Windows bias by presenting Windows command prompt instructions before macOS terminal equivalents when creating the project directory. However, all other instructions, examples, and tooling are cross-platform (Node.js, VS Code, http-server), and Linux is implicitly supported, though not explicitly mentioned.
Recommendations
  • Present platform-specific instructions in parallel or grouped together, rather than listing Windows first.
  • Explicitly mention Linux in platform support and provide Linux-specific command examples where relevant.
  • Clarify that all terminal commands work on Linux as well as macOS, or provide a Linux example alongside the macOS example.
GitHub Create Pull Request
Communication Services include file ...nication-services/samples/includes/web-calling-hero.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation refers to opening 'PowerShell, Windows Terminal, Command Prompt or equivalent' as the first step for cloning the repository, listing Windows tools first and not mentioning Linux/macOS terminals by name. No explicit Linux/macOS examples or terminal instructions are provided, though the commands themselves are cross-platform.
Recommendations
  • Explicitly mention Linux/macOS terminal applications (e.g., 'Terminal on macOS or Linux') alongside Windows tools.
  • Rephrase instructions to be platform-neutral, such as 'Open your terminal application (PowerShell, Windows Terminal, Command Prompt, Terminal on macOS or Linux)'.
  • Consider providing any platform-specific notes if there are differences in setup or troubleshooting steps for Linux/macOS users.
GitHub Create Pull Request
Container Apps Tutorial: Communication between microservices in Azure Container Apps ...es/container-apps/communicate-between-microservices.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring cross-platform coverage. However, PowerShell examples are given equal prominence and, in some sections (notably the 'Deploy front end application'), the PowerShell workflow is much more verbose and detailed than the Bash equivalent. There is a slight 'Windows-first' bias in the sense that PowerShell is treated as the main alternative to Bash, with no mention of Linux-specific tools or workflows beyond Bash, and PowerShell examples are sometimes more elaborate, potentially making Windows users feel more supported.
Recommendations
  • Ensure that Bash and PowerShell instructions are equally detailed, especially for complex workflows.
  • Consider adding explicit notes about Linux/macOS compatibility, and clarify that Bash instructions work on both Linux and macOS.
  • Where PowerShell examples require additional steps, provide equivalent Bash guidance if relevant.
  • Mention that PowerShell Core is available cross-platform, but clarify that Bash is the default shell for Linux/macOS.
  • If possible, add troubleshooting tips for Linux/macOS users (e.g., permissions, environment variable syntax differences).
GitHub Create Pull Request
Confidential Computing Quickstart - Create Intel SGX VM in the Azure Marketplace ...les/confidential-computing/quick-create-marketplace.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows tools (PowerShell, RDP) are mentioned first or in parallel with Linux equivalents, and instructions sometimes reference Windows-specific patterns before Linux ones. The SSH example is generic, but PowerShell is mentioned as an SSH client before Bash. There are no Linux-specific command-line examples for VM creation, and the connection instructions reference Windows tools and workarounds (WSL, Azure Cloud Shell) for older Windows versions.
Recommendations
  • Present Linux and macOS tools/examples before or alongside Windows ones, especially in connection instructions.
  • Add explicit Linux/macOS CLI examples for VM creation and management, not just portal-based instructions.
  • Avoid referencing Windows tools (PowerShell, RDP) before Linux equivalents (Bash, SSH) in generic instructions.
  • Ensure parity in troubleshooting and driver update instructions for both platforms.
  • Consider a dedicated section for Linux/macOS users, highlighting platform-specific tips and best practices.
GitHub Create Pull Request
Container Apps Generate GitHub Actions workflow with Azure CLI in Azure Container Apps ...lob/main/articles/container-apps/github-actions-cli.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but PowerShell examples are always shown immediately after Bash, and the PowerShell syntax is given equal prominence. There are no Windows-only tools or patterns, but the presence of PowerShell examples may suggest a slight Windows bias, especially since macOS/Linux users would only use Bash.
Recommendations
  • Make it clear that Bash examples are for Linux/macOS and PowerShell for Windows, perhaps with a short note at the top.
  • Consider showing Bash examples first and making them the default, as Azure CLI is cross-platform and Bash is more universal.
  • Optionally, collapse PowerShell examples by default or move them to a separate section for Windows users.
  • Add a brief note about running Azure CLI in Bash on Windows (e.g., via WSL) for parity.
GitHub Create Pull Request