6323
Pages Scanned
1411
Pages Flagged
6323
Changed Pages
22.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
18:00:27
Scan Information
Started At: 2025-12-29 18:00:27
Finished At: In Progress
Status: cancelled
Target Repo: Azure
Current Phase: discovery
Files Queued: 13793
Files Completed: 6323
Problematic Pages
1411 issues found
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-web-app-dotnet.md
...cles/active-directory-b2c/quickstart-web-app-dotnet.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation assumes the use of Visual Studio (a Windows-centric IDE) and provides instructions exclusively for running the sample application in Visual Studio, with no mention of Linux-compatible tools (such as VS Code, JetBrains Rider, or command-line .NET CLI usage). There are no Linux-specific instructions or alternatives for running or debugging the application, and Windows tools and patterns are mentioned exclusively.
Recommendations
- Add instructions for running the sample application using cross-platform tools such as Visual Studio Code or JetBrains Rider.
- Provide examples for building and running the application using the .NET CLI (e.g., 'dotnet build', 'dotnet run'), which work on Linux, macOS, and Windows.
- Explicitly mention that Visual Studio is only available on Windows, and suggest alternatives for Linux users.
- Include screenshots or terminal commands relevant to Linux environments.
- Ensure that all steps (such as configuring multiple startup projects) have Linux-compatible equivalents or workarounds documented.
Create Pull Request
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tenant-management-directory-quota.md
...ive-directory-b2c/tenant-management-directory-quota.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides only a PowerShell script for monitoring directory quota, which is specific to Windows environments. There are no equivalent examples for Linux or cross-platform tools (e.g., Bash, curl, Python). The instructions and tooling are Windows-centric, potentially excluding users on Linux or macOS from easily following the steps.
Recommendations
- Provide equivalent examples using Bash and curl, which are available on Linux and macOS.
- Include a cross-platform example using Python, which works on both Windows and Linux.
- Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation guidance if PowerShell is the preferred tool.
- Reorder or parallelize instructions so that Windows and Linux/macOS users are equally supported, rather than presenting only Windows-first solutions.
- Add a note clarifying that the steps can be performed on any OS, and link to relevant cross-platform tools.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/view-audit-logs.md
.../main/articles/active-directory-b2c/view-audit-logs.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script for programmatically accessing audit logs, with no equivalent examples for Linux users (e.g., Bash/cURL or Python). The script assumes use of PowerShell, which is primarily a Windows tool, and there is no mention of cross-platform alternatives or guidance for Linux/macOS users. This creates a Windows-centric bias in the programmatic access section.
Recommendations
- Add a Bash/cURL example for calling the Microsoft Graph API to retrieve audit logs, suitable for Linux/macOS users.
- Provide a Python script example, as Python is widely available cross-platform and commonly used for automation.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or provide instructions for installing it if retaining PowerShell examples.
- Ensure that all code examples are presented in both Windows (PowerShell) and Linux (Bash/cURL or Python) variants where possible.
- Review the documentation for other implicit Windows tool assumptions and clarify cross-platform compatibility.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/register-discover-mcp-server.md
...in/articles/api-center/register-discover-mcp-server.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing the Azure portal (a web-based tool often associated with Windows-centric workflows) as the primary method for registering and discovering MCP servers. There are no command-line examples (e.g., Azure CLI, Bash, or PowerShell), and no Linux-specific tools or workflows are mentioned. The only development tool referenced is Visual Studio Code, which is cross-platform, but the overall workflow assumes use of the Azure portal, which is more familiar to Windows users. There are no explicit Linux or cross-platform command-line examples or instructions.
Recommendations
- Add Azure CLI and/or Bash examples for registering and managing MCP servers to provide parity with the Azure portal instructions.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, to reduce the perception of a Windows-only workflow.
- Include references to Linux-compatible tools and workflows, such as using curl or other command-line utilities to interact with APIs.
- Provide PowerShell and Bash script examples side-by-side where scripting is relevant.
- Clarify that Visual Studio Code is cross-platform and suggest other editors or tools popular in Linux environments if appropriate.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-arm-template.md
.../articles/api-center/set-up-api-center-arm-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ARM templates, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is mentioned before Bash or Linux-native tools. There are no explicit Bash or Linux shell script examples, and the PowerShell requirements are called out in a dedicated section. The documentation does not mention Linux-specific tools or workflows, and the structure implies parity between PowerShell and CLI, despite CLI being more cross-platform.
Recommendations
- Add explicit Bash/Linux shell script examples for deploying ARM templates, in addition to Azure CLI and PowerShell.
- Mention that Azure CLI is cross-platform and can be used on Windows, macOS, and Linux, while PowerShell is more common on Windows.
- If possible, provide Bash one-liners or scripts for common deployment tasks.
- List Azure CLI (Bash) examples before PowerShell to reduce Windows-first impression.
- Clarify in prerequisites that Azure CLI is recommended for Linux/macOS users.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/synchronize-aws-gateway-apis.md
...in/articles/api-center/synchronize-aws-gateway-apis.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation shows a Windows bias by referencing the Azure portal (a web GUI, often associated with Windows workflows) and by providing Azure CLI examples with a note that they can run in PowerShell or bash, but does not provide explicit Linux shell (bash) examples where variable syntax might differ. The instructions and screenshots are oriented toward the Azure portal, which is more familiar to Windows users. There are no explicit Linux-specific instructions or troubleshooting tips, and the documentation does not mention Linux tools or patterns (e.g., using environment variables, curl, or jq).
Recommendations
- Provide explicit bash/Linux shell examples for Azure CLI commands, especially where variable syntax differs from PowerShell.
- Include screenshots or instructions for using the Azure CLI in a Linux terminal.
- Mention and link to Linux-native tools or workflows where relevant (e.g., using the CLI in WSL, bash, or native Linux).
- Clarify in prerequisites that the instructions are cross-platform and highlight any platform-specific steps.
- Add troubleshooting tips for common Linux-specific issues (e.g., permissions, path differences).
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-ca-certificates.md
...api-management/api-management-howto-ca-certificates.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, with no equivalent example for Linux users (e.g., Azure CLI, Bash, or REST API). The only non-portal automation method mentioned is PowerShell, which is primarily a Windows tool. There is no mention of cross-platform alternatives or Linux-first approaches.
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 examples for certificate management, which are platform-agnostic.
- When mentioning PowerShell, also provide equivalent commands for Azure CLI and/or Bash scripts.
- Explicitly state that PowerShell Core is cross-platform if recommending PowerShell, and clarify compatibility.
- Reorder or present all automation options together (PowerShell, Azure CLI, REST API) rather than only mentioning PowerShell.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-log-event-hubs.md
.../api-management/api-management-howto-log-event-hubs.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a Windows bias by providing example commands and tooling primarily for Azure PowerShell, which is most commonly used on Windows. The only CLI-based example for creating a logger with connection string credentials is given in PowerShell, with no equivalent shown for Bash, Azure CLI, or other Linux-native tools. References to tools (e.g., PowerShell cmdlets) are made before mentioning cross-platform alternatives, and there is no explicit guidance or examples for Linux users or those using Bash/Azure CLI.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, especially for creating loggers with connection string credentials.
- Include Bash shell snippets where appropriate, demonstrating how to use REST API calls via curl or az rest.
- Explicitly mention that Bicep and ARM templates are cross-platform and can be used on Linux, macOS, and Windows.
- Where PowerShell is referenced, clarify that it is available cross-platform, but also provide alternatives for users who prefer Bash or Azure CLI.
- Review all tool references and ensure Linux-native tools (Azure CLI, Bash, curl) are mentioned and demonstrated alongside Windows tools.
- Consider adding a 'Platform considerations' section to guide users on how to perform steps on both Windows and Linux.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/multiple-token-endpoints.md
...icles/active-directory-b2c/multiple-token-endpoints.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented towards Windows development environments. All examples and instructions reference Visual Studio, .sln solution files, and editing .cs and .config files typical of Windows/.NET development. There are no mentions of Linux-compatible tools, editors, or workflows, nor are there any CLI or cross-platform instructions. The only development environment referenced is Visual Studio, and all file paths and configuration steps assume a Windows context.
Recommendations
- Add instructions for opening and editing the project using cross-platform editors like VS Code or JetBrains Rider, and mention how to build/run the project using the .NET CLI (dotnet build/run) on Linux.
- Include Linux/macOS-specific instructions for file paths and configuration changes, or clarify that the steps are cross-platform if applicable.
- Mention that the sample code can be used on Linux and macOS with the .NET SDK, and provide any prerequisites or caveats for non-Windows environments.
- Provide examples of using command-line tools (e.g., dotnet CLI) instead of only referencing Visual Studio.
- Explicitly state the cross-platform compatibility of the OWIN/Katana middleware and the sample application.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/manage-users-portal.md
...n/articles/active-directory-b2c/manage-users-portal.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page primarily describes user management tasks in the Azure portal, which is cross-platform. However, for advanced tasks such as revoking a user's session, only Microsoft Graph PowerShell (and specifically 'Windows PowerShell') is mentioned, with no equivalent examples for Linux or macOS users. The instructions and terminology (e.g., 'In your Windows PowerShell') suggest a Windows-centric approach, and there are no CLI or bash examples provided.
Recommendations
- Provide equivalent examples using cross-platform tools, such as Azure CLI or Microsoft Graph CLI, especially for tasks like session revocation.
- Clarify that Microsoft Graph PowerShell is available on all platforms (Windows, macOS, Linux) and avoid language that implies it is Windows-only.
- Include bash or shell command examples where appropriate, or explicitly state that the PowerShell module can be used on Linux/macOS.
- When referencing PowerShell, use neutral language such as 'in your terminal' or 'in PowerShell', rather than 'in your Windows PowerShell', to avoid implying Windows exclusivity.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-experian.md
...main/articles/active-directory-b2c/partner-experian.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by instructing users to publish the integration code using Visual Studio (a Windows-centric tool) without mentioning cross-platform alternatives. There are no examples or instructions for deploying the API from Linux or macOS environments, nor are there references to CLI-based or platform-agnostic deployment methods. The documentation assumes the use of Azure App Service and Visual Studio, which are most commonly used on Windows, and does not provide parity for Linux users.
Recommendations
- Add instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions.
- Provide examples for publishing the code from Linux and macOS environments, for example using 'dotnet publish' and 'az webapp deploy'.
- Mention Visual Studio Code as an alternative editor, which is cross-platform, and provide relevant steps.
- Ensure that all deployment and configuration steps are documented in a platform-agnostic way, or provide parallel instructions for Windows and Linux/macOS users.
- Explicitly state that Visual Studio is optional and link to documentation for alternative deployment methods.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-idology.md
.../main/articles/active-directory-b2c/partner-idology.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions for publishing the API, without mentioning or providing alternatives for Linux or cross-platform development environments. There are no examples or instructions for deploying the API from Linux or using cross-platform tools such as VS Code, Azure CLI, or GitHub Actions.
Recommendations
- Provide alternative instructions for deploying the API using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions.
- Include explicit examples for Linux and macOS users, such as command-line deployment steps or Docker-based deployment.
- Avoid referencing only Visual Studio or Windows-specific tools; if Visual Studio is mentioned, also mention VS Code or other cross-platform IDEs.
- Where possible, use neutral language and tool recommendations that do not assume a Windows environment.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-jumio.md
...ob/main/articles/active-directory-b2c/partner-jumio.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell scripts for key steps such as certificate creation and random string generation, without offering equivalent Linux or cross-platform alternatives. The use of Windows-centric tooling (PowerShell, Visual Studio) is assumed, and there are no references to Linux command-line tools or methods for these tasks.
Recommendations
- Provide equivalent Linux and macOS instructions for creating self-signed certificates (e.g., using OpenSSL).
- Include examples using bash or other cross-platform scripting languages for generating random strings.
- Mention alternative deployment methods for the API (e.g., using Azure CLI, GitHub Actions, or VS Code) that do not require Visual Studio.
- Clearly indicate which steps are platform-specific and offer parity for non-Windows environments.
- Add notes or links to official Azure documentation for Linux/macOS users where relevant.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-f5.md
.../blob/main/articles/active-directory-b2c/partner-f5.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates Windows bias by referencing IIS as the example application for testing, providing a link to IIS setup instructions, and omitting any mention of Linux-based web servers (such as Apache or Nginx). All application setup and testing guidance is focused on Windows/IIS, with no Linux equivalents or parity in examples. This may lead Linux administrators to feel excluded or unsupported when following the tutorial.
Recommendations
- Include Linux-based web application examples (e.g., Apache, Nginx) alongside IIS for testing the integration.
- Provide links or instructions for setting up a test web application on Linux, similar to the IIS setup guidance.
- Mention Linux-compatible SSL certificate management and web server configuration steps.
- Clarify that the solution is platform-agnostic and provide troubleshooting tips for both Windows and Linux environments.
- Ensure any references to application pools, server configuration, or troubleshooting are not exclusively tied to Windows/IIS terminology.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-onfido.md
...b/main/articles/active-directory-b2c/partner-onfido.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation shows a bias towards Windows by recommending Visual Studio for API deployment and referencing Azure Storage Explorer (a tool with limited Linux support) for file management. There are no explicit Linux or cross-platform alternatives provided for these steps, and no CLI or code-based examples are given for Linux users. The order and choice of tools suggest a Windows-first approach.
Recommendations
- Include cross-platform deployment instructions for the API, such as using the .NET CLI (`dotnet publish` and `az webapp deploy`) or GitHub Actions, in addition to Visual Studio.
- Provide examples for uploading files to Azure Blob Storage using Azure CLI (`az storage blob upload`) or AzCopy, both of which are cross-platform.
- Mention and link to cross-platform tools (e.g., Visual Studio Code, AzCopy, Azure CLI) alongside or before Windows-specific tools.
- Explicitly state that all steps can be performed on Linux, macOS, or Windows, and provide command-line alternatives where possible.
- Avoid assuming the use of Windows-only tools in instructions; always offer Linux/macOS equivalents.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-use-managed-service-identity.md
...t/api-management-howto-use-managed-service-identity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by providing detailed Azure PowerShell examples for all identity management tasks, while omitting equivalent examples for Linux-friendly tools such as Azure CLI. PowerShell is a Windows-centric tool, and its usage is presented before or instead of alternatives. There are no Linux-specific instructions or examples, and no mention of cross-platform command-line options. The ARM template and portal instructions are platform-neutral, but all scripting guidance is PowerShell-only.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure CLI can be used for these tasks, and link to relevant CLI documentation.
- Where scripting is shown, present both PowerShell and CLI examples side-by-side, or indicate which is recommended for each platform.
- Consider including Bash shell script snippets for automation scenarios.
- Review and update any referenced sample links to ensure Linux parity.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-saviynt.md
.../main/articles/active-directory-b2c/partner-saviynt.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides instructions for enabling Saviynt to delete users in Azure AD B2C exclusively using the Microsoft Graph PowerShell module, specifying installation on a Windows workstation or server. No Linux or cross-platform alternatives (such as Azure CLI, Bash, or PowerShell Core on Linux/macOS) are mentioned. The PowerShell example is given without any equivalent for non-Windows environments, and Windows is referenced first and exclusively in the tooling section.
Recommendations
- Add instructions for installing and using Microsoft Graph PowerShell on Linux and macOS, including PowerShell Core.
- Provide equivalent examples using Azure CLI or REST API calls, which are cross-platform.
- Explicitly state platform compatibility for all tools and commands.
- Include notes or links for Linux/macOS users on how to perform the same operations.
- Avoid language that implies Windows is required unless absolutely necessary, and clarify platform requirements.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-native-app-desktop.md
.../active-directory-b2c/quickstart-native-app-desktop.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows, specifically using a WPF (Windows Presentation Foundation) desktop application and Visual Studio. All instructions and screenshots are for Windows tools and workflows, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for running or developing the sample application on Linux or macOS, nor are there suggestions for equivalent tools or frameworks.
Recommendations
- Provide instructions and examples for running a cross-platform desktop application (e.g., using .NET MAUI, Avalonia, or Electron) that can be developed and executed on Linux.
- Include guidance for setting up the development environment on Linux (e.g., using Visual Studio Code, JetBrains Rider, or the dotnet CLI).
- Offer alternative steps for restoring NuGet packages and running the application using the command line (dotnet restore, dotnet run) instead of Visual Studio.
- Add Linux/macOS-specific screenshots and troubleshooting tips.
- Clearly indicate which steps are Windows-only and provide parity for other platforms where possible.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-role-based-access-control.md
...management/api-management-role-based-access-control.md
High Priority
View Details â
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 custom role creation and assignment, referencing PowerShell before Azure CLI and REST API, and omitting equivalent Linux/bash examples. The use of PowerShell-centric instructions and lack of cross-platform scripting alternatives may disadvantage Linux users or those preferring bash/CLI workflows.
Recommendations
- Add equivalent Azure CLI and bash examples for custom role creation and assignment alongside PowerShell scripts.
- Present Azure CLI and REST API options before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly mention cross-platform compatibility for all tools and scripts.
- Include notes or links to Linux-specific instructions or troubleshooting for common RBAC tasks.
- Ensure that all code samples are available in both PowerShell and bash/CLI formats to improve accessibility for non-Windows users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-using-with-vnet.md
...icles/api-management/api-management-using-with-vnet.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing the Azure portal (a GUI tool most familiar to Windows users) as the primary configuration method and by linking to related content that specifically mentions PowerShell for VPN Gateway connections, without providing equivalent Linux/CLI/Bash examples. There are no explicit Linux or cross-platform command-line instructions, and no mention of Azure CLI or Bash scripting alternatives.
Recommendations
- Add Azure CLI (cross-platform) examples for configuring VNet connectivity and API Management deployment, alongside or before PowerShell/portal instructions.
- Where PowerShell scripts or references are provided (e.g., in related content), include equivalent Bash/Azure CLI commands.
- Explicitly mention that all steps can be performed from Linux/macOS using the Azure CLI or Cloud Shell, and provide links to relevant documentation.
- Balance the order of instructions so that cross-platform (CLI) methods are presented before or alongside Windows-specific tools.
- Review related content links to ensure Linux users are not directed only to PowerShell-based guides.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/automation-manage-api-management.md
...les/api-management/automation-manage-api-management.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exclusively references Azure PowerShell cmdlets and PowerShell workflow scripts for managing Azure API Management via Azure Automation. All examples and tutorials are PowerShell-based, with no mention of Linux-native tools, Bash, Azure CLI, or cross-platform scripting options. This creates a strong Windows and PowerShell bias, potentially excluding Linux users or those preferring platform-neutral automation approaches.
Recommendations
- Add equivalent examples using Azure CLI for API Management tasks within Azure Automation.
- Include Bash or Python script samples for managing API Management, demonstrating cross-platform automation.
- Mention that Azure Automation supports both PowerShell and Python runbooks, and provide links or examples for non-Windows environments.
- Reorder or balance references so that Windows and Linux tools are presented equally, or clarify cross-platform support up front.
- Highlight any limitations or considerations for Linux users, and provide guidance for setting up Azure Automation from Linux environments.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-alternative-processes-self-host.md
...nt/developer-portal-alternative-processes-self-host.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
azure_tools_heavy
Summary
The documentation page focuses exclusively on Azure-centric tools and workflows, with all examples using Azure CLI, Azure Functions, and Azure CDN. There are no Linux-specific instructions, nor are alternative non-Azure or Linux-native tools mentioned. The examples and recommendations assume the use of Azure services, which are most commonly used in Windows environments, and do not provide parity for Linux users or those using open-source alternatives.
Recommendations
- Provide explicit instructions and examples for Linux environments, such as using bash scripts, Linux-native CLI tools, or alternative hosting solutions (e.g., Apache, Nginx, or open-source CDNs).
- Include non-Azure options for hosting and CDN, such as Amazon S3, Google Cloud Storage, Cloudflare CDN, or self-hosted solutions.
- Clarify that all commands (npm, curl, az) are cross-platform, and specify any platform-specific considerations (e.g., installation steps for Azure CLI or Azure Functions Core Tools on Linux).
- Add troubleshooting notes for common Linux issues (e.g., permissions, environment variables, file system differences).
- Balance recommendations by mentioning both Windows and Linux approaches where relevant, and avoid assuming Azure as the default platform.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-faq.md
...b/main/articles/api-management/developer-portal-faq.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation shows a bias towards Windows environments by providing only PowerShell scripts for role assignment and management, referencing .bat scripts for cleanup, and omitting equivalent Bash or CLI examples for Linux/macOS users. Windows tools and patterns are mentioned exclusively, with no Linux alternatives or parity guidance.
Recommendations
- Provide Azure CLI or Bash script equivalents for all PowerShell examples, especially for role creation and assignment.
- Include instructions for running cleanup scripts on Linux/macOS (e.g., provide a .sh script or explain how to adapt the .bat script).
- When referencing scripts or commands, mention both Windows and Linux options, or clarify cross-platform compatibility.
- Order examples so that cross-platform or Linux-native tools (e.g., Azure CLI) are presented before or alongside Windows/PowerShell tools.
- Explicitly state platform requirements or limitations when only Windows tools are available, and link to alternative guidance for Linux users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/devops-api-development-templates.md
...les/api-management/devops-api-development-templates.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows and Azure-centric tools and workflows. It exclusively references Azure DevOps (Azure Repos, Azure Pipelines), GitHub Actions, and the Azure APIOps Toolkit, all of which are primarily oriented toward Windows or Azure environments. There are no explicit examples or mentions of Linux-native CI/CD tools (such as Jenkins, GitLab CI, or Travis CI), nor are there any command-line examples for Linux shells (bash, sh). The documentation also assumes the use of ARM templates and .NET-based tools, which are more common in Windows-centric workflows. While Terraform is mentioned, its usage is described only in the context of Azure Pipelines and GitHub Actions, not in a broader, platform-agnostic way.
Recommendations
- Include examples using popular Linux-native CI/CD tools such as Jenkins, GitLab CI, or Travis CI, and show how they can be used to publish APIs to Azure API Management.
- Provide command-line examples for both PowerShell (Windows) and Bash (Linux/macOS) where relevant, especially for tasks like deploying ARM templates or using the Azure CLI.
- Mention and link to Azure CLI documentation and examples, which are cross-platform, rather than focusing solely on Azure Pipelines or PowerShell-based workflows.
- Highlight that all tools and workflows described can be executed from Linux environments, and provide explicit instructions or notes where there are differences.
- Add a section or callout on best practices for Linux-based development environments, including containerized CI/CD runners and integration with open-source tools.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/graphql-api.md
...-docs/blob/main/articles/api-management/graphql-api.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides examples for the Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell section is Windows-centric, and there is no mention of Linux-specific tools or shell environments (e.g., Bash). The prerequisites list Azure PowerShell and Azure CLI, but the PowerShell section is given equal prominence to CLI, and there are no explicit Linux/Bash examples or troubleshooting notes for Linux users. The documentation also references the Azure Portal, which is web-based and platform-neutral, but command-line examples do not highlight Linux parity.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands using Bash syntax (e.g., export instead of set for environment variables).
- Add a note clarifying that PowerShell examples are primarily for Windows users, and suggest using Azure CLI for Linux/macOS users.
- Include troubleshooting tips or environment setup notes for Linux users, such as installing Azure CLI on Linux.
- Consider adding a Bash-specific example or a section showing how to perform the same tasks in a typical Linux shell environment.
- Where possible, avoid giving the impression that PowerShell is the default or preferred method for all users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/grpc-api.md
...ure-docs/blob/main/articles/api-management/grpc-api.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on the Azure portal (a web-based, cross-platform tool, but often associated with Windows environments), and by only providing .NET/.NET Core examples for calling gRPC services, which are most commonly used on Windows. There are no examples or references for Linux-specific tools, workflows, or alternative client stacks (e.g., grpcurl, curl, or gRPC tools for Linux/macOS). No Linux command-line or shell examples are provided, and the documentation does not mention Linux-specific considerations or tools.
Recommendations
- Add examples for importing gRPC APIs using Linux-friendly tools such as Azure CLI or REST APIs, with bash shell commands.
- Include references to cross-platform or Linux-native gRPC client tools (e.g., grpcurl, grpc_cli) for testing and interacting with gRPC APIs.
- Provide parity in documentation by including .NET, Java, Python, and Go client examples, with explicit mention of Linux/macOS compatibility.
- Mention any Linux-specific prerequisites or troubleshooting steps, if applicable.
- Clarify that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows-centricity.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-api-from-oas.md
...ob/main/articles/api-management/import-api-from-oas.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. The PowerShell example uses Windows-style variable assignment and context setup, which may not be familiar or directly usable for Linux users. The documentation refers to Azure PowerShell requirements in the prerequisites, reinforcing the Windows bias.
Recommendations
- Add explicit bash examples for Azure CLI commands, showing usage in a Linux shell environment.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- De-emphasize PowerShell as the default scripting environment, or provide parity by including bash/zsh examples.
- Mention installation and usage steps for Azure CLI and PowerShell on Linux and macOS, not just Windows.
- If PowerShell is included, note that PowerShell Core is available cross-platform, and provide examples compatible with Linux/macOS.
- Consider adding a table or section comparing workflows on Windows vs. Linux, highlighting any differences.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/protect-with-ddos-protection.md
...rticles/api-management/protect-with-ddos-protection.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation references enabling DDoS IP Protection via a link to a PowerShell-based guide, which is typically associated with Windows environments. There are no examples or instructions for Linux-native tools (such as Azure CLI or Bash), nor is there mention of cross-platform alternatives. The instructions and screenshots focus on the Azure Portal (web UI), which is platform-agnostic, but the only command-line reference is PowerShell, indicating a Windows bias.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide links or code snippets for both.
- Include Bash script examples where appropriate, especially for automation scenarios.
- Review linked pages (such as manage-ddos-protection-powershell-ip.md) to ensure Linux parity and add CLI/Bash alternatives if missing.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/quickstart-arm-template.md
...ain/articles/api-management/quickstart-arm-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page primarily focuses on using the Azure Portal for deployment and only briefly mentions alternative methods (Azure PowerShell, Azure CLI, REST API) without providing any examples. The mention of Azure PowerShell and Azure CLI is secondary, and no Linux-specific instructions or screenshots are provided. The workflow and screenshots are tailored to the Azure Portal, which is more familiar to Windows users, and there are no command-line examples for Linux users.
Recommendations
- Add explicit, step-by-step examples for deploying the ARM template using Azure CLI, which is cross-platform and popular among Linux users.
- Provide both Azure PowerShell and Azure CLI command examples side-by-side, ensuring parity for Windows and Linux users.
- Include screenshots or terminal output examples from Linux environments (e.g., Bash shell) to balance the visual bias toward the Azure Portal.
- Mention that Azure CLI can be used on Windows, Linux, and macOS, and provide installation links for all platforms.
- Consider adding a section or callout specifically for Linux/macOS users, highlighting any differences or tips relevant to those platforms.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/quickstart-terraform.md
...b/main/articles/api-management/quickstart-terraform.md
High Priority
View Details â
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 PowerShell is a Windows-centric tool and is presented as an equal alternative to Azure CLI. There are no explicit Linux shell examples (e.g., bash), and prerequisites mention Azure PowerShell without clarifying its cross-platform status or providing Linux-specific guidance. The documentation implicitly assumes familiarity with Windows tooling and does not offer parity for Linux users beyond Azure CLI.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, or provide explicit bash/Linux shell examples where appropriate.
- Add a dedicated Linux section or call out Linux-specific instructions, especially for environment setup and verification steps.
- Ensure that CLI examples use syntax and environment variables compatible with both Windows and Linux shells, or provide separate examples for each.
- Review prerequisites to include Linux-specific installation instructions for Terraform and Azure CLI/PowerShell.
- Consider mentioning or linking to WSL (Windows Subsystem for Linux) for Windows users who prefer a Linux environment.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/set-backend-service-policy.md
.../articles/api-management/set-backend-service-policy.md
High Priority
View Details â
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 Linux-native alternatives (such as Azure CLI or Bash scripting). No Linux-specific examples or tools are provided, and PowerShell is listed as a primary management method. There are no examples or instructions for managing backend entities from Linux environments.
Recommendations
- Add references and examples for managing backend entities using Azure CLI, which is cross-platform and widely used on Linux.
- Include Bash or shell scripting examples for common backend management tasks.
- Explicitly mention that management can be performed from Linux, macOS, and Windows, and provide parity in tooling instructions.
- List Azure CLI before or alongside PowerShell when enumerating management options.
- Ensure that all code and command examples are platform-neutral or provide both Windows and Linux alternatives.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/secure-mcp-servers.md
...lob/main/articles/api-management/secure-mcp-servers.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Visual Studio Code (a Microsoft tool popular on Windows) as the primary example for client configuration and secure key management. No Linux-specific tools, shells, or configuration examples are provided, and there is no mention of Linux command-line usage or alternative editors. The only client-side tool mentioned is Visual Studio Code, and the documentation does not address Linux-first or cross-platform workflows.
Recommendations
- Include Linux-native examples, such as using curl or httpie for API requests with authentication headers.
- Mention and provide examples for configuring MCP server access using common Linux editors (e.g., Vim, nano) or configuration files.
- Add guidance for managing secrets and environment variables securely on Linux (e.g., using .env files, gnome-keyring, or pass).
- Clarify that Visual Studio Code is cross-platform, or provide alternative instructions for Linux users.
- Where possible, provide shell script or command-line examples (bash/zsh) for Linux users alongside any Windows/PowerShell or Visual Studio Code instructions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md
...ain/articles/app-service/app-service-best-practices.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. It references Windows-specific tools and patterns (e.g., web.config, iisnode) without providing equivalent Linux alternatives or examples. In sections discussing configuration and troubleshooting, only Windows-centric approaches are described, and Linux methods are either omitted or mentioned secondarily. There are also missing Linux-specific examples for common scenarios, such as configuring auto-healing or Node.js process management outside of containers.
Recommendations
- For every mention of web.config or iisnode, provide equivalent Linux configuration methods (e.g., app settings, environment variables, or nginx/Apache config).
- Include Linux-specific examples for auto-healing and process management, such as using PM2 or systemd for Node.js apps.
- When referencing tools or configuration files, clarify which are Windows-specific and offer parallel Linux guidance.
- Ensure that troubleshooting and best practice sections include both Windows and Linux workflows, with examples for each.
- Review and update the Node.js section to include Linux-native hosting guidance, not just iisnode.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias by presenting Windows (non-Linux) examples and tools first in several sections. PowerShell is given equal or more prominence than Azure CLI, and the Azure portal (a GUI tool more familiar to Windows users) is the primary method described for most operations. Linux-specific instructions are minimal and only appear for SKU availability checks.
Recommendations
- Provide Linux examples and instructions alongside or before Windows/PowerShell examples, especially in automation sections.
- Include Bash shell and scripting examples for Linux users, not just Azure CLI and PowerShell.
- Clarify that Azure CLI commands can be run on both Windows and Linux, and provide context for cross-platform usage.
- Add screenshots or walkthroughs using the Azure CLI in a Linux terminal, not just the Azure portal.
- Ensure that any references to the Azure portal are supplemented with equivalent command-line instructions for both platforms.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-injection-resources.md
.../api-management/virtual-network-injection-resources.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily through its references to Windows-centric tools and patterns. For example, the 'Related content' section links to a guide specifically about connecting virtual networks using PowerShell, a tool most commonly associated with Windows. There are no equivalent references to Linux-native tools (such as Azure CLI or Bash scripting), nor are there examples or guidance for Linux users. The documentation does not provide parity for Linux environments, and Windows/PowerShell tools are mentioned exclusively.
Recommendations
- Add equivalent Linux-focused examples and links, such as how to connect virtual networks using Azure CLI or Bash.
- Ensure that for every PowerShell or Windows tool reference, there is a corresponding Azure CLI or Linux-native command example.
- Update the 'Related content' section to include links to Linux/CLI-based guides, not just PowerShell.
- Explicitly mention that all operations can be performed from Linux environments using Azure CLI or REST APIs, and provide sample commands.
- Review the documentation for other implicit Windows-first assumptions and revise language to be platform-neutral where possible.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-workspaces-resources.md
...api-management/virtual-network-workspaces-resources.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates Windows bias primarily by referencing Windows paths before Linux equivalents (e.g., hosts file location), and by using screenshots and instructions that appear to be Azure Portal-centric (which often aligns with Windows workflows). There are no explicit Linux or cross-platform CLI examples (such as Azure CLI or Bash), and the only mention of Linux is secondary, in parentheses after the Windows path. There are no Linux-specific tools or commands provided.
Recommendations
- Provide explicit Linux and macOS examples alongside Windows, especially for common tasks like editing the hosts file.
- Include Azure CLI and Bash command examples for network configuration and resource management, not just portal-based instructions.
- When referencing file paths, list Linux/macOS paths first or equally, not only as a parenthetical after Windows.
- Add screenshots or instructions for cross-platform tools (e.g., Azure CLI, Bash) in addition to or instead of portal screenshots.
- Ensure that any PowerShell or Windows-specific instructions are matched with equivalent Linux/macOS command-line examples.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-key-vault-references.md
...ticles/app-service/app-service-key-vault-references.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuration tasks, but PowerShell examples are always presented immediately after CLI, and there is no mention of Linux-specific tools or shell environments (e.g., Bash, zsh). The CLI examples are generic, but the PowerShell examples reinforce a Windows-centric approach. There are no explicit Linux shell script examples, nor is there discussion of Linux-specific patterns or troubleshooting steps. The troubleshooting and portal navigation instructions do not mention platform differences, but the overall example set leans toward Windows/PowerShell usage.
Recommendations
- Add explicit Bash/zsh shell examples for configuration tasks alongside Azure CLI and PowerShell.
- Clarify that Azure CLI commands work cross-platform and provide shell-specific notes for Linux users.
- Include troubleshooting steps or notes relevant to Linux environments, such as file permissions or environment variable handling.
- Avoid presenting PowerShell examples immediately after CLI by alternating or grouping examples by platform.
- Reference Linux tools or patterns where appropriate, such as using environment variables in Bash scripts.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by presenting Windows-specific information and tools first, such as SKU availability for Windows before Linux, and PowerShell examples alongside Azure CLI. The Azure portal (a Windows-centric tool) is emphasized for configuration steps, and there are no Linux shell or automation examples (e.g., Bash scripts). Linux-specific patterns, such as using Bash or Linux-native tools, are missing, and the documentation does not mention Linux container limitations until after Windows details.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
- Include Bash script examples for automation, especially for Linux users, alongside Azure CLI and PowerShell.
- Clarify when instructions or features differ for Linux and Windows, and provide explicit Linux container guidance.
- Add references to Linux-native tools and workflows (e.g., using SSH, Bash, or Linux package managers) where relevant.
- Ensure that all examples (CLI, scripting, portal) are equally applicable to Linux environments, and note any platform-specific limitations up front.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-undelete.md
...blob/main/articles/app-service/app-service-undelete.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell. All command-line examples are provided exclusively using PowerShell cmdlets (Az PowerShell module), with no mention of Azure CLI, Bash, or cross-platform alternatives. The only non-portal method described is PowerShell, which is primarily associated with Windows environments. There is no guidance for Linux or macOS users, nor are there references to tools or workflows common on those platforms.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, or provide instructions for installing and using PowerShell on Linux/macOS if PowerShell is required.
- Reorder sections or provide parallel instructions so that Azure CLI and PowerShell are presented with equal prominence.
- Include Bash script examples or references to REST API usage for advanced users who may not use PowerShell.
- Clearly indicate any platform-specific limitations or requirements for the tools being used.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md
...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
powershell_heavy
Summary
The documentation is heavily focused on Windows-based hosting using IIS and iisnode, with exclusive references to Windows concepts, tools, and configuration files (such as web.config, named pipes, Win32 error codes, and DLLs). There are no Linux or cross-platform examples, and troubleshooting steps, file paths, and error codes are all Windows-specific. Linux equivalents, tools, or deployment patterns are not mentioned or provided.
Recommendations
- Add sections or examples for running Node.js on Azure App Service for Linux, including configuration and troubleshooting steps relevant to Linux-based environments.
- Provide Linux/Unix equivalents for file paths, error logs, and process management (e.g., referencing /var/log or using PM2 instead of iisnode).
- Include examples using Linux-native tools and patterns (such as systemd, Nginx/Apache reverse proxy, or environment variables) alongside or before Windows/IIS-specific ones.
- Clarify early in the document that the guidance is specific to Windows-based App Service plans, and link to Linux-specific documentation if available.
- Balance the use of Windows-centric terminology (like Win32 error codes, DLLs, web.config) with Linux alternatives (such as exit codes, .env files, or JSON-based configuration).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation contains a minor Windows bias. The only explicit OS-specific command mentioned is for clearing the DNS cache, where only the Windows 'ipconfig /flushdns' command is provided. No equivalent Linux or macOS commands are given. Additionally, the troubleshooting section references Windows first and omits parity for other platforms. There are no PowerShell-heavy sections or exclusive use of Windows tools elsewhere, but the lack of Linux/macOS examples is a notable omission.
Recommendations
- When providing OS-specific troubleshooting commands (such as clearing DNS cache), include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- Wherever Windows-specific tools or patterns are mentioned, ensure Linux and macOS equivalents are also referenced, or clarify that the instructions are cross-platform.
- Review the documentation for any other implicit Windows-first assumptions and add clarifying notes or alternative steps for non-Windows users.
- Consider adding a short section or callout noting that all steps can be performed from any OS, and link to platform-specific DNS troubleshooting guides if needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-customize-sign-in-out.md
...vice/configure-authentication-customize-sign-in-out.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias in the 'Server level (Windows apps only)' section, where IIS and web.config-based authorization is described exclusively for Windows apps, with no Linux equivalent or alternative provided. Windows-specific tools (IIS, web.config) are mentioned, and Linux is only referenced to state that it is unsupported for these features, without offering guidance for Linux users.
Recommendations
- Provide equivalent authorization guidance for Linux-based App Service apps, such as using middleware, configuration files (e.g., appsettings.json), or code samples for popular frameworks (Node.js, Python, .NET Core).
- Include Linux-specific examples and tools where relevant, or link to external resources for Linux authorization patterns.
- When describing platform-specific features, present both Windows and Linux options side-by-side, or clearly direct Linux users to alternative solutions.
- Avoid language that simply states Linux is unsupported; instead, offer actionable alternatives or workarounds for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-user-identities.md
...pp-service/configure-authentication-user-identities.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page provides detailed C#/.NET examples and references to Windows-centric frameworks (ASP.NET, .NET Core, Microsoft.Identity.Web) before mentioning alternatives for other languages. There are no explicit Linux shell, Python, or Node.js code examples, and the only non-.NET examples are brief mentions (PHP, Java) without code. There is no discussion of accessing headers or decoding claims in Linux-native tools or languages, nor any mention of Linux-specific patterns or shell commands.
Recommendations
- Add code examples for popular Linux-first languages such as Python (Flask/Django), Node.js (Express), or Ruby, showing how to access and decode the claims headers.
- Include shell/command-line examples (e.g., using curl and jq) to demonstrate how to inspect or decode the X-MS-CLIENT-PRINCIPAL header.
- Present non-Windows examples (e.g., Python, Node.js) before or alongside .NET/C# examples to avoid a Windows-first impression.
- Expand the 'Framework-specific alternatives' section with concrete code snippets for Linux-prevalent stacks.
- Clarify that the approach is cross-platform and that all examples are equally applicable on Linux and Windows hosts.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-encrypt-at-rest-using-cmk.md
...les/app-service/configure-encrypt-at-rest-using-cmk.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Azure Storage Explorer with Windows-specific instructions and tabs, and by omitting Linux alternatives or parity in tooling and examples. There are no Linux-specific instructions or mentions of Linux-compatible tools for uploading files or generating SAS tokens. The documentation also references GUI-based workflows (Azure portal, Storage Explorer) that are more common on Windows, without CLI or Linux-native alternatives.
Recommendations
- Include instructions for uploading package files and generating SAS tokens using cross-platform tools such as Azure CLI, azcopy, or REST API, with explicit Linux command examples.
- Add Linux-specific tabs or sections alongside Windows instructions when referencing Azure Storage Explorer, or clarify cross-platform compatibility.
- Mention and provide examples for Linux users on how to perform key operations (file upload, SAS generation) without relying on Windows-only tools.
- Ensure that all referenced tools and workflows are available and documented for both Windows and Linux environments, or provide alternatives where necessary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-gateway-required-vnet-integration.md
...service/configure-gateway-required-vnet-integration.md
High Priority
View Details â
Detected Bias Types
windows_only
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily biased towards Windows environments. Gateway-required virtual network integration is explicitly stated to only work for Windows plans, with Linux apps excluded. All troubleshooting and connectivity examples use Windows tools (e.g., PowerShell's Test-NetConnection, netstat), with no mention of Linux equivalents. There are no Linux-specific instructions, examples, or troubleshooting steps, and Windows terminology and tools are used exclusively throughout.
Recommendations
- Clearly state Linux alternatives and limitations at the top of the document, including guidance for Linux users.
- Provide Linux-specific troubleshooting steps and tool equivalents (e.g., use 'nc', 'telnet', or 'ss' for connectivity checks instead of Test-NetConnection and netstat).
- Where features are Windows-only, link to Linux-compatible alternatives (such as regional virtual network integration) and provide migration guidance.
- Include examples and screenshots from Linux environments where possible.
- Ensure parity in documentation structure, so Linux users can easily find relevant information and steps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnet-framework.md
...les/app-service/configure-language-dotnet-framework.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based deployment and configuration patterns, such as Visual Studio publishing, Kudu (CMD/PowerShell), and Windows filesystem paths. There are no Linux-specific examples or instructions, and Windows tools and workflows are mentioned first and exclusively, leaving Linux users without guidance for equivalent tasks.
Recommendations
- Add Linux-specific examples for listing .NET Framework versions, such as using SSH or Linux-based diagnostic tools in App Service Linux environments.
- Include instructions for accessing Kudu or equivalent diagnostic consoles in Linux-based App Service plans.
- Provide guidance for deploying ASP.NET apps from Linux development environments (e.g., using VS Code, CLI, or Git from Linux).
- Mention differences in environment variable access and configuration between Windows and Linux App Service plans.
- Clarify which instructions apply only to Windows App Service and provide parallel steps for Linux where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-linux-open-ssh-session.md
...ticles/app-service/configure-linux-open-ssh-session.md
High Priority
View Details â
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 command-line usage, troubleshooting, and sample output. In contrast, Windows containers are only mentioned briefly, with no equivalent CLI or PowerShell examples, and it is stated that SSH sessions through Azure CLI are not supported for Windows. The documentation focuses on Linux tools and workflows, with no Windows-specific command-line instructions or parity in example depth.
Recommendations
- Add equivalent step-by-step instructions for connecting to Windows containers, including any supported command-line or PowerShell workflows.
- If Azure CLI is not supported for Windows containers, clarify alternative methods (such as PowerShell, RDP, or other remote tools) and provide examples.
- Include troubleshooting steps and sample output for Windows container SSH sessions, similar to the Linux section.
- Ensure that both Linux and Windows sections have comparable detail and actionable guidance for administrators.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnetcore.md
.../articles/app-service/configure-language-dotnetcore.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits a Windows-first bias: Windows instructions and tools (such as Visual Studio and Kudu) are mentioned before Linux equivalents, and Windows-specific patterns (like using CMD/PowerShell in Kudu) are described in detail. Visual Studio is presented as the default publishing tool, with Linux container deployment discussed as an alternative. Linux instructions are present but often follow Windows sections, and some tooling (Kudu, Visual Studio) is Windows-centric.
Recommendations
- Present Windows and Linux instructions in parallel, giving equal prominence to both platforms.
- Include Linux-native tooling and workflows (such as VS Code, CLI, or GitHub Actions) alongside Visual Studio and Kudu.
- Where possible, avoid assuming Visual Studio as the default publishing tool; mention cross-platform alternatives.
- Expand Linux sections to match the detail and clarity of Windows sections, especially for build, deployment, and diagnostics.
- Ensure that introductory and summary content does not prioritize Windows over Linux, and avoid language that frames Linux as secondary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/app-service-app-service-environment-geo-distributed-scale.md
...-service-app-service-environment-geo-distributed-scale.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples for configuring Azure Traffic Manager and App Service Environments. There are no CLI, Bash, or Linux-oriented instructions, and Windows/PowerShell tooling is referenced first and exclusively. This may hinder Linux users or those preferring cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands to support Linux and macOS users.
- Include Bash script snippets or instructions where relevant.
- Explicitly mention that both PowerShell and CLI approaches are supported and provide links to cross-platform tooling.
- Reorganize sections so that cross-platform options (e.g., Azure CLI) are presented before or alongside PowerShell.
- Add notes or callouts for Linux/macOS users regarding tool installation and usage.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-apm.md
...in/articles/app-service/configure-language-java-apm.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation generally provides parity between Windows and Linux instructions, but there are subtle signs of Windows bias. Windows-specific tools (e.g., Kudu console) are mentioned for file operations, while Linux relies on SSH. In some cases, Windows-specific settings (such as 'XDT_MicrosoftApplicationInsights_Java=1') are included, and Windows instructions sometimes appear before or are more detailed than Linux equivalents. There is also a tendency to reference Windows-centric patterns (like Kudu) without offering Linux alternatives (e.g., SCP, SFTP, or Azure CLI for file uploads).
Recommendations
- For file operations, mention Linux-native tools (SCP, SFTP, Azure CLI) alongside SSH, not just SSH for Linux and Kudu for Windows.
- Ensure that Linux instructions are as detailed as Windows ones, especially regarding environment variables and agent configuration.
- When introducing platform-specific settings (like 'XDT_MicrosoftApplicationInsights_Java=1'), explain their Linux equivalents or clarify if not needed.
- Avoid Windows-first ordering in examples and instructions; present Linux and Windows in parallel or alternate which comes first.
- Where possible, provide cross-platform CLI instructions and avoid referencing Windows-only tools unless absolutely necessary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-nodejs.md
...main/articles/app-service/configure-language-nodejs.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (IISNode, web.config) and troubleshooting steps are described in detail, while their Linux equivalents are either omitted or referenced less prominently. Windows instructions and examples often appear before Linux ones, and PowerShell is mentioned for Application Insights instrumentation, with no Linux CLI or Bash alternative. Some sections (e.g., troubleshooting, web.config) are Windows-only, with Linux equivalents missing or relegated to includes. The overall structure and depth of Windows content exceeds that of Linux.
Recommendations
- Ensure Linux instructions/examples are presented with equal prominence and detail as Windows, including troubleshooting and configuration steps.
- Provide Linux/Bash alternatives for PowerShell instructions, especially for instrumentation and automation tasks.
- Include explicit Linux equivalents for Windows-specific tools (e.g., IISNode, web.config), or clarify when they are not needed on Linux.
- Avoid presenting Windows instructions before Linux ones; use parallel structure or combine where possible.
- Expand Linux troubleshooting guidance to match the detail provided for Windows.
- Where platform-specific includes are used, summarize their content or link to them directly for parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-data-sources.md
...es/app-service/configure-language-java-data-sources.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, the Windows section is notably more detailed, with extensive PowerShell scripting and Windows-specific patterns (e.g., startup.cmd, configure.ps1, use of %HOME%, %LOCAL_EXPANDED%, and Windows environment variables). The Linux instructions are more concise and rely on standard shell scripting and package installation, but lack the depth and step-by-step guidance found in the Windows examples. The Windows configuration uses PowerShell and Windows batch files, while the Linux configuration uses shell scripts and standard Linux tools, but the Windows approach is described with more explicit detail and troubleshooting steps. Additionally, Windows-specific tools and patterns (PowerShell, batch files, Windows environment variables) are emphasized, and the Windows section appears before the Linux section in the shared server-level resources area.
Recommendations
- Expand the Linux section to provide equally detailed, step-by-step instructions, including troubleshooting tips and example scripts for common scenarios.
- Provide Linux equivalents for all Windows-specific tools and patterns (e.g., show how to automate configuration with Bash scripts, use environment variables, and manage ephemeral file changes).
- Ensure that Linux instructions appear before or alongside Windows instructions in each section to avoid implicit prioritization.
- Include example startup scripts for Linux that match the complexity and completeness of the Windows PowerShell scripts.
- Add more guidance on managing Tomcat/JBoss configuration files in Linux, including handling ephemeral storage and persistent configuration.
- Where possible, use cross-platform tools and patterns (e.g., Azure CLI, environment variables) in examples to reduce platform-specific bias.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-security.md
...ticles/app-service/configure-language-java-security.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page generally presents security configuration for Java apps on Azure App Service in a cross-platform manner, but there is evidence of Windows bias. Windows concepts and settings (such as Application Settings for disabling features) are mentioned before Linux equivalents, and Linux-specific instructions (such as Java key store management and SSH access) are isolated to a separate section near the end. There are no explicit Linux command-line examples (e.g., bash, Linux CLI), and Windows-centric terminology (like 'Application Setting') is used throughout. Linux tools and patterns (such as environment variable injection, keytool usage) are only briefly covered and not given parity in example depth.
Recommendations
- Provide Linux-specific examples earlier in the documentation, not just in a dedicated section at the end.
- Include Linux command-line examples (e.g., bash scripts, Azure CLI on Linux) alongside any Windows or portal instructions.
- When mentioning configuration via 'Application Settings', clarify how this maps to Linux environments and containers.
- Offer parity in troubleshooting and debugging instructions for both Windows and Linux (e.g., Powershell vs. SSH/bash).
- Explicitly state when instructions apply to both Windows and Linux, or provide side-by-side examples for each platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-php.md
...ob/main/articles/app-service/configure-language-php.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page generally maintains parity between Windows and Linux, using zone pivots to separate platform-specific instructions. However, there are several signs of Windows bias: Windows instructions and examples often appear before Linux ones, especially in sections like 'Show the PHP version', 'Set the PHP version', and 'Change the site root'. Windows-specific tools and paths (e.g., KuduScript, d:\home\site, .dll extensions) are referenced in detail, sometimes with more step-by-step guidance than their Linux equivalents. The Windows deployment automation section is more elaborate, while the Linux section is more concise and refers out to external documentation (Oryx). Some examples, such as enabling diagnostic logs, are more detailed for Windows. There is also a heavier reliance on Windows-centric terminology and tools (e.g., Advanced Tools, KuduScript, .dll files) before mentioning Linux alternatives (.so files, NGINX config).
Recommendations
- Ensure Linux instructions and examples are given equal prominence and detail as Windows, possibly by alternating the order or providing a summary table for both platforms.
- Where Windows-specific tools (e.g., KuduScript, Advanced Tools) are mentioned, provide equivalent Linux tooling or clarify Linux alternatives (e.g., Oryx, SSH, Bash).
- Expand Linux sections to include step-by-step guidance matching the detail given for Windows, especially for deployment automation and troubleshooting.
- Avoid Windows-first ordering in sections; consider starting with Linux or providing a neutral introduction before platform pivots.
- Where file paths or extension types are discussed (.dll vs .so), provide parallel examples and clarify compatibility requirements for both platforms.
- Ensure troubleshooting and diagnostic sections include Linux-specific guidance and examples, not just references to external documentation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by prioritizing PowerShell automation, referencing Azure PowerShell scripts directly, and lacking Linux-specific command-line examples (such as Bash or Azure CLI). While Azure CLI is mentioned, no direct CLI code samples are provided, and the scripting section features only PowerShell code. There are no references to Linux tools or workflows for certificate management, nor are Linux-specific file formats or commands discussed.
Recommendations
- Add direct Azure CLI code samples for certificate binding alongside PowerShell examples.
- Include Linux/Bash workflows for uploading and managing certificates, such as using OpenSSL to generate or convert certificates.
- Reference Linux-specific documentation or guides for certificate management and automation.
- Ensure that scripting and automation sections present both Windows (PowerShell) and Linux (CLI/Bash) options equally and in parallel.
- Mention relevant Linux tools (e.g., OpenSSL, keytool) when discussing certificate formats and uploads.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-managed-instance.md
...ain/articles/app-service/configure-managed-instance.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows-specific features and tooling. All configuration script examples use PowerShell (.ps1), and only Windows Installer (MSI), COM registration, IIS configuration, and registry keys are discussed. Storage mounts reference drive letters and UNC paths, which are Windows-centric. RDP and Bastion access are described solely for Windows environments. There is no mention of Linux equivalents, nor any examples or guidance for Linux-based managed instances.
Recommendations
- Add explicit notes clarifying that Managed Instance on Azure App Service is currently Windows-only, or provide Linux support details if available.
- Where possible, provide parity for Linux: include Bash or shell script examples, discuss Linux configuration patterns (e.g., .sh scripts, systemd services), and describe Linux storage mount conventions (e.g., mounting NFS or SMB shares to /mnt).
- If registry key adapters are Windows-only, clarify this and suggest Linux alternatives (such as environment variables or config files).
- For remote access, mention SSH as the Linux equivalent to RDP/Bastion and provide guidance if/when Linux support is available.
- Review FAQ and examples to ensure Linux users are not misled or excluded; add sections or links for Linux scenarios if/when supported.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-vnet-integration-enable.md
...icles/app-service/configure-vnet-integration-enable.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring virtual network integration, but the PowerShell section is significantly more detailed, with step-by-step instructions and multiple code blocks. PowerShell is a Windows-centric tool, and its prominence (with more elaborate guidance) suggests a bias toward Windows users. There are no Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The ordering also places PowerShell after CLI, but the depth of PowerShell coverage is greater.
Recommendations
- Add equivalent step-by-step instructions for Azure CLI, matching the detail provided for PowerShell.
- Include bash shell examples for Linux users, especially for subnet delegation and resource configuration.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- If possible, provide links or references to Linux-specific guidance or troubleshooting.
- Balance the depth of coverage between PowerShell and CLI to ensure Linux parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate-in-code.md
...icles/app-service/configure-ssl-certificate-in-code.md
High Priority
View Details â
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, examples, and code samples first and in greater detail. Windows certificate store usage is explained thoroughly with C# and Java code, while Linux examples are limited to C# file loading and lack parity in other languages. References to Windows tools and patterns (certificate store, environment variables, user profile loading) are frequent, while Linux equivalents are only briefly mentioned or deferred to external documentation. Non-Windows languages (Node.js, PHP, Python, Java) are not given direct Linux examples.
Recommendations
- Provide Linux-first or parallel examples for all major languages (C#, Java, Node.js, PHP, Python) showing how to load certificates from files or environment variables.
- Expand Linux-specific instructions, including how to use certificate files and environment variables in common Linux application stacks.
- Add explicit Linux code samples for Java, Node.js, PHP, and Python, not just C#.
- Balance explanations of certificate storage and access patterns between Windows and Linux, including container scenarios.
- Reference Linux tools and patterns (e.g., OpenSSL, file permissions, environment variables) alongside Windows tools.
- Ensure that instructions for setting app settings and accessing certificates are equally clear for Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-authentication-types.md
...in/articles/app-service/deploy-authentication-types.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows-centric tools and workflows. Windows tools such as Azure PowerShell, Visual Studio, and migration assistants are featured prominently, often with dedicated rows and references. Visual Studio (Windows-only) is listed before Visual Studio Code (cross-platform), and PowerShell is given its own section. There is a lack of explicit Linux or cross-platform CLI examples, and no mention of Linux-specific deployment tools or workflows (e.g., Bash scripts, SCP, rsync, or Linux package managers). The documentation does not provide parity for Linux users in terms of examples or tool recommendations.
Recommendations
- Add explicit Linux deployment examples, such as using Bash scripts, SCP, rsync, or Linux-based CI/CD tools.
- Include references to cross-platform editors and tools (e.g., VS Code, JetBrains IDEs) before or alongside Windows-only tools like Visual Studio.
- Provide Azure CLI examples using Bash or Zsh shells, and clarify that Azure CLI is cross-platform.
- Mention Linux-native authentication workflows and how they integrate with Azure App Service.
- Balance the documentation by listing cross-platform or Linux-first tools and workflows before or alongside Windows-centric ones.
- Add guidance for deploying from Linux environments, including troubleshooting and best practices.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-best-practices.md
...lob/main/articles/app-service/deploy-best-practices.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific deployment mechanisms (Kudu as a separate process in Windows App Service, WebDeploy, FTP) before mentioning their Linux equivalents. The description of Kudu emphasizes its Windows implementation first and only briefly notes its Linux container role. WebDeploy is a Windows-centric tool, and no Linux-native alternatives (such as rsync, SCP, or SFTP) are discussed. There are no explicit Linux shell or command-line examples for deployment, and the language-specific sections (Java, Node, .NET) do not provide Linux-specific deployment guidance or examples. The only explicit Linux reference is in the GitHub Actions workflow (runs-on: ubuntu-latest), but this is generic and not discussed as a parity point.
Recommendations
- Provide Linux-native deployment examples, such as using SCP, rsync, or SFTP, alongside FTP/WebDeploy.
- Clarify Kudu's role and implementation in Linux App Service before or alongside the Windows description.
- Mention Linux equivalents or alternatives to WebDeploy for file-based deployments.
- Include explicit Linux shell command examples for common deployment tasks.
- Add guidance for troubleshooting and diagnostics using Linux tools or logs, not just Azure portal navigation.
- Ensure language-specific sections (Java, Node, .NET) include Linux deployment caveats or best practices where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-configure-credentials.md
...n/articles/app-service/deploy-configure-credentials.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to CLI. There are no explicit Linux shell (bash) or cross-platform scripting examples, and PowerShell is mentioned as an alternative for most actions. The documentation does not mention Linux-specific tools or patterns, nor does it provide guidance for Linux users beyond a brief note about escaping the dollar sign in Bash. The structure presents Azure CLI first, but PowerShell is always present as a parallel option, which may reinforce a Windows-centric workflow.
Recommendations
- Add explicit bash shell examples for common tasks, such as using curl or other Linux-native tools where appropriate.
- Include notes or sections on using these commands in Linux/macOS environments, including installation and authentication differences.
- Clarify that Azure CLI is cross-platform and provide guidance for using it in Linux environments.
- Where PowerShell is not supported (e.g., user-scope credential creation), provide Linux-native alternatives or clarify the CLI method is recommended for Linux users.
- Add troubleshooting tips for Linux users, such as handling file permissions, environment variables, and shell-specific issues.
- Consider mentioning or linking to documentation for deploying from Linux-based CI/CD pipelines.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-container-azure-pipelines.md
...ticles/app-service/deploy-container-azure-pipelines.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on deploying Windows containers, with all examples, variables, and YAML snippets referencing Windows-specific images (e.g., 'windows-latest') and App Service for Windows. There are no Linux container examples, nor any mention of how to adapt the pipeline for Linux-based workloads. The prerequisites and deployment steps exclusively reference Windows tooling and patterns, omitting Linux alternatives.
Recommendations
- Add parallel examples and instructions for deploying Linux containers to App Service, including YAML snippets using 'ubuntu-latest' or other Linux VM images.
- Include a section in prerequisites for Linux-based apps and Dockerfiles.
- Mention and demonstrate the use of App Service for Containers (Linux) and the corresponding deployment task settings.
- Clarify which steps are Windows-specific and provide guidance for adapting them to Linux scenarios.
- Ensure variable names and pipeline pool settings are not hardcoded to Windows unless strictly required by the scenario.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-intelligent-apps-dotnet-to-azure-sql.md
...service/deploy-intelligent-apps-dotnet-to-azure-sql.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing Windows-centric workflows and tools (e.g., right-clicking in Visual Studio, using Azure Data Studio, and referencing ADO.NET connection strings). There are no explicit Linux or cross-platform CLI examples, nor are Linux-specific tools or deployment patterns discussed. The instructions and code samples assume a Windows GUI workflow and do not mention alternatives for Linux users, such as using VS Code, command-line tools, or Linux-native SQL editors.
Recommendations
- Add explicit instructions for Linux users, such as using VS Code or JetBrains Rider for .NET development, and provide command-line alternatives for file creation and editing.
- Include examples of connecting to Azure SQL using cross-platform tools like sqlcmd, Azure CLI, or DataGrip, and mention how to run the sample app on Linux (e.g., dotnet run).
- Reference Linux-native editors and workflows (e.g., nano, vim, or VS Code) for editing files and managing code.
- Provide guidance for installing .NET SDK and dependencies on Linux distributions (Ubuntu, Fedora, etc.), including package manager commands.
- Ensure all code samples and deployment steps are platform-agnostic or include both Windows and Linux instructions where workflows differ.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-local-git.md
...ocs/blob/main/articles/app-service/deploy-local-git.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples, but PowerShell instructions are given equal prominence and detail, which is a Windows-centric tool. There are references to Windows-specific issues (e.g., native Node.js modules lacking Windows binaries), and troubleshooting mentions Windows errors before Linux equivalents. The use of PowerShell and references to Git Credential Manager (commonly used on Windows) further reinforce a Windows bias. There is no explicit mention of Linux-specific tools or troubleshooting steps, and Linux terminal examples are less detailed.
Recommendations
- Add explicit Linux shell examples alongside PowerShell, especially for steps like creating and configuring web apps.
- Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, SSH keys, case sensitivity).
- Mention Linux equivalents for Git Credential Manager (such as libsecret or credential helpers) and clarify cross-platform authentication steps.
- Ensure that error messages and resolutions cover both Windows and Linux scenarios, including platform-specific build errors.
- Balance the prominence of PowerShell and CLI examples, perhaps by listing CLI (cross-platform) first and PowerShell second.
- Add notes or links for installing and using Azure CLI and Git on Linux/macOS, not just generic installation links.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-zip.md
...zure-docs/blob/main/articles/app-service/deploy-zip.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits several signs of Windows bias. Windows-specific paths (e.g., D:\home\site\wwwroot) are mentioned before Linux equivalents, and the Kudu UI ZIP deploy feature is noted as unavailable for Linux, with only a brief suggestion to use FTP or API instead. The instructions for accessing Kudu (via Azure portal > Advanced Tools) are tailored to Windows environments, and PowerShell examples are provided throughout, while Linux-specific shell examples are limited to generic CLI or cURL commands. There is little discussion of Linux-native tools or workflows, and some features (e.g., ZIP deploy UI) are described as unavailable on Linux without offering Linux alternatives or parity.
Recommendations
- Present Linux and Windows paths and behaviors equally, ideally side-by-side, rather than listing Windows first.
- For features unavailable on Linux (e.g., Kudu ZIP deploy UI), provide detailed Linux alternatives and workflows, such as step-by-step FTP or API usage, and link to Linux-specific guides.
- Include Linux-native tooling and shell examples (e.g., scp, rsync, or Linux file system navigation) where appropriate, not just Azure CLI and cURL.
- Clarify which features are cross-platform and which are Windows-only, and avoid implying Windows as the default or primary environment.
- Expand documentation for Linux users, including troubleshooting, environment setup, and integration with common Linux deployment pipelines.
- Consider adding a parity table or section summarizing feature availability and differences between Windows and Linux App Service environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-publish-profile.md
...ithub-actions/deploy-github-actions-publish-profile.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides platform-specific examples for deploying various app types to Azure Web Apps. For ASP.NET (classic), only a Windows-based workflow is shown, using Windows-specific tools (NuGet, MSBuild) and runs-on: windows-latest. In contrast, all other stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) use Ubuntu runners and cross-platform tools. There is no Linux-based example for classic ASP.NET, and Windows tools are mentioned exclusively for that stack.
Recommendations
- Add a Linux-based workflow example for classic ASP.NET, if supported (e.g., using Mono or .NET Core for legacy projects).
- If classic ASP.NET deployment is only supported on Windows, clarify this limitation explicitly in the documentation.
- Where possible, mention cross-platform alternatives to Windows-only tools (NuGet, MSBuild) or note their platform restrictions.
- Ensure that all stacks have both Windows and Linux examples if supported, or clearly state platform requirements for each.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md
...ent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by primarily referencing Windows-centric development patterns and tools. Instructions for creating and editing files use Visual Studio and right-click context menus, which are exclusive to Windows environments. NuGet package installation is described first via Visual Studio (Windows), with CLI instructions mentioned second. There are no explicit Linux or cross-platform editor instructions (e.g., VS Code, command line, or text editors like nano/vim). The deployment and configuration steps do not mention Linux-specific workflows or tools, and there are no examples of using Linux shell commands or Linux-native editors.
Recommendations
- Add instructions for creating and editing files using cross-platform tools such as VS Code, nano, or vim, and include command-line examples for file creation.
- Present NuGet CLI installation instructions before or alongside Visual Studio instructions to avoid Windows-first ordering.
- Include Linux-specific deployment steps or mention that the process is identical on Linux, clarifying any differences.
- Reference cross-platform editors and workflows throughout, not just Windows-exclusive tools.
- Provide screenshots or terminal commands for Linux environments where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-openid-connect.md
...github-actions/deploy-github-actions-openid-connect.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides platform-specific deployment examples for several languages. For ASP.NET (classic), the workflow exclusively uses Windows runners and Windows-only tools (NuGet, MSBuild), with no Linux alternative or mention. In contrast, all other language examples (ASP.NET Core, Java, Tomcat, Node.js, Python) use Ubuntu runners and cross-platform tools. The ASP.NET section is presented before Java, Node.js, and Python, and does not offer parity for Linux users, indicating a Windows bias in that section.
Recommendations
- Add an ASP.NET (classic) deployment example using Linux runners, if supported, or clarify platform limitations.
- Mention Linux-compatible alternatives to NuGet and MSBuild, or note their platform restrictions.
- Ensure all language tabs provide both Windows and Linux runner options where possible.
- Explicitly state platform requirements and limitations for each example to inform users of cross-platform support.
- Consider reordering or grouping examples so that Windows-specific workflows do not appear to be the default or preferred approach.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-service-principal.md
...hub-actions/deploy-github-actions-service-principal.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides platform-specific examples for several languages. For ASP.NET (classic), only a Windows-based workflow is shown, using Windows-specific tools (NuGet, MSBuild) and 'runs-on: windows-latest'. In contrast, all other stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) use 'runs-on: ubuntu-latest' and cross-platform tools. There is no Linux-based example for classic ASP.NET, nor any mention of Mono or cross-platform build alternatives for .NET Framework. Windows tools and patterns (NuGet, MSBuild, Windows paths) are used exclusively for ASP.NET, and the Windows workflow is presented before Linux alternatives (which are missing for ASP.NET).
Recommendations
- Add a Linux-based example for classic ASP.NET, using Mono or other cross-platform build tools if possible.
- Mention cross-platform alternatives to NuGet and MSBuild for .NET Framework projects, or clarify their platform limitations.
- Explicitly state platform requirements and limitations for each workflow, so users know if Windows is required.
- Consider reordering or grouping examples so that Linux and Windows parity is clear for each language stack.
- For ASP.NET, provide guidance or links for building and deploying on Linux if supported, or explain why only Windows is shown.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md
...ent-apps/deploy-intelligent-apps-linux-python-pivot.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows-first bias, primarily by referencing Windows in quickstart links and deployment instructions, and mentioning Visual Studio as a deployment tool. There is a lack of explicit Linux-specific examples or instructions, especially for deployment, environment variable management, and local development. While some cross-platform elements (like Azure CLI and bash) are referenced in quickstart links, Linux tooling and patterns are not given equal prominence or clarity.
Recommendations
- Add explicit Linux deployment instructions, including examples using Linux-native tools (e.g., VS Code on Linux, GitHub Actions, Azure CLI from bash).
- Ensure that quickstart and sample links do not default to Windows tabs, or provide clear Linux/Bash tabs as the first option.
- Mention Linux environment variable management (e.g., using export in bash, .env files) alongside portal-based configuration.
- Include troubleshooting steps for common Linux deployment issues (e.g., file permissions, case sensitivity).
- Reference Linux-friendly editors and workflows (e.g., VS Code, nano, vim) in addition to Visual Studio.
- Clarify that all code and configuration steps work equally on Linux and Windows, and highlight any platform-specific caveats.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/remove-resource-group-visual-studio-code-2.md
...t-python/remove-resource-group-visual-studio-code-2.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation describes deleting a resource group by right-clicking in a graphical interface, which is a pattern most commonly associated with Windows environments. There is no mention of equivalent Linux workflows, such as using command-line tools (e.g., Azure CLI or Bash). The instructions implicitly assume a Windows-style GUI is being used, and do not provide parity for Linux users.
Recommendations
- Add instructions for deleting a resource group using Azure CLI, including example commands for Bash.
- Clarify which interface is being referenced (e.g., Azure Portal) and mention that the process is the same across platforms if true.
- If applicable, provide screenshots or examples for both Windows and Linux environments.
- Ensure that Linux users are not excluded by offering non-GUI alternatives.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-zip-azure-portal-1.md
...ial-python-postgresql-app/deploy-zip-azure-portal-1.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation references the Azure portal UI, which is a graphical tool commonly used on Windows. There are no examples or instructions for configuring application settings via Linux-friendly methods such as the Azure CLI, Bash, or ARM templates. The instructions implicitly assume use of the portal, which is often associated with Windows workflows, and do not provide parity for Linux users or those preferring command-line interfaces.
Recommendations
- Add equivalent instructions for configuring application settings using the Azure CLI (az webapp config appsettings set) with Bash examples.
- Include ARM template or Bicep configuration snippets for automation and cross-platform usage.
- Explicitly mention that the Azure portal is accessible from any OS, but provide alternatives for users who prefer command-line or automated approaches.
- Ensure that future documentation provides both GUI and CLI examples, with CLI examples not being relegated to secondary status.
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 â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Windows file types and tools (cmd, bat, exe, PowerShell) first and in greater detail, including explicit mention of PowerShell scripts. Windows examples are more numerous and specific, while Linux sections only mention shell scripts (*.sh*) and provide fewer concrete examples. There is a lack of parity in examples and supported file types between Windows and Linux sections.
Recommendations
- Expand Linux sections to list supported file types beyond *.sh*, such as *.py* (Python), *.pl* (Perl), *.rb* (Ruby), *.js* (Node.js), and *.jar* (Java), where applicable.
- Provide explicit examples for Linux, similar to the Windows sections, e.g., 'Using Bash: *.sh*, Using Python: *.py*, Using Node.js: *.js*'.
- Mention Linux tools and runtimes (e.g., Bash, Python, Node.js) with the same specificity as Windows tools (cmd, PowerShell).
- Ensure that examples for language-specific scripts (Java, Node.js, Python) are present in both Windows and Linux sections.
- Consider reordering or presenting Windows and Linux information in parallel to avoid implicit prioritization of Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjobs-supported-platforms.md
...includes/webjobs-create/webjobs-supported-platforms.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation lists Windows hosting options before Linux and gives precedence to Windows-specific file types (.exe, .cmd, .bat) and PowerShell scripts (.ps1) before mentioning Bash scripts and other cross-platform scripting languages. This ordering and emphasis may suggest a bias toward Windows environments and tooling.
Recommendations
- Alternate the order of platform and file type listings to avoid implying priority (e.g., list Linux options first in some sections).
- Provide equal prominence to Linux-native tools and scripting formats (e.g., highlight Bash scripts and Linux containers alongside Windows equivalents).
- Add explicit examples for both Windows and Linux environments to demonstrate parity.
- Clarify that all listed scripting languages and runtimes are equally supported on both platforms, where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-sidecar-multi-container-apps.md
...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by requiring PowerShell for both the script-based migration and for decoding base64 values, providing only PowerShell script examples, and listing PowerShell as a prerequisite. There are no Linux shell (bash/sh) equivalents, and Windows tools and patterns (PowerShell scripting, Windows-style command syntax) are mentioned exclusively and before any Linux alternatives. The manual migration also references PowerShell for base64 decoding, omitting Linux shell commands.
Recommendations
- Provide bash/sh script equivalents for all PowerShell commands, especially for base64 decoding and running migration scripts.
- Offer a Linux-compatible migration script (e.g., update_sidecars.sh) and document its usage alongside the PowerShell script.
- List prerequisites for both Windows and Linux environments, including bash or compatible shells.
- Ensure all examples (script and manual) include both PowerShell and bash/sh commands, presented side-by-side or in separate sections.
- Clarify that Azure CLI is cross-platform and show usage in both Windows and Linux contexts.
- Avoid assuming PowerShell is available by default; mention installation steps for both PowerShell and bash if needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-per-app.md
...blob/main/articles/app-service/manage-scale-per-app.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
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 (such as Azure CLI or Bash). The use of PowerShell cmdlets and parameters is exclusive, and there is no mention of Linux shell commands or cross-platform alternatives. This may disadvantage users working on Linux or macOS environments.
Recommendations
- Add Azure CLI examples for all PowerShell commands shown, demonstrating equivalent functionality in Bash or other Linux shells.
- Include notes or sections clarifying cross-platform support and usage, especially for developers not using Windows.
- Reference Linux-native tools (e.g., Bash, Azure CLI) alongside PowerShell, and avoid presenting Windows tools as the default or only option.
- Ensure that ARM template examples are supplemented with CLI or REST API examples that can be run from any platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/monitor-instances-health-check.md
...articles/app-service/monitor-instances-health-check.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias in several areas: diagnostic information collection and process monitoring are described only for Windows applications (mentioning Process Explorer and memory dumps), with no Linux equivalents or guidance. Windows-specific features (such as the x-ms-auth-internal-token header) are called out, while Linux alternatives or limitations are not explained. In sections where platform differences exist, Windows is mentioned first or exclusively, and Linux parity is not addressed.
Recommendations
- Add equivalent instructions and tooling for Linux-based App Service instances, such as how to collect diagnostics and monitor processes (e.g., using SSH, Linux process tools, or Azure diagnostics extensions).
- Clearly indicate which features are Windows-only and provide Linux alternatives or workarounds where possible.
- Include examples and screenshots for Linux App Service instances, especially in sections on diagnostics and monitoring.
- Where platform-specific limitations exist (such as the x-ms-auth-internal-token header), explain what Linux users should expect and how to achieve similar security or monitoring outcomes.
- Ensure that documentation structure and order does not consistently prioritize Windows features over Linux, and present both platforms equally where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-local-cache.md
...blob/main/articles/app-service/overview-local-cache.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific paths (e.g., D:\home), mentioning Windows containers before Linux containers, and omitting Linux-specific examples or equivalents. Tools and folder structures are described using Windows conventions, and there are no Linux command-line or file path examples. The instructions and troubleshooting steps assume a Windows environment, with no parity for Linux users.
Recommendations
- Include Linux-specific examples, such as file paths (/home/site, /var/log, etc.) and command-line instructions for Linux environments.
- Mention Linux containers and KuduLite earlier and provide guidance for enabling and managing local cache in Linux-based App Service environments.
- Clarify differences in folder structure, environment variables, and cache behavior between Windows and Linux App Service plans.
- Provide equivalent troubleshooting steps and best practices for Linux users, including how to inspect environment variables and manage cache/logs.
- Ensure that references to tools (e.g., Azure Web Apps Disk Usage) are available or have alternatives for Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-managed-instance.md
...main/articles/app-service/overview-managed-instance.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation for Managed Instance on Azure App Service is heavily Windows-centric. All examples, configuration instructions, and tooling references are specific to Windows (e.g., PowerShell scripts, registry, COM, MSI, IIS, GAC, RDP). There are no Linux equivalents, examples, or tooling mentioned, and the platform is explicitly stated as Windows-only. Windows features and patterns are described in detail, while Linux support is only referenced as an alternative in the 'Choosing the Right Hosting Option' section.
Recommendations
- Clearly state Windows-only support in the introduction and limitations sections to set expectations.
- Where possible, provide parity documentation for Linux (or container) hosting options, including configuration, scripting, and troubleshooting workflows.
- Add comparative tables or sections that highlight differences and similarities between Windows and Linux hosting options on App Service.
- Reference Linux tools (e.g., Bash, shell scripts, systemd, Linux file paths) and patterns in relevant sections, even if only to clarify their absence or future roadmap.
- Include links to Linux-focused documentation for users seeking non-Windows solutions.
- If Linux support is planned, add a roadmap or FAQ addressing future parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-security.md
...cs/blob/main/articles/app-service/overview-security.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits subtle Windows bias, particularly in the 'Network security' section, where IP access restrictions mention configuring dynamic IP restrictions through web.config files on Windows apps, without referencing Linux equivalents. There are no explicit Linux-specific examples or instructions throughout the page, and Windows-centric configuration patterns (e.g., web.config) are mentioned before or instead of cross-platform or Linux alternatives. No PowerShell-heavy bias is present, but the overall guidance assumes or prioritizes Windows deployment scenarios.
Recommendations
- Include Linux-specific instructions or examples alongside Windows ones, such as how to configure IP restrictions for Linux-based App Service apps (e.g., using app settings, .htaccess for Apache, or nginx config).
- Avoid referencing Windows-only configuration files (like web.config) without mentioning Linux equivalents or providing cross-platform alternatives.
- Where platform-specific security features or behaviors differ, explicitly call out differences and provide guidance for both Windows and Linux App Service environments.
- Add examples or links for Linux deployment scenarios, such as securing FTP/FTPS deployments on Linux, configuring TLS/SSL certificates, and managing environment variables.
- Review and update documentation to ensure parity in tooling and configuration references, avoiding implicit prioritization of Windows patterns.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-private-endpoint.md
...main/articles/app-service/overview-private-endpoint.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits mild Windows bias. In the 'Related content' section, Windows-centric tools (Azure PowerShell and ARM templates) are listed before Linux-friendly options (Azure CLI, Terraform). PowerShell is given its own quickstart link, and ARM templates are more commonly used in Windows environments. There are no explicit Linux shell examples, and the page does not mention Linux-specific tools or patterns. However, the page does state that private endpoints work for both Windows and Linux apps, and does include a Terraform script link (which is cross-platform).
Recommendations
- Ensure that Azure CLI examples and quickstarts are listed before or alongside PowerShell and ARM template options, as CLI is more commonly used on Linux.
- Add explicit Linux shell (bash) command examples where relevant, especially in sections discussing DNS or network configuration.
- Mention Linux-specific considerations or troubleshooting steps if any exist for private endpoints.
- Clarify that all listed tools (CLI, PowerShell, ARM templates, Terraform) are cross-platform, and provide guidance for both Windows and Linux users.
- Consider adding a section or note on using private endpoints from Linux-based environments, including sample commands and best practices.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview.md
.../azure-docs/blob/main/articles/app-service/overview.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation page demonstrates a Windows bias, particularly in the section describing Managed Instance (preview), which exclusively highlights Windows-specific features such as COM, registry access, MSI, drive mapping, and PowerShell scripts. Windows tools and patterns (e.g., RDP, IIS, ACL, MSMQ) are mentioned without Linux equivalents or alternatives. The Linux and container support is only referenced as 'not supported' for Managed Instance, with no examples or details for Linux users. Command-line tooling mentions Azure PowerShell before Azure CLI, and there are no Linux-specific deployment or management examples.
Recommendations
- Add Linux-specific examples and scenarios, especially in sections discussing deployment, management, and automation.
- When listing command-line tools, mention Azure CLI before or alongside Azure PowerShell, and provide Bash shell examples.
- For features exclusive to Windows (e.g., COM, registry), clarify Linux alternatives or workarounds, or explicitly state the parity gap.
- Include Linux/container-focused quickstart and decision guides, with clear instructions and links.
- Balance tool and pattern mentions by referencing Linux-native tools (e.g., Bash, SSH, systemd) where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-custom-container.md
...in/articles/app-service/quickstart-custom-container.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Windows pivots and tools (such as Visual Studio, Powershell, and Windows CLI) before their Linux equivalents. There are multiple pivots for Windows-specific tools and workflows, including Powershell and Visual Studio, while Linux pivots are fewer and focus mainly on Visual Studio Code and the Azure Portal. There is no explicit Linux CLI or shell example provided, and Windows tools are mentioned more frequently and prominently.
Recommendations
- Add Linux CLI and shell examples (e.g., Bash, Azure CLI on Linux) to match the Windows CLI and Powershell pivots.
- Ensure Linux pivots are listed with equal prominence and order as Windows pivots.
- Include examples using common Linux tools and workflows, such as Docker commands in Bash.
- Balance the number of Windows and Linux pivots to provide parity in guidance.
- Explicitly mention Linux alternatives when referencing Windows-specific tools (e.g., Visual Studio vs Visual Studio Code).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/routine-maintenance-downtime.md
...n/articles/app-service/routine-maintenance-downtime.md
High Priority
View Details â
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 concepts such as IIS Application Initialization and .NET Core stdout logging are described in detail, while Linux alternatives are mentioned briefly or as afterthoughts. There is a lack of parity in example depth and guidance for Linux users, and Windows terminology and tools are referenced more frequently throughout the document.
Recommendations
- Provide equally detailed Linux examples and explanations for features like application initialization, warm-up, and logging.
- Introduce Linux-specific tools and patterns (e.g., systemd, Nginx, Apache, container health checks) alongside Windows/IIS features.
- Ensure that Linux options (such as WEBSITE_WARMUP_PATH) are described with the same depth and practical guidance as Windows features.
- Avoid presenting Windows features first; alternate or parallelize explanations for Windows and Linux where possible.
- Include troubleshooting and testing scenarios specifically tailored for Linux environments, not just Windows.
- Reference Linux documentation and best practices for logging, start-up, and health checks.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/resources-kudu.md
...-docs/blob/main/articles/app-service/resources-kudu.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page for Kudu service overview demonstrates a Windows bias by referencing IIS diagnostic dumps, IIS processes, and deployment webhooks specifically for Windows apps. There are no explicit examples or mentions of Linux-specific features, tools, or deployment patterns, and Windows-related terminology (IIS, Windows apps) is presented without Linux equivalents or parity.
Recommendations
- Include examples and documentation for Linux-based App Service environments, such as how to access Linux diagnostic logs or manage Linux processes via Kudu.
- Clarify which features are Windows-specific and provide Linux alternatives or note feature parity (e.g., mention Docker logs for Linux apps alongside IIS dumps for Windows).
- Add deployment webhook instructions for Linux apps if supported, or explicitly state any limitations.
- Ensure that references to server management (e.g., IIS) are balanced with equivalent Linux technologies (e.g., Nginx, Apache) where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-nodejs.md
...cs/blob/main/articles/app-service/quickstart-nodejs.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides both Linux and Windows deployment instructions, but Windows-specific tools and patterns (such as web.config, Application Insights, and resource group naming conventions) are mentioned in detail, sometimes before or with more emphasis than their Linux equivalents. Some sections, especially under Visual Studio Code deployment, provide more granular steps for Windows (e.g., web.config generation) without equivalent Linux-specific troubleshooting or configuration guidance. The CLI instructions default to Linux, but Windows is always called out as a special case, and some troubleshooting notes (e.g., web.config) are only present for Windows. There is also a slight tendency to mention Windows-specific requirements (like web.config) without offering Linux-specific configuration notes.
Recommendations
- Ensure Linux-specific troubleshooting and configuration steps (such as dealing with startup scripts, environment variables, or permissions) are included and given equal prominence to Windows-specific notes.
- Where Windows-specific tools or files (e.g., web.config) are discussed, provide equivalent Linux context (e.g., startup command configuration, app settings) and cross-reference Linux documentation.
- Balance the order and detail of instructions so that Linux and Windows are presented with parity, both in depth and in sequence.
- Include Linux-specific deployment caveats, such as file permissions, default startup scripts, or common issues, similar to the detailed Windows notes.
- If advanced options (like Application Insights or resource group naming) are discussed for Windows, ensure Linux users are informed of their equivalents or differences.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-webjobs.md
...s/blob/main/articles/app-service/quickstart-webjobs.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows examples and tools before Linux equivalents. The Windows tab includes more scripting options (CMD, Batch, PowerShell, F#) that are specific to Windows, while the Linux tab only lists cross-platform languages. Windows-specific tools and patterns (CMD, Batch, PowerShell) are highlighted, and the order of presentation prioritizes Windows. There is no mention of Linux-specific scripting languages (e.g., shell variants beyond Bash) or Linux-native tools.
Recommendations
- Present Linux and Windows options with equal prominence, possibly listing Linux first or side-by-side.
- Include Linux-native scripting examples (e.g., Perl, Ruby, or other common Linux scripting languages) if relevant.
- Add explanations for why certain scripting languages/tools are only available on Windows, and suggest Linux alternatives.
- Ensure that instructions and samples for both platforms are equally detailed and comprehensive.
- Avoid listing Windows-specific tools (CMD, Batch, PowerShell) without Linux equivalents or alternatives.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-storage.md
...cles/app-service/scenario-secure-app-access-storage.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by providing installation instructions using Visual Studio's Package Manager Console (PowerShell) and referencing Windows-specific tooling before mentioning cross-platform alternatives. There is no explicit mention of Linux or macOS environments, nor are there examples using Linux-native tools or instructions for non-Windows users.
Recommendations
- Add explicit instructions for installing NuGet packages on Linux/macOS, such as using the .NET CLI (which is cross-platform) and clarify that it works on all platforms.
- Reorder installation instructions to present the .NET Core command-line (dotnet CLI) method first, as it is platform-agnostic, before mentioning Windows-specific Package Manager Console.
- Include a note or section for Linux/macOS users, highlighting any platform-specific considerations (e.g., how to open a terminal, install .NET SDK, etc.).
- Avoid referencing Visual Studio or Windows-only tools without also mentioning cross-platform alternatives.
- Ensure that all examples and instructions are clearly marked as cross-platform where applicable, and provide parity for Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/samples-resource-manager-templates.md
...cles/app-service/samples-resource-manager-templates.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_examples
missing_linux_example
Summary
The documentation provides both Linux and Windows template samples, but Windows examples are generally listed before Linux equivalents in several sections. There are more Windows-specific scenarios (including Windows containers and database connections) than Linux ones, and some sections group Linux examples separately, suggesting Windows as the default. Some connected resource examples are only shown for Windows, with Linux equivalents either missing or listed separately.
Recommendations
- Present Linux and Windows examples together, in parallel, rather than grouping Windows as default and Linux as a special case.
- Ensure every Windows scenario (e.g., database connections, containers) has a Linux equivalent, or explicitly state if not supported.
- Alternate the order of examples, or use neutral headings (e.g., 'App Service plan and basic app (Linux/Windows)').
- Add more Linux-focused samples, such as Linux container deployments, to match Windows parity.
- Review and update connected resource examples to ensure both OS platforms are equally represented.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in its instructions for installing NuGet packages: it lists the Visual Studio Package Manager Console (PowerShell-based, Windows-only) before mentioning the .NET Core CLI, and provides PowerShell install commands without equivalent Linux/macOS shell examples. There is no explicit mention of Linux or cross-platform development environments, nor are Linux-specific instructions or screenshots provided.
Recommendations
- Provide explicit Linux/macOS instructions for installing NuGet packages, such as using the .NET CLI in bash/zsh.
- List cross-platform (CLI) instructions before Windows-specific (Visual Studio/PowerShell) instructions.
- Clarify that the .NET CLI commands work on Windows, Linux, and macOS, and include example shell commands for Linux/macOS environments.
- Avoid referencing Windows-only tools (like Package Manager Console) without mentioning alternatives for other platforms.
- Include notes or screenshots for Linux/macOS environments where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/terraform-secure-backend-frontend.md
...p-service/scripts/terraform-secure-backend-frontend.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively using Windows-based App Service resources (azurerm_windows_web_app, os_type: Windows) in the Terraform examples. There are no examples or mentions of Linux-based web apps (azurerm_linux_web_app, os_type: Linux), nor any guidance on deploying Linux workloads. The documentation also references Windows-specific service plans and omits Linux equivalents, which may mislead users into thinking only Windows is supported or recommended.
Recommendations
- Include parallel examples using azurerm_linux_web_app and os_type: Linux to demonstrate Linux parity.
- Mention that both Windows and Linux App Service plans are supported and provide guidance for choosing between them.
- Add notes or sections highlighting differences and considerations for Linux-based deployments (e.g., app settings, runtime support).
- Ensure that any referenced tools, scripts, or commands are cross-platform or provide Linux alternatives where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/template-deploy-private-endpoint.md
...pp-service/scripts/template-deploy-private-endpoint.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates bias towards Windows by exclusively providing a PowerShell example for resource cleanup, without mentioning or providing equivalent commands for Linux users (such as Azure CLI or Bash). The use of PowerShell cmdlets and lack of cross-platform instructions may hinder Linux users from following the guide seamlessly.
Recommendations
- Include Azure CLI examples alongside PowerShell for resource group deletion (e.g., 'az group delete --name <your resource group name>').
- Explicitly mention that both Windows and Linux users can use the Azure Portal for deployment, and provide CLI/Bash alternatives where possible.
- Add notes or sections clarifying cross-platform compatibility and provide links to relevant Linux documentation.
- Review other steps for implicit Windows assumptions and ensure parity in instructions for Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-http-502-http-503.md
...articles/app-service/troubleshoot-http-502-http-503.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary CLI tool for managing Azure resources, mentioning DOS commands in the Kudu console, and suggesting the use of Windows-specific tools like ProcDump. There are no examples or mentions of Linux shell equivalents, nor are Linux troubleshooting tools or commands provided. Windows-centric patterns and terminology appear before or instead of Linux alternatives.
Recommendations
- Include Linux shell (bash/sh) command examples for managing Azure resources, such as using Azure CLI in bash.
- Mention Linux-compatible diagnostic tools (e.g., gcore, strace, lsof) alongside ProcDump for memory dumps and troubleshooting.
- Clarify that the Kudu console supports both PowerShell and bash, and provide examples for both environments.
- Avoid using Windows/DOS terminology exclusively; provide parity with Linux commands and workflows.
- Add explicit instructions or links for troubleshooting on Linux-based App Service environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-performance-degradation.md
...es/app-service/troubleshoot-performance-degradation.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways. It references Windows-specific tools (such as IIS logs, Procdump from SysInternals, and PowerShell), and links to resources with 'Windows' in the title. Examples and instructions for Linux-based App Service environments are missing, and Windows-centric terminology and tools are mentioned first or exclusively. There is no mention of Linux equivalents for diagnostics, logging, or troubleshooting, nor are Bash or Linux command-line examples provided.
Recommendations
- Add explicit instructions and examples for Linux-based App Service environments, including how to access logs, enable diagnostics, and troubleshoot performance.
- Include Bash or Linux shell command examples alongside PowerShell commands.
- Reference Linux-native tools (such as strace, lsof, top, or gdb) for diagnostics and memory dumps, and explain how to use them in App Service on Linux.
- Clarify which features and tools are available on Windows vs. Linux App Service plans, and provide links to Linux-specific documentation where appropriate.
- Avoid using Windows-centric terminology (e.g., IIS, web.config) without noting Linux alternatives (e.g., Apache/Nginx, app settings).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-auth-aad.md
...cs/blob/main/articles/app-service/tutorial-auth-aad.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. Windows instructions and examples are presented before Linux equivalents in several sections, and some tooling references (such as Azure portal navigation and 'Advanced Tools') are more familiar to Windows users. While Linux-specific pivots are present, they are sometimes less detailed or appear after Windows instructions. There are no PowerShell-specific examples, but the overall flow and screenshots are more Windows-centric.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which platform appears first in each section.
- Ensure screenshots and portal navigation steps are equally clear for Linux users, possibly including Linux-specific screenshots where UI differs.
- Explicitly mention any differences in tooling or behavior between Windows and Linux App Service plans.
- Where possible, provide CLI-only instructions that work identically on both platforms, reducing reliance on portal steps.
- Review all examples for parity in detail and clarity between Windows and Linux pivots.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-app-access-sql-database-as-user-dotnet.md
...utorial-connect-app-access-sql-database-as-user-dotnet.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. While the main workflow uses Azure CLI (cross-platform), several sections reference Windows-centric tools (SQL Server Management Studio, Visual Studio, and Integrated Windows authentication) without mentioning Linux alternatives or giving parity to Linux workflows. The publishing instructions and local debugging guidance are focused on Visual Studio and Git Bash, omitting Linux-native editors and deployment methods. There are no explicit Linux or macOS examples for connecting to SQL Database, debugging, or publishing, and Windows tools are mentioned first or exclusively in some cases.
Recommendations
- Include examples for connecting to Azure SQL Database using Linux-native tools such as Azure Data Studio, sqlcmd on Linux, or other cross-platform clients.
- Add instructions for publishing code using Linux editors (e.g., VS Code on Linux, JetBrains Rider) and deployment via Azure CLI or Git from Linux/macOS terminals.
- When referencing SQL Server Management Studio (SSMS), also mention Azure Data Studio as a cross-platform alternative.
- Provide local debugging guidance for Linux and macOS environments, including how to obtain and use access tokens outside of Windows.
- Avoid mentioning Windows authentication patterns unless directly relevant, and clarify differences for Linux users.
- Ensure screenshots and step-by-step instructions are not Windows-specific, or provide Linux/macOS equivalents where appropriate.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/includes/include-deploy-sample-application.md
...-testing/includes/include-deploy-sample-application.md
High Priority
View Details â
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 and Windows-centric instructions for deploying the sample application. All command-line examples use PowerShell syntax, and the deployment script is a PowerShell script. Linux and macOS users are only briefly mentioned in a tip about installing PowerShell, but no native Bash or shell examples are provided. The documentation also references Windows tools and patterns (e.g., .ps1 scripts, PowerShell modules) without offering Linux alternatives.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, especially for deployment steps.
- Include instructions for running the deployment using native Linux tools (e.g., Bash, sh), or provide a cross-platform script.
- Mention Linux-first approaches, such as using Azure CLI directly in Bash, and list these before or alongside Windows/PowerShell instructions.
- Reference Linux-specific tools or commands where applicable, such as using 'curl' or 'wget' for downloading files, and provide region code lookup via Azure CLI instead of PowerShell modules.
- Clearly indicate which steps are platform-specific and offer parity for each major OS.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-dotnet-deploy-vs.md
.../main/articles/app-service/webjobs-dotnet-deploy-vs.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows development environments, specifically Visual Studio, and provides instructions and examples exclusively for Windows users. There are no references to Linux development workflows, tools, or deployment patterns. All UI instructions, screenshots, and project templates are based on Visual Studio for Windows, and there is no mention of cross-platform alternatives or command-line approaches suitable for Linux users.
Recommendations
- Add instructions for developing and deploying WebJobs using cross-platform tools such as VS Code, the Azure CLI, or GitHub Actions.
- Include Linux-specific examples for creating, configuring, and deploying WebJobs, such as using the dotnet CLI and zip deployment.
- Reference alternative editors and workflows (e.g., JetBrains Rider, VS Code) that work on Linux and macOS.
- Provide guidance for managing WebJobs from Linux environments, including file structure and deployment steps.
- Ensure parity in screenshots and step-by-step guides for non-Windows platforms.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-assign-roles.md
...ticles/app-testing/load-testing/how-to-assign-roles.md
High Priority
View Details â
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 role management, with no mention of Azure CLI or Bash equivalents commonly used on Linux and macOS. The 'Configure Azure RBAC' section presents PowerShell before any cross-platform alternatives, and does not reference Linux-specific tools or workflows. This may hinder Linux users who do not use PowerShell.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, using Bash syntax where appropriate.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
- Provide links to Azure CLI documentation alongside PowerShell references.
- Consider reordering sections to present cross-platform tools (Azure CLI) before platform-specific ones (PowerShell).
- Include troubleshooting steps and examples relevant to Linux environments.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-configure-customer-managed-keys.md
...load-testing/how-to-configure-customer-managed-keys.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI and portal instructions, but PowerShell is often presented before CLI. The use of PowerShell-specific cmdlets and terminology (e.g., New-AzKeyVault, Add-AzKeyVaultKey) reflects a Windows-centric approach. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or patterns. The documentation assumes familiarity with Windows tools and workflows, which may disadvantage Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell usage notes where relevant.
- Add example shell commands using Bash (e.g., variable assignment, piping output) to illustrate Linux-native workflows.
- Avoid referring to PowerShell as the default automation tool; clarify that both PowerShell and Azure CLI are supported.
- Where screenshots or UI instructions are given, clarify any OS-specific differences (if any) in the Azure portal experience.
- Consider adding a section or note for Linux users, highlighting best practices or common issues when using Azure CLI and Key Vault.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-key-vault-common-errors.md
...gateway/application-gateway-key-vault-common-errors.md
High Priority
View Details â
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 Azure CLI or Linux shell commands. The troubleshooting steps and guidance are oriented around the Azure portal and PowerShell, which are more commonly used on Windows platforms. There is no mention of Linux tools or cross-platform alternatives, and PowerShell is presented as the default method for scripting tasks.
Recommendations
- Add Azure CLI examples alongside PowerShell for all certificate management and troubleshooting steps, ensuring parity for Linux and macOS users.
- Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and link to cross-platform installation guides.
- Include screenshots or instructions for Azure CLI usage in addition to Azure portal steps.
- Review all scripting and automation guidance to ensure both Windows and Linux users are supported equally.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/quickstart-automate-end-to-end-testing.md
...t-workspaces/quickstart-automate-end-to-end-testing.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments and tooling. PowerShell and AzPowershell are used in CI examples, and Windows-centric tools (PowerShell, Azure PowerShell) are referenced for authentication and setup. There is a lack of explicit Linux shell (bash/sh) examples, and Windows tools are mentioned before their Linux equivalents, even in contexts (CI runners) that are cross-platform. The documentation does not provide parity for Linux-native commands or workflows, and assumes familiarity with Windows/PowerShell patterns.
Recommendations
- Provide equivalent bash/sh examples for all PowerShell commands, especially for CI/CD steps and authentication.
- Reference cross-platform Azure CLI commands before or alongside Azure PowerShell, especially for authentication and service principal creation.
- Explicitly mention Linux and macOS compatibility in setup instructions, and provide examples for these platforms.
- Avoid using Windows-specific terminology (e.g., 'AzPowershell') as the default; clarify when steps are platform-specific.
- Add a section or tab for Linux-first workflows, including common shell usage and troubleshooting tips for non-Windows environments.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias primarily through its 'Next steps' section, which links only to a PowerShell-based tutorial for creating an autoscaling, zone-redundant Application Gateway. There are no equivalent examples or references for Linux users (e.g., Azure CLI or ARM templates), and PowerShellâa Windows-centric toolâis presented as the default or sole method for deployment tasks.
Recommendations
- Add equivalent tutorials and examples using Azure CLI, which is cross-platform and widely used on Linux.
- Include ARM/Bicep template deployment instructions for infrastructure-as-code parity.
- Explicitly mention that PowerShell is just one of several supported tools, and provide links to Linux-friendly alternatives.
- Review all code samples and ensure that both Windows and Linux usage scenarios are covered equally.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/tutorial-run-end-to-end-tests.md
...playwright-workspaces/tutorial-run-end-to-end-tests.md
High Priority
View Details â
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'), and does not provide Linux/macOS-specific shell examples or mention platform differences. The use of 'terminal or command window' language and the absence of explicit Linux instructions or screenshots further reinforce the Windows-centric approach.
Recommendations
- Provide command-line examples using both PowerShell/Command Prompt and Bash/zsh syntax, or use cross-platform commands where possible.
- Explicitly mention that instructions apply to Windows, Linux, and macOS, and clarify any platform-specific steps.
- Include screenshots or references for Linux/macOS environments where relevant (e.g., terminal, file paths).
- Avoid using only Windows terminology such as 'command window'; use 'terminal' or specify both.
- Add a section or note about platform compatibility and any differences in setup or usage.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/quickstart-run-end-to-end-tests.md
...aywright-workspaces/quickstart-run-end-to-end-tests.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-centric tools and workflows, such as the Azure portal (with Windows-style screenshots), Visual Studio Code, and PowerShell/dotnet commands. There is a lack of explicit Linux or cross-platform examples for key steps (e.g., environment variable setup, CLI usage, authentication), and no mention of Linux-specific tools or terminal environments. The instructions and visuals assume a Windows user experience, with no guidance for Linux users on alternative workflows.
Recommendations
- Add explicit Linux and macOS examples for CLI commands, environment variable setup, and file paths (e.g., bash, zsh, export PLAYWRIGHT_SERVICE_URL).
- Include screenshots or instructions for using Azure portal and Playwright CLI from Linux desktop environments.
- Mention alternative editors (e.g., VS Code on Linux, Vim, etc.) and provide parity for test running outside Visual Studio Code.
- Clarify that the Azure CLI and Playwright CLI are cross-platform, and provide troubleshooting tips for Linux users.
- Where PowerShell or dotnet commands are shown, also show equivalent bash/zsh commands for Linux users.
- Add a section or callout for Linux prerequisites (e.g., installing Node.js, Azure CLI on Linux) and note any OS-specific considerations.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md
...les/application-gateway/application-gateway-ilb-arm.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively uses Windows PowerShell and Azure PowerShell cmdlets for all steps, with no mention of Linux, Bash, Azure CLI, or cross-platform alternatives. Windows-centric tools and patterns are referenced throughout, and there are no examples or instructions for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Add a section or callouts for Linux/macOS users, including prerequisites and installation instructions for Azure CLI.
- Reference Bash scripting and show how to perform the same operations using shell scripts.
- Avoid language such as 'switch PowerShell mode' or 'Using Windows PowerShell' without mentioning alternatives.
- Ensure that links to further documentation include both PowerShell and CLI/Bash options.
- Consider adding a table comparing PowerShell and CLI commands for each major step.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-diagnostics.md
...application-gateway/application-gateway-diagnostics.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for enabling diagnostic logging, referencing Windows-centric tools (Excel, Power BI, Visual Studio, C#), and omitting equivalent Linux or cross-platform CLI instructions (such as Azure CLI or Bash). The guidance for log conversion and analysis also centers on Windows developer tools, with no mention of Linux-friendly alternatives. Windows/PowerShell methods are presented first and exclusively in the automation section.
Recommendations
- Add equivalent Azure CLI (az) examples for enabling diagnostic logging, suitable for Linux/macOS users.
- Include instructions or scripts using Bash or other cross-platform shells for log retrieval and processing.
- Mention and provide examples for viewing and analyzing logs with Linux-native tools (e.g., jq, awk, grep, pandas in Python).
- Reference cross-platform data visualization tools (e.g., Grafana, Kibana) alongside Power BI and Excel.
- Provide log conversion examples using open-source or platform-neutral tools (e.g., Python scripts) rather than Visual Studio/C#.
- Ensure that automation and scripting sections present both Windows and Linux approaches, or use platform-neutral methods where possible.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md
...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the primary method for viewing cipher suite ordering and configuring TLS policies. There is no mention of Linux-specific tools or command-line examples (such as Bash, OpenSSL, or Linux Azure CLI usage). The 'Next steps' section links only to a PowerShell-based configuration guide, and instructions for setting policies mention PowerShell before CLI, with no Linux shell or cross-platform parity. This may hinder Linux administrators or those using non-Windows environments.
Recommendations
- Add Linux-specific examples for configuring TLS policies, such as using Azure CLI in Bash or shell scripts.
- Include references to Linux tools (e.g., OpenSSL, curl) for verifying TLS versions and cipher suites.
- Ensure that CLI instructions are presented alongside or before PowerShell examples to promote cross-platform parity.
- Provide links to documentation for configuring TLS policies from Linux/macOS environments.
- Clarify that Azure CLI is cross-platform and provide explicit instructions for its use on Linux.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell examples before Azure CLI, referencing PowerShell-specific cmdlets, and using terminology and screenshots that align with Windows-centric workflows (e.g., Azure portal navigation, PowerShell commands). There is no explicit mention of Linux shell scripting or alternative Linux-native tools, and the CLI examples are less detailed than their PowerShell counterparts. The documentation does not provide parity for Linux users in terms of command-line examples, troubleshooting, or tool recommendations.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
- Include Bash shell scripting examples for common tasks, especially for feature registration and NSG/route table configuration.
- Add explicit references to Linux environments, such as using Azure CLI on Linux/macOS, and clarify that CLI commands work cross-platform.
- Provide troubleshooting steps and screenshots for Linux users (e.g., Azure CLI in Bash, terminal output).
- Mention and link to Linux-native automation tools (e.g., Ansible, shell scripts) where appropriate.
- Ensure that all instructions and examples are validated on both Windows and Linux platforms.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/certificates-for-backend-authentication.md
...ion-gateway/certificates-for-backend-authentication.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Windows Certificate Manager and PowerShell for certificate export instructions. All screenshots and step-by-step guidance are based on Windows GUI tools, with no mention of Linux or cross-platform alternatives. There are no CLI or OpenSSL examples, and the only reference to further configuration is via PowerShell, further reinforcing the Windows-centric approach.
Recommendations
- Add equivalent instructions for exporting certificates using OpenSSL or other common Linux tools.
- Include CLI-based examples for both Windows and Linux to ensure parity and accessibility for users on non-Windows platforms.
- Mention and demonstrate how to perform these tasks on macOS, if relevant.
- Provide links or references to cross-platform certificate management documentation.
- Avoid implying that Windows tools are the default or only option; present alternatives side-by-side.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-ssl-portal.md
...main/articles/application-gateway/create-ssl-portal.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows, with all certificate creation and VM setup examples using Windows PowerShell and Windows Server. There are no Linux equivalents or alternative instructions for creating self-signed certificates or deploying backend servers with Linux. Windows tools and patterns (e.g., New-SelfSignedCertificate, Export-PfxCertificate, Add-WindowsFeature) are used exclusively, and Windows is presented as the default/first option throughout.
Recommendations
- Add equivalent Linux instructions for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
- Provide examples for deploying Linux VMs as backend servers, including installation of a web server (e.g., Apache or Nginx) for testing.
- Include Bash/Azure CLI commands alongside PowerShell for resource management and VM extension installation.
- Clearly state that both Windows and Linux are supported as backend targets, and provide parity in step-by-step guidance.
- Mention cross-platform certificate management tools and reference relevant documentation for Linux users.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-multiple-sites-portal.md
...es/application-gateway/create-multiple-sites-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation exhibits a clear Windows bias: virtual machine creation is demonstrated exclusively with Windows Server, IIS installation is shown only via PowerShell, and host file editing and DNS commands use Windows-specific paths and tools. There are no Linux VM examples, nor instructions for Apache/Nginx setup, nor Linux shell commands for host file editing or DNS cache management.
Recommendations
- Add parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend server.
- Provide Linux-based web server setup steps (e.g., install Apache or Nginx) using Bash or Azure CLI.
- Include host file editing instructions for Linux/macOS (e.g., /etc/hosts) and relevant commands for DNS cache flushing (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo service network-manager restart').
- Show Azure CLI examples alongside PowerShell for VM extension installation and other automation tasks.
- Clarify that Application Gateway supports both Windows and Linux backend servers, and provide links to relevant Linux documentation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/deploy-basic-portal.md
...in/articles/application-gateway/deploy-basic-portal.md
High Priority
View Details â
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 preview registration and IIS installation use Azure PowerShell, with no mention of Bash, CLI, or Linux alternatives. The VM creation walkthrough exclusively uses Windows Server 2019, and IIS (a Windows-only web server) is used for backend testing, with no Linux VM or Apache/Nginx examples. The documentation does not provide parity for Linux users, omitting instructions for deploying Linux VMs or using Linux-native tools.
Recommendations
- Provide Azure CLI (bash) examples alongside PowerShell for preview registration and unregistration.
- Include instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
- Offer guidance for installing and testing with Apache or Nginx on Linux VMs, in addition to IIS on Windows.
- Mention Linux as a supported backend OS in the VM creation section.
- Ensure screenshots and walkthroughs are not exclusively tied to Windows Server, and clarify that backend pools can use both Windows and Linux VMs.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/diagnostics.md
...cles/application-gateway/for-containers/diagnostics.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides a detailed PowerShell example for enabling diagnostic logs, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only automation example is Windows-centric, and Windows tools (PowerShell, Excel) are mentioned before or instead of cross-platform or Linux-native alternatives. This creates a bias toward Windows users and may hinder Linux users from easily following the instructions.
Recommendations
- Add Azure CLI and Bash examples for enabling diagnostic logs, alongside the PowerShell example.
- Mention cross-platform tools (such as jq, grep, or Linux text editors) for viewing and analyzing logs, in addition to Excel and Power BI.
- Ensure that instructions and screenshots are not Windows-specific, or provide parity for Linux/macOS environments.
- Present examples for both Windows and Linux environments side-by-side, or in tabs, to improve accessibility for all users.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-tcp-tls-proxy.md
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
High Priority
View Details â
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 example and referencing SQL Server Management Studio (a Windows-only tool) for client connectivity. There are no instructions or examples for deploying SQL Server on Linux, nor for connecting from Linux clients or using cross-platform tools. Windows options are mentioned first and exclusively throughout the guide.
Recommendations
- Provide parallel instructions for deploying SQL Server on Linux (e.g., Ubuntu) using supported images.
- Include examples for connecting to SQL Server from Linux clients, such as using sqlcmd, Azure Data Studio, or other cross-platform tools.
- Mention both Windows and Linux options when describing SQL Server license selection and deployment.
- Add screenshots or CLI commands relevant to Linux environments.
- Clarify that Application Gateway TCP/TLS proxy works with both Windows and Linux backends.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation displays mild Windows bias in the Helm installation section, where Windows installation instructions (including use of Windows Package Manager 'winget' and PowerShell syntax) are presented before Linux instructions. The use of 'winget' is a Windows-specific tool, and the PowerShell example is given explicitly. Most other commands are cross-platform (Azure CLI, Helm, kubectl, bash), and Linux instructions are present, but Windows is prioritized in ordering and tooling.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel tabs or in the same order, or default to Linux first as it is more common for Kubernetes workloads.
- Provide explicit Bash examples for all commands where PowerShell is shown, especially for Azure CLI and Helm usage.
- Mention Linux package managers (apt, yum, dnf, snap) for Helm installation alongside 'winget' for Windows.
- Clarify that Azure CLI and Helm commands are cross-platform and can be run in Bash, PowerShell, or Azure Cloud Shell.
- Avoid presenting Windows-specific tools (like 'winget') before Linux equivalents; give equal prominence to both.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/troubleshooting-guide.md
...cation-gateway/for-containers/troubleshooting-guide.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is given after the Linux example (using grep), which is a positive sign for parity. However, the Windows example uses the generic 'cli' tag rather than 'powershell', and there are no PowerShell-specific examples or Windows-only tools referenced. The rest of the documentation is platform-neutral, focusing on kubectl and helm commands, which are cross-platform. There is no evidence of missing Linux examples, but the Windows example could be improved by specifying PowerShell usage if relevant.
Recommendations
- Ensure that both Linux and Windows examples are provided wherever OS-specific commands are needed.
- Clarify whether the Windows example is intended for Command Prompt or PowerShell, and provide PowerShell syntax if different.
- Consider using tabs or callouts to make OS-specific instructions more visually distinct and easy to follow.
- Review future updates to ensure Linux and Windows parity in troubleshooting steps, especially for log filtering and file redirection.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/http-response-codes.md
...in/articles/application-gateway/http-response-codes.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing NTLM authentication (a Windows-specific protocol) and linking to Microsoft Windows documentation. In the 504 Gateway time-out section, IIS (a Windows web server) is mentioned and described first, with configuration details and links, while Nginx (a common Linux web server) is mentioned second with less detail. There are no Linux-specific troubleshooting examples or parity in tool coverage, and no PowerShell or CLI examples are present, but the overall pattern prioritizes Windows technologies and documentation.
Recommendations
- Provide equivalent Linux examples and troubleshooting steps, such as Apache or Nginx configuration details for time-out settings, with links to official documentation.
- When discussing authentication issues, mention Linux-compatible authentication mechanisms (e.g., Kerberos, OAuth) and provide troubleshooting steps for those.
- Ensure that references to backend server configuration (IIS, Nginx) are presented in parallel, with equal detail and prominence.
- Include examples or links for both Windows and Linux environments when discussing backend pool health, diagnostics, or probe configuration.
- Avoid referencing Windows-specific protocols (like NTLM) without mentioning alternatives or implications for Linux-based backends.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-arm-template.md
...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates bias towards Windows by exclusively using IIS (a Windows web server) for backend validation, referencing only PowerShell (Remove-AzResourceGroup) for resource cleanup, and omitting Linux-based alternatives or examples (such as using Nginx/Apache or Azure CLI/Bash commands). No Linux VM configuration or validation steps are provided.
Recommendations
- Include examples of deploying Linux-based VMs (e.g., Ubuntu with Nginx or Apache) in the backend pool.
- Provide validation steps using Linux tools (e.g., curl, wget) to test the application gateway.
- Offer resource cleanup instructions using Azure CLI (az group delete) and Bash commands alongside PowerShell.
- Clarify that IIS is optional and suggest Linux alternatives for users preferring open-source stacks.
- Ensure screenshots and walkthroughs are platform-neutral or show both Windows and Linux scenarios.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-install-existing.md
...ication-gateway/ingress-controller-install-existing.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Several command examples use PowerShell syntax and variables, especially in identity and role assignment steps, rather than pure Bash or cross-platform shell. The backup instructions reference the Azure portal's export, which includes PowerShell scripts, and Windows-centric tools are mentioned. PowerShell examples are given before or instead of equivalent Bash commands in some cases. While Cloud Shell is recommended (which is cross-platform), the documentation assumes familiarity with PowerShell scripting and does not always provide Linux/Bash alternatives for all steps.
Recommendations
- Provide Bash equivalents for all PowerShell command examples, especially for identity and role assignment steps.
- Clarify that PowerShell examples are for Windows users and add explicit Bash alternatives for Linux/macOS users.
- When referencing exported scripts (e.g., from Azure portal), note which are for Windows (PowerShell) and which are for Linux (Bash), and provide guidance for both.
- Avoid using PowerShell variable syntax ($variable) in command examples unless specifically targeting Windows; use Bash syntax where appropriate.
- Ensure that all instructions and examples are platform-neutral or include both Windows and Linux/macOS variants.
- Review the order of examples to avoid presenting Windows/PowerShell commands before Linux/Bash equivalents unless justified.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-overview.md
.../application-gateway/mutual-authentication-overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows bias by providing detailed PowerShell examples and references before Azure CLI equivalents, and by linking to a PowerShell-specific configuration guide as the primary next step. There are no Linux-specific examples or mentions of Linux tools for certificate management or configuration, and the CLI example is minimal compared to the PowerShell section. The documentation does not mention or demonstrate Linux-native workflows, such as using OpenSSL or Bash scripting, for certificate extraction or management.
Recommendations
- Provide Linux-specific examples for certificate extraction and management, such as using OpenSSL commands.
- Expand Azure CLI examples to match the detail and coverage of PowerShell examples.
- Include Bash or shell script snippets for common tasks, such as uploading certificates or verifying OCSP status.
- Link to both PowerShell and CLI configuration guides in the 'Next steps' section, and consider adding a Linux-focused guide.
- Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux administrators throughout the documentation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/multiple-site-overview.md
...articles/application-gateway/multiple-site-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a mild Windows bias by consistently mentioning Azure PowerShell before Azure CLI in instructions and examples, and by providing explicit PowerShell parameter details (e.g., '-HostNames') prior to CLI equivalents. The references to Azure PowerShell and CLI are presented as separate, but PowerShell is often listed first, and the step-by-step guides link to PowerShell before CLI. There is also a focus on Windows-centric tooling (PowerShell), with no mention of Linux-specific shell usage or examples, nor any explicit parity checks for Linux environments.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI references, or present CLI examples first to balance platform representation.
- Provide explicit bash or Linux shell examples where relevant, especially for Azure CLI usage.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, while PowerShell is primarily Windows-centric (though now available cross-platform).
- Include notes or links for Linux users regarding installation and usage of Azure CLI and PowerShell on Linux.
- Ensure that all example commands are shown in both PowerShell and bash/CLI syntax, and avoid assuming the reader is using Windows tools.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-certificate-management.md
...ateway/mutual-authentication-certificate-management.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively describing certificate export procedures using Windows GUI tools (Certificate Manager, Certificate Export Wizard) and referencing PowerShell for certificate management. There are no Linux-specific instructions or examples for exporting certificates, and the Linux command is only mentioned for concatenating files, not for the main certificate export workflow. Windows tools and screenshots dominate the guide, with Linux alternatives missing or relegated to a secondary role.
Recommendations
- Add step-by-step instructions for exporting certificates using Linux command-line tools such as openssl.
- Include Linux-specific screenshots or terminal output examples for certificate export and inspection.
- Present Linux and Windows procedures in parallel, or clearly separate them, to ensure parity and clarity for users of both platforms.
- Reference Linux certificate stores and management tools (e.g., certtool, openssl, keytool) where appropriate.
- Avoid assuming the use of Windows GUI tools; provide CLI alternatives for cross-platform accessibility.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is given a dedicated section with detailed step-by-step instructions and full command examples before the Azure CLI section. The PowerShell section is more verbose and references Windows-specific cmdlets, while the CLI section is somewhat shorter and less explanatory. There are no Linux shell or scripting examples (e.g., Bash), and no mention of Linux-specific tools or considerations. The ordering and depth of PowerShell coverage suggest a 'Windows-first' approach.
Recommendations
- Add Bash shell examples for key steps, especially for subnet and endpoint configuration, to improve Linux parity.
- Ensure CLI instructions are as detailed and explanatory as PowerShell instructions, including troubleshooting and verification steps.
- Explicitly mention cross-platform compatibility for Azure CLI and clarify that PowerShell Core can be used on Linux/macOS.
- Consider reordering sections so that CLI and Bash examples appear before or alongside PowerShell, rather than after.
- Add notes or links for Linux users regarding installation and usage of Azure CLI and PowerShell Core on non-Windows platforms.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-http-to-https-portal.md
...s/application-gateway/redirect-http-to-https-portal.md
High Priority
View Details â
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 use PowerShell, including certificate creation and IIS installation. The virtual machine scale set is configured with Windows Server 2016 by default, and instructions for backend web server setup exclusively use IIS and Windows-centric tooling. There are no examples or guidance for Linux-based VMSS, certificate creation on Linux, or using Linux web servers such as Apache or Nginx.
Recommendations
- Provide equivalent Linux examples for certificate creation (e.g., using OpenSSL) and exporting PFX files.
- Include instructions for creating a VMSS with a Linux OS image (such as Ubuntu or CentOS) and installing a Linux web server (Apache, Nginx) in the backend pool.
- Offer Bash/Azure CLI alternatives to PowerShell commands throughout the tutorial.
- Clarify that both Windows and Linux are supported and link to relevant Linux-focused documentation.
- Add screenshots and walkthroughs for Linux-based backend configuration and testing.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation page demonstrates Windows bias by referencing configuration via the Azure portal and linking to a PowerShell-based tutorial for next steps, without mentioning or providing equivalent Linux-oriented instructions (such as Azure CLI or Bash). There are no examples or references to Linux tools or workflows, and the only actionable configuration guidance is Windows-centric.
Recommendations
- Include equivalent instructions and examples using Azure CLI and Bash for Linux users.
- Provide links to tutorials or documentation for configuring Application Gateway redirection via Linux-friendly tools.
- Ensure that next steps and code samples are presented for both Windows (PowerShell) and Linux (CLI/Bash) environments.
- Explicitly mention cross-platform options in the overview and configuration sections.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/proxy-buffers.md
...lob/main/articles/application-gateway/proxy-buffers.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides configuration examples using Azure CLI, PowerShell, and ARM templates. PowerShell is given a dedicated section with detailed examples for both creating and updating Application Gateways, while no equivalent Linux shell or Bash examples are provided. The PowerShell method is presented before the ARM template method, and PowerShell is a Windows-centric tool. There is also a reference to the Azure SDK for .NET, another Windows-preferred technology, without mention of cross-platform SDKs. No explicit Linux/Bash or cross-platform scripting alternatives are shown.
Recommendations
- Add Bash shell examples for configuring buffer settings using Azure CLI to demonstrate parity for Linux users.
- Clarify that Azure CLI commands work on both Windows and Linux, and provide explicit Bash syntax where relevant.
- Include examples using cross-platform SDKs (e.g., Python, Java) in addition to .NET.
- Reorder example sections so that cross-platform methods (Azure CLI, ARM templates) are presented before Windows-specific tools like PowerShell.
- Explicitly mention that PowerShell Core is available on Linux, if relevant, or provide guidance for Linux users on using PowerShell Core.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-portal.md
...in/articles/application-gateway/quick-create-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a bias toward Windows environments. The only virtual machine example provided is Windows Server 2016 Datacenter, with no mention of Linux VM alternatives. The instructions for backend setup and testing exclusively use Windows tools (IIS) and Azure PowerShell, with no Linux equivalent (e.g., Apache/Nginx, Bash/SSH) provided or referenced. The step-by-step VM creation process is Windows-centric, and the installation/testing steps rely on Windows-specific technologies.
Recommendations
- Add parallel instructions for creating and configuring a Linux VM (e.g., Ubuntu) as a backend server.
- Provide Linux-based examples for installing a web server (e.g., Apache or Nginx) and testing connectivity.
- Include Azure CLI and Bash/SSH commands for Linux VM setup and web server installation, alongside PowerShell examples.
- Explicitly mention that Application Gateway supports both Windows and Linux backends, and link to relevant Linux documentation.
- Present Windows and Linux options side-by-side, or alternate which is shown first, to avoid 'windows_first' bias.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/renew-certificates.md
...ain/articles/application-gateway/renew-certificates.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, referencing PowerShell-specific patterns (such as SecureString), and omitting any Linux-specific guidance or examples. There are no mentions of Linux tools, shell environments, or platform-specific considerations for certificate file handling or scripting. The CLI example is generic and does not address Linux-specific nuances.
Recommendations
- Add explicit Linux shell (bash) examples for certificate renewal, including file path conventions and password handling.
- Clarify any platform-specific differences in certificate file formats or command usage between Windows and Linux.
- Present Azure CLI instructions before or alongside PowerShell to avoid Windows-first ordering.
- Include troubleshooting tips or notes for Linux users, such as file permissions or environment setup.
- Reference Linux-native tools (e.g., OpenSSL) for certificate management where relevant.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/retirement-faq.md
...ob/main/articles/application-gateway/retirement-faq.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of Azure PowerShell scripts for migration guidance, with no mention of Linux-friendly alternatives such as Azure CLI or Bash scripts. All automation and migration examples reference PowerShell, a Windows-centric tool, and there is no parity for Linux users. Additionally, Windows tools and patterns are mentioned first and exclusively, with no consideration for cross-platform usage.
Recommendations
- Provide equivalent Azure CLI and Bash script examples for migration tasks, especially for retaining public IPs and configuration migration.
- Explicitly mention cross-platform support and clarify which steps can be performed on Linux/macOS systems.
- Add notes or sections for Linux users, including troubleshooting and environment setup guidance.
- Ensure that all PowerShell script references are accompanied by Azure CLI alternatives where possible.
- Review and update documentation to avoid assuming Windows as the default platform for automation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Linux equivalents or Bash/CLI alternatives. The instructions assume a Windows environment (e.g., file paths like c:\appgwcert.pfx) and do not provide guidance for users on Linux or macOS platforms. There are no Azure CLI or Bash script examples, and Windows tools/patterns are mentioned exclusively and first.
Recommendations
- Add equivalent Azure CLI (az) commands for each step, especially for resource creation and configuration.
- Provide instructions and examples for generating self-signed certificates on Linux/macOS (e.g., using openssl).
- Use platform-neutral file paths and note differences for Windows vs. Linux/macOS.
- Include a section or callout for Linux/macOS users, highlighting any required changes or alternative commands.
- Where possible, use cross-platform tools and avoid exclusive reliance on Windows-specific utilities.
- Consider reordering or parallelizing examples so Linux/macOS options are presented alongside Windows/PowerShell.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/self-signed-certificates.md
...ticles/application-gateway/self-signed-certificates.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates some Windows bias. Windows and Windows-specific tools (IIS, PowerShell) are mentioned before or more prominently than Linux equivalents. The Azure PowerShell example is provided in detail, while no Azure CLI (cross-platform) example is given. IIS instructions are listed before Apache/NGINX, and the PowerShell upload sample is provided without a Linux/CLI alternative.
Recommendations
- Add Azure CLI examples for uploading certificates and configuring Application Gateway, alongside PowerShell.
- Present Linux and Windows web server configuration instructions in parallel, or alternate the order to avoid Windows-first bias.
- Include explicit instructions for certificate management on Linux (e.g., how to add a root certificate to Linux trusted store).
- Reference Linux tools and patterns (such as using systemd or Linux file paths) where appropriate.
- Ensure parity in troubleshooting and verification steps for both Windows and Linux environments.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-arc.md
...e-docs/blob/main/articles/automanage/automanage-arc.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation lists Windows Server versions first in the supported operating systems section and includes a Windows-only service (Microsoft Antimalware) in the participating services table. There are no Linux-specific examples, tools, or configuration patterns provided, and the guidance does not mention Linux alternatives for antimalware or other OS-specific management tasks.
Recommendations
- List Linux distributions before or alongside Windows Server versions in the supported operating systems section to avoid 'windows_first' bias.
- For services like antimalware, mention Linux equivalents (e.g., integration with third-party Linux antivirus solutions) or clarify that the feature is Windows-only and suggest alternatives for Linux users.
- Provide Linux-specific examples, configuration patterns, or troubleshooting steps where relevant, especially for services that behave differently on Linux.
- Include links to Linux best practices or documentation for configuring and managing supported Linux distributions with Automanage.
- Highlight any limitations or differences in feature support between Windows and Linux, so users are aware of OS-specific considerations.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-smb-over-quic.md
...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition as the required VM image for SMB over QUIC and Automanage capabilities. All examples and instructions are tailored to Windows environments, with no mention of Linux support, equivalents, or alternative tooling. The only deep link for further learning is to Windows Server documentation, reinforcing the Windows-centric approach.
Recommendations
- Clarify whether SMB over QUIC and Automanage best practices are supported on Linux VMs. If not, explicitly state this limitation.
- If Linux support exists or is planned, provide equivalent instructions and examples for deploying and managing SMB over QUIC on Linux VMs.
- Include references to Linux documentation or tooling where applicable, such as Samba or other SMB implementations.
- Present platform options side-by-side, rather than Windows-only, to ensure parity and reduce bias.
- If only Windows is supported, add a section explaining why and what alternatives Linux users can consider.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/move-automanaged-configuration-profile.md
...s/automanage/move-automanaged-configuration-profile.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. There are no Linux or cross-platform CLI (e.g., Bash, curl, Azure CLI) equivalents provided, which may disadvantage users on Linux or macOS systems. The page assumes familiarity with PowerShell and does not mention alternative approaches for non-Windows environments.
Recommendations
- Add equivalent examples using Bash and curl for REST API calls.
- Provide Azure CLI commands for profile management, which are cross-platform.
- Explicitly mention that the process can be performed from Linux/macOS and provide sample commands.
- Consider a 'Platform parity' section highlighting differences and options for Windows, Linux, and macOS users.
- Avoid assuming PowerShell as the default or only method; present alternatives side-by-side.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/tutorial-create-assignment-python.md
...ticles/automanage/tutorial-create-assignment-python.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation demonstrates Windows bias by exclusively providing examples for creating a Windows virtual machine, omitting Linux VM creation steps. Both Azure CLI and PowerShell instructions are given, but PowerShell (a Windows-centric tool) is presented as an equal alternative, and no Linux-specific shell or command examples are provided. The tutorial does not mention or show how to use Linux images or create Linux VMs, nor does it address Linux-specific considerations for Automanage.
Recommendations
- Add examples for creating a Linux virtual machine using both Azure CLI and PowerShell, including specifying a Linux image (e.g., Ubuntu, CentOS).
- Explicitly mention Linux support in the prerequisites and steps, clarifying that Automanage can be used with both Windows and Linux VMs.
- Include screenshots or portal instructions that show Automanage applied to Linux VMs.
- If there are differences in Automanage profile assignment or prerequisites for Linux VMs, document those clearly.
- Consider adding bash or shell script equivalents for steps where PowerShell is used, to improve accessibility for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-configuration-based-on-stig.md
...tomation/automation-dsc-configuration-based-on-stig.md
High Priority
View Details â
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 tooling references centered around PowerShell DSC and Windows environments. Linux is only mentioned in passing, with no concrete examples, instructions, or equivalent tooling for Linux systems. The guidance, resources, and next steps are exclusively Windows/PowerShell-oriented.
Recommendations
- Include explicit examples and instructions for configuring Linux servers with STIG baselines using Azure Automation State Configuration.
- Reference and link to Linux DSC resources or equivalent configuration management tools (e.g., Chef, Ansible, or native Linux DSC support).
- Provide parity in documentation by showing how to generate and apply configurations for Linux, not just Windows.
- Clarify any limitations or differences in Azure Automation State Configuration support for Linux vs. Windows.
- Add Linux-focused next steps and resources, such as guides for onboarding Linux machines and managing their configurations.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-config-aws-account.md
...n/articles/automation/automation-config-aws-account.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing only Windows-centric tools and documentation, such as linking to AWS PowerShell credential instructions and omitting any mention of Linux or cross-platform alternatives. There are no examples or guidance for Linux users, such as using AWS CLI or bash scripts, and the documentation assumes familiarity with Windows patterns and Azure portal workflows.
Recommendations
- Include examples for authenticating AWS from Linux environments, such as using AWS CLI and bash scripts.
- Reference AWS documentation for both PowerShell and CLI tools, providing links to Linux/macOS instructions.
- Clarify that Azure Automation runbooks can be authored in multiple languages (PowerShell, Python, etc.), and provide sample code for each.
- Add guidance for storing and retrieving credentials using cross-platform methods, not just Azure portal workflows.
- Explicitly mention platform-agnostic approaches and ensure parity in instructions for both Windows and Linux users.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/repair-automanage-account.md
.../main/articles/automanage/repair-automanage-account.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates Windows bias by mentioning PowerShell as a primary method for ARM deployments before Linux alternatives, providing explicit PowerShell module references, and omitting Linux-specific shell examples (e.g., Bash). Windows tools and patterns (PowerShell, Azure portal screenshots) are referenced directly, while Linux equivalents are not discussed or shown.
Recommendations
- Add explicit Bash shell examples for ARM template deployment alongside PowerShell, using Azure CLI commands suitable for Linux/macOS.
- When listing command-line options, present Azure CLI (cross-platform) before PowerShell, or at least in parallel, to avoid Windows-first ordering.
- Include screenshots or instructions for Azure portal usage on non-Windows platforms (if relevant), or clarify that the portal is platform-agnostic.
- Reference Linux/macOS environments in prerequisites or notes, and provide troubleshooting tips for those platforms.
- Avoid referring to PowerShell modules as the default or primary method; instead, present both PowerShell and Bash/Azure CLI as equal options.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/add-user-assigned-identity.md
...main/articles/automation/add-user-assigned-identity.md
High Priority
View Details â
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 use PowerShell, which is primarily a Windows tool (despite cross-platform support, most Linux users prefer Bash or CLI). There are no Bash, Azure CLI, or Linux-native shell examples. REST API and ARM template deployment steps are also shown using PowerShell. Even the Python example uses Windows-centric environment variables and patterns. The documentation does not mention or demonstrate Linux workflows, nor does it provide parity for Linux users who may use Bash, Azure CLI, or other native tools.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for all PowerShell examples.
- Provide Bash shell script examples for REST API calls and ARM template deployments.
- Explicitly mention Linux support and provide steps for Linux environments, including authentication and environment variable handling.
- Clarify cross-platform compatibility for PowerShell scripts, or recommend alternatives for Linux users.
- Include troubleshooting and verification steps using Azure CLI and Bash.
- Ensure that Python examples work seamlessly on Linux and document any OS-specific considerations.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-child-runbooks.md
.../main/articles/automation/automation-child-runbooks.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page is heavily focused on PowerShell-based runbooks and Windows-centric tools and patterns. All examples use PowerShell syntax and cmdlets, such as Start-AzAutomationRunbook, Get-AzVM, and Disable-AzContextAutosave, with no mention of Linux-native scripting languages (e.g., Bash, Python) or cross-platform alternatives. Windows/PowerShell terminology is used exclusively, and there are no Linux or non-PowerShell examples or guidance. The documentation assumes the user is working in a Windows/PowerShell environment, omitting Linux-specific considerations and parity.
Recommendations
- Provide equivalent examples using Python runbooks, which are supported in Azure Automation and commonly used on Linux.
- Include Bash or shell script runbook examples and guidance for Linux users.
- Mention cross-platform considerations, such as authentication and context management for Linux-based runbooks.
- Clarify which features and cmdlets are available or limited on Linux, and provide alternatives where possible.
- Add links to documentation for creating and managing runbooks in Linux environments.
- Avoid using Windows/PowerShell terminology exclusively; use neutral language where possible.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-managing-data.md
...b/main/articles/automation/automation-managing-data.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows-specific instructions and links are presented before Linux equivalents, PowerShell cmdlets are referenced heavily for resource management and backup, and Windows registry/TLS settings are described in detail while Linux guidance is minimal or generic. Linux examples are limited, with only a single Python script for TLS configuration and no Linux-native command-line or automation tool references for backup/export tasks.
Recommendations
- Provide Linux-native examples for all resource management and backup operations, such as using Azure CLI, Bash scripts, or Python scripts for exporting runbooks, DSC configurations, and other assets.
- Reference Linux tools and patterns (e.g., cron jobs, shell scripts, Azure CLI) alongside or before Windows/PowerShell equivalents to ensure parity.
- Include explicit instructions for Linux users on how to confirm TLS settings, export resources, and manage assets, rather than relying on generic OpenSSL references.
- Balance the documentation by giving equal prominence and detail to Linux and Windows procedures, including links to relevant Linux documentation.
- Avoid assuming PowerShell is the default automation tool; mention cross-platform alternatives like Azure CLI or REST API where possible.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-connections.md
...lob/main/articles/automation/automation-connections.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. PowerShell cmdlets and workflows are presented first and in detail, with explicit references to 'Windows PowerShell' and Az modules. There are no examples or guidance for Linux shell environments (e.g., Bash, CLI), nor are Linux-native tools or patterns mentioned. The only alternatives provided are Python examples, but these are not positioned as Linux-specific, and the overall workflow assumes a Windows-centric approach to automation and connection management.
Recommendations
- Add Azure CLI examples for managing connections, including creation, retrieval, and deletion, to provide parity for Linux and cross-platform users.
- Include Bash shell script samples for accessing connection assets and authenticating with Azure, where possible.
- Explicitly mention cross-platform compatibility and clarify which steps/tools are Windows-only versus available on Linux/macOS.
- Reorder sections so that PowerShell and CLI/Bash examples are presented side-by-side or in parallel tabs, rather than PowerShell-first.
- Reference Linux-native tools and workflows (e.g., OpenSSL, jq, curl) where appropriate, especially in custom module and authentication scenarios.
- Provide troubleshooting and usage notes for Linux environments, including any differences in module installation or asset management.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-create-standalone-account.md
...les/automation/automation-create-standalone-account.md
High Priority
View Details â
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 management and runbook creation, referencing PowerShell runbooks and cmdlets extensively, and omitting equivalent instructions for Linux users (e.g., Azure CLI or Bash). The 'Next steps' section also prioritizes PowerShell tutorials and references, with Python mentioned only after multiple PowerShell links. No Linux-specific tools or workflows are discussed.
Recommendations
- Add Azure CLI (az) command examples for all operations currently shown only with Azure PowerShell, such as key rotation.
- Include Bash or shell script examples where relevant, especially for Linux users.
- In the 'Next steps' section, provide equal prominence to Python and Azure CLI tutorials, and add links to Bash or cross-platform automation resources.
- Mention cross-platform tools and workflows (e.g., Azure CLI, REST API) alongside PowerShell, not just as an afterthought.
- Clearly indicate that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide alternative instructions for those platforms.
- Wherever a PowerShell cmdlet is referenced, provide the equivalent Azure CLI command.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-config-from-server.md
...ticles/automation/automation-dsc-config-from-server.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows and PowerShell. It only references Windows PowerShell 5.1, PowerShell DSC, and Windows-centric tools and resources (SharePointDSC, ReverseDSC). There are no Linux-specific examples, tools, or instructions, and all guidance assumes a Windows environment. Linux onboarding is mentioned only as a link, with no substantive content or parity in the main instructions.
Recommendations
- Add explicit examples and instructions for Linux environments, including how to generate configurations from Linux servers.
- Reference and link to Linux equivalents for Desired State Configuration, such as Open Management Infrastructure (OMI) or Ansible.
- Clarify which steps are Windows-specific and provide alternative steps for Linux users.
- Include sample scripts or walkthroughs for Linux configuration extraction and MOF file generation.
- Ensure that documentation titles, introductions, and prerequisites reflect cross-platform applicability, or clearly state Windows-only scope if Linux is not supported.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-overview.md
...ob/main/articles/automation/automation-dsc-overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing primarily on PowerShell DSC, listing Windows operating systems and requirements in detail before Linux, referencing Windows-specific tools (WMF, WinRM), and providing examples and links that are PowerShell-centric. Linux support is mentioned but lacks equivalent detail, examples, and tool references. There are no Linux-specific configuration or onboarding examples, and the continuous deployment example uses Chocolatey, a Windows package manager.
Recommendations
- Provide Linux-specific examples for onboarding, configuration, and management using Azure Automation State Configuration.
- Include parity in operating system requirements by listing supported Linux distributions explicitly, not just referencing external documentation.
- Add examples of continuous deployment pipelines using common Linux tools (e.g., apt, yum, or Ansible) alongside the Chocolatey example.
- Reference and link to Linux-specific DSC resources and documentation in the same detail as Windows/PowerShell resources.
- Clarify any feature differences or limitations for Linux nodes, especially in areas like proxy support and reporting.
- Ensure that PowerShell and Windows terminology is balanced with Linux equivalents throughout the documentation.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-remediate.md
...b/main/articles/automation/automation-dsc-remediate.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation prioritizes Windows remediation by providing a direct PowerShell example and referencing Windows-specific tools first. Linux remediation is described in less detail, lacks direct script examples, and is presented as less convenient, with no equivalent to the Windows Run Command feature. References and next steps further emphasize Windows/PowerShell tools.
Recommendations
- Provide explicit Linux shell script examples for remediation, similar to the PowerShell example given for Windows.
- Clarify and expand on Linux remediation options, including any available command-line or automation tools.
- Present Windows and Linux instructions in parallel sections, giving equal prominence to both.
- Reference Linux-specific tools and modules (e.g., Azure CLI, Python scripts) with direct links and usage examples.
- Avoid language that implies Linux is less supported or more difficult to remediate; instead, highlight alternative workflows.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-faq.md
...e-docs/blob/main/articles/automation/automation-faq.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several areas. In the section about Hybrid Runbook Workers and Python version selection, only Windows-specific environment variables and file paths (e.g., C:\Python2\python.exe) are described in detail, with no equivalent Linux examples or instructions. Windows Hybrid Runbook Workers are mentioned before Linux ones, and the guidance for Linux is less specific. There are no Linux-specific code examples, environment variable names, or file path conventions provided. The documentation assumes familiarity with Windows tools and patterns, while Linux users are left with generic recommendations.
Recommendations
- Add explicit Linux examples for environment variables and file paths (e.g., /usr/bin/python3).
- Provide step-by-step instructions for configuring Python versions on Linux Hybrid Runbook Workers, similar to the Windows guidance.
- Include Linux-specific troubleshooting tips and references where Windows ones are given.
- Ensure that Linux and Windows instructions are presented with equal detail and prominence.
- Where possible, provide cross-platform code samples or clarify platform-specific differences.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-aws-deployment.md
...icles/automation/automation-scenario-aws-deployment.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively uses PowerShell and Windows-centric tooling (PowerShell Gallery, PowerShell ISE) for all examples and instructions. There are no references to Linux-native tools, Bash, or cross-platform alternatives for authoring or deploying runbooks. The instructions assume the user is familiar with PowerShell and Windows environments, and do not provide parity for Linux users or those preferring AWS CLI or Python SDKs.
Recommendations
- Add equivalent examples using Bash scripts and the AWS CLI for VM provisioning.
- Include instructions for importing and using AWS CLI or Python modules in Azure Automation, which are supported on Linux-based Hybrid Runbook Workers.
- Mention cross-platform editors (such as VS Code) and how to author runbooks for Linux environments.
- Provide guidance on authenticating to AWS using environment variables or credential files, which are common on Linux.
- Clarify which steps are Windows-specific and offer Linux alternatives where possible.
- Reference AWS documentation for Linux and CLI usage alongside PowerShell links.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-hybrid-runbook-worker.md
...rticles/automation/automation-hybrid-runbook-worker.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-centric tools are mentioned as onboarding and management channels before Linux equivalents, and there is a lack of explicit Linux-specific examples or instructions. The documentation refers to the 'System' account for Windows and only briefly mentions the 'nxautomation' account for Linux, without further Linux-specific operational details. The onboarding and management channels (Azure portal, PowerShell cmdlets, Bicep, ARM templates, REST API, Azure CLI) are listed with PowerShell first, reinforcing a Windows-first perspective. There are no Linux shell (bash) or Linux-native tool examples, and troubleshooting or operational guidance is not balanced between Windows and Linux.
Recommendations
- Provide explicit Linux shell (bash) examples alongside PowerShell for installation, management, and troubleshooting.
- Ensure Linux-specific operational details (such as permissions, service accounts, log locations, and troubleshooting steps) are documented at parity with Windows.
- List onboarding and management channels in a neutral order or alternate between Windows and Linux tools (e.g., Azure CLI before PowerShell in some sections).
- Include screenshots or walkthroughs for Linux environments, not just Windows.
- Clarify any differences in behavior, limitations, or requirements between Windows and Linux Hybrid Runbook Workers.
- Add troubleshooting guidance and common scenarios specifically for Linux hosts.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-network-configuration.md
...rticles/automation/automation-network-configuration.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page shows evidence of Windows bias. It references Windows-specific DSC resources (such as WaitFor resources with a Windows documentation link), and does not provide Linux equivalents or examples. There are no explicit Linux-focused instructions or references to Linux DSC resources, nor are there examples or guidance for Linux systems. The documentation implicitly assumes a Windows environment by mentioning Windows DSC resources and omitting Linux-specific details.
Recommendations
- Include examples and references for Linux DSC resources, such as links to Linux DSC documentation.
- Provide explicit instructions or notes for configuring network requirements for Linux nodes, including any Linux-specific considerations.
- Add parity in documentation by mentioning both Windows and Linux DSC resources, and clarify when instructions apply to both or only one platform.
- Where Windows-specific resources (e.g., WaitForAllResource) are mentioned, also mention or link to Linux equivalents or note their absence.
- Ensure that examples and references do not default to Windows unless the feature is Windows-only, and clarify platform support where relevant.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-authoring.md
...in/articles/automation/automation-runbook-authoring.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Windows operating systems first in the supported OS matrix, focusing heavily on PowerShell (with Windows PowerShell 5.1 and PowerShell Core), and providing directory path examples only in Windows format (e.g., C:\abc). There is a lack of Linux/macOS-specific examples, such as directory paths or shell commands, and the documentation does not mention Linux-specific tools or patterns. Debugging features are described only for PowerShell, with Python debugging relegated to a generic suggestion to install a debugger extension.
Recommendations
- Include Linux/macOS directory path examples (e.g., /home/user/abc) alongside Windows paths.
- Provide shell command equivalents (e.g., bash/zsh) for relevant operations where possible.
- List supported operating systems in a neutral or alphabetical order rather than Windows-first.
- Add examples and instructions for using the extension on Linux/macOS, including installation of Python packages and PowerShell modules.
- Clarify support and limitations for Linux/macOS users, especially regarding debugging and asset management.
- Mention Linux/macOS-specific tools or patterns where applicable, such as file permissions or environment setup.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-orchestrator-migration.md
...ticles/automation/automation-orchestrator-migration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias. All examples and tooling references are centered on Windows PowerShell, with no mention of Linux or cross-platform alternatives. The conversion process, modules, and cmdlets are described exclusively in terms of Windows tools and file paths. There are no Linux shell (bash) examples, nor any discussion of Linux-compatible automation workflows or modules. The documentation assumes the user is operating in a Windows environment and does not address Linux users or provide parity in guidance.
Recommendations
- Include Linux/bash examples for runbook conversion and management, where possible.
- Clarify whether the Runbook Converter and related modules can be used on Linux/macOS (e.g., via PowerShell Core), and provide instructions if so.
- Mention cross-platform PowerShell (PowerShell Core/7+) compatibility and any limitations.
- Provide guidance for Linux users on how to prepare, convert, and import runbooks, including file path conventions and asset management.
- Reference Linux tools or patterns for automation alongside Windows tools, or explicitly state if only Windows is supported.
- Add a section addressing Linux-specific considerations, such as Hybrid Runbook Worker deployment on Linux machines.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-gallery.md
...main/articles/automation/automation-runbook-gallery.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell. All examples, scenarios, and tooling references are centered around PowerShell, the PowerShell Gallery, and Windows-centric workflows. There are no Linux-specific examples, tools, or instructions, and even Python runbooks are mentioned only briefly. Scenarios such as copying files to/from Azure VMs are described only for Windows, with no mention of Linux equivalents. The documentation assumes familiarity with Windows and PowerShell, with no parity for Linux users or Bash/Shell scripting.
Recommendations
- Include Linux-specific examples for common scenarios, such as copying files to/from Linux Azure VMs using SSH or SCP.
- Provide instructions and examples for creating and importing Bash or Python runbooks, not just PowerShell.
- Mention and link to Linux tools and patterns (e.g., Bash scripts, cron jobs, Linux authentication methods) where relevant.
- Ensure that scenarios and tooling references are presented in a cross-platform manner, with Windows and Linux options side-by-side.
- Clarify module compatibility with Linux and PowerShell Core, and provide guidance for Linux users on module selection and usage.
- Add documentation sections or notes specifically for Linux users, highlighting any differences or additional steps required.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-graphical-error-handling.md
...omation/automation-runbook-graphical-error-handling.md
High Priority
View Details â
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 concepts, cmdlets, and error types. All examples, terminology, and recommended practices are centered around PowerShell and Windows-centric tools (e.g., Write-Warning, Start-AzAutomationRunbook, Start-AzVM). There is no mention of Linux equivalents, Bash scripting, or cross-platform considerations, and the error handling discussion is framed entirely in terms of PowerShell behavior.
Recommendations
- Add examples using Bash or Python activities in graphical runbooks, illustrating error handling for Linux-based automation.
- Discuss error types and handling patterns relevant to Linux environments, such as exit codes and stderr/stdout parsing.
- Reference cross-platform cmdlets or tools, and clarify which features are available on Linux Hybrid Workers.
- Include notes or sections on differences in error handling between Windows and Linux runbook executions.
- Provide links to documentation for Linux automation scenarios and best practices.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-using-watcher-task.md
...s/automation/automation-scenario-using-watcher-task.md
High Priority
View Details â
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 scripts and commands, referencing Windows filesystem paths (e.g., D:\examplefiles), and providing examples only for Windows environments. There are no Linux or cross-platform equivalents mentioned, and the instructions assume the use of Windows tools and conventions throughout. Linux scenarios, such as using Bash or Linux file paths, are entirely omitted.
Recommendations
- Include Linux-specific examples, such as using Bash scripts and Linux file paths (e.g., /home/examplefiles).
- Clarify whether watcher tasks and hybrid runbook workers support Linux hosts, and provide setup instructions for Linux if supported.
- Provide equivalent commands for creating test files on Linux (e.g., using 'touch ExampleFile1.txt').
- Mention cross-platform considerations for runbook authoring, such as using PowerShell Core or Bash.
- Add notes or sections highlighting differences or additional steps required for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/context-switching.md
...ocs/blob/main/articles/automation/context-switching.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively uses PowerShell and Az/AzureRM cmdlets for all examples and explanations, which are primarily associated with Windows environments. There are no references to Linux-native tools, Bash, CLI examples, or cross-platform scripting approaches. The guidance, terminology, and code samples are all Windows-centric, with no mention of how Linux users or those using Bash/CLI might manage Azure context switching in Automation runbooks.
Recommendations
- Add equivalent Azure CLI (az) examples for context management and switching, especially for runbooks that might be authored in Bash or Python.
- Explicitly mention cross-platform support for Azure Automation, including how context switching issues manifest and are resolved in Linux-based runbooks.
- Include a section comparing PowerShell and CLI approaches, and clarify which recommendations apply regardless of OS.
- Provide sample Bash or Python runbook code snippets demonstrating context isolation and management.
- Reference Linux tools and patterns (e.g., environment variables, az login, az account set) alongside PowerShell cmdlets.
- Reorder sections or examples so that Windows and Linux approaches are presented with equal prominence.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-overview.md
...in/articles/automation/automation-security-overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets as the primary automation interface, mentioning Azure Resource Manager and PowerShell together, and omitting Linux-specific examples or tools. There is no mention of Bash, Linux CLI, or cross-platform scripting approaches. The documentation implicitly assumes a Windows-centric workflow and does not provide parity for Linux users or administrators.
Recommendations
- Include examples and references for Bash, Azure CLI, and Linux shell scripting alongside PowerShell examples.
- Explicitly mention cross-platform support for runbooks, including how to authenticate from Linux-based Hybrid Runbook Workers.
- Provide guidance on using Linux tools (e.g., curl, OpenSSL) for authentication and automation tasks.
- Add documentation sections or notes clarifying how Linux users can perform equivalent operations and where to find relevant resources.
- Ensure that examples and instructions are presented in a platform-neutral order or grouped by platform, rather than defaulting to Windows/PowerShell first.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-use-azure-ad.md
...ob/main/articles/automation/automation-use-azure-ad.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page is heavily biased toward Windows and PowerShell usage. All code examples and instructions use PowerShell, with explicit references to Windows PowerShell modules and cmdlets. There are no examples or guidance for Linux users, such as using Bash, Azure CLI, or cross-platform scripting. Windows tools and patterns (PSCredential, Get-Credential, PowerShell Gallery) are mentioned exclusively and before any Linux or cross-platform equivalents.
Recommendations
- Add equivalent examples using Azure CLI and Bash for Linux/macOS users.
- Mention cross-platform authentication methods, such as using service principals with Azure CLI.
- Clarify which steps and modules are available on Linux and macOS, and provide links to relevant documentation.
- Include a section comparing PowerShell and Azure CLI approaches for Azure Automation authentication.
- Avoid using 'Windows PowerShell' terminology when referring to cross-platform PowerShell Core, or clarify the distinction.
- Reference Microsoft Graph SDK usage in non-PowerShell environments, such as Python or REST API.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/change-tracking-data-collection-rule-creation.md
...cking/change-tracking-data-collection-rule-creation.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows by providing detailed registry settings and a reference JSON script exclusively for Windows file settings, while Linux settings are less detailed and lack equivalent examples. Windows-specific concepts (e.g., registry keys, drive letters) are prominent, and the 'Next steps' link prioritizes Windows tutorials. Linux examples are present but less comprehensive and not given equal prominence.
Recommendations
- Provide a reference JSON script for Linux file settings, similar to the Windows example.
- Include detailed Linux-specific configuration options (e.g., common config file paths, service management patterns) alongside Windows registry settings.
- Balance the documentation by presenting Linux and Windows examples in parallel, rather than focusing first or exclusively on Windows.
- Update 'Next steps' and tutorial links to include Linux-specific guidance and tabs.
- Explicitly mention platform differences and ensure parity in explanation depth for both Windows and Linux.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-local-authentication.md
...in/articles/automation/disable-local-authentication.md
High Priority
View Details â
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 (PowerShell cmdlets) for managing Azure Automation authentication settings. There are no examples or guidance for Linux users, such as using curl, bash, or other cross-platform tools to interact with the REST API. The instructions and verification steps are written entirely in PowerShell, which is traditionally associated with Windows environments, and no alternatives for Linux shells or platforms are mentioned.
Recommendations
- Add equivalent REST API usage examples using curl or HTTPie in bash, suitable for Linux and macOS users.
- Include instructions for verifying the disableLocalAuth property using Azure CLI (az) or direct REST calls from Linux.
- Explicitly mention cross-platform options and clarify that PowerShell Core is available on Linux, but provide native bash examples for parity.
- Reorder or parallelize examples so that Linux-friendly methods are presented alongside or before Windows/PowerShell methods.
- Reference documentation for Azure CLI and REST API usage in addition to PowerShell cmdlets.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-managed-identity-for-automation.md
.../automation/disable-managed-identity-for-automation.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides detailed instructions and examples using PowerShell cmdlets, which are primarily Windows-centric. There are no equivalent examples for Linux users (e.g., using Azure CLI, curl, or bash scripting), and Windows tools (PowerShell, Az modules) are mentioned exclusively and before any cross-platform alternatives. This creates a bias toward Windows users and leaves Linux users without clear guidance.
Recommendations
- Add equivalent examples using Azure CLI and/or curl for REST API calls, suitable for Linux/macOS environments.
- Include bash script snippets for authentication and request execution.
- Mention cross-platform tools (e.g., Azure CLI) alongside PowerShell, and present them in parallel or before Windows-specific tools.
- Explicitly state that the steps can be performed on Linux/macOS and provide links to relevant cross-platform documentation.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md
...e-docs/blob/main/articles/automation/delete-account.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
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 PowerShell instructions are presented before any mention of cross-platform alternatives, and there is no guidance for Linux or macOS users. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell and the Azure portal, without offering parity for Linux environments.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell examples are primarily for Windows users, and provide Bash/CLI alternatives for Linux/macOS users.
- Include instructions for managing Automation accounts using REST API with curl or similar Linux tools.
- Ensure that cross-platform tools and patterns are presented before or alongside Windows-specific ones, rather than after.
- Add a section or tab for Linux/macOS users, detailing steps and commands relevant to those platforms.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/move-account.md
...s/blob/main/articles/automation/how-to/move-account.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for resource deletion and action group removal, referencing Windows-centric tools (PowerShell cmdlets) without mentioning equivalent Azure CLI or REST API commands. The step-by-step instructions and screenshots focus on the Azure portal, which is platform-neutral, but all command-line automation is shown using PowerShell, with no Linux shell or Azure CLI alternatives. This may disadvantage users working primarily on Linux or macOS environments.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, such as resource and action group deletion.
- Explicitly mention that both PowerShell and Azure CLI (and REST API) can be used, and provide links or code samples for each.
- Ensure that command-line instructions are presented in a platform-neutral way, or provide parallel examples for Windows (PowerShell) and Linux/macOS (Azure CLI/bash).
- Where possible, order examples so that platform-neutral or cross-platform tools (e.g., Azure CLI) are shown before or alongside Windows-specific tools.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/private-link-security.md
...in/articles/automation/how-to/private-link-security.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides a PowerShell-only example for configuring the 'Public Network Access' property, with no equivalent CLI or Linux-native instructions. PowerShell is a Windows-centric tool, and its exclusive use here suggests a Windows bias. Additionally, the documentation references Windows and Linux agents in parity, but the only explicit command-line example is for PowerShell, and there are no Azure CLI, Bash, or ARM template examples. The documentation also describes PowerShell DSC in the State Configuration section, which is Windows-focused, and does not mention Linux equivalents such as Chef, Ansible, or native Linux DSC support.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash examples for all PowerShell scripts, especially for configuring 'publicNetworkAccess'.
- Include ARM/Bicep template snippets for resource property configuration to support cross-platform automation.
- Mention and provide examples for Linux-native configuration management tools (e.g., Ansible, Chef) or clarify Linux DSC support.
- Ensure that any references to agents, configuration, or automation steps are accompanied by both Windows and Linux instructions where applicable.
- Consider reordering or balancing examples so that Linux and Windows are presented with equal prominence.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/create-azure-automation-account-portal.md
.../quickstarts/create-azure-automation-account-portal.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on using the Azure portal (web UI) to create an Automation account, which is cross-platform. However, the 'Next steps' section directs users to a PowerShell runbook tutorial, implying a Windows-centric automation approach. There are no references to Linux tools, Bash, or cross-platform scripting alternatives, and PowerShell is mentioned as the default next step for automation, which can be perceived as Windows-first and PowerShell-heavy bias. No Linux-specific examples or parity guidance are provided.
Recommendations
- Include links to tutorials for creating Automation accounts using Azure CLI and Bash, which are cross-platform and commonly used on Linux.
- Add examples or references for creating and managing Automation accounts using REST API or ARM templates, which are platform-agnostic.
- In the 'Next steps' section, provide parallel tutorials for creating runbooks using Python or Bash, not just PowerShell.
- Explicitly mention that PowerShell can be used cross-platform, but also highlight Linux-native options for automation.
- Ensure that screenshots and instructions do not imply Windows-only usage, and clarify that the Azure portal is accessible from any OS.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runtime-environment.md
...main/articles/automation/manage-runtime-environment.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell as the primary scripting language, referencing Windows PowerShell modules and patterns, and providing examples and instructions that are PowerShell-centric. Windows tools (e.g., PowerShell Gallery, Az PowerShell module, Get-Module cmdlet) are mentioned and used extensively, while Linux-specific tools, patterns, or examples are either absent or only briefly referenced (e.g., Python packages for Linux). The documentation lacks parity in examples and guidance for Linux users, especially in terms of package management, scripting, and troubleshooting.
Recommendations
- Provide equivalent Linux/bash examples alongside PowerShell instructions, especially for common automation tasks.
- Include guidance on using Azure CLI and bash scripts as first-class citizens, not only as add-ons to PowerShell environments.
- Reference Linux package formats (e.g., .tar.gz, .deb, .rpm) and repositories (e.g., PyPI, system package managers) where appropriate.
- Offer troubleshooting steps and module/package management examples for Linux environments, not just PowerShell.
- Clarify when instructions or screenshots are Windows-specific and provide Linux alternatives where possible.
- Highlight Python and Azure CLI as cross-platform automation options, with equal detail and prominence as PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/credentials.md
...in/articles/automation/shared-resources/credentials.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias, primarily focusing on PowerShell cmdlets and workflows. All command-line examples are given in PowerShell, with no mention of Linux shell equivalents or cross-platform CLI tools. Windows-specific tools and patterns (e.g., PSCredential, PowerShell modules) are referenced exclusively and before Python alternatives. There are no bash, Azure CLI, or Linux-native examples for credential management, and the documentation does not address Linux automation scenarios.
Recommendations
- Add equivalent examples using Azure CLI (az) for credential management, which is cross-platform and works on Linux.
- Include bash or shell script examples for common credential operations, such as retrieving secrets from Azure Key Vault.
- Clarify which features and cmdlets are available or not available on Linux-based hybrid workers, and provide guidance for Linux users.
- Mention Python and other cross-platform SDKs earlier in the documentation, not only after extensive PowerShell coverage.
- Provide a comparison table of credential management approaches for Windows (PowerShell), Linux (bash/Azure CLI), and Python.
- Explicitly state any platform limitations or differences in credential asset usage between Windows and Linux environments.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-sql-server-in-automation.md
...articles/automation/manage-sql-server-in-automation.md
High Priority
View Details â
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 database management examples. There are no references to Linux-native tools, Bash, or cross-platform scripting alternatives. Instructions for installing modules and configuring Hybrid Runbook Workers assume a Windows environment (elevated PowerShell prompt), and no Linux-specific guidance or examples are provided. The documentation also references Windows environment variables and patterns before any mention of Linux equivalents.
Recommendations
- Include equivalent Bash or Azure CLI examples for connecting and managing Azure SQL databases, especially for runbooks that can run on Linux Hybrid Workers.
- Provide instructions for installing required modules and configuring Hybrid Runbook Workers on Linux systems, including package manager commands and environment setup.
- Reference cross-platform scripting options (e.g., Python, Azure CLI) where possible, and clarify which steps or modules are Windows-specific.
- Add notes or sections highlighting Linux compatibility and differences, such as environment variables, shell commands, and module installation.
- Ensure that all code samples and instructions are clearly marked as Windows-specific if they do not apply to Linux, and provide Linux alternatives where feasible.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-3-packages.md
...ocs/blob/main/articles/automation/python-3-packages.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation shows evidence of Windows bias. Windows tools and patterns (such as PowerShell cmdlets) are heavily featured for managing Python 3.8 packages, with no equivalent Linux CLI or Bash examples provided. In the section on building wheel files, the Windows workflow is described in detail for Python 3.8, while the Linux workflow is only described for Python 3.10. PowerShell cmdlets are used exclusively for package management tasks, and there are no examples using Azure CLI, Bash, or cross-platform tools. This may disadvantage Linux users or those working in non-Windows environments.
Recommendations
- Provide equivalent Linux/Bash/Azure CLI examples for all PowerShell cmdlets shown, especially for common tasks like adding, listing, updating, and removing Python packages.
- When describing workflows (such as building wheel files), always present both Windows and Linux instructions side by side, or clearly indicate platform-specific differences.
- Avoid using Windows-specific terminology or tools as the default or only option; introduce cross-platform or Linux-first alternatives where possible.
- Explicitly mention when a feature or workflow is only available on Windows, and provide guidance for Linux users.
- Add a section summarizing cross-platform support and recommended tools for both Windows and Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-run-as-accounts-managed-identity.md
...automation/migrate-run-as-accounts-managed-identity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively uses PowerShell scripts and cmdlets (Connect-AzAccount, Get-AzResourceGroup, etc.) for all examples and migration steps, which are native to Windows and commonly used in Windows environments. There is no mention of Linux shell equivalents (such as Azure CLI/bash), nor are there examples for Linux-based automation workers. All tooling and migration scripts referenced are PowerShell-based, and the workflow assumes familiarity with Windows/PowerShell patterns. No Linux-first or cross-platform guidance is provided.
Recommendations
- Add equivalent Azure CLI (az) examples for authentication and resource management using managed identities, suitable for Linux and cross-platform environments.
- Include guidance and sample scripts for runbooks written in Python or Bash, which are supported in Azure Automation and commonly used on Linux.
- Explicitly mention how Linux-based hybrid runbook workers can authenticate using managed identities, with step-by-step instructions.
- Reference cross-platform tools and patterns (such as az CLI, REST API usage) alongside PowerShell, and avoid assuming PowerShell as the default.
- Reorder examples or provide tabs for both Windows/PowerShell and Linux/CLI approaches, ensuring parity and discoverability for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/dsc-configuration.md
...n/articles/automation/quickstarts/dsc-configuration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a strong Windows bias by exclusively using PowerShell syntax and DSC modules (e.g., nx), referencing the PowerShell Gallery, and relying on Windows-centric tools and workflows. Although the configuration example targets a LAMP stack (Linux), all instructions and code are written in PowerShell, and there is no mention of Linux-native tools or workflows. The documentation also notes that Azure Automation DSC for Linux has been retired, further marginalizing Linux users.
Recommendations
- Provide equivalent examples using Linux-native configuration management tools (e.g., Ansible, Chef, or native shell scripts) where possible.
- Include instructions for configuring Linux VMs using the recommended Azure Guest Configuration feature, with Linux-specific workflows and code samples.
- Clarify in the prerequisites and introduction that the documented approach is now Windows-centric due to the retirement of Linux DSC, and direct Linux users to supported alternatives.
- If PowerShell is still recommended for Linux, provide explicit instructions for installing and using PowerShell Core on Linux, and clarify any limitations.
- Update the 'Next steps' section to include Linux-relevant resources or migration guides for users affected by the retirement of Linux DSC.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/remove-user-assigned-identity.md
...n/articles/automation/remove-user-assigned-identity.md
High Priority
View Details â
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 use PowerShell cmdlets, which are native to Windows and not commonly used on Linux. There are no examples using Azure CLI, Bash, or other Linux-native tools. Even REST API usage is shown via PowerShell scripts. Windows tools and patterns are mentioned exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
- Add equivalent Azure CLI examples for all operations, as Azure CLI is cross-platform and commonly used on Linux.
- Provide Bash shell script examples for REST API calls using curl or similar tools.
- Mention and demonstrate how to perform these tasks on Linux/macOS environments, including authentication and file handling.
- Where PowerShell is used, clarify that it is available cross-platform, but also offer alternatives for users who prefer native Linux tools.
- Ensure that verification steps (such as checking identity type) are shown using Azure CLI as well as PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runtime-environment-overview.md
...in/articles/automation/runtime-environment-overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by prioritizing PowerShell as the primary scripting language, referencing multiple PowerShell versions, and focusing on Windows-centric tools such as PowerShell and Azure CLI in the context of PowerShell. There is a lack of Linux-specific examples, tools, or guidance, and the documentation does not mention Bash, shell scripting, or Linux package management, nor does it provide parity in examples or instructions for Linux environments.
Recommendations
- Include Linux-specific scripting examples, such as Bash or shell scripts, alongside PowerShell examples.
- Mention Linux-native tools (e.g., Bash, sh, or Linux CLI utilities) and how they can be used in Azure Automation runbooks.
- Provide guidance on package management for Python in Linux environments, including pip and system packages.
- Clarify cross-platform compatibility and explicitly state how runbooks can be authored and executed on Linux-based environments.
- Add documentation links and examples for Linux users, such as references to Bash scripting documentation or Linux automation best practices.
- Ensure that examples and instructions are presented in a platform-neutral order or provide parallel examples for both Windows and Linux.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/state-configuration/remove-node-and-configuration-package.md
...configuration/remove-node-and-configuration-package.md
High Priority
View Details â
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 tools, especially for unregistering nodes and deleting configurations. Windows/PowerShell methods are described in detail and given before Linux equivalents, with Linux instructions often relegated to brief manual steps or optional sections. Linux-specific examples and parity in tooling are limited, and the use of Windows-centric cmdlets (e.g., Remove-DscConfigurationDocument) is emphasized.
Recommendations
- Provide Linux-specific command-line examples for unregistering nodes, such as using OMI or DSC agent commands, if available.
- Include parity in step-by-step instructions for Linux, not just manual file deletion (e.g., scripts or commands to unregister nodes from Linux CLI).
- Present Windows and Linux instructions side-by-side or in parallel tabs, rather than Windows/PowerShell first.
- Reference Linux-native tools or automation methods where possible, and avoid assuming PowerShell is the default for all platforms.
- Expand Linux sections with troubleshooting, verification, and re-registration steps, matching the detail given to Windows/PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/schedules.md
...main/articles/automation/shared-resources/schedules.md
High Priority
View Details â
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 schedule management in Azure Automation. All CLI instructions use PowerShell syntax, and there is no mention of Bash, Azure CLI, or Linux-native tooling. Windows/PowerShell tools are referenced first and exclusively, with no Linux or cross-platform alternatives provided.
Recommendations
- Add equivalent Azure CLI examples for all schedule management tasks, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Include Bash script examples where appropriate, especially for automation scenarios.
- Explicitly mention that PowerShell Core is available cross-platform, but clarify any differences in usage or prerequisites for Linux/macOS users.
- Reference Linux-native tools or patterns where applicable, such as cron integration or using REST API calls from Bash.
- Reorder sections so that cross-platform options (Azure CLI, REST API) are presented before or alongside PowerShell examples.
- Add notes or links for Linux users regarding installation and usage of PowerShell Core, if PowerShell is required.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/collect-data-microsoft-azure-automation-case.md
...eshoot/collect-data-microsoft-azure-automation-case.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides separate sections for Linux and Windows, but the Windows section includes more detailed instructions (e.g., specific event logs to export and their formats), while the Linux section is less detailed and lacks equivalent log collection specifics. Windows tools (EVTX format, event logs) are mentioned explicitly, whereas Linux log collection is referenced only via a third-party tool and folder compression. Some general troubleshooting steps (e.g., job and module issues) do not specify Linux or Windows differences, potentially assuming Windows defaults.
Recommendations
- Provide equally detailed Linux instructions, such as which log files to collect and their formats, analogous to the Windows event logs.
- List Linux tools and commands for log collection (e.g., journalctl, /var/log/syslog) alongside Windows tools.
- Ensure that general troubleshooting steps clarify any OS-specific differences, rather than assuming Windows-centric workflows.
- Where screenshots or UI instructions are given, note any differences for Linux users (if applicable).
- Review referenced KB articles to ensure Linux parity in examples and instructions.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/desired-state-configuration.md
...automation/troubleshoot/desired-state-configuration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias. Troubleshooting steps, examples, and tools are almost exclusively presented in terms of PowerShell DSC, Windows event logs, and Windows-specific cmdlets. Windows tools (e.g., xDscDiagnostics, w32tm) and Azure portal workflows are described in detail, while Linux troubleshooting is only briefly mentioned in a single scenario. Linux-specific errors, logs, and remediation steps are largely absent, and Linux onboarding is referenced only as a link, not with explicit examples or guidance.
Recommendations
- Provide Linux-specific troubleshooting steps and examples for common scenarios, including log locations, error messages, and remediation commands.
- Include parity for Linux onboarding, configuration, and agent registration, with explicit instructions and sample commands (e.g., shell commands, systemd service checks, certificate management on Linux).
- Reference Linux equivalents for Windows tools (e.g., show how to check time sync on Linux, parse DSC logs, manage certificates).
- Ensure that Linux scenarios are presented alongside Windows scenarios, not only as afterthoughts or links.
- Where PowerShell is used, clarify if and how PowerShell Core can be used on Linux, or provide alternative native Linux approaches.
- Expand documentation for Linux retirement and alternatives, given the end-of-life announcements.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/managed-identity.md
...n/articles/automation/troubleshoot/managed-identity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting examples and code snippets use PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM), which are Windows-centric and do not mention or provide equivalent Bash/CLI commands for Linux users. The troubleshooting steps and error messages reference Windows tools and patterns exclusively, and there is no guidance for Linux-based automation environments or hybrid scenarios. This may hinder Linux users from effectively troubleshooting managed identity issues in Azure Automation.
Recommendations
- Add equivalent troubleshooting examples using Azure CLI (az) and Bash scripts for each scenario.
- Include error messages and resolution steps relevant to Linux-based Hybrid Runbook Workers.
- Explicitly mention cross-platform options and clarify when PowerShell is required versus when CLI/Bash can be used.
- Provide links to Linux-specific documentation or guides for Azure Automation managed identities.
- Ensure screenshots and UI instructions are not Windows-specific, or provide Linux alternatives where applicable.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/start-runbooks.md
...e-docs/blob/main/articles/automation/start-runbooks.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a clear Windows bias by exclusively providing examples and instructions for starting Azure Automation runbooks using Windows PowerShell. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform PowerShell Core. Windows tools and patterns are mentioned first and exclusively, with no parity for Linux or macOS environments.
Recommendations
- Add equivalent examples for starting runbooks using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Include instructions and sample code for PowerShell Core (pwsh), clarifying its cross-platform compatibility.
- Explicitly mention that PowerShell cmdlets can be used on Linux/macOS with PowerShell Core, and provide any necessary setup steps.
- Provide Bash or REST API curl examples for starting runbooks, especially in the section discussing the Azure Automation API.
- Reorder or balance the presentation so that Windows-specific tools are not always mentioned first, and ensure Linux/macOS methods are equally visible.
- Add troubleshooting and next steps resources relevant to Linux/macOS users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/shared-resources.md
...n/articles/automation/troubleshoot/shared-resources.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits a strong Windows bias, with all troubleshooting steps and code examples provided exclusively in PowerShell. Windows-centric tools and patterns (such as PowerShell cmdlets and references to DLLs) are mentioned throughout, with no equivalent guidance or examples for Linux environments or cross-platform automation. The documentation assumes the use of Windows-based tooling and does not address Linux scenarios or provide bash/CLI alternatives.
Recommendations
- Provide equivalent troubleshooting steps and code examples using Azure CLI, bash, or Python for Linux users.
- Explicitly mention cross-platform compatibility and note any differences in behavior or requirements between Windows and Linux environments.
- Include references to Linux tools and patterns where applicable (e.g., handling modules, authentication, error messages).
- Add a section or notes for users running Azure Automation from Linux, including common issues and resolutions.
- Where DLLs or Windows-specific components are referenced, clarify their relevance (or irrelevance) to Linux users and suggest alternatives if available.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/tutorial-configure-servers-desired-state.md
...automation/tutorial-configure-servers-desired-state.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows environments and PowerShell tooling. All code examples use PowerShell and target Windows VMs, specifically referencing IIS installation. Prerequisites and links are Windows-centric, and there is no example or guidance for Linux machines. Although Linux support is mentioned in passing, there are no Linux-specific instructions, examples, or parity in tooling.
Recommendations
- Add equivalent examples for onboarding and configuring Linux VMs, including sample DSC configurations for common Linux packages/services.
- Include instructions and code samples using cross-platform tools (such as Azure CLI or bash scripts) where possible, not just PowerShell.
- Update prerequisites to reference both Windows and Linux VM creation guides, and clarify current support status for Linux.
- Provide guidance on managing Linux nodes, including any differences in configuration, onboarding, and compliance checking.
- If Linux support is deprecated, make this clear at the start and provide migration or alternative recommendations for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/whats-new.md
.../azure-docs/blob/main/articles/automation/whats-new.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its heavy emphasis on PowerShell runbooks and Windows-centric tooling. Most examples and feature announcements focus on PowerShell versions, with Python support mentioned but less frequently and often as a secondary note. Windows tools and patterns, such as PowerShell modules (AzureRM, Az) and VS Code extensions for PowerShell, are highlighted more prominently than their Linux or cross-platform equivalents. There is a lack of explicit Linux shell (bash) examples, and Windows/PowerShell features are often mentioned first or exclusively, with Linux support referenced only in passing or as an afterthought.
Recommendations
- Provide equivalent Linux/bash examples alongside PowerShell examples for runbook creation and management.
- Highlight cross-platform capabilities and ensure announcements mention Linux support explicitly and equally.
- Include references to Linux-native tools and scripting environments (e.g., bash, sh, cron) where relevant.
- Balance documentation of PowerShell and Python runbooks with examples and migration guides for both.
- When describing new features, avoid listing Windows/PowerShell options first unless there is a technical reason; alternate ordering or group by platform.
- Add guidance for Linux users on using Azure Automation, including troubleshooting and best practices for Linux environments.
Avere Vfxt
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/avere-vfxt/disaster-recovery.md
...ocs/blob/main/articles/avere-vfxt/disaster-recovery.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Azure-based tools such as AzCopy, Azure PowerShell, and Azure Data Factory for copying data, all of which are primarily Windows-centric or presented as such. No Linux-native or cross-platform CLI tools (e.g., Azure CLI, rsync, rclone) are referenced, nor are Linux-specific usage examples provided. The order of tool presentation also places Windows tools before any cross-platform alternatives.
Recommendations
- Include Linux-native and cross-platform tools such as Azure CLI, rsync, or rclone as options for data copying.
- Provide explicit Linux usage examples alongside Windows/PowerShell examples for all relevant procedures.
- Ensure that tool recommendations are presented in a platform-neutral order, or grouped by platform, to avoid implicit prioritization.
- Clarify which tools are cross-platform and provide installation/use instructions for both Windows and Linux environments.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-aspnet-netfx.md
...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority
View Details â
Detected Bias Types
windows_first
visual_studio_only
powershell_heavy
missing_linux_example
Summary
The documentation is heavily oriented toward Windows development environments. Visual Studio is the only IDE mentioned, and all project creation steps assume its use. While environment variable setup includes Linux/macOS commands, Windows tools (cmd, PowerShell) are listed first and in more detail. There are no instructions or examples for developing or running the application on Linux (e.g., using Mono or .NET Framework alternatives), nor any mention of cross-platform IDEs or build tools.
Recommendations
- Add instructions for creating and running the ASP.NET application on Linux using Mono or .NET Core (if possible), or clarify Windows-only requirements.
- Include examples for setting environment variables on Linux/macOS before Windows, or present all OS instructions in parallel.
- Mention cross-platform IDEs (such as VS Code) and command-line build tools (dotnet CLI) where applicable.
- Explicitly state platform limitations (e.g., .NET Framework is Windows-only) early in the prerequisites.
- Provide guidance for Linux users on alternative approaches or migration paths to .NET Core/ASP.NET Core if dynamic configuration is needed cross-platform.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet.md
...p-configuration/enable-dynamic-configuration-dotnet.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation displays a Windows bias by listing Windows tools (Visual Studio, Command Prompt, PowerShell) before Linux/macOS equivalents, and by focusing on Windows-centric development patterns. Environment variable setup instructions consistently present Windows methods first and in greater detail, with PowerShell and Command Prompt examples preceding bash. The build/run instructions assume Visual Studio, which is primarily a Windows tool, and suggest restarting Visual Studio to apply changes, a step not relevant for Linux users. There are no Linux-specific development environment recommendations or parity in tooling guidance.
Recommendations
- Present environment variable setup instructions for Windows, Linux, and macOS in parallel, or alternate the order to avoid Windows-first bias.
- Include instructions for building and running the app using cross-platform .NET CLI tools (e.g., dotnet build/run) alongside Visual Studio.
- Mention alternative development environments for Linux (e.g., VS Code, JetBrains Rider) and provide relevant steps.
- Clarify which steps are Windows-specific (e.g., restarting Visual Studio) and offer Linux/macOS equivalents or note when they are unnecessary.
- Ensure screenshots and terminal output examples include Linux/macOS variants where applicable.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core.md
...figuration/enable-dynamic-configuration-dotnet-core.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows-first bias in several areas. In the 'Build and run the app locally' section, instructions for setting environment variables are presented in the order: Windows Command Prompt, PowerShell, then macOS/Linux. Windows-specific tools (Command Prompt, PowerShell) are mentioned by name and shown in screenshots, while Linux/macOS equivalents are not. The refresh demonstration references pressing Enter in the Command Prompt or PowerShell window, again highlighting Windows environments. Although Linux/macOS instructions are present, they are consistently listed after Windows instructions and lack visual parity (no screenshots or explicit terminal references).
Recommendations
- Present environment variable instructions for all platforms in parallel or rotate the order to avoid Windows-first bias.
- Include screenshots or explicit references for Linux/macOS terminal usage, not just Windows Command Prompt/PowerShell.
- Refer to 'terminal' or 'console' generically when describing user actions (e.g., pressing Enter), rather than only mentioning Windows tools.
- Ensure that all examples and instructions are equally detailed for Linux/macOS users, including troubleshooting notes and tool recommendations.
- Consider adding a table or collapsible sections for platform-specific instructions to emphasize parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-integrate-azure-managed-service-identity.md
...tion/howto-integrate-azure-managed-service-identity.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates a moderate Windows bias. It references Windows tools and patterns (e.g., Azure portal screenshots, App Service, Visual Studio Code with a Windows-first mention, and .NET as the primary example). While Java/Spring and Linux are supported, the .NET (commonly associated with Windows) path is presented first, and there is no explicit mention or example of Linux-specific deployment or command-line tools (e.g., Azure CLI/Bash). The use of Azure portal UI steps and screenshots also leans toward a Windows-centric workflow, and there is no PowerShell example, but the overall structure and tool recommendations are Windows-oriented.
Recommendations
- Provide Linux-specific examples and screenshots (e.g., using Azure CLI or Bash for role assignments and managed identity setup).
- Alternate the order of .NET and Java/Spring pivots or clarify that both are equally supported.
- Include deployment instructions for both Windows and Linux platforms explicitly, not just via pivots.
- Add explicit mentions and examples of using Linux-native tools (e.g., Bash, Azure CLI) for all steps that currently use the Azure portal.
- Ensure that tool recommendations (e.g., Visual Studio Code) are not presented in a way that implies Windows is the default or preferred platform.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-variant-feature-flags-python.md
...pp-configuration/howto-variant-feature-flags-python.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation shows evidence of Windows bias, particularly in the 'Build and run the app' section. Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. The 'Prerequisites' section links only to Windows-specific Python setup documentation, omitting Linux/macOS. The virtual environment activation example uses Windows syntax ('.\venv\Scripts\Activate') without showing the Linux/macOS equivalent ('source venv/bin/activate').
Recommendations
- Provide Linux/macOS instructions alongside Windows instructions, not after them. For example, show both 'setx'/'$Env:' and 'export' commands together, or in parallel columns.
- In the 'Prerequisites' section, include links to Python installation guides for Linux and macOS, not just Windows.
- When showing how to activate a Python virtual environment, include both Windows ('.\venv\Scripts\Activate') and Linux/macOS ('source venv/bin/activate') commands.
- Avoid defaulting to Windows tools or patterns; present cross-platform instructions equally.
- Consider using tabbed or side-by-side layouts for platform-specific commands to improve clarity and parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/integrate-kubernetes-deployment-helm.md
...-configuration/integrate-kubernetes-deployment-helm.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides a PowerShell script for passing secrets to Helm but does not offer an equivalent Bash/Linux shell example. The only provided script for dynamic --set usage is in PowerShell, and there is no mention of Linux or cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux or macOS users following the tutorial.
Recommendations
- Provide a Bash (or POSIX shell) equivalent script for the PowerShell example that uses az appconfig kv list and helm upgrade --set.
- Explicitly mention that the PowerShell example is for Windows and offer cross-platform alternatives.
- Ensure that all command-line examples (especially those using az CLI and Helm) are shown in a cross-platform way, or provide both Windows and Linux/macOS versions.
- Review the documentation for any other implicit assumptions of a Windows environment and clarify where platform-specific steps are required.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/monitor-app-configuration.md
...s/azure-app-configuration/monitor-app-configuration.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several ways: Windows PowerShell is mentioned explicitly and given its own section, with instructions to 'open a Windows PowerShell command window.' In the Azure CLI section, Windows PowerShell is suggested as an example of a 'command console application,' with no mention of Linux/macOS terminals. There are no explicit Linux or macOS examples, nor are cross-platform shell differences discussed. Windows tools and terminology (PowerShell, Windows command window) are referenced before or instead of Linux equivalents.
Recommendations
- In CLI instructions, mention cross-platform shells (e.g., Bash, Terminal on macOS, Linux shells) alongside Windows PowerShell.
- In PowerShell sections, clarify that Azure PowerShell is available on Linux and macOS, and provide installation/use instructions for those platforms.
- Provide explicit Linux/macOS examples for CLI and PowerShell usage, or note that commands are platform-agnostic where appropriate.
- Avoid phrases like 'open a Windows PowerShell command window'; use 'open a terminal or PowerShell window' and clarify platform options.
- Add notes or tabs for Linux/macOS users where workflows or commands differ, ensuring parity in guidance.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/integrate-ci-cd-pipeline.md
...es/azure-app-configuration/integrate-ci-cd-pipeline.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows command prompt and PowerShell examples before macOS and Linux equivalents, and by referencing Windows-centric tools and patterns (such as Visual Studio Code and MSBuild .csproj scripting). Although Linux and macOS examples are present, the ordering and emphasis favor Windows users. The build instructions and tooling references (MSBuild, .csproj) are also more familiar to Windows environments.
Recommendations
- Present Linux/macOS examples before or alongside Windows examples to avoid ordering bias.
- Include explicit instructions for Linux/macOS build environments, such as using Makefiles or shell scripts, in addition to MSBuild.
- Highlight cross-platform tooling and workflows, such as .NET CLI and VS Code, with equal emphasis on Linux/macOS compatibility.
- Add troubleshooting notes for common Linux/macOS issues (e.g., file path separators, permissions).
- Where possible, use platform-neutral language and examples, or provide tabs for each OS with equal prominence.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-java-spring-app.md
.../azure-app-configuration/quickstart-java-spring-app.md
High Priority
View Details â
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 (setx, PowerShell) are mentioned by name and syntax. Linux/macOS instructions are included but are listed after Windows, and the overall framing assumes a Windows-first workflow for environment variable setup and command-line usage.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel, rather than listing Windows first.
- Use generic shell commands (e.g., export) as the primary example, with platform-specific notes as needed.
- Avoid Windows-specific tools (like setx) as the default; provide equivalent Linux/macOS instructions with equal prominence.
- Consider using tabbed or segmented code blocks for platform-specific instructions to improve parity and clarity.
- Explicitly mention that all steps are cross-platform and provide clear guidance for each OS.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-azure-functions-csharp.md
...app-configuration/quickstart-azure-functions-csharp.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias by listing Windows tools (Visual Studio) as prerequisites, presenting Windows command prompt and PowerShell instructions before Linux/macOS equivalents, and focusing on Visual Studio for development and debugging. Linux and macOS instructions are present but consistently appear after Windows guidance, and there is no mention of cross-platform editors like VS Code or CLI-based workflows.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or in equal order, rather than always listing Windows first.
- Include Visual Studio Code and Azure Functions Core Tools CLI as alternative, cross-platform development environments in the prerequisites and workflow steps.
- Provide explicit instructions for developing, running, and debugging Azure Functions using CLI and VS Code, not just Visual Studio.
- Clarify that all code and configuration steps are cross-platform, and highlight any platform-specific differences where relevant.
- Where screenshots are used, consider including examples from both Windows and Linux/macOS environments.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-dotnet-app.md
...icles/azure-app-configuration/quickstart-dotnet-app.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is heavily oriented towards Windows development environments. It assumes the use of Visual Studio (a Windows-centric IDE), .NET Framework (not .NET Core/.NET, which is cross-platform), and provides step-by-step instructions using Windows tools (Command Prompt, PowerShell) before mentioning Linux/macOS equivalents. The examples and workflow are tailored to Windows users, with Linux/macOS instructions presented only as alternatives. There are no Linux-specific development environment suggestions or examples.
Recommendations
- Provide equivalent instructions for setting up and running the app using cross-platform .NET (e.g., .NET 6/8) and editors like VS Code or JetBrains Rider.
- Include Linux/macOS development environment setup steps, such as using Mono or .NET on Linux, and mention alternative editors.
- Present Linux/macOS commands before or alongside Windows commands, not after.
- Clarify which steps are Windows-specific and offer parallel Linux/macOS workflows (e.g., building and running the app from the terminal).
- Add troubleshooting notes for common Linux/macOS issues (e.g., case sensitivity, file paths, environment variable persistence).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-dotnet.md
...re-app-configuration/quickstart-feature-flag-dotnet.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a strong Windows bias. All environment variable examples use Windows Command Prompt or PowerShell, with no mention of Linux/macOS equivalents (e.g., Bash). Visual Studio is the only IDE referenced, and all instructions assume a Windows environment. There are no CLI or cross-platform editor options, and screenshots are of Windows Command Prompt. Linux and macOS users are not addressed, and their workflows are omitted.
Recommendations
- Add Bash/zsh examples for setting environment variables (e.g., export Endpoint=...) alongside Windows commands.
- Mention and provide instructions for using cross-platform editors like Visual Studio Code or JetBrains Rider.
- Include screenshots and instructions for running the app from a terminal on Linux/macOS.
- Clarify that the .NET SDK and Azure App Configuration libraries are cross-platform, and provide parity in instructions.
- Reorder or parallelize instructions so that Linux/macOS and Windows workflows are presented equally, rather than Windows-first.
- Explicitly state any Windows-only requirements, or confirm that all steps are cross-platform where possible.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-azure-functions-csharp.md
...tion/quickstart-feature-flag-azure-functions-csharp.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific tools and workflows, such as Visual Studio and Azure Functions Core CLI installation via Visual Studio. Environment variable setup instructions list Windows command prompt and PowerShell before Linux/macOS, and all local development examples assume Visual Studio, which is primarily a Windows IDE. There is no mention of Linux-native editors (e.g., VS Code) or cross-platform CLI workflows for creating and running Azure Functions. The documentation does not provide parity for Linux users in terms of development environment setup or alternative tooling.
Recommendations
- Add instructions for setting up and running Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
- Present environment variable setup examples for Linux/macOS before or alongside Windows examples, rather than after.
- Include guidance for installing and using the Azure Functions Core Tools directly via CLI on Linux/macOS, not just via Visual Studio.
- Mention alternative editors (e.g., VS Code) and provide equivalent steps for project creation and debugging on Linux/macOS.
- Clarify which steps are platform-agnostic and which are Windows-specific, and provide Linux/macOS equivalents where needed.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-python.md
...re-app-configuration/quickstart-feature-flag-python.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation displays a Windows bias by listing Windows command prompt and PowerShell instructions before macOS and Linux equivalents, and by providing a dedicated link to 'Python on Windows documentation' in the prerequisites. The use of 'setx' (a Windows-specific tool) is highlighted, and Windows-specific instructions are more detailed. Linux and macOS instructions are present but appear after Windows, and do not receive the same level of explanation or validation steps.
Recommendations
- Present platform instructions in a neutral or rotating order (e.g., Linux/macOS first sometimes, or group all platforms equally).
- Provide equally detailed instructions and validation steps for Linux and macOS, not just Windows.
- Include links to official Python installation/setup documentation for Linux and macOS, not only Windows.
- Avoid using Windows-specific tools (like 'setx') as the primary example; show cross-platform alternatives or note platform differences clearly.
- Consider using tabbed or parallel layouts for platform-specific commands to avoid implying priority.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-javascript.md
...icles/azure-app-configuration/quickstart-javascript.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a mild Windows bias in several areas. In the prerequisites, installation instructions for Node.js mention Windows and WSL before Linux. When configuring environment variables, Windows command prompt (setx) and PowerShell instructions are presented before Linux/macOS equivalents. Windows-specific tools and patterns (setx, PowerShell) are explicitly mentioned, while Linux instructions are more generic and less detailed. There are no missing Linux examples, but the ordering and emphasis favor Windows users.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
- Provide parity in detail and explanation for Linux/macOS commands (e.g., mention .bashrc/.zshrc for persistent environment variables).
- Include WSL as a Linux environment, but avoid conflating it with native Linux.
- Consider grouping environment variable instructions by OS, or using tabs for each platform to avoid implicit prioritization.
- Add troubleshooting notes for common Linux/macOS issues (e.g., shell persistence, permissions) as are often included for Windows.
- Review all examples and ensure equal visibility and clarity for Linux/macOS users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/rest-api-authorization-azure-ad.md
...e-app-configuration/rest-api-authorization-azure-ad.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure CLI, PowerShell, and the Azure portal for managing role assignments, but it lists PowerShell (a Windows-centric tool) before mentioning the Azure CLI, and does not provide any explicit Linux or cross-platform command-line examples. There are no Linux-specific instructions or examples, and the only linked example is for the Azure portal, which is platform-agnostic but not command-line focused.
Recommendations
- Provide explicit Azure CLI examples for managing role assignments, as Azure CLI is cross-platform and widely used on Linux.
- List Azure CLI before PowerShell when mentioning command-line tools to avoid Windows-first bias.
- Include Linux shell (bash) command examples where relevant.
- Clarify that all procedures can be performed on Linux, macOS, and Windows, and link to cross-platform documentation.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/use-key-vault-references-spring-boot.md
...-configuration/use-key-vault-references-spring-boot.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows-first bias, especially in the environment variable setup section. Windows Command Prompt (setx) and PowerShell commands are presented first and in more detail, while Linux/macOS instructions are provided later and less prominently. The use of Windows-specific tools and patterns (e.g., setx, PowerShell syntax) is emphasized, and screenshots/instructions for Azure Portal navigation are implicitly Windows-centric. There are no Linux-specific screenshots or explicit parity in CLI usage examples.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first and Linux/macOS last.
- Use cross-platform shell commands (e.g., export for Unix, set for Windows) in a more balanced way, and clearly indicate which commands are for which OS.
- Provide screenshots or notes that clarify the Azure Portal is accessible from any OS/browser, and avoid implying a Windows-only workflow.
- Where possible, use Azure CLI or other cross-platform tools for all command-line examples, and avoid Windows-specific tools unless absolutely necessary.
- Add explicit Linux/macOS examples for any step that might differ (e.g., environment variable persistence, file paths, etc.).
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-best-practices-connection.md
...ure-cache-for-redis/cache-best-practices-connection.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page primarily references .NET/ASP.NET and StackExchange.Redis (a .NET library), with examples and patterns tailored to Windows-centric development. While there is a section on Linux TCP settings, there are no equivalent Linux-specific code examples, tools, or client libraries (e.g., redis-py for Python, redis-cli usage, or systemd integration). The only explicit code sample is for ASP.NET, and the guidance for ForceReconnect and connection management is focused on .NET/Windows environments. Linux is only mentioned in the context of a TCP kernel parameter, not in application-level patterns or examples.
Recommendations
- Add examples using popular Linux-based Redis client libraries (e.g., redis-py for Python, Jedis for Java, redis-cli for shell scripting) alongside the .NET/StackExchange.Redis examples.
- Include Linux/Unix-specific application patterns, such as using systemd for service restarts or shell scripts for connection testing.
- Provide equivalent configuration/code snippets for Linux environments, not just kernel parameter tuning.
- When mentioning .NET/ASP.NET, also mention and provide parity for common Linux-first frameworks and languages.
- Ensure that any Windows/PowerShell-specific guidance is matched with Bash/Linux command equivalents.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-best-practices-performance.md
...re-cache-for-redis/cache-best-practices-performance.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation shows a moderate Windows bias. Command-line examples are consistently shown using the 'dos' code block (which implies Windows CMD), and there are no explicit Linux shell (bash) or PowerShell examples. The redis-benchmark examples use Windows-style command formatting and parameters, and the documentation does not clarify cross-platform usage or provide Linux-specific installation or usage notes. While memtier-benchmark examples use 'bash', the primary focus and all step-by-step instructions use Windows-centric tools and syntax.
Recommendations
- Provide explicit Linux (bash) and PowerShell examples for all redis-benchmark commands, using appropriate code blocks and syntax.
- Clarify that redis-benchmark is cross-platform and note any platform-specific differences in usage or installation.
- When listing steps or instructions, avoid using only Windows-centric terminology (such as 'client VM' without specifying OS) and include Linux equivalents.
- For each example, provide both Windows CMD and Linux bash versions, and consider using tabbed code blocks to let users select their platform.
- Mention package managers (e.g., apt, yum, brew) for installing redis-benchmark on Linux/macOS, not just the Redis documentation link.
- If referencing tools like stunnel, provide installation and usage examples for both Windows and Linux.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-managed-identity.md
...ticles/azure-cache-for-redis/cache-managed-identity.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure Portal (a GUI tool most familiar to Windows users), Azure PowerShell, and Azure CLI for all command-line examples. PowerShell is featured equally with CLI, and there are no explicit Linux shell (bash) or cross-platform scripting examples. There are no references to Linux-specific tools, nor are there any screenshots or instructions for Linux environments. The Azure Portal workflow is described in detail, but no mention is made of using the Azure CLI in a native Linux shell or with scripting. The order of presentation (Portal, CLI, PowerShell) also subtly prioritizes Windows-centric tools and workflows.
Recommendations
- Add explicit Linux shell (bash) examples for Azure CLI commands, including copy-pasteable commands and notes about running them in a Linux terminal.
- Include screenshots or instructions for using the Azure CLI in a Linux environment (e.g., Ubuntu terminal), or mention that the CLI commands work cross-platform.
- Clarify that Azure PowerShell is available on Linux, but also provide bash or shell script equivalents for all PowerShell examples.
- Consider reordering sections to present Azure CLI (which is cross-platform) before PowerShell, and clarify the cross-platform nature of the CLI.
- Add a note or section about using these workflows on Linux, including any differences or prerequisites (such as installing the Azure CLI on Linux).
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-troubleshoot-connectivity.md
...ure-cache-for-redis/cache-troubleshoot-connectivity.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page shows Windows bias by providing a PowerShell/Windows tool (psping) as the only alternative to redis-cli for connectivity testing, without mentioning or providing equivalent Linux commands (e.g., nc, telnet). The Windows tool is introduced before any Linux alternatives, and no Linux-specific example is given for this common troubleshooting step.
Recommendations
- Add Linux equivalents for connectivity testing, such as using 'nc <cachename> <port>' or 'telnet <cachename> <port>' alongside the psping example.
- Present both Windows and Linux troubleshooting commands together, or clearly label them as OS-specific.
- Consider including macOS examples where relevant, or note cross-platform alternatives.
- Review other sections for similar tool recommendations and ensure Linux parity throughout.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-remove-tls-10-11.md
...ticles/azure-cache-for-redis/cache-remove-tls-10-11.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts and commands for checking and configuring TLS settings, with no equivalent Linux/bash examples. The instructions and scripts assume a Windows environment, and there is no mention of Linux tools or cross-platform alternatives. The Azure portal UI instructions are platform-neutral, but all command-line automation is Windows-centric.
Recommendations
- Provide bash or Azure CLI examples for checking TLS versions from Linux/macOS environments, such as using openssl s_client or curl.
- Include cross-platform Azure CLI commands for configuring the Minimum TLS version, and clarify any limitations or alternatives for Linux users.
- Mention and demonstrate how to perform TLS checks using common Linux tools (e.g., openssl) alongside PowerShell.
- Order examples so that platform-neutral or cross-platform solutions (like Azure CLI or REST API) are presented before or alongside Windows/PowerShell-specific ones.
- Explicitly state when a script or command is Windows-only, and provide equivalent steps for Linux users.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-vnet-migration.md
...articles/azure-cache-for-redis/cache-vnet-migration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell cmdlets (Export/Import-AzRedisCache) and AzCopy without mentioning Linux equivalents or alternatives. PowerShell is presented as the primary automation tool for migration steps, and no Bash, CLI, or Linux-native commands are provided. The order of tool presentation and lack of cross-platform instructions further reinforce a Windows-centric approach.
Recommendations
- Provide Azure CLI examples (az redis export/import) alongside or before PowerShell cmdlets for data migration.
- Explicitly mention that AzCopy is cross-platform and provide example commands for Linux/macOS environments.
- Include Bash or shell script snippets for common migration tasks, such as copying RDB files or automating Redis commands.
- Clarify when PowerShell is required and offer equivalent steps for Linux users, such as using Azure CLI or REST API.
- Add a section or callout for Linux/macOS users, summarizing the migration process using non-Windows tools.
- Review all tool references to ensure Linux and cross-platform alternatives are equally represented and not presented after Windows-specific tools.
Azure Compute Fleet
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-compute-fleet/quickstart-create-portal.md
...ticles/azure-compute-fleet/quickstart-create-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page for creating an Azure Compute Fleet using the Azure portal exhibits mild Windows bias. Password requirements link to Windows VM documentation, and Windows Server is mentioned before Linux images. There is no explicit Linux-focused example or parity in password/SSH key instructions, and Linux resources are referenced only as alternatives. Linux-specific guidance is less detailed and secondary.
Recommendations
- Provide equal prominence to Linux images by listing them before or alongside Windows Server in examples.
- Link to both Windows and Linux documentation for password and SSH key requirements, not just Windows.
- Include a Linux-focused example, such as deploying a Compute Fleet with Ubuntu and SSH keys, with step-by-step instructions.
- Clarify Linux-specific options and best practices, such as SSH key generation and management.
- Ensure all referenced documentation covers both Windows and Linux scenarios, or provide separate links for each.
Azure Compute Fleet
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-compute-fleet/quickstart-create-rest-api.md
...cles/azure-compute-fleet/quickstart-create-rest-api.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell and Azure portal instructions for resource provider registration, omitting Azure CLI or Bash equivalents. The ARM template exclusively deploys Windows Server VMs, with no mention or example of Linux images. The use of Windows-specific tools and patterns is prevalent, and Linux alternatives are not referenced or shown.
Recommendations
- Add Azure CLI (Bash) examples for resource provider registration alongside PowerShell and portal instructions.
- Include an ARM template example or parameterization for deploying Linux-based VMs (e.g., Ubuntu, CentOS) in addition to Windows.
- Mention and link to documentation for using Azure CLI and Bash for all major steps, not just PowerShell.
- Where possible, present cross-platform instructions in parallel tabs (PowerShell, CLI, Portal) to ensure parity.
- Clarify in the template and text that both Windows and Linux VMs are supported, and show how to select either.
Azure Change Tracking Inventory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-change-tracking-inventory/disable-azure-change-tracking-inventory-monitoring-agent.md
...sable-azure-change-tracking-inventory-monitoring-agent.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation claims applicability to both Windows and Linux VMs, but the examples and screenshots focus on Windows-centric tools and UI elements (e.g., 'Windows Registry', 'Windows Files', 'Windows Software'). There are no explicit Linux command-line examples or Linux-specific UI references. The extension name includes both 'Windows/Linux', but the steps and visuals do not demonstrate Linux parity or provide Linux-specific guidance.
Recommendations
- Add explicit Linux examples, such as command-line instructions for uninstalling the extension on Linux VMs (e.g., using Azure CLI or relevant shell commands).
- Include screenshots or UI references that show the process on a Linux VM, highlighting any differences.
- Mention Linux-specific considerations, such as file paths, package managers, or troubleshooting steps unique to Linux.
- Balance the mention of Windows and Linux tools/features in the introduction and throughout the documentation.
- If the process is identical for both OSes, explicitly state this and clarify any OS-specific nuances.
Azure Change Tracking Inventory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-change-tracking-inventory/overview-monitoring-agent.md
...change-tracking-inventory/overview-monitoring-agent.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides a general overview of Azure Change Tracking and Inventory, mentioning both Windows and Linux support in several places. However, it exhibits bias by focusing extensively on Windows-specific features (such as registry key tracking) without providing Linux equivalents or examples. The only detailed example table is for Windows registry keys, and there are no comparable Linux configuration or daemon examples. Additionally, Windows terminology and tools are mentioned first or exclusively in several sections.
Recommendations
- Add equivalent Linux-focused sections, such as tracking changes to important Linux configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config) or monitoring Linux daemon/service changes.
- Provide example tables for Linux, similar to the Windows registry key table, listing common Linux files or directories that can be tracked.
- Include Linux command-line examples (e.g., using Bash or shell commands) where relevant, especially in sections that currently only reference Windows tools or concepts.
- Ensure that mentions of supported features and workflows consistently reference both Windows and Linux, and avoid listing Windows features first unless there is a technical reason.
- Clarify any differences in feature support or behavior between Windows and Linux, and link to Linux-specific guidance where available.
Azure Change Tracking Inventory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-change-tracking-inventory/enable-change-tracking-at-scale-policy.md
...ng-inventory/enable-change-tracking-at-scale-policy.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page mentions both Windows and Linux VMs in its scope, but there is a noticeable Windows bias. Windows-specific features (Registry, Files, Software) are listed explicitly, while Linux equivalents are less detailed. The examples and screenshots focus on generic Azure portal workflows without showing OS-specific steps, but Windows terminology (e.g., 'Configure ChangeTracking Extension for Windows virtual machines') is mentioned before Linux. There are no Linux-specific examples, screenshots, or references to Linux configuration files or package tracking, and Windows tools are referenced more explicitly.
Recommendations
- Include explicit Linux examples and screenshots, such as tracking changes to /etc or installed packages.
- Mention Linux-specific tracked items (e.g., configuration files, package managers) alongside Windows Registry and Software.
- Present Windows and Linux steps in parallel, or alternate their order to avoid Windows-first bias.
- Reference Linux tools and patterns (e.g., shell commands, configuration file paths) where relevant.
- Clarify parity of features between Windows and Linux, noting any differences in supported change tracking items.
Azure Change Tracking Inventory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-change-tracking-inventory/change-tracking-inventory-support-matrix.md
...-inventory/change-tracking-inventory-support-matrix.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a Windows-first bias in several areas: Windows-specific data types and examples are consistently listed before Linux equivalents, and Windows-centric tools and paths are referenced more frequently. Powershell/Windows command-line examples and screenshots are provided, while Linux-specific instructions are less detailed or absent. Query and alerting examples focus heavily on Windows paths and registry keys, with only minimal Linux daemon coverage. Some configuration options (like frequency sliders) are described only for Windows services, with no Linux equivalent or UI guidance.
Recommendations
- Alternate the order of Windows and Linux examples and terminology to avoid consistently prioritizing Windows.
- Provide equal detail and UI guidance for Linux-specific features (e.g., frequency configuration for Linux daemons).
- Expand query and alerting examples to include more Linux-centric scenarios (e.g., /etc/hosts, /var/log, Linux package changes).
- Include Linux command-line examples (e.g., bash, shell) where relevant, not just Powershell or Windows CLI.
- Ensure that screenshots and UI walkthroughs are available for both Windows and Linux workflows.
- Clarify any feature parity gaps and provide timelines or workarounds for Linux users where features are Windows-only.
Azure Change Tracking Inventory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-change-tracking-inventory/extension-version-details.md
...change-tracking-inventory/extension-version-details.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows is consistently listed before Linux in release note tables and issue descriptions. Several features and issues are described only for Windows (e.g., Windows Registry support, KB IDs for patches, environment variable support in file paths, Windows services data issues), with Linux often marked as 'None' or with less detail. Workarounds and tool recommendations (e.g., using KQL functions for base64 decoding) are provided only for Windows-specific issues, and there are no equivalent Linux-specific examples or guidance.
Recommendations
- Alternate the order of Windows and Linux in tables and descriptions, or present them together where possible.
- Provide Linux-specific examples, features, and known issues with equal detail and frequency as Windows.
- Include Linux equivalents for Windows tools and workarounds (e.g., suggest Linux commands or scripts for similar tasks).
- Highlight Linux-specific enhancements or fixes where applicable, not just Windows-centric ones.
- Ensure that guidance and recommendations (such as upgrading agents or using specific functions) are provided for both platforms when relevant.
Azure Change Tracking Inventory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-change-tracking-inventory/tutorial-change-workspace-configure-data-collection-rule.md
...torial-change-workspace-configure-data-collection-rule.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
windows_heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific features (such as Registry tracking) are given their own sections, and Windows examples (e.g., file paths, environment variables) are often listed before Linux equivalents. The documentation references Windows tools and patterns (e.g., Windows Registry, environment variables like %winDir%) more prominently and in more detail than Linux equivalents. However, Linux is also covered, and Linux-specific instructions are present, but not always with parity in detail or prominence.
Recommendations
- Ensure Linux examples (e.g., file paths, environment variables) are given equal prominence and detail as Windows examples.
- When listing options or examples, alternate the order or present Linux and Windows side-by-side rather than always listing Windows first.
- Expand Linux-specific sections (e.g., tracking Linux configuration files or directories) to match the detail provided for Windows Registry and files.
- If referencing Windows tools (like Registry), consider mentioning Linux equivalents (such as tracking changes in /etc or other config directories) or explicitly state if there is no equivalent.
- Review screenshots and UI instructions to ensure Linux users see their experience reflected, not just Windows-centric UI elements.
Azure Change Tracking Inventory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-change-tracking-inventory/quickstart-monitor-changes-collect-inventory-azure-change-tracking-inventory.md
...nges-collect-inventory-azure-change-tracking-inventory.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits a Windows-first bias in several areas. The prerequisites section links only to Windows VM creation, omitting a Linux equivalent. Throughout the portal-based enablement steps, there are references to Windows-specific features (e.g., Windows Registry, Windows Files, Windows Software) without parallel emphasis on Linux-specific features. In the CLI section, both Linux and Windows commands are provided, but Linux instructions are not as prominent or as detailed elsewhere. There are no direct Linux VM creation links or explicit Linux portal walkthroughs, and Windows terminology often appears first.
Recommendations
- Add a link to the Linux VM creation quickstart in the prerequisites section, alongside the Windows link.
- Ensure that Linux-specific features (such as tracking changes in Linux configuration files or packages) are mentioned with equal prominence as Windows features.
- Where examples or screenshots reference Windows-specific UI elements or terminology, provide Linux equivalents or clarify applicability.
- In all lists or instructions, alternate the order of Windows and Linux references, or group them together to avoid implicit prioritization.
- Include explicit Linux portal walkthroughs or notes where behavior or options differ from Windows.
- Review all sections for parity in detail and clarity between Windows and Linux instructions.
Azure Fluid Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/concepts/customer-managed-keys.md
...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided and discussed before Azure CLI examples, and the PowerShell module is mentioned first in each relevant section. There are no explicit Linux-specific examples or references to Linux shells or scripting environments. The CLI examples are present, but PowerShell is consistently prioritized, and no Bash or cross-platform scripting guidance is given. Additionally, the prerequisites link to a tutorial for managed identities that is Windows VM-specific.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Add explicit Bash or shell scripting examples where relevant, or clarify that Azure CLI commands work identically on Linux/macOS.
- Review and update prerequisite links to ensure they are not Windows-specific (e.g., avoid linking to Windows VM tutorials unless necessary).
- Mention that PowerShell examples can also be run on Linux/macOS if using PowerShell Core, or provide Bash equivalents for common tasks.
- Where possible, include troubleshooting steps or notes relevant to Linux environments (e.g., file path formats, authentication differences).
Azure Fluid Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/how-tos/use-audience-in-fluid.md
...les/azure-fluid-relay/how-tos/use-audience-in-fluid.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing 'Command Prompt' and using Windows-style paths (e.g., C:\My Fluid Projects, \src\App.js) throughout. All command-line instructions assume a Windows environment, with no mention of Linux or macOS equivalents (e.g., using 'cd' with Windows paths, no mention of terminal or shell). There are no examples or instructions for Linux users, and the only terminal environment referenced is Windows Command Prompt.
Recommendations
- Add Linux/macOS equivalents for all command-line instructions, including path formats (e.g., ~/fluid-projects or ./src/App.js) and terminal usage.
- Replace references to 'Command Prompt' with more inclusive terms like 'terminal' or 'command line', or specify instructions for both Windows and Linux/macOS.
- Show both Windows and Linux/macOS path examples when navigating directories or opening files.
- Explicitly state that the instructions apply to all platforms, or provide platform-specific notes where behavior differs.
- Consider including screenshots or code snippets that use Linux/macOS environments in addition to Windows.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/bring-dependency-to-functions.md
...icles/azure-functions/bring-dependency-to-functions.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways: Java examples use Windows-style paths and reference ffmpeg.exe, with no Linux equivalent shown. The Java section does not mention Linux deployment considerations, while the Python section does. PowerShell is mentioned as an upload option before Linux alternatives. There is no parity in showing Linux-specific examples for Java, and Windows tools/patterns (e.g., .exe, Windows paths) are presented first or exclusively.
Recommendations
- Add Linux-specific examples for Java, including how to reference and execute Linux binaries (e.g., ffmpeg) and handle permissions.
- In the Java section, clarify cross-platform deployment considerations, such as path formats and executable extensions.
- When mentioning upload options, list Azure CLI and Linux-native tools before or alongside PowerShell, not after.
- Avoid using Windows-only file extensions (e.g., .exe) in generic examples; provide both Windows and Linux variants.
- Explicitly note any platform differences in environment variables, file system paths, and permissions for both Python and Java.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/disable-function.md
...blob/main/articles/azure-functions/disable-function.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides examples for the Azure Portal, Azure CLI, and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, and PowerShell is presented as a primary method. The documentation does not mention or provide parity for Linux-native tools or scripting environments, and the only local example is for local.settings.json, not for command-line usage. There is also a note about a Linux limitation, but no guidance or alternatives are provided for Linux users.
Recommendations
- Add bash (Linux shell) command-line examples for managing app settings, using Azure CLI in a Linux context.
- Clarify that Azure CLI is cross-platform and recommend it as the primary command-line tool for both Windows and Linux.
- De-emphasize PowerShell as a primary method, or clearly label it as Windows-specific, and ensure it is not presented before cross-platform solutions.
- Provide guidance or workarounds for the Linux-specific limitation regarding hyphens in function names.
- Include explicit instructions or examples for Linux users, such as using environment variables or configuration files in Linux environments.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md
...able/durable-functions-isolated-create-first-csharp.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively providing instructions for Visual Studio and Visual Studio Code, both of which are primarily Windows-focused tools (though VS Code is cross-platform). The Visual Studio section is entirely Windows-specific, with no mention of Linux or macOS alternatives. There are no command-line or platform-agnostic instructions, and no explicit Linux/macOS examples or troubleshooting notes. The use of Azurite and Azure Functions Core Tools is mentioned, but only in the context of Visual Studio/VS Code workflows, not in standalone CLI or non-Windows IDE scenarios.
Recommendations
- Add explicit instructions for creating and testing Durable Functions apps on Linux and macOS, including terminal/CLI workflows using Azure Functions Core Tools.
- Provide examples using cross-platform editors (e.g., VS Code on Linux/macOS) and clarify any OS-specific steps or differences.
- Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences, firewall configuration).
- Mention alternative tools or workflows for users who do not use Visual Studio or Visual Studio Code, such as JetBrains Rider or plain text editors.
- Ensure that all screenshots and step-by-step instructions are either platform-neutral or include Linux/macOS variants.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-roslyn-analyzer.md
...functions/durable/durable-functions-roslyn-analyzer.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation primarily references Windows-centric tools (Visual Studio, Visual Studio Code) and configuration paths, with detailed instructions and screenshots for Visual Studio, which is predominantly used on Windows. There are no examples or instructions for configuring the Roslyn Analyzer in Linux-native editors or environments (e.g., JetBrains Rider, command-line usage, or cross-platform .NET CLI integration). The documentation does not mention or prioritize Linux or cross-platform workflows.
Recommendations
- Add instructions for configuring and running the Roslyn Analyzer using the .NET CLI (dotnet build/analyze) on Linux and macOS.
- Include examples or references for using the analyzer in JetBrains Rider or other cross-platform editors.
- Clarify that Visual Studio Code is available on Linux and macOS, and provide any Linux/macOS-specific notes if needed.
- Provide screenshots or terminal examples from Linux environments to demonstrate parity.
- Mention any differences or limitations when using the analyzer on non-Windows platforms.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/quickstart-python-vscode.md
...es/azure-functions/durable/quickstart-python-vscode.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation shows some Windows bias. While it does provide activation commands for Linux, macOS, and Windows, the Windows (PowerShell) example is given last, which is less problematic. However, the overall tooling focus is on Visual Studio Code and its integrated terminal, which is more commonly used on Windows. The storage emulator section only mentions Azurite via the Visual Studio Code extension, not the CLI, which is more cross-platform. There are no explicit Linux-specific tools or troubleshooting steps, and the HTTP test tool is referenced generically without mentioning common Linux tools like curl or httpie. The documentation does not provide terminal or shell-specific guidance for Linux users beyond the virtual environment activation.
Recommendations
- Add explicit Linux and macOS CLI instructions for installing and running Azurite (e.g., 'npm install -g azurite; azurite') in addition to the Visual Studio Code extension.
- Include example HTTP requests using curl or httpie for testing the function, not just browser-based instructions.
- Mention common Linux package managers (apt, yum, brew) for installing prerequisites like Python and Azure Functions Core Tools.
- Ensure troubleshooting steps or notes are included for common Linux/macOS issues (e.g., permissions, path issues).
- Where possible, provide parity in screenshots or terminal output from Linux/macOS environments, not just Visual Studio Code on Windows.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/quickstart-netherite.md
...ticles/azure-functions/durable/quickstart-netherite.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation shows mild Windows bias, primarily by referencing Windows tools and patterns first or exclusively in certain sections. For example, the use of the 'cmd' prompt in CLI examples, explicit instructions for Windows storage emulation, and the mention of 64-bit architecture validation for Windows apps. Linux equivalents are mentioned but often as afterthoughts or in notes, and there are no explicit Linux shell examples or Linux-first instructions.
Recommendations
- Provide CLI examples using both Windows (cmd/PowerShell) and Linux (bash) syntax where applicable.
- Include explicit instructions for Linux users, such as how to install dependencies or validate settings on Linux.
- Mention Linux tools and workflows alongside Windows ones, not only in notes or as exceptions.
- Ensure screenshots and portal instructions clarify any OS-specific differences, especially for Linux users.
- Where a section is Windows-only (e.g., 64-bit architecture validation), provide a parallel Linux section explaining the default behavior and how to check architecture if needed.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/quickstart-mssql.md
...n/articles/azure-functions/durable/quickstart-mssql.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation shows a Windows bias in several ways: PowerShell is used exclusively for local SQL Server setup, with no Bash or native Linux shell equivalents provided. Windows tools and patterns (e.g., SQL Server Express on Windows, PowerShell scripting, Visual Studio Code instructions referencing Windows dialogs) are mentioned before or instead of Linux alternatives. There are no explicit Bash or Linux-native command examples for common developer tasks, and troubleshooting steps reference Docker Desktop, which is more common on Windows. While Docker is cross-platform, the instructions assume familiarity with Windows-centric tools and workflows.
Recommendations
- Provide Bash/zsh shell equivalents for all PowerShell commands, especially for Docker-based SQL Server setup and validation.
- Explicitly mention and show examples for Linux and macOS users, including native package installation commands for tools like sqlcmd.
- When referencing tools (e.g., SQL Server Express), clarify cross-platform options and provide links or instructions for Linux and macOS.
- Balance the order of tool mentions (e.g., mention SQL Server Docker image before SQL Server Express on Windows) to avoid Windows-first impression.
- Add troubleshooting steps relevant to Linux (e.g., using 'docker ps' and 'docker logs' instead of Docker Desktop UI).
- Ensure all screenshots and UI instructions are either cross-platform or have Linux/macOS equivalents.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0008.md
...tions/errors-diagnostics/diagnostic-events/azfd0008.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation references file paths using backslashes (e.g., 'azure-webjobs-secrets\<FUNCTION_APP_NAME>\host.json'), which is a Windows convention. There are no explicit Linux or cross-platform examples for file paths or command-line instructions. The documentation does not mention or provide parity for Linux/macOS users, nor does it clarify that the instructions apply equally across platforms.
Recommendations
- Use forward slashes (/) in file paths or clarify that both backslash (\) and forward slash (/) can be used, depending on the platform.
- Explicitly state that the instructions apply to all platforms, or provide platform-specific notes where relevant.
- If command-line instructions are added, provide both Windows (PowerShell/CMD) and Linux/macOS (Bash/CLI) examples.
- Add a note for cross-platform users about how to navigate to the blob storage location using Azure Portal, Azure CLI, or Azure Storage Explorer, with examples for both Windows and Linux environments.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-add-openai-text-completion.md
...zure-functions/functions-add-openai-text-completion.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio Code and the Azurite storage emulator without clarifying cross-platform compatibility or providing Linux/macOS-specific instructions. The use of 'Press F1' and 'Press F5' in Visual Studio Code, as well as references to 'Terminal' and 'Core Tools', implicitly assume a Windows environment. There are no explicit Linux/macOS terminal commands, nor are there troubleshooting notes for non-Windows users. The Azurite emulator is referenced, but its installation and usage are not shown for Linux/macOS. The documentation does not mention or link to platform-specific guidance for Linux users, and all examples and instructions are presented in a way that is most familiar to Windows users.
Recommendations
- Explicitly state that Visual Studio Code and Azurite are cross-platform, and provide installation and usage instructions for Linux/macOS alongside Windows.
- For all command-line instructions (e.g., 'dotnet add package', Azurite usage), show both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) command examples where syntax or behavior differs.
- Clarify that 'Press F1' and 'Press F5' in Visual Studio Code work on all platforms, and mention any keyboard shortcut differences for macOS.
- Add troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, path differences, dependency installation).
- When referencing tools like Azurite, provide platform-agnostic installation commands (e.g., 'npm install -g azurite') and mention how to start Azurite from the terminal on Linux/macOS.
- Ensure that any references to file paths or environment variables use cross-platform conventions or provide both Windows and Linux/macOS examples.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-add-output-binding-azure-sql-vs-code.md
...ions/functions-add-output-binding-azure-sql-vs-code.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Visual Studio Code's integrated command palette and Azure portal UI for all steps, with no mention of Linux-specific tools, CLI alternatives, or terminal-based workflows. All instructions for creating resources, managing settings, and interacting with Azure SQL Database rely on GUI-based tools that are most familiar to Windows users. There are no examples using cross-platform command-line tools (e.g., Azure CLI, sqlcmd), and no explicit guidance for Linux users. The use of keyboard shortcuts and right-click actions further reinforces a Windows-centric workflow.
Recommendations
- Add parallel instructions using Azure CLI and/or PowerShell for resource creation, app settings management, and deployment, making sure to show cross-platform commands.
- Include examples of connecting to Azure SQL Database and running SQL queries using sqlcmd or Azure Data Studio, both of which are available on Linux.
- Explicitly mention that all steps can be performed on Linux, and provide Linux-specific keyboard shortcuts or terminal commands where applicable.
- Provide screenshots or terminal output from Linux environments to reinforce parity.
- Clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform, and ensure all instructions are validated on Linux and macOS as well as Windows.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-cache-trigger-redispubsub.md
...ctions/functions-bindings-cache-trigger-redispubsub.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific connection string formats (e.g., <cacheName>.redis.cache.windows.net:6380), includes PowerShell as a first-class example language, and uses Windows-centric terminology in configuration and examples. There is no explicit mention of Linux-specific tools, patterns, or troubleshooting, and the examples do not address platform differences (such as environment variable handling or file permissions) that may affect Linux users.
Recommendations
- Add notes or examples for Linux users, such as how to set environment variables and file permissions for function apps running on Linux.
- Include Bash or shell script examples alongside PowerShell to demonstrate parity for Linux environments.
- Clarify that the connection string format is platform-agnostic, or provide Linux-specific examples if differences exist.
- Mention any platform-specific limitations or considerations (e.g., file paths, case sensitivity, permissions) for Linux-hosted Azure Functions.
- Ensure that troubleshooting and advanced configuration sections address both Windows and Linux scenarios.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-service-bus.md
...cles/azure-functions/functions-bindings-service-bus.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on .NET/C# and NuGet, which are Windows-centric tools and patterns. There are no explicit Linux or cross-platform command-line examples (e.g., using pip for Python, npm for JavaScript, or CLI commands for Linux environments). The only installation instructions are for NuGet, and there are no mentions of Linux-specific workflows or tools. The documentation does not provide parity in examples or instructions for Linux users, nor does it mention cross-platform considerations. Additionally, PowerShell is listed as a supported language, but there are no Linux shell (bash) equivalents or examples.
Recommendations
- Add installation instructions and examples for Linux environments, such as using the Azure Functions Core Tools on Linux/macOS.
- Provide cross-platform command-line examples (e.g., bash, zsh) alongside PowerShell or Windows-specific instructions.
- Include package installation instructions for other languages (e.g., pip for Python, npm for JavaScript) and clarify cross-platform compatibility.
- Explicitly mention that the .NET/NuGet instructions are cross-platform if applicable, or provide guidance for .NET development on Linux/macOS.
- Add a section or note on cross-platform support and any OS-specific considerations for Azure Functions development.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md
...ctions/functions-compare-logic-apps-ms-flow-webjobs.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns (e.g., PowerShell, Visual Studio, .cmd/.bat scripts) and mentioning them before or instead of Linux equivalents. Examples and management tooling focus on PowerShell and Visual Studio, with limited or no mention of Linux-native tools or workflows (such as Bash, VS Code on Linux, or Azure CLI usage on Linux). There is also a lack of explicit Linux examples or guidance for Linux users, especially in sections about management and supported languages.
Recommendations
- Add explicit Linux/Bash examples alongside PowerShell and .cmd/.bat script references.
- Highlight Azure CLI usage and provide examples for both Windows and Linux environments.
- Mention and demonstrate development workflows using VS Code on Linux, not just Visual Studio.
- Clarify cross-platform support for all tools and SDKs, including how to use them on Linux.
- Include references to Linux package managers (e.g., apt, yum) where relevant.
- Ensure parity in documentation for Linux users by providing step-by-step guides for common Linux scenarios (deployment, monitoring, management).
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-http-endpoint.md
...cles/azure-functions/functions-create-http-endpoint.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias by consistently listing Windows-centric tools (Visual Studio, Visual Studio Code) before cross-platform or Linux-native tools, and by including a dedicated PowerShell section. References to 'Terminal/command prompt' are ambiguous and may not clearly address Linux users. There is little explicit mention of Linux-specific tools, workflows, or terminology, and Windows development environments are often presented first.
Recommendations
- Explicitly mention Linux and macOS compatibility in all references to 'Terminal/command prompt', or use 'Terminal (Linux/macOS)' and 'Command Prompt (Windows)' to clarify.
- Add Linux-native editor options (e.g., JetBrains Rider, Vim, Emacs) where appropriate, or clarify that Visual Studio Code is cross-platform.
- Ensure that cross-platform or Linux-native tools (such as Azure CLI in bash) are listed before or alongside Windows tools like Visual Studio.
- Provide explicit Linux/macOS shell commands and screenshots where relevant, not just generic or Windows-centric instructions.
- Balance PowerShell examples with bash/zsh equivalents, or provide tabs for both where scripting is involved.
- Review and update terminology to avoid Windows-first language (e.g., avoid 'command prompt' as a generic term).
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-function-resource-manager.md
...ns/functions-create-first-function-resource-manager.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ARM templates. However, the PowerShell examples are given equal prominence to Azure CLI, and there is no mention of Bash or Linux-native scripting alternatives beyond Azure CLI. The use of PowerShell (a Windows-centric tool, though now cross-platform) and the absence of Bash or shell script examples may indicate a Windows bias. Additionally, the PowerShell section is presented as a primary tab, which may reinforce the perception of Windows-first documentation.
Recommendations
- Add Bash or shell script examples for Linux/macOS users, especially for common deployment tasks.
- Clarify that Azure CLI commands can be run in Bash, Cloud Shell (Bash), or other shells, and provide explicit Bash examples where appropriate.
- If PowerShell is included, note its cross-platform availability, but avoid implying it is the default or preferred method for all users.
- Consider reordering or balancing the prominence of PowerShell and CLI sections, or explicitly stating that Azure CLI is recommended for cross-platform use.
- Include troubleshooting notes or tips for Linux/macOS users if there are known differences in behavior or prerequisites.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-your-first-function-visual-studio.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-your-first-function-visual-studio.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows by exclusively using Visual Studio (Windows-only) for all steps, referencing Windows UI elements and workflows, and omitting any Linux or cross-platform development instructions. There are no examples or guidance for using Linux tools or workflows, and the only mention of Linux is in the context of the Azure hosting environment, not the development process.
Recommendations
- Provide parallel instructions for developing C# Azure Functions using Visual Studio Code, which is cross-platform, or JetBrains Rider, which also supports Linux.
- Include CLI-based examples (using Azure Functions Core Tools and .NET CLI) for creating, running, and deploying functions, suitable for Linux and macOS users.
- Explicitly mention and link to Linux/macOS development guides in the prerequisites and introduction, not just as an alternative buried in the introduction.
- When referencing tools like Azurite, clarify installation and usage steps for Linux/macOS environments.
- Balance screenshots and UI walkthroughs with terminal/command-line equivalents where possible.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-github-actions.md
...les/azure-functions/functions-how-to-github-actions.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows is consistently mentioned before Linux in OS selection instructions and example tabs, and Windows-specific tools and terminology (such as PowerShell and Windows-latest runners) are prominent. PowerShell is included as a language option, but Python is explicitly noted as unsupported on Windows, which is a positive for Linux parity. However, the overall structure and ordering favor Windows, and Windows terminology is used more frequently and with more detail.
Recommendations
- Alternate the order of Windows and Linux examples/tabs to avoid always listing Windows first.
- Provide equal detail and prominence for Linux-specific instructions, tools, and terminology.
- Explicitly mention Linux equivalents for any Windows-specific tools or commands, and ensure Linux is not treated as a secondary option.
- Add more context or tips for Linux users, such as troubleshooting or environment setup guidance.
- Review the language and structure to ensure both platforms are presented as first-class options throughout the documentation.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-identity-access-azure-sql-with-managed-identity.md
...ctions-identity-access-azure-sql-with-managed-identity.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell and Azure portal as primary methods for several steps, with Azure CLI examples provided but not always emphasized first. The SQL tool example uses sqlcmd in Cloud Shell, which is cross-platform, but there is no mention of Linux-specific tools or workflows (e.g., Azure Data Studio, native Linux authentication patterns). There are no explicit Linux shell or environment examples, and the documentation does not address differences or considerations for Linux users.
Recommendations
- Include explicit Linux shell examples (e.g., bash, zsh) and clarify that Azure CLI commands work cross-platform.
- Provide examples using Linux-native tools (e.g., Azure Data Studio, or mention that sqlcmd is available on Linux).
- When referencing PowerShell, also provide equivalent bash/CLI commands and note platform compatibility.
- Add a section or callout for Linux users, highlighting any differences in authentication, tool installation, or environment setup.
- Ensure that instructions do not assume use of Windows or PowerShell as the default, and present CLI examples before or alongside portal/PowerShell instructions.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-identity-based-connections-tutorial.md
...tions/functions-identity-based-connections-tutorial.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a clear Windows bias. It explicitly states that the tutorial 'currently supports C# class library functions on Windows specifically,' and references Azure Files as the default file system for Windows deployments. There are no equivalent Linux examples, nor is there guidance for Linux-specific scenarios or tools. The ARM template and portal instructions are generic, but the context and examples are tailored to Windows environments, with Linux considerations only briefly mentioned as caveats.
Recommendations
- Add explicit Linux examples, including how to configure function apps on Linux plans (e.g., Consumption, Premium, Dedicated) and how to handle storage and identity scenarios specific to Linux.
- Provide parity in instructions for Linux, such as how to avoid secrets in app settings for Linux-based function apps, and clarify any differences in deployment or configuration steps.
- Mention Linux tools and patterns (e.g., Azure CLI, Bash scripting) alongside or before Windows/portal instructions, and provide sample commands.
- Clearly state any limitations or differences for Linux up front, and link to relevant Linux documentation or workarounds.
- Where features are Windows-only, provide alternative recommendations or timelines for Linux support.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-monitoring.md
.../main/articles/azure-functions/functions-monitoring.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation page exhibits mild Windows bias. It references features and tools (such as built-in log streaming) that are not available or are limited on Linux, without always providing Linux alternatives or calling out Linux limitations up front. The order of presentation and examples tends to assume Windows/App Service as the default, and there are no explicit Linux command-line or tooling examples. Some features (like Performance Counters and log streaming) are described without clear Linux parity or alternatives.
Recommendations
- Explicitly call out Linux limitations and provide alternative workflows or tools for Linux users where features are not available (e.g., for log streaming and performance counters).
- Add Linux-specific examples or instructions, such as using Azure CLI, Bash, or cross-platform tools, especially in sections that discuss enabling features or accessing logs.
- When describing features that are Windows-only or have limited Linux support, mention this early and provide links or guidance for Linux users.
- Ensure that examples and instructions are balanced between Windows and Linux, or use cross-platform approaches by default.
- Consider adding a comparison table or section summarizing feature parity and differences between Windows and Linux hosting plans for Azure Functions.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-custom-remote-mcp-server.md
...s/azure-functions/scenario-custom-remote-mcp-server.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation generally maintains cross-platform parity, but there are subtle signs of Windows bias. In the 'Connect to your remote MCP server' section, the Windows (PowerShell) script is presented after the Linux/macOS (bash) script, which is good, but the PowerShell script is more complex and detailed, and the documentation uses Windows-centric tools and patterns throughout (e.g., Visual Studio Code, Azurite, and Azure CLI, which are cross-platform but often associated with Windows). There are also references to pressing F1 and using the command palette, which are more familiar to Windows users. The PowerShell script is provided for Windows, but there is no explicit mention of WSL or Git Bash as alternatives for Windows users who prefer bash. There are no explicit Linux-only examples, and the documentation does not highlight Linux-specific workflows or tools.
Recommendations
- Ensure that Linux/macOS and Windows examples are always presented with equal prominence and detail.
- Explicitly mention that bash scripts can be run on Windows using WSL or Git Bash, not just on Linux/macOS.
- Where possible, provide examples using native Linux tools or workflows, not just cross-platform tools that are more popular on Windows.
- Consider adding a section or callout for common Linux-specific troubleshooting or environment setup steps.
- Avoid assuming Visual Studio Code as the only editor; mention alternatives like Vim, Emacs, or JetBrains IDEs where appropriate.
- Where keyboard shortcuts are given, clarify if they differ on Linux (e.g., Cmd vs Ctrl, or F1 behavior).
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-premium-plan.md
...ain/articles/azure-functions/functions-premium-plan.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates several forms of Windows bias. In command-line examples, both Azure CLI and Azure PowerShell are consistently provided, but there is a notable emphasis on PowerShell, a Windows-centric tool. In some sections (e.g., migration), only Windows migration is supported and documented, with Linux explicitly excluded. Throughout, Windows is often mentioned first (e.g., in region tables, OS requirements), and there is a lack of Linux-specific guidance or parity in examples. Additionally, Windows tools and patterns (like PowerShell) are given equal or greater prominence than cross-platform tools, and there are no Linux shell (bash) or scripting examples provided.
Recommendations
- Ensure all command-line examples are clearly marked as cross-platform, and provide bash or shell script equivalents where possible, especially for Linux users.
- When referencing PowerShell, clarify its cross-platform availability or provide alternatives (e.g., bash/Cloud Shell) for Linux users.
- Avoid consistently listing Windows first in tables and descriptions; alternate or clarify that both OSes are equally supported where applicable.
- For migration and other features not supported on Linux, provide clear guidance, workarounds, or timelines for Linux support.
- Add Linux-specific notes, troubleshooting, and best practices to match the level of detail provided for Windows.
- Review and balance the use of Windows-centric terminology and tools with Linux equivalents throughout the documentation.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-versions.md
...ob/main/articles/azure-functions/functions-versions.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows tools (Visual Studio, .csproj, .NET Framework) and workflows (Visual Studio project settings) before or instead of Linux equivalents. There are no explicit Linux-specific examples or instructions, and the only mention of Linux is in the context of pinning to a minor version, which refers the reader elsewhere. The focus on Visual Studio and .NET-centric workflows further centers Windows development patterns, with little parity for Linux users.
Recommendations
- Add explicit Linux development examples, such as using Azure Functions Core Tools on Linux, including relevant shell commands.
- Provide instructions for configuring runtime versions using Linux-native tools (e.g., Azure CLI, environment variables) and show these before or alongside Windows/Visual Studio instructions.
- Include examples for non-.NET languages (e.g., Python, JavaScript) that are common on Linux, demonstrating how to set or migrate runtime versions.
- Clarify any differences in workflow or configuration for Linux users, especially in sections that currently focus on Visual Studio or .csproj files.
- Ensure that any references to 'how to' guides (such as pinning to a minor version) include both Windows and Linux instructions inline, not just via links.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/how-to-create-function-azure-cli.md
...es/azure-functions/how-to-create-function-azure-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation shows some Windows bias, particularly in the ordering and selection of shell examples. In the Java section, command examples are provided for Bash, PowerShell, and Cmd, with Bash not always listed first. PowerShell and Cmd (Windows-specific shells) are given equal prominence to Bash, and in some cases, PowerShell is listed before Bash. There are also references to 'command prompt' and 'PowerShell' throughout, and no explicit Linux-specific instructions or troubleshooting. The use of Windows-style paths (e.g., _\src\main\java\com\fabrikam_) in Java examples further reinforces the bias. There are no explicit Linux/Mac-specific troubleshooting notes or guidance, and no mention of common Linux tools beyond jq and Azure CLI.
Recommendations
- Ensure Bash (Linux/macOS) examples are always listed first, with PowerShell and Cmd clearly marked as Windows-only.
- Where file paths are shown, provide both Windows (\) and POSIX (/) path examples, or use POSIX paths by default.
- Add explicit notes or troubleshooting for Linux/macOS users, especially around environment variables, permissions, and common issues.
- Review all references to 'command prompt' and clarify when it means Windows Command Prompt versus a generic terminal.
- Where possible, provide parity in shell scripting examples (e.g., Bash scripts for Linux/macOS, PowerShell for Windows) and highlight cross-platform commands.
- Mention Linux tools and patterns (e.g., use of export for environment variables, common text editors) where relevant.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/how-to-create-function-vs-code.md
...cles/azure-functions/how-to-create-function-vs-code.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation shows some Windows bias, primarily by referencing Windows tools and patterns, mentioning Windows-specific instructions before Linux equivalents, and focusing on PowerShell as a language. Some sections (e.g., troubleshooting) call out Windows-specific issues, and PowerShell is treated as a first-class language alongside cross-platform options. There are also places where Linux-specific instructions are less detailed or are presented after Windows instructions.
Recommendations
- Ensure all platform-specific instructions are presented in parallel, with equal detail for Windows, Linux, and macOS.
- Where PowerShell is referenced, clarify its cross-platform availability and provide Bash/zsh equivalents where appropriate.
- Avoid phrases like 'When running on Windows...' unless there is a true platform-specific difference; otherwise, clarify for all platforms.
- In troubleshooting and setup sections, include Linux/macOS-specific guidance (e.g., default shell issues, permissions) alongside Windows.
- For custom handler compilation, consider presenting Linux/macOS instructions before Windows, or group them equally.
- Add explicit Linux/macOS examples for any command-line or tool usage, not just Windows (e.g., for setting environment variables).
- Review all links and references to ensure they do not default to Windows-only documentation or installers.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/manage-connections.md
...ob/main/articles/azure-functions/manage-connections.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows/.NET bias by providing only .NET (C#) and JavaScript examples, with a heavy focus on .NET libraries and patterns (e.g., HttpClient, SqlClient, ADO.NET, Entity Framework). There are no examples or mentions of Linux-specific tools, patterns, or languages (such as Python or Java), nor are there any references to Linux-specific configuration or troubleshooting. The configuration file references (e.g., local.settings.json) are generic, but the overall guidance and code samples are Windows/.NET-centric.
Recommendations
- Add code examples for additional languages commonly used on Linux, such as Python and Java, especially for HTTP and database client usage.
- Include references to Linux-native tools, patterns, or configuration files where relevant (e.g., environment variables, .env files, or Linux-based troubleshooting steps).
- Ensure that any mention of configuration files or application settings includes Linux development workflows (e.g., using environment variables in bash, or settings for local development on Linux).
- Provide parity in code samples and explanations for both Windows/.NET and Linux/open-source stacks, making it clear that the guidance applies cross-platform.
- Mention and link to Linux-specific documentation or best practices where appropriate.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/ip-addresses.md
...ocs/blob/main/articles/azure-functions/ip-addresses.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits a mild Windows bias. It consistently presents Azure PowerShell examples alongside Azure CLI, and in some cases, PowerShell is given its own section. The only local utility mentioned for finding inbound IP addresses is 'nslookup', which is available on Windows by default but not always on Linux/macOS. There is no mention of Linux-specific tools (e.g., 'dig'), and the documentation does not clarify parity or differences for Linux/macOS users. The Azure portal and Resource Explorer are also Windows-centric in their presentation.
Recommendations
- Add Linux/macOS command-line examples (e.g., using 'dig' for DNS lookups) alongside or before 'nslookup'.
- Explicitly state that 'nslookup' is available on most platforms, but provide alternatives for Linux/macOS users.
- Where Azure PowerShell is shown, clarify that it is cross-platform, or provide Bash/Azure CLI equivalents first.
- Review all instructions to ensure that Linux and macOS users are equally supported and not implicitly deprioritized.
- Consider adding a note or tab for Linux/macOS users in sections where command-line utilities are referenced.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/machine-learning-pytorch.md
...n/articles/azure-functions/machine-learning-pytorch.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux (bash) and Windows (PowerShell, Cmd) command examples in most sections, but Windows-specific tools and patterns are often mentioned first or more prominently. For example, the Python version check lists the Windows command ('py --version') after the Linux/macOS command, but the PowerShell and Cmd tabs are always present and sometimes precede bash. Windows-specific troubleshooting (e.g., long path errors and registry edits) is included, while Linux-specific troubleshooting is minimal. Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of Linux-preferred editors. The use of 'py' (the Windows Python launcher) is shown in PowerShell/Cmd examples, while bash uses 'python'.
Recommendations
- Ensure that Linux (bash) examples are always presented first, or at least alternate the order with Windows examples.
- Provide Linux-specific troubleshooting tips where appropriate, such as common permission issues or package installation errors.
- Mention popular Linux editors (e.g., Vim, Emacs, Gedit) alongside Visual Studio Code to acknowledge Linux developer preferences.
- When referencing the Python launcher, clarify that 'py' is Windows-specific and 'python' is used on Linux/macOS.
- Include a note that all steps are equally supported on Linux, and highlight any platform-specific differences explicitly.
- Add Linux-specific error messages or solutions if any are common (e.g., missing dependencies, virtual environment activation issues).
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migrate-dotnet-to-isolated-model.md
...es/azure-functions/migrate-dotnet-to-isolated-model.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by exclusively providing Azure PowerShell scripts for identifying function apps, without offering Bash/CLI or cross-platform alternatives. It references Visual Studio and VS Code for tooling and deployment, which are predominantly used on Windows, and does not mention Linux/macOS equivalents or workflows. There are no explicit Linux shell or Azure CLI examples, and the initial scripting guidance assumes a Windows/PowerShell environment.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash shell examples alongside PowerShell scripts for identifying and managing function apps, ensuring cross-platform accessibility.
- Explicitly mention that Azure CLI and Bash can be used on Linux/macOS, and provide links or references to relevant documentation.
- Include deployment and configuration instructions using cross-platform tools (e.g., Azure CLI, GitHub Actions, or VS Code on Linux/macOS) in addition to Visual Studio.
- When referencing editor or IDE settings, clarify how to perform these actions on Linux/macOS (e.g., VS Code settings on Linux, or alternatives to Visual Studio).
- Review all scripting and automation steps to ensure parity for Linux/macOS users, and add tabs or callouts for platform-specific instructions where necessary.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migrate-version-3-version-4.md
...rticles/azure-functions/migrate-version-3-version-4.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation shows Windows bias by providing only a PowerShell script to identify function apps for migration, without any equivalent Bash or cross-platform CLI example. Windows/PowerShell tools are mentioned first and exclusively in key migration steps, and there is no mention of Linux-specific tools or instructions for this critical discovery step. This could hinder Linux/macOS users who do not use PowerShell.
Recommendations
- Provide equivalent Bash (Azure CLI) scripts alongside PowerShell for identifying function apps to migrate, ensuring cross-platform parity.
- When referencing scripts or tools, mention both Windows and Linux/macOS options, or clarify cross-platform compatibility.
- If PowerShell is required, explicitly note its availability on Linux/macOS and provide installation guidance or alternatives.
- Review other steps for similar bias and ensure all critical migration actions have both Windows and Linux/macOS instructions or examples.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/openapi-apim-integrate-visual-studio.md
...zure-functions/openapi-apim-integrate-visual-studio.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows and Visual Studio, with all instructions and examples tailored to the Windows platform. There are no mentions of Linux-compatible tools, editors, or workflows, and the publishing process explicitly targets 'Azure Function App (Windows)'. The use of Visual Studio and NuGet Package Manager Console (which is Windows-centric) further excludes Linux users. No alternative instructions for Linux or cross-platform development environments are provided.
Recommendations
- Add equivalent instructions for developing and deploying Azure Functions using cross-platform tools such as Visual Studio Code or the Azure Functions Core Tools CLI.
- Include Linux-specific setup steps, such as using dotnet CLI and VS Code for project creation, extension installation, and local testing.
- Provide examples of publishing to 'Azure Function App (Linux)' and clarify platform choices during deployment.
- Mention and demonstrate how to use the Azure Portal, Azure CLI, or GitHub Actions for deployment, which are platform-agnostic.
- Ensure all code and configuration steps are compatible with both Windows and Linux environments, and explicitly note any platform-specific differences.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/opentelemetry-howto.md
...b/main/articles/azure-functions/opentelemetry-howto.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates some Windows bias. It references Windows-specific tools and patterns, such as using the Windows command prompt (`cmd`) for .NET package installation and PowerShell for module installation. The PowerShell section provides explicit instructions using PowerShell commands and module management, while there are no equivalent Linux shell (bash) or cross-platform instructions for these steps. The .NET examples use `dotnet add package` commands, which are cross-platform, but the command prompt syntax (`cmd`) is used. There are no explicit Linux or bash shell examples, and the PowerShell section is detailed, reinforcing a Windows-centric approach. Additionally, the order of language pivots often places Windows-centric languages (C#, PowerShell) before others.
Recommendations
- Add explicit bash/zsh shell examples for package installation and module management, especially for .NET and PowerShell sections.
- Where PowerShell commands are shown, provide equivalent bash or cross-platform alternatives, or clarify when instructions are Windows-only.
- Use neutral or cross-platform shell prompts (e.g., $ for bash, > for PowerShell) and clarify which platforms each example applies to.
- Ensure Linux/macOS users are guided on how to install dependencies and configure their environments, especially for PowerShell and .NET scenarios.
- Review the order of language pivots to avoid consistently prioritizing Windows-centric languages.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/python-memory-profiler-reference.md
...es/azure-functions/python-memory-profiler-reference.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a mild Windows bias. In the local development section, Windows PowerShell is mentioned first, and Windows-specific commands (e.g., 'py -m venv .venv', '.venv\Scripts\Activate.ps1') are presented before their Linux equivalents. The file path separator in the sample output uses backslashes (\), which is Windows-specific. There is also a slight emphasis on Windows tools and patterns, such as referencing PowerShell explicitly and using Windows-style paths in examples.
Recommendations
- Present Linux and Windows commands side-by-side or in parallel tabs, rather than listing Windows first.
- Use platform-agnostic language when referring to shells (e.g., 'terminal' instead of 'PowerShell or Linux shell').
- Show both Windows and Linux file paths in sample outputs, or clarify that the path format may differ by OS.
- Ensure that Linux (and macOS) users see their commands and patterns with equal prominence and clarity.
- Consider adding a table or section summarizing all platform-specific commands for quick reference.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/recover-python-functions.md
...n/articles/azure-functions/recover-python-functions.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits mild Windows bias in several areas. Windows tools and patterns (e.g., PowerShell commands, 'py' launcher, Windows-first instructions) are often mentioned before or alongside their Linux equivalents. Some examples and troubleshooting steps prioritize Windows commands or tools, and Linux-specific guidance is sometimes less detailed or omitted. There is also a tendency to reference Windows development environments and workflows (e.g., Visual Studio Code, pip freeze from Windows), with less emphasis on Linux-native approaches.
Recommendations
- Ensure that Linux and macOS examples are provided alongside Windows/PowerShell commands, and that they appear with equal prominence.
- When referencing command-line instructions (e.g., checking Python bitness, deleting directories), present Linux/Bash examples first or at least equally.
- Include explicit guidance for common Linux development workflows, such as using Linux package managers, Python environment management, and deployment from Linux systems.
- Avoid assuming Windows as the default local development environment; clarify cross-platform differences and best practices for Linux users.
- Where platform-specific issues are discussed (e.g., pip freeze, pywin32), provide actionable Linux alternatives and highlight Linux compatibility considerations.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-blob-storage-events.md
...ticles/azure-functions/scenario-blob-storage-events.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation shows a moderate Windows bias. Visual Studio Code is the only editor mentioned, and the workflow is tightly coupled to its command palette and extensions. Windows-specific instructions and terminology (such as references to 'Cmd', 'func.exe', and PowerShell) are present. In the Python section, Windows instructions are split into 'Windows (bash)' and 'Windows (Cmd)', and the troubleshooting note specifically references Windows/WSL. The use of the Azurite emulator and Azure Functions Core Tools is cross-platform, but the documentation does not always clarify Linux/macOS equivalents or highlight parity. There are no explicit Linux-only tools or workflows, and Windows patterns are sometimes mentioned first or exclusively.
Recommendations
- Add explicit instructions and troubleshooting notes for Linux/macOS users where only Windows is mentioned (e.g., default terminal issues, process names).
- When listing platform-specific steps (such as activating Python virtual environments), present Linux/macOS instructions first or in parallel with Windows, not after.
- Where PowerShell is referenced, clarify if Bash/zsh equivalents exist and provide them.
- Mention and link to cross-platform alternatives for any Visual Studio Code extensions or features that may not be available or work identically on Linux/macOS.
- Avoid using Windows-specific process names (e.g., 'func.exe') in generic instructions; use platform-neutral terms.
- Include a short section or callout at the top clarifying that all steps are supported on Linux/macOS, and highlight any differences or limitations.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-database-changes-azure-cosmosdb.md
...-functions/scenario-database-changes-azure-cosmosdb.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as PowerShell commands and references to the Windows command prompt) are mentioned explicitly and sometimes before or more prominently than their Linux equivalents. There is a specific warning about not using WSL Bash as the default terminal on Windows, and the PowerShell execution policy command is provided for Windows, while Linux/macOS users are simply told to chmod scripts. The document also refers to stopping the 'func.exe' process, which is a Windows-specific executable name. Linux instructions are present but sometimes less detailed or secondary.
Recommendations
- Ensure Linux/macOS and Windows instructions are presented with equal prominence and detail, ideally side-by-side or in parallel tabs.
- Where PowerShell or Windows command prompt commands are given, provide equivalent Bash or shell commands for Linux/macOS users.
- Avoid Windows-specific terminology (e.g., 'func.exe') when cross-platform alternatives exist; use generic terms like 'func' or 'host process'.
- Add troubleshooting notes for Linux/macOS users, similar to the WSL Bash note for Windows.
- Review all examples and ensure that Linux/macOS users are not required to infer steps from Windows instructions.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/set-runtime-version.md
...b/main/articles/azure-functions/set-runtime-version.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell examples are consistently presented before Linux equivalents, and PowerShell is included as a first-class method for managing settings, while Linux-specific command-line tools (other than Azure CLI) are not mentioned. Some instructions (e.g., portal steps) are not clearly differentiated for Linux, and Linux users are sometimes directed to use Azure CLI exclusively, with no mention of Bash scripting or other Linux-native approaches. The documentation also references Visual Studio and .csproj files, which are primarily Windows-centric development tools, without Linux alternatives.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which platform appears first in each section.
- Include Bash or shell script examples for Linux users where PowerShell is provided for Windows.
- Clarify any differences in portal UI or workflow for Linux-hosted function apps.
- When referencing Visual Studio or .csproj, provide equivalent instructions for Linux-friendly tools (e.g., VS Code, command-line publishing).
- Explicitly state when a method (e.g., PowerShell) is not available for Linux, and suggest alternatives.
- Add more Linux-native context and troubleshooting tips, not just Azure CLI commands.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/storage-considerations.md
...ain/articles/azure-functions/storage-considerations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific plans and behaviors are often mentioned first or exclusively (e.g., Consumption plan (Windows only)), and PowerShell is referenced as a supported language for managed dependencies without equivalent mention of Bash or other Linux scripting. In several sections, Windows deployment patterns and tools are described before their Linux equivalents, and some examples (such as log streaming and file share mounting) are more detailed for Windows or PowerShell. Linux-specific instructions are present but often isolated or less emphasized. There are also cases where Linux examples are missing or less comprehensive.
Recommendations
- Ensure that Linux and Windows instructions/examples are presented with equal prominence and detail throughout the documentation.
- When referencing PowerShell or Windows-specific features, provide equivalent Bash/CLI or Linux-native alternatives where possible.
- Avoid phrasing such as 'Windows only' without immediately clarifying Linux support or alternatives.
- Add Linux-specific troubleshooting and deployment guidance where only Windows is currently covered.
- For every PowerShell example, include a Bash/Azure CLI equivalent, especially in sections about mounting shares, configuring settings, or deploying apps.
- Review the order of presentation so that Linux and Windows are treated equally (e.g., do not always list Windows first).
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/connect-with-azure-pipelines.md
...icles/azure-government/connect-with-azure-pipelines.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a strong bias towards Windows by exclusively providing PowerShell scripts and instructions for generating a service principal, referencing Windows-specific tools (PowerShell, Set-ExecutionPolicy), and omitting any Linux or cross-platform alternatives. There are no Bash, Azure CLI, or cross-platform shell examples, and the instructions assume a Windows environment.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for service principal creation, suitable for Linux and macOS users.
- Include instructions for running scripts on Linux/macOS (e.g., using Azure CLI or Bash), not just PowerShell.
- Mention cross-platform tools and patterns before or alongside Windows-specific ones.
- Clarify when instructions are Windows-specific and offer alternatives for other platforms.
- Add a note or section highlighting cross-platform compatibility and linking to relevant Azure CLI documentation.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-aad-auth-qs.md
...ure-government/documentation-government-aad-auth-qs.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a clear Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) and ASP.NET Core applications, with no mention of Linux development environments, editors, or deployment patterns. There are no Linux-specific instructions or examples, and all configuration steps assume the use of Windows tools and workflows.
Recommendations
- Add instructions for configuring Microsoft Entra authentication in popular Linux-based development environments, such as using VS Code on Linux or JetBrains Rider.
- Provide examples for deploying and running the sample application on Linux (e.g., using the dotnet CLI, configuring appsettings.json, and running the app on Linux).
- Include command-line examples (e.g., using Bash or the dotnet CLI) for registering and configuring the application, in addition to or instead of Visual Studio-centric steps.
- Mention cross-platform editors and tools, and clarify that the steps are applicable to both Windows and Linux unless otherwise noted.
- Explicitly state Linux support and provide troubleshooting tips for common Linux-specific issues.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-connect-ssms.md
...re-government/documentation-government-connect-ssms.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, for connecting to Azure Government SQL resources. There are no examples or guidance for Linux or cross-platform alternatives, such as Azure Data Studio or command-line tools. All instructions and screenshots are tailored to the Windows GUI, and no mention is made of Linux-compatible workflows.
Recommendations
- Add instructions for connecting to Azure Government SQL resources using Azure Data Studio, which is cross-platform.
- Include examples using sqlcmd or other command-line tools available on Linux.
- Explicitly mention platform compatibility and provide links or notes for Linux/macOS users.
- Consider reordering or supplementing the documentation to present cross-platform options alongside or before Windows-specific instructions.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-cognitiveservices.md
...vernment/documentation-government-cognitiveservices.md
High Priority
View Details â
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 commands and referencing Azure PowerShell for provisioning and managing Azure AI services. There are no examples or instructions for Linux users (e.g., Bash, Azure CLI), and Windows tools/patterns are mentioned first and exclusively. The quickstart links also favor Windows and Visual Studio tabs, with no mention of Linux or cross-platform alternatives.
Recommendations
- Add equivalent Azure CLI (az) commands for all provisioning and management steps, with clear instructions for Linux/macOS users.
- Include Bash shell examples alongside PowerShell, especially for resource provider registration and account creation.
- Ensure quickstart links and code samples include Linux/macOS tabs or instructions, not just Windows/Visual Studio.
- Explicitly mention cross-platform compatibility and provide guidance for users on non-Windows platforms.
- Review and update screenshots and UI references to ensure they are not Windows-specific where possible.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-developer-guide.md
...government/documentation-government-developer-guide.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell and Visual Studio connection guides before CLI and Python SDK options, and by providing explicit links to Windows-centric tools (PowerShell, Visual Studio) without equivalent emphasis on Linux-native tools or editors. There are no explicit Linux-specific examples or mentions of Linux-first workflows.
Recommendations
- Reorder the 'Quickstarts' section to list cross-platform tools (e.g., Azure CLI, Python SDK) before Windows-specific tools (PowerShell, Visual Studio).
- Add explicit examples or links for connecting to Azure Government using Bash or Linux-native shells.
- Include guidance or quickstarts for popular Linux editors (e.g., VS Code on Linux) alongside Visual Studio.
- Ensure that all code snippets and connection instructions are provided for both Windows (PowerShell) and Linux (Bash/CLI) environments.
- Explicitly mention Linux support and parity where possible, and link to Linux-specific documentation if available.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-extension.md
...azure-government/documentation-government-extension.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands (a Windows-centric tool) for listing Azure Government VM extensions, without offering equivalent examples for Linux users (e.g., using Azure CLI or Bash). The instructions reference connecting via PowerShell and do not mention or prioritize Linux-compatible tools or workflows. Additionally, the 'Next steps' section lists Windows before Linux.
Recommendations
- Add equivalent Azure CLI (az) command examples for Linux/macOS users to obtain the list of VM extensions.
- Explicitly mention that PowerShell is not required and that users can use Azure CLI or Cloud Shell from any platform.
- Reorder or parallelize 'Next steps' to avoid always listing Windows before Linux, or group them together as equal options.
- Provide links to both Windows and Linux extension documentation in the main body, not just in 'Next steps'.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-get-started-connect-to-storage.md
...ocumentation-government-get-started-connect-to-storage.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias primarily by recommending Windows-specific tools (Visual Studio 2019) as a prerequisite for .NET development and not mentioning cross-platform alternatives. The only graphical tool discussed is Azure Storage Explorer, which is cross-platform, but no command-line or Linux-native tools (such as Azure CLI or azcopy) are mentioned. All code examples are language-based and cross-platform, but the setup and prerequisites for .NET development assume a Windows environment. There are no explicit Linux or macOS setup instructions or examples, and no mention of how to use the Storage API from Bash, Azure CLI, or PowerShell Core on Linux.
Recommendations
- In the prerequisites for .NET development, mention and provide instructions for using cross-platform editors like Visual Studio Code or JetBrains Rider, and clarify that the .NET SDK is available for Linux and macOS.
- Add examples or references for using Azure CLI (az storage ...) and/or azcopy for interacting with Azure Storage from the command line, which are popular on Linux.
- Include explicit instructions or notes for Linux/macOS users regarding environment variable setup, installation of SDKs, and running code samples.
- If Visual Studio is mentioned, clarify its availability on Windows only, and provide alternatives for other platforms.
- Consider adding a section or callout box highlighting cross-platform development options and tools.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-howto-deploy-webandmobile.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-howto-deploy-webandmobile.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows development environments, specifically Visual Studio, and does not provide any guidance or examples for Linux or cross-platform users. All deployment steps are described using Visual Studio, a Windows-centric tool, with no mention of Linux-compatible alternatives such as Azure CLI, GitHub Actions, or VS Code. There are no Linux or cross-platform command-line examples, and the prerequisites and workflow assume a Windows environment.
Recommendations
- Add a section describing how to deploy an Azure App Services app using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include examples for deploying from Linux or macOS, such as using Git, GitHub Actions, or VS Code (which is cross-platform) with Azure extensions.
- Mention and link to documentation for non-Windows tools and workflows, such as Azure DevOps pipelines, Azure CLI, or ARM/Bicep templates.
- Reorganize the tutorial to present cross-platform or OS-neutral methods first, or provide parallel instructions for both Windows (Visual Studio) and Linux/macOS (CLI or code editors).
- Clearly state in the prerequisites that Visual Studio is only required for the Windows-specific workflow, and offer alternatives for other operating systems.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-image-gallery.md
...e-government/documentation-government-image-gallery.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands for listing Azure Government Marketplace images, without offering equivalent Azure CLI or Bash examples. The 'Next steps' section lists Windows VM creation guides before Linux, and the only Linux-related link is for the portal, not for command-line tools. There is no mention of Linux tools or workflows for image discovery, and the guidance assumes use of Windows-centric tools.
Recommendations
- Add Azure CLI and Bash examples for listing VM images, alongside the PowerShell example.
- Include Linux-focused instructions for connecting to Azure Government and managing images.
- In the 'Next steps' section, provide parity by including links to Linux VM creation with CLI and PowerShell, and consider alternating the order or grouping by OS.
- Mention cross-platform tools (e.g., Azure CLI) earlier and equally with PowerShell to avoid implying Windows is the default or preferred environment.
Azure Large Instances
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/onboarding-requirements.md
...icles/azure-large-instances/onboarding-requirements.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides onboarding requirements for Azure Large Instances but shows a clear bias towards Windows environments. All command-line examples for enabling ExpressRoute Fast Path and related networking tasks are given exclusively in PowerShell/Azure CLI with PowerShell syntax, with no equivalent Bash or Linux-native CLI examples. The instructions for enabling accelerated networking mention both Windows and Linux VMs, but the linked documentation is not surfaced or summarized here. There are no Linux shell (bash/az CLI) examples for common tasks, and the PowerShell approach is presented as the default/only method.
Recommendations
- Provide equivalent az CLI (bash/shell) examples for all PowerShell commands, especially for enabling ExpressRoute Fast Path and managing network resources.
- When referencing enabling features like Accelerated Networking, include explicit Linux (bash/az CLI) command examples or direct links to Linux-specific instructions.
- Avoid assuming PowerShell as the default; introduce both Windows and Linux command-line options in parallel or in a clearly separated manner.
- Where possible, clarify which steps are OS-agnostic and which require OS-specific tooling, and provide guidance for both platforms.
- Include a note at the beginning of technical sections stating that both Windows and Linux users are supported, and link to relevant platform-specific guides.
Azure Large Instances
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/work-with-azure-large-instances-in-azure-portal.md
...ces/work-with-azure-large-instances-in-azure-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively providing instructions and screenshots for the Azure portal (which is typically accessed via a web browser, often on Windows) and the Azure CLI. There are no examples or references to Linux-specific tools, shell environments, or command-line patterns (e.g., Bash, scripting, or automation with Linux tools). The documentation does not mention or provide parity for Linux-native experiences, such as using Azure CLI on Linux, nor does it reference cross-platform scripting or automation scenarios. Additionally, there is an implicit assumption of a Windows-centric workflow (e.g., double-clicking in the portal, which is a Windows UI metaphor), and no mention of Linux equivalents or considerations.
Recommendations
- Add explicit examples and instructions for using Azure CLI on Linux, including shell-specific notes (e.g., Bash, Zsh).
- Include screenshots or terminal output from Linux environments to demonstrate parity.
- Mention cross-platform compatibility of Azure CLI and clarify that all CLI commands work on Linux, macOS, and Windows.
- Avoid Windows-specific UI metaphors (e.g., 'double-click') and use neutral language (e.g., 'select').
- If relevant, provide automation examples using Bash scripts or other Linux-native tools.
- Reference Azure Cloud Shell, which is accessible from any OS, and demonstrate its use for managing Azure Large Instances.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/elevation-data-services.md
...ob/main/articles/azure-maps/elevation-data-services.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools (Azure Storage Explorer, WSL) are mentioned without Linux alternatives, and instructions for running rio-rgbify are given in the context of WSL (Windows Subsystem for Linux), implying a Windows-first audience. There are no explicit Linux or macOS instructions for tasks like uploading to Azure Blob Storage or running Azure Functions locally. The use of localhost and Windows drive mounting in WSL further reinforces the Windows-centric approach.
Recommendations
- Provide explicit Linux and macOS instructions for all steps, including installing and running rio-rgbify natively (not via WSL), uploading files to Azure Blob Storage (e.g., using azcopy or Azure CLI), and running Azure Functions locally.
- Mention cross-platform alternatives to Azure Storage Explorer, such as azcopy or Azure CLI, and provide example commands for Linux/macOS.
- Avoid assuming WSL as the default for non-Windows users; include native Linux/macOS workflows.
- Where file paths or commands are shown, use platform-agnostic syntax or provide both Windows and Linux/macOS examples.
- Add notes or tables summarizing tool availability and installation steps for all major platforms.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-create-template.md
...lob/main/articles/azure-maps/how-to-create-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation primarily describes deploying an Azure Maps account via the Azure Portal, with only a brief mention of alternative methods (Azure PowerShell, Azure CLI, REST API) after the main Windows-centric workflow. The 'Deploy templates' link points to a PowerShell-focused page, and there are no explicit Linux or cross-platform examples for template deployment. While Azure CLI is used for post-deployment tasks, the initial deployment workflow and linked resources favor Windows/PowerShell users.
Recommendations
- Provide explicit Azure CLI examples for deploying ARM templates, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash shell examples alongside PowerShell where scripts or commands are shown.
- Reorder or clarify the 'Deploy the template' section to present Azure CLI and REST API methods equally with the Azure Portal and PowerShell.
- Update the 'Deploy templates' link to point to a page covering all deployment methods (Portal, PowerShell, CLI, REST) rather than just PowerShell.
- Add a note or section highlighting cross-platform compatibility and recommending tools for Linux/macOS users.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-csharp-sdk.md
...ain/articles/azure-maps/how-to-dev-guide-csharp-sdk.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands for project setup, package installation, and environment variable configuration. No Bash or Linux shell equivalents are given, and all command-line examples assume a Windows/PowerShell environment. This may hinder Linux or macOS users who use Bash or other shells.
Recommendations
- Provide equivalent Bash (or generic shell) command examples alongside PowerShell for creating projects, installing packages, and setting environment variables.
- Explicitly mention that the .NET SDK and Azure CLI are cross-platform, and clarify that the instructions apply to Linux and macOS as well.
- Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
- Where screenshots or UI references are given, ensure they are not Windows-specific or provide alternatives if necessary.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md
...ob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md
High Priority
View Details â
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 management, without providing equivalent Linux/macOS shell examples. All CLI and environment variable instructions are shown in PowerShell syntax, and no mention is made of Bash or other Unix shells. This may hinder Linux/macOS users from following the guide seamlessly.
Recommendations
- Provide equivalent Bash (Linux/macOS) examples alongside PowerShell commands for project setup (e.g., mkdir, cd, touch demo.py).
- Show how to set environment variables in Bash (e.g., export AZURE_CLIENT_ID=...) in addition to PowerShell.
- Explicitly mention cross-platform compatibility and direct users to choose the appropriate shell commands for their OS.
- Consider using generic CLI commands (e.g., Azure CLI) in a way that is OS-agnostic, or provide both Windows and Linux/macOS instructions side by side.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using PowerShell commands for project setup, package installation, and running scripts. No Linux or macOS shell equivalents (such as Bash) are provided, and Windows/PowerShell commands are presented first and exclusively. This may create confusion or extra work for developers using Linux or macOS systems.
Recommendations
- Provide Bash equivalents for all PowerShell commands, such as using 'mkdir mapsDemo && cd mapsDemo' and 'npm init' in Bash.
- Use generic cross-platform commands (e.g., 'node search.js') without PowerShell syntax, or show both PowerShell and Bash examples side by side.
- Add a note clarifying that the commands work on Windows (PowerShell) and provide instructions for Linux/macOS users.
- Where file system operations are shown, use syntax that is valid on all platforms, or explicitly show both.
- Review all code blocks and tips to ensure Linux/macOS users are not excluded or forced to translate commands themselves.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-npm-package.md
...lob/main/articles/azure-maps/how-to-use-npm-package.md
High Priority
View Details â
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 instructions, which may imply a Windows-centric approach. There are no explicit Linux or macOS shell examples, nor any mention of platform-specific considerations for non-Windows environments. This could lead Linux/macOS users to feel the documentation is not tailored for them.
Recommendations
- Provide command-line examples using generic shell syntax (e.g., bash) or use unmarked code blocks for cross-platform commands like 'npm install'.
- Add notes clarifying that all npm commands work identically on Linux, macOS, and Windows, and that PowerShell is not required.
- Where relevant, mention any platform-specific differences (such as file paths, permissions, or browser opening methods).
- Consider alternating or combining shell and PowerShell examples, or use a neutral prompt (e.g., '$') for commands.
- Explicitly state that the instructions apply to all major operating systems, and link to official Node.js installation guides for Linux/macOS as well as Windows.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/power-bi-visual-add-path-layer.md
.../articles/azure-maps/power-bi-visual-add-path-layer.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation assumes the use of Power BI (a Windows-centric tool) and Power Query for data transformation, with no mention of Linux or cross-platform alternatives. All examples and instructions are tailored to the Windows/Power BI environment, and there are no references to how users on Linux or other platforms might perform equivalent tasks.
Recommendations
- Explicitly state platform requirements and limitations (e.g., Power BI Desktop is Windows-only, but Power BI Service is web-based and cross-platform).
- Provide guidance or references for Linux users, such as using Power BI Service or alternative data transformation tools (e.g., pandas in Python) to prepare data.
- Include equivalent data transformation examples using open-source or cross-platform tools (e.g., Python scripts for data unpivoting).
- Clarify whether all features are available in the browser-based Power BI Service, and if not, suggest workarounds for non-Windows users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-to-subscription.md
...azure-resource-manager/bicep/deploy-to-subscription.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files at the subscription scope. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and there are no explicit Bash or Linux shell examples. The CLI example is platform-neutral, but the PowerShell section may signal a Windows bias, especially as there is no mention of Linux-specific tools or workflows. There are also no explicit instructions or notes for Linux/macOS users, and the 'Cloud Shell' reference is only in the links, not in the main example flow.
Recommendations
- Add explicit Bash/Linux shell examples where appropriate, or clarify that Azure CLI commands work cross-platform.
- Consider mentioning that Azure CLI is available on all major platforms and is recommended for Linux/macOS users.
- If PowerShell is included, clarify that PowerShell Core is cross-platform, or provide Bash equivalents.
- Add a short section or note for Linux/macOS users to ensure parity and inclusivity.
- Consider reordering to present Azure CLI (platform-neutral) before PowerShell, or clarify that both are supported equally.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-kubernetes-extension.md
...e-resource-manager/bicep/bicep-kubernetes-extension.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Visual Studio Code (a tool often associated with Windows) as the primary editor for importing Kubernetes manifests, and by mentioning the 'Import Kubernetes manifest' command in Visual Studio Code without providing equivalent instructions for Linux-native editors or command-line alternatives. There are no examples or guidance for using Linux tools or workflows, and no mention of Linux-specific considerations.
Recommendations
- Provide examples or instructions for importing Kubernetes manifests using popular Linux editors (e.g., Vim, Emacs) or command-line tools.
- Mention and link to cross-platform alternatives for Visual Studio Code, or clarify that VS Code is available on Linux and macOS.
- Add explicit Linux command-line examples for managing kubeconfig files, such as using kubectl or base64 utilities.
- Ensure that any tooling or workflow described is either cross-platform or that Linux/macOS alternatives are documented alongside Windows/VS Code instructions.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/power-bi-visual-geocode.md
...ob/main/articles/azure-maps/power-bi-visual-geocode.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Power BI Desktop and SQL Server Data Tools (SSDT), both of which are primarily Windows applications. There are no examples or mentions of Linux or cross-platform alternatives for data categorization or geocoding workflows. The screenshots and instructions assume a Windows environment, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Include information about Power BI on the web and its feature parity for geocoding and data categorization, especially for non-Windows users.
- Mention any available cross-platform or Linux-compatible tools for data modeling and categorization, or clarify platform limitations.
- Add explicit notes about platform support and alternatives for users on Linux or macOS, such as using Power BI Service or Azure Data Studio.
- Provide screenshots and instructions for web-based interfaces where possible, not just Windows desktop applications.
- If certain features are Windows-only, clearly state this and suggest workarounds or alternatives for other platforms.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-cmd-ref-backup.md
...articles/azure-netapp-files/azacsnap-cmd-ref-backup.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides detailed, step-by-step instructions for running the tool with administrator privileges on Windows, including launching elevated CMD, PowerShell, and Task Scheduler. These instructions are given before the Linux equivalent, which is only briefly mentioned (using the 'sync' command). The Windows section includes multiple methods and explicit PowerShell code, while the Linux section lacks comparable detail or examples. This demonstrates a 'windows_first' and 'powershell_heavy' bias, as well as a focus on Windows-specific tools.
Recommendations
- Provide equally detailed instructions for Linux, including step-by-step guidance for running azacsnap with the necessary privileges (e.g., using sudo), and examples for common shells (bash, sh).
- Include Linux-specific automation examples, such as using cron jobs or systemd timers, similar to the Task Scheduler example for Windows.
- Ensure that Linux instructions are presented before or alongside Windows instructions, not after them.
- Add troubleshooting tips for Linux environments (e.g., permissions, log file locations) to match the depth of the Windows section.
- Where PowerShell or CMD examples are given, provide equivalent bash or shell script examples for Linux users.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-cmd-ref-configure.md
...icles/azure-netapp-files/azacsnap-cmd-ref-configure.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways. Examples and configuration guidance for Microsoft SQL Server use Windows-specific paths (e.g., C:\MSSQL_BKP\) and connection strings, with no mention of Linux-based SQL Server deployments. There are no explicit Linux shell or tool examples for SQL Server, nor is there guidance for Linux-specific configuration or file paths. The documentation also references Azure Cloud Shell and service principal authentication, but does not clarify parity or differences for Linux environments. Overall, Windows tools and patterns are mentioned exclusively or before Linux equivalents, and Linux-specific usage is missing.
Recommendations
- Add explicit examples and configuration guidance for SQL Server on Linux, including Linux file paths and connection string formats.
- Clarify whether AzAcSnap supports SQL Server on Linux and provide instructions for installation and usage in Linux environments.
- Include Linux shell command examples (e.g., using bash, cat, etc.) for all supported databases, not just SAP HANA.
- Where file paths or tools are mentioned, provide both Windows and Linux equivalents side-by-side.
- Review all references to authentication and service principal setup to ensure Linux parity and document any differences.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-configure-storage.md
...icles/azure-netapp-files/azacsnap-configure-storage.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Azure Resource Manager, Azure CLI, and service principal files) without explicitly providing parity for Linux or non-Windows environments. While some commands are shown in Bash (Cloud Shell), there is an implicit assumption of a Windows/Azure-centric workflow, and there are no explicit Linux-native or cross-platform examples for authentication, file permissions, or environment setup. The documentation does not provide PowerShell-specific commands, but it also does not address Linux-specific nuances (e.g., SELinux, systemd, or non-Azure authentication patterns).
Recommendations
- Add explicit Linux examples for authentication, file permissions, and environment setup, including common Linux distributions.
- Clarify when instructions are cross-platform and highlight any differences for Linux users (e.g., file paths, permission commands, environment variables).
- Provide parity for Linux-native tools and workflows, such as using systemd for service management, or alternatives to Azure CLI if applicable.
- Include troubleshooting tips for common Linux-specific issues (e.g., SELinux/AppArmor, file permission errors, dependency installation).
- Clearly indicate when instructions are Azure/Windows-specific and offer Linux alternatives where possible.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-installation.md
...n/articles/azure-netapp-files/azacsnap-installation.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Linux and Windows instructions for installing and managing AzAcSnap, but there are subtle signs of Windows bias. Windows is often mentioned before Linux in lists and instructions (e.g., in the download section and environment variable setup). Windows-specific tools and terminology (such as GUI-based steps, use of `%PATH%`, and 'Open a terminal session' on Windows) are referenced without always providing equivalent Linux context or tools. Some command examples and explanations are more detailed for Windows, and the structure sometimes assumes a Windows-first perspective. However, Linux instructions are present and generally complete.
Recommendations
- Ensure Linux and Windows instructions are always presented in parallel, with Linux examples given first or both shown side-by-side.
- Avoid Windows-first ordering in lists and downloads; alternate or group by platform.
- Where Windows GUI or tools are mentioned, provide explicit Linux equivalents (e.g., for user creation, path management, and binary location).
- Clarify when steps are platform-specific and avoid assuming familiarity with Windows tools or patterns.
- Consider adding more Linux-specific troubleshooting and verification steps, matching the detail given for Windows.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-government.md
...b/main/articles/azure-netapp-files/azure-government.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and command tables, while not mentioning or providing equivalent Linux shell (bash) or cross-platform scripting examples. PowerShell is highlighted as the primary scripting interface, and there is no explicit guidance for Linux users beyond Azure CLI, nor are Linux-native tools or workflows referenced. The order of presentation also places PowerShell (a Windows-centric tool) after Azure CLI but gives it a dedicated, detailed section, reinforcing its prominence.
Recommendations
- Add explicit bash or Linux shell examples for connecting to Azure Government, especially for common tasks such as authentication and resource management.
- Include cross-platform scripting guidance, such as using Azure CLI in bash/zsh, and clarify that Azure CLI is available on all major platforms.
- Mention and provide examples for using REST API tools common on Linux (e.g., curl, httpie) for REST API access.
- Balance the PowerShell section with equivalent Linux shell or Python scripting examples to ensure parity.
- Reorder sections or clarify that PowerShell is cross-platform, but also highlight Linux-native approaches where appropriate.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md
...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways. All examples and instructions for managing SMB permissions and shares are given using Windows tools (MMC, Windows Security tab), with no mention of Linux SMB clients or their management tools. The 'non-browsable-share' feature is described only in terms of Windows client behavior and Windows commands. There are no examples or guidance for Linux users on how to mount, access, or manage SMB volumes, nor are Linux tools (such as smbclient, mount.cifs, or Samba utilities) referenced.
Recommendations
- Add equivalent instructions and screenshots for managing SMB permissions and shares from Linux clients (e.g., using smbclient, setfacl, or mount.cifs).
- Describe how Linux users can mount and access SMB volumes, including example commands.
- Clarify which features (such as non-browsable shares, access-based enumeration, and SMB3 encryption) are supported and behave on Linux clients.
- Reference Linux documentation and tools alongside Windows tools, and avoid presenting Windows instructions exclusively or first.
- Include troubleshooting steps and best practices for Linux SMB clients.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-sdk-cli.md
...icles/azure-netapp-files/azure-netapp-files-sdk-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation lists both Azure CLI and PowerShell as supported CLI tools, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being cross-platform and PowerShell being historically Windows-focused. No explicit Linux shell (bash) examples or references are provided, and no Linux-specific tools or usage patterns are mentioned. The documentation does not clarify that Azure CLI is the recommended or default tool for Linux users, nor does it provide Linux-oriented guidance or examples.
Recommendations
- Explicitly state that Azure CLI is cross-platform and the primary tool for Linux users.
- Provide example commands using bash/zsh shells to demonstrate usage on Linux.
- Clarify the platform compatibility of PowerShell and Azure CLI, noting that PowerShell Core is available on Linux but is less commonly used than CLI.
- Add a section or note for Linux users, highlighting best practices and any platform-specific considerations.
- Ensure that CLI examples precede PowerShell examples, or provide parallel examples for both environments.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md
...etapp-files/azure-netapp-files-set-up-capacity-pool.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page displays a Windows bias by referencing PowerShell and its module update command, providing explicit instructions for PowerShell users, and mentioning PowerShell before any Linux equivalents. There are no Linux-specific instructions or examples, such as Bash or shell commands for updating the Azure CLI or interacting with Azure NetApp Files, and no mention of Linux tools or patterns.
Recommendations
- Add Linux-specific instructions, such as how to update the Azure CLI on Linux (e.g., using apt, yum, or curl).
- Include Bash or shell command examples alongside PowerShell commands for parity.
- Mention cross-platform compatibility for CLI and REST API usage, clarifying that steps apply to both Windows and Linux environments.
- Provide links or references to Linux documentation for Azure NetApp Files management.
- Ensure that examples and tool references are presented in a platform-neutral order, or alternate between Windows and Linux where appropriate.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-cache-volumes.md
...articles/azure-netapp-files/configure-cache-volumes.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias primarily in the feature registration section, where Azure PowerShell commands are presented first and in detail, with Azure CLI (which is cross-platform and more common on Linux) only briefly mentioned as an alternative. The PowerShell examples are highlighted and formatted, while the CLI commands are referenced via a link, not shown inline. Additionally, there is a general assumption of familiarity with Windows-centric tools and patterns (e.g., Active Directory, SMB, PowerShell), and Linux equivalents (such as LDAP, NFS) are mentioned but not given equal prominence or step-by-step examples. No explicit Linux shell (bash) commands or instructions are provided for feature registration or management.
Recommendations
- Provide Azure CLI command examples inline and with equal prominence as PowerShell, especially for feature registration and status checking.
- Explicitly mention and show bash shell command examples where applicable, not just PowerShell.
- Ensure Linux-native tools and patterns (e.g., LDAP, NFS) are described in as much detail as their Windows counterparts (e.g., AD, SMB).
- When referencing commands, do not default to Windows/PowerShell first; present both options side-by-side or in tabs.
- Clarify any platform-specific requirements or differences in the workflow for Linux and Windows administrators.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-customer-managed-keys.md
.../azure-netapp-files/configure-customer-managed-keys.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure Portal (GUI) and Azure PowerShell instructions before Azure CLI examples. PowerShell is a Windows-centric tool, and its inclusion as a primary method, alongside the absence of explicit Linux shell examples (e.g., Bash), reinforces this bias. There are no Linux-specific command-line examples or troubleshooting steps, and the documentation does not mention or address Linux environments or tools directly. The use of screenshots and instructions is focused on the Azure Portal, which is OS-agnostic but often associated with Windows workflows. No mention is made of Linux-native scripting, automation, or integration patterns.
Recommendations
- Present Azure CLI (which is cross-platform and preferred on Linux) examples before PowerShell examples, or at least give them equal prominence.
- Explicitly mention that Azure CLI commands are suitable for Linux, macOS, and Windows, and provide Bash-specific usage notes where relevant.
- Add troubleshooting and scripting examples that use Bash shell idioms (e.g., environment variables, piping, jq for JSON parsing) to illustrate Linux-native workflows.
- Where PowerShell is shown, provide equivalent Bash scripts or shell commands for common automation scenarios.
- Clarify in the introduction or requirements that all command-line instructions are cross-platform unless otherwise noted, and highlight any OS-specific caveats.
- Include references or links to Linux-specific Azure CLI installation and usage guides.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-kerberos-encryption.md
...es/azure-netapp-files/configure-kerberos-encryption.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by relying heavily on PowerShell commands (e.g., Set-ADComputer) and referencing Windows-specific tools (RSAT) for critical Active Directory configuration steps. There are no equivalent Linux-based instructions for managing the required AD computer account properties, and the documentation assumes access to a Windows environment for these steps. Linux client configuration is covered only for NFS mounting, not for the AD/kerberos setup, and Windows tools are mentioned before any Linux alternatives (which are not provided).
Recommendations
- Provide equivalent instructions for configuring the Kerberos encryption type on the AD computer account using Linux-based tools such as 'ldapmodify', 'adcli', or 'samba-tool'.
- Include Linux command-line examples for all steps currently shown only with PowerShell, especially for environments where administrators do not have access to Windows servers or RSAT.
- Clearly indicate when a step requires a Windows environment, and suggest alternatives for Linux-only environments.
- Reorganize sections so that Linux and Windows methods are presented in parallel, or prioritize Linux instructions when the primary client is Linux.
- Add troubleshooting tips for common Linux-side Kerberos/AD integration issues.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-ldap-over-tls.md
...articles/azure-netapp-files/configure-ldap-over-tls.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server tools (Certification Authority, MMC snap-in) for certificate generation and management, and does not provide equivalent instructions or examples for Linux environments. All certificate export steps are described using Windows interfaces and screenshots, with no mention of Linux alternatives or cross-platform command-line methods.
Recommendations
- Add instructions for generating and exporting root CA certificates using common Linux tools (e.g., OpenSSL) alongside the Windows Server method.
- Include Linux command-line examples for certificate management and export, such as using openssl to create and export certificates in Base-64 encoded X.509 (.CER) format.
- Provide guidance on viewing and managing certificates on Linux systems, such as using keytool, openssl, or other relevant utilities.
- Add screenshots or terminal output examples for Linux workflows to match the visual aids provided for Windows.
- Explicitly state that both Windows and Linux domain controllers are supported, if applicable, and clarify any platform-specific requirements.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-ldap-extended-groups.md
...s/azure-netapp-files/configure-ldap-extended-groups.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows/Active Directory bias by exclusively supporting and referencing Microsoft Active Directory Domain Services (AD DS) and Microsoft Entra Domain Services for LDAP integration, with explicit statements that OpenLDAP or other third-party LDAP directory services are not supported. All attribute management examples and screenshots use Windows tools (Active Directory Users and Computers MMC snap-in, Multi-valued String Editor, Attribute Editor). Guidance for setting LDAP attributes is Windows-centric, and Linux tools or workflows for managing POSIX attributes in LDAP are not mentioned. Linux/NFS client configuration is referenced only briefly and always after the Windows/AD configuration steps.
Recommendations
- Clarify in the introduction and considerations sections why only AD DS and Microsoft Entra Domain Services are supported, and if possible, provide a roadmap or alternatives for Linux/OpenLDAP environments.
- Add Linux/OpenLDAP examples for managing POSIX attributes (e.g., using ldapmodify, phpldapadmin, or command-line tools) even if not supported, to help users understand the differences.
- Where screenshots show Windows tools (e.g., Attribute Editor), provide equivalent command-line or Linux-based examples for attribute management, or explicitly state that only Windows tools are supported.
- In the steps section, provide more parity by including Linux client configuration steps earlier, and clarify any limitations or differences for Linux-based LDAP servers.
- If possible, add troubleshooting tips for common Linux client issues when integrating with AD DS LDAP, and reference relevant Linux documentation.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-network-features.md
...icles/azure-netapp-files/configure-network-features.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell/Azure PowerShell commands are presented first and in detail for feature registration and volume management, with Azure CLI and REST API alternatives provided but not prioritized. The initial registration steps and many code blocks default to PowerShell, and there is a strong focus on Azure Portal workflows, which are more familiar to Windows users. Linux-specific shell or scripting examples are absent, and there is little mention of Linux-native tools or workflows. The documentation does include Azure CLI and REST API examples, which are cross-platform, but PowerShell is consistently emphasized and appears before CLI in several sections.
Recommendations
- Present Azure CLI examples before PowerShell examples, or at least in parallel, to avoid the impression that PowerShell is the primary or preferred method.
- Explicitly mention that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide bash shell examples where appropriate.
- Include Linux shell (bash) scripting examples for automation scenarios, especially for registration and volume management tasks.
- Clarify that all REST API and Azure CLI instructions are fully cross-platform.
- Where PowerShell is used, provide equivalent bash or shell script snippets for Linux users.
- Add a short section or note highlighting Linux and macOS support for Azure CLI and REST API, and link to relevant installation guides.
- Ensure that screenshots and UI instructions do not assume a Windows environment (e.g., avoid referencing Windows-specific UI elements or terminology).
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/control-plane-security.md
.../articles/azure-netapp-files/control-plane-security.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools as primary interfaces for managing Azure NetApp Files. While it mentions 'CLI' generically, PowerShell is the only command-line interface explicitly named, and there are no Linux-specific tools, shell examples, or references to Bash/Azure CLI usage. The order of interface mention (APIs, PowerShell, CLI, Portal) also places PowerShell before CLI, reinforcing a Windows-first perspective. No Linux or cross-platform command-line examples or tools are provided.
Recommendations
- Explicitly mention Azure CLI (az) as a cross-platform tool alongside PowerShell when listing management interfaces.
- Provide Linux/Bash shell examples for common tasks, or at least reference that Azure CLI can be used from Linux/macOS.
- When listing interfaces, alternate or rotate the order (e.g., 'APIs, Azure CLI, PowerShell, or the Azure portal') to avoid implicit prioritization of Windows tools.
- Add a section or callout highlighting cross-platform management options, including Azure CLI and REST API usage from Linux/macOS.
- Where scripting or automation is discussed, provide both PowerShell and Bash/Azure CLI script snippets or links to equivalent documentation.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-short-term-clone.md
...articles/azure-netapp-files/create-short-term-clone.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell commands for feature registration and status checking, mentioning Azure CLI as an alternative only after the PowerShell examples. There are no explicit Linux shell (bash) or cross-platform CLI examples, and the initial instructions focus on PowerShell, which is more common on Windows systems.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell examples for all feature registration and status checking steps.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
- Where possible, include bash shell script examples for automation scenarios.
- Review the order of tool presentation to avoid always listing Windows-centric tools first.
- Add a note clarifying that all operations can be performed from Linux or macOS using Azure CLI.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-volumes-dual-protocol.md
...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by exclusively describing the management of LDAP POSIX attributes using Windows tools (Active Directory Users and Computers MMC snap-in) and providing step-by-step instructions only for Windows systems. There are no equivalent instructions or examples for managing POSIX attributes or configuring LDAP from Linux systems. Additionally, Windows terminology and tools are mentioned first and in detail, while Linux alternatives are only referenced via links or omitted.
Recommendations
- Provide equivalent instructions for managing LDAP POSIX attributes using common Linux tools (e.g., ldapmodify, phpldapadmin, or command-line utilities).
- Include Linux-based examples for accessing and editing LDAP attributes, such as using ldapsearch and ldapmodify.
- When describing attribute management, present both Windows and Linux approaches side-by-side or in parallel sections.
- Avoid assuming the administrator is using a Windows environment; clarify that either platform can be used and provide guidance for both.
- Where Windows-specific features or limitations are described, add notes about Linux equivalents or differences.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-region-replication-create-peering.md
...etapp-files/cross-region-replication-create-peering.md
High Priority
View Details â
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 example for feature registration and status checking, mentioning Azure CLI only as an alternative. There are no explicit Linux shell or bash examples, and PowerShell is presented first and in detail. The rest of the guide relies heavily on Azure Portal UI steps, which are platform-agnostic, but the only command-line examples are PowerShell-centric.
Recommendations
- Provide Azure CLI (bash) examples alongside PowerShell for all command-line steps, especially for feature registration and status checking.
- Present Azure CLI and PowerShell examples in parallel or in tabs, rather than listing PowerShell first and CLI as an afterthought.
- Explicitly mention that both PowerShell and CLI are supported, and provide guidance for users on Linux/macOS.
- Where possible, add bash shell equivalents for any scripting or automation steps.
- Review future documentation to ensure parity between Windows and Linux tooling and examples.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-zone-region-replication-configure.md
...etapp-files/cross-zone-region-replication-configure.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides only Azure PowerShell examples for feature registration, which is Windows-centric. Although it briefly mentions Azure CLI as an alternative, no CLI commands are shown. There are no Linux-specific instructions or examples, and the PowerShell approach is presented first and in detail.
Recommendations
- Add explicit Azure CLI command examples for feature registration and status checking, alongside PowerShell.
- Present Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
- Clarify that all steps can be performed from Linux/macOS using Azure CLI or Cloud Shell.
- Where screenshots or UI instructions are given, note any OS-specific differences or confirm cross-platform parity.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/default-individual-user-group-quotas-introduction.md
...s/default-individual-user-group-quotas-introduction.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Observing user quota settings and consumption' section, Windows client instructions and screenshots are presented before Linux client instructions. Windows-specific tools (Windows Explorer, dir command) are mentioned explicitly, while only the quota(1) command is referenced for Linux. There is no mention of Linux graphical file managers or alternative CLI tools. The 'Next steps' section includes a link to Windows Security Identifiers documentation but does not provide a Linux equivalent (such as a link to information about UNIX UIDs/GIDs).
Recommendations
- Present Linux and Windows client instructions in parallel or alternate the order to avoid Windows-first bias.
- Include examples of observing quotas using popular Linux graphical file managers (e.g., Nautilus, Dolphin) if supported.
- Expand Linux CLI instructions to mention alternative commands (e.g., df, ls) where relevant.
- In the 'Next steps' section, add links to documentation about UNIX user and group IDs to match the Windows SID reference.
- Clarify protocol-specific instructions (e.g., SMB for Windows, NFS for Linux) to ensure parity in guidance.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/dual-protocol-permission-behaviors.md
...ure-netapp-files/dual-protocol-permission-behaviors.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows/NTFS concepts and tools before their Linux/NFS equivalents, providing more detail for Windows-specific behaviors, and omitting concrete Linux/NFS command examples for permission management. Windows terminology (NTFS, SID, Windows RPC, Active Directory) is used more prominently, while Linux/NFS management is described as CLI-only and less accessible. There are no step-by-step Linux examples or tool recommendations, and Windows management is presented as the default or primary use case.
Recommendations
- Provide parallel Linux/NFS examples for permission management, such as step-by-step usage of nfs4_getfacl/nfs4_setfacl, chown, chmod, and relevant NFS client tools.
- Balance the order of presentation so that Linux/NFS concepts and tools are described before or alongside Windows/NTFS equivalents, rather than after.
- Include screenshots or GUI management options for Linux/NFS where possible, or clarify the limitations and suggest alternative workflows.
- Explicitly mention Linux identity sources (such as LDAP, NIS, or local passwd/group files) and how they interact with Azure NetApp Files.
- Add troubleshooting sections for common Linux/NFS permission issues, similar to the detail provided for Windows/NTFS scenarios.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/disable-showmount.md
.../main/articles/azure-netapp-files/disable-showmount.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page primarily uses Azure PowerShell commands for feature registration and management, which are most commonly used on Windows. While it briefly mentions Azure CLI as an alternative, no explicit CLI examples are provided, and there are no Linux-specific instructions or examples. The documentation assumes familiarity with PowerShell and does not address Linux shell usage or provide parity for Linux administrators.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell commands, especially for feature registration and status checks.
- Include instructions or notes for running these commands from a Linux shell or macOS terminal.
- Clarify that both PowerShell and Azure CLI are cross-platform, and link to installation guides for Linux users.
- Consider reordering examples so that CLI commands (which are more platform-neutral) are presented before PowerShell commands.
- Add a section or note addressing Linux administrators, ensuring they understand how to perform these actions without relying on Windows tools.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-application-resilience.md
...icles/azure-netapp-files/faq-application-resilience.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. SMB/Windows-centric scenarios are described in greater detail, with explicit mention of Windows-only features (e.g., SMB Continuous Availability, Transparent Failover) and Windows workloads (Citrix, FSLogix, MS SQL Server). Linux equivalents are either omitted, referenced only in passing, or not provided with comparable detail. For example, SQL Server on Linux is explicitly excluded from SMB CA support, and Boomi recommendations specify Windows for SMB and Linux for NFS, but only Windows SMB mounting is linked in 'Next steps'. There are no PowerShell-heavy examples, but Windows tools and patterns are mentioned before or instead of Linux ones in several places.
Recommendations
- Provide equivalent Linux examples and guidance for SMB scenarios, including any supported Linux SMB workloads and configuration steps.
- Clarify whether features like SMB Continuous Availability or Transparent Failover are available or planned for Linux clients, and document any limitations.
- Add links and references to Linux mounting guides for SMB volumes, not just NFS.
- Where Windows tools or patterns are mentioned, ensure Linux alternatives are described with equal prominence and detail.
- Explicitly state support boundaries for both Windows and Linux in all relevant sections, avoiding Windows-first phrasing.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/includes/smb-continuous-availability.md
...e-netapp-files/includes/smb-continuous-availability.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows-based workloads (Citrix, FSLogix, MSIX, SQL Server on Windows) and explicitly stating that Linux SQL Server is not supported. All examples and guidance reference Windows tools and patterns (Active Directory, Windows security privileges), with no Linux equivalents or alternatives provided.
Recommendations
- Clearly state the lack of Linux support at the beginning to set expectations.
- If possible, provide information on roadmap or alternatives for Linux users.
- Include examples or guidance for Linux environments if/when support becomes available.
- Reference cross-platform tools or clarify which features are Windows-only to avoid confusion.
- Consider mentioning any workarounds or related features for Linux users, if applicable.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/enable-continuous-availability-existing-SMB.md
...p-files/enable-continuous-availability-existing-SMB.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively provides instructions and verification steps for Windows environments, using PowerShell commands and referencing Windows system behaviors (e.g., rebooting Windows systems). There are no examples or guidance for Linux or macOS clients, nor are equivalent tools or commands mentioned for non-Windows platforms.
Recommendations
- Include instructions for verifying SMB Continuous Availability from Linux clients, such as using 'smbstatus' or appropriate SMB client tools.
- Clarify whether Linux and macOS clients are supported for SMB CA and, if so, provide relevant steps or caveats.
- Present both Windows and Linux/macOS examples side-by-side where possible, or at least mention Linux/macOS considerations.
- Avoid assuming all users are on Windows; use more neutral language (e.g., 'client systems' instead of 'Windows systems') and provide parity in troubleshooting and verification steps.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. While it mentions both Linux (rsync for NFS) and Windows (robocopy for SMB) tools, the Windows tool (robocopy) is referenced with a direct Microsoft Docs link, and there are no Linux command-line examples or explicit parity in tool explanations. There are no PowerShell-heavy sections, but Windows tools are slightly more emphasized, and Linux examples are minimal or absent.
Recommendations
- Provide explicit Linux command-line examples for NFS and SMB migrations, such as sample rsync and smbclient commands.
- Include links to Linux tool documentation (e.g., rsync, smbclient, cifs-utils) similar to the robocopy link for Windows.
- When listing migration tools, present Linux and Windows options together and with equal detail, rather than referencing Windows tools more prominently.
- Add a table or section comparing common Linux and Windows migration tools and their usage scenarios.
- Ensure that for every Windows-specific tool or example, a Linux equivalent is also provided.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-smb.md
...-docs/blob/main/articles/azure-netapp-files/faq-smb.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. Most examples, troubleshooting steps, and tool references are Windows-centric (e.g., MMC, Active Directory Users and Computers, Windows Server DFS Namespace). There is little to no mention of Linux clients, tools, or configuration patterns for SMB, nor are Linux-specific troubleshooting steps or examples provided. The documentation assumes a Windows environment for both administration and client access, and omits guidance for Linux or macOS users accessing SMB shares.
Recommendations
- Add explicit examples for mounting and accessing Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or Nautilus).
- Include troubleshooting steps and best practices for Linux SMB clients (such as handling permissions, file locking, and offline files).
- Mention Linux equivalents for Windows tools (e.g., alternatives to MMC for managing shares, or using smbstatus/smbcontrol for sessions and open files).
- Clarify support and limitations for non-Windows SMB clients, including any differences in feature support (e.g., DFS-N, Alternate Data Streams, oplocks).
- Provide parity in configuration and management instructions for both Windows and Linux environments, ensuring Linux administrators can follow along without relying on Windows-only tools.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/generate-user-group-quota-reports.md
...zure-netapp-files/generate-user-group-quota-reports.md
High Priority
View Details â
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 commands before Azure CLI alternatives, and omitting direct Linux shell or CLI examples. The registration steps are described primarily using PowerShell, which is native to Windows, while Linux users are only briefly referenced via a link to Azure CLI documentation, without explicit command examples. No Linux-specific tools or patterns are discussed, and the workflow assumes familiarity with Windows-centric tooling.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell for feature registration and status checking, formatted for bash/shell environments.
- Mention Azure CLI as an equal alternative to PowerShell, not just as a secondary option.
- Include notes or examples for Linux/macOS users, clarifying how to perform the same steps in their environments.
- Ensure screenshots and UI instructions do not assume a Windows environment unless necessary.
- Add a section or callout for cross-platform usage, highlighting any differences or considerations for Linux users.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/includes/netlogon-april-2023.md
...les/azure-netapp-files/includes/netlogon-april-2023.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page focuses exclusively on the Windows platform, referencing the April 2023 Windows Update and Netlogon Secure Channel changes without mentioning Linux or cross-platform considerations. No Linux tools, commands, or equivalent guidance are provided, and the only example or context is Windows-specific.
Recommendations
- Add information about how the Netlogon Secure Channel changes may (or may not) impact Linux-based clients or Samba implementations.
- Include Linux-specific troubleshooting steps or guidance for administrators managing Azure NetApp Files with Linux systems.
- Provide parity in examples by referencing both Windows and Linux tools/utilities where applicable.
- Clarify if the update is only relevant to Windows environments, and explicitly state the impact (or lack thereof) on Linux environments.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol-schemas.md
...files/lightweight-directory-access-protocol-schemas.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation page demonstrates a strong Windows bias. All examples, attribute descriptions, and configuration instructions are centered around Microsoft Active Directory and Windows-specific tools (such as ADSI Edit). There are no examples or guidance for configuring equivalent LDAP schema or attribute indexing in common Linux-based LDAP servers (e.g., OpenLDAP). The documentation assumes the use of Windows environments and does not address Linux LDAP administration tools or patterns.
Recommendations
- Add parallel examples and instructions for configuring LDAP schemas and attribute indexing in Linux-based LDAP servers such as OpenLDAP.
- Mention and document Linux tools (e.g., ldapmodify, slapd-config, phpldapadmin) for schema and attribute management alongside Windows tools.
- Reorder sections or provide dual-path guidance so that Linux/OpenLDAP equivalents are presented alongside or before Windows/Active Directory instructions.
- Clarify that Azure NetApp Files supports integration with non-Active Directory LDAP servers and provide references or links to relevant Linux LDAP documentation.
- Include screenshots or command-line examples for Linux-based LDAP administration tasks where Windows screenshots are currently shown.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/lightweight-directory-access-protocol.md
...-netapp-files/lightweight-directory-access-protocol.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Microsoft Active Directory as the primary LDAP server, referencing Windows-specific tools (e.g., nslookup with Windows syntax), and providing examples and configuration details mainly for Windows environments. Linux alternatives (such as FreeIPA, OpenLDAP, Red Hat Directory Server) are mentioned only in a note and not elaborated upon. Linux tools (e.g., dig) are referenced but not exemplified, and there are no Linux-specific configuration or troubleshooting examples.
Recommendations
- Provide equal coverage and examples for Linux LDAP servers (FreeIPA, OpenLDAP, Red Hat Directory Server), including configuration and troubleshooting steps.
- Include Linux command-line examples (e.g., dig, ldapsearch) alongside Windows nslookup examples, with sample outputs.
- Clarify support and configuration differences for Linux-based LDAP servers in Azure NetApp Files, not just AD DS.
- Reorganize sections to present both Windows and Linux options together, rather than focusing on Windows first.
- Add guidance for extending LDAP schemas and managing UNIX attributes in Linux environments.
- Ensure that all features and limitations are described for both Windows and Linux LDAP server types.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-cool-access.md
...main/articles/azure-netapp-files/manage-cool-access.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell commands are presented as the primary method for feature registration, with Azure CLI commands mentioned only as an alternative and without explicit examples. The step-by-step instructions and screenshots focus on GUI actions typical of Windows environments (e.g., right-clicking), with no mention of Linux-specific workflows or command-line alternatives for Linux users. There are no examples or guidance for managing cool access using Linux shell commands or automation tools, and the documentation does not address Linux-specific considerations or parity.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell for all registration and management steps, including full syntax and sample output.
- Include Linux shell (bash) equivalents for relevant operations, such as using az CLI in bash scripts.
- Add screenshots or instructions for managing cool access using the Azure Portal in Linux environments (if applicable), or clarify that the GUI steps are cross-platform.
- Mention and document any differences or considerations for Linux users, such as file system compatibility, automation, or scripting.
- Ensure that all code blocks and examples are presented in both PowerShell and bash/CLI formats, with tabs or toggles for user selection.
- Review and update terminology to avoid Windows-centric language (e.g., 'right-click') and provide alternative instructions for keyboard or command-line navigation.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-smb-share-access-control-lists.md
...-netapp-files/manage-smb-share-access-control-lists.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation exclusively describes Windows-based methods (Windows Explorer, Microsoft Management Console) for managing SMB share ACLs in Azure NetApp Files. There are no Linux or cross-platform examples, and all tools and workflows mentioned are Windows-specific. The documentation does not mention or provide alternatives for Linux users, nor does it clarify if such operations are possible from non-Windows systems.
Recommendations
- Add information about whether SMB share ACLs can be viewed or managed from Linux clients, and if not, state this explicitly.
- If possible, provide Linux-based methods (e.g., using smbclient, setfacl, or other Samba tools) for viewing or managing SMB share ACLs.
- Include command-line examples (e.g., PowerShell and Bash/smbclient) for parity.
- Clarify any platform limitations in a dedicated section so Linux administrators understand their options.
- Consider referencing cross-platform tools or APIs (such as REST, if available) for managing SMB share ACLs.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/migrate-volumes.md
...ob/main/articles/azure-netapp-files/migrate-volumes.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing a PowerShell sample script for the migration assistant workflow and using Azure PowerShell commands as the primary example for feature registration, with Azure CLI only mentioned as an alternative. There are no explicit Linux shell or Bash examples, and the PowerShell workflow is referenced before any cross-platform alternatives. This may disadvantage Linux users or those who prefer Bash/CLI tools.
Recommendations
- Provide equivalent Bash or Azure CLI scripts alongside PowerShell examples for all steps, especially for migration assistant workflows.
- When referencing sample scripts, include both PowerShell and Bash/CLI versions, or clarify cross-platform compatibility.
- List Azure CLI commands before or alongside PowerShell commands to avoid implying Windows-first workflows.
- Explicitly mention that all REST API steps can be performed from any OS, and provide Bash/cURL examples for REST API calls.
- Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tools.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-file-permissions-smb.md
...-netapp-files/network-attached-file-permissions-smb.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page focuses exclusively on NTFS ACLs and references Microsoft's Windows documentation for access control, without mentioning Linux equivalents (such as POSIX permissions or NFSv4 ACLs). No Linux or cross-platform examples are provided, and only Windows terminology and tools are referenced.
Recommendations
- Include a section comparing NTFS ACLs with Linux/UNIX permissions (e.g., POSIX permissions, NFSv4 ACLs) to provide context for Linux users.
- Provide examples or references for managing SMB permissions from Linux clients (e.g., using smbclient, setfacl, or mount.cifs options).
- Mention any limitations or considerations when accessing Azure NetApp Files SMB volumes from Linux systems.
- Add links to relevant Linux documentation or tools for managing SMB file permissions.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/monitor-volume-capacity.md
...articles/azure-netapp-files/monitor-volume-capacity.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation presents Windows client methods before Linux equivalents, describes Windows-specific tools (File Explorer, dir command) in more detail, and references PowerShell in the REST API section. Linux examples are present but less elaborated, and Linux tools are not mentioned first or in equal detail.
Recommendations
- Present Linux and Windows client methods in parallel or alternate order to avoid implicit prioritization.
- Expand Linux section to include additional commands (e.g., ls, stat, ncdu) and GUI tools (e.g., GNOME Disks, KDE Dolphin) for parity with Windows File Explorer.
- Include REST API usage examples for Linux environments (e.g., curl, wget, Python scripts) alongside PowerShell.
- Clarify that both Windows and Linux clients are equally supported and provide troubleshooting tips for both platforms.
- Ensure screenshots and examples are balanced between Windows and Linux environments.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/mount-volumes-vms-smb.md
...n/articles/azure-netapp-files/mount-volumes-vms-smb.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively covers mounting SMB volumes on Windows virtual machines, providing only Windows client instructions and screenshots. There are no examples or instructions for mounting SMB volumes on Linux clients, nor are Linux tools or commands mentioned. The focus is entirely on Windows tools and workflows.
Recommendations
- Add a section with instructions for mounting SMB volumes on Linux clients, including relevant commands (e.g., using 'mount -t cifs' or 'smbclient').
- Provide Linux-specific screenshots or terminal output to illustrate the process.
- Mention Linux tools and patterns alongside Windows tools, ensuring parity in the order and detail of instructions.
- Consider updating the title and description to clarify if the page is intended to be Windows-specific, or broaden the scope to include Linux if applicable.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-file-permissions.md
...zure-netapp-files/network-attached-file-permissions.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates Windows bias by describing Windows (SMB) permission inheritance first, providing a screenshot of the Windows interface, and referencing Windows-specific tools and patterns (e.g., 'advanced permission view'). Linux/NFS equivalents are mentioned later and lack visual examples or command-line instructions. There are no Linux shell or setfacl/chmod/chown examples, and the explanation of NFS permission inheritance is less detailed.
Recommendations
- Provide Linux/NFS examples with equivalent detail, including screenshots of common Linux tools (e.g., setfacl, chmod, chown) or command-line examples for managing NFS permissions and inheritance.
- Present SMB and NFS sections in parallel or alternate order to avoid consistently prioritizing Windows.
- Include explanations and visuals for how to manage inheritance and permissions on Linux clients, not just Windows.
- Add links to Linux/NFS-specific documentation and tools where appropriate.
- Clarify differences and similarities in permission management workflows between Windows and Linux environments.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-file-system-group-memberships.md
...-netapp-files/network-file-system-group-memberships.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by focusing on Microsoft Active Directory as the LDAP implementation, referencing Windows group membership logic, and providing examples and screenshots exclusively from Windows tools (such as ldp.exe and Windows group member fields). There are no examples or instructions for Linux LDAP servers (such as OpenLDAP), nor are Linux-native tools or patterns mentioned.
Recommendations
- Include equivalent examples for Linux LDAP servers (e.g., OpenLDAP), showing how group memberships and supplemental groups are managed and queried.
- Provide screenshots and command-line examples using Linux tools such as ldapsearch, getent, or nslcd.
- Clarify whether Azure NetApp Files supports non-Active Directory LDAP servers and document any differences in behavior or configuration.
- Mention Linux group membership logic and schema attributes (such as memberUid) alongside Windows-specific attributes.
- Ensure that references to Windows tools (e.g., ldp.exe) are balanced with Linux alternatives, and avoid presenting Windows-first workflows unless required by the service.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/network-attached-storage-permissions.md
...e-netapp-files/network-attached-storage-permissions.md
High Priority
View Details â
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), with no mention of Linux or cross-platform alternatives. Examples and screenshots for SMB features (such as access-based enumeration, nonbrowsable shares, and ACLs) are all shown using Windows Explorer or Windows-specific commands, with no Linux or macOS equivalents. The documentation refers to 'net view' and Windows Explorer as the primary ways to interact with SMB shares, and does not provide parity for Linux users (e.g., using smbclient, mount.cifs, or other tools). There are no examples or instructions for managing SMB share permissions or accessing SMB shares from Linux clients.
Recommendations
- Include instructions and examples for managing SMB share permissions and accessing SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or relevant Linux tools).
- Mention and demonstrate how Linux/macOS users can view and interact with SMB shares, including how access-based enumeration and nonbrowsable shares behave in those environments.
- Provide parity in screenshots and examples, showing both Windows and Linux client perspectives for SMB features.
- Reference cross-platform tools for managing SMB shares and ACLs, such as setfacl, smbclient, or other open-source utilities.
- Clarify whether features like access-based enumeration and nonbrowsable shares apply equally to non-Windows clients, and document any differences.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/object-rest-api-browser.md
...articles/azure-netapp-files/object-rest-api-browser.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by providing certificate installation steps that are specific to Windows (using Edge, GUI dialogs, and the Windows certificate store) without mentioning Linux or macOS equivalents. The S3 Browser example is Windows-only, and the certificate installation process does not cover Linux CLI or browser-agnostic methods. While the AWS CLI section includes both Windows and Linux installation instructions, the overall flow and tool selection favor Windows environments.
Recommendations
- Add instructions for installing the certificate on Linux systems, including CLI-based methods (e.g., using update-ca-certificates or copying to /usr/local/share/ca-certificates).
- Include examples for macOS users, such as using Keychain Access to install certificates.
- Mention and provide examples for S3-compatible clients available on Linux (e.g., s3cmd, rclone, or Cyberduck) in addition to S3 Browser.
- When listing AWS CLI installation steps, present Linux and Windows instructions in parallel or in a platform-neutral order.
- Avoid GUI-only instructions; provide CLI alternatives where possible for cross-platform parity.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/ransomware-configure.md
...in/articles/azure-netapp-files/ransomware-configure.md
High Priority
View Details â
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 example for feature registration and status checking, with Azure CLI (which is cross-platform and more common on Linux) only mentioned secondarily and without explicit command examples. No Linux-specific instructions, screenshots, or shell examples are provided, and the documentation assumes familiarity with PowerShell and Windows-centric workflows.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell for all registration and status-checking steps (e.g., show 'az feature register' and 'az feature show' commands).
- When referencing command-line instructions, present Azure CLI (cross-platform) examples first, or at least in parallel with PowerShell.
- Include notes or sections for Linux/macOS users, clarifying that all features are accessible via Azure CLI and the Azure Portal.
- Ensure screenshots and UI instructions do not assume a Windows environment unless necessary.
- Where possible, add bash/zsh shell equivalents for any scripts or automation steps.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/sever-message-block-support.md
...cles/azure-netapp-files/sever-message-block-support.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. Most examples, terminology, and feature explanations reference Windows tools, protocols, and patterns (e.g., NTFS, Hyper-V, MS SQL Server, VSS, LMHOSTS, Windows quota semantics, Windows Indexing Service). Windows-specific features are described in detail, while Linux or macOS equivalents are rarely mentioned or are described as unsupported or disabled (e.g., UNIX extensions, export policies for SMB, deletion semantics). References to Linux clients are minimal and lack concrete configuration or usage examples. The documentation assumes familiarity with Windows environments and omits guidance for Linux-based SMB clients, their configuration, and troubleshooting.
Recommendations
- Add explicit examples and configuration steps for Linux-based SMB clients (e.g., mounting Azure NetApp Files SMB shares from Linux using smbclient, mount.cifs, or similar tools).
- Include Linux-specific troubleshooting tips and caveats, such as handling permissions, symlinks, and file attribute differences.
- Provide parity in describing features and limitations for both Windows and Linux/macOS clients, especially where behaviors differ (e.g., delete semantics, offline files, symbolic links).
- Reference Linux tools and documentation (e.g., Samba, cifs-utils) alongside Windows tools.
- Clarify which features are relevant or available to Linux/macOS clients and provide guidance for mixed-environment deployments.
- Avoid assuming Windows as the default client; use neutral language and order examples for both platforms equally.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/tools-reference.md
...ob/main/articles/azure-netapp-files/tools-reference.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation lists several tools for Azure NetApp Files, but the only automation/scripted tool with a specific platform mentioned is ANFHealthCheck, which is described as a PowerShell runbook. There are no Linux/bash equivalents or cross-platform scripting examples provided. This suggests a bias towards Windows/PowerShell environments, with a lack of parity for Linux users.
Recommendations
- Provide equivalent bash or Python scripts for Linux users where PowerShell runbooks are offered (e.g., for ANFHealthCheck).
- Explicitly mention if tools are cross-platform or provide platform-specific instructions/examples for both Windows and Linux.
- Highlight or add Linux-native automation options (such as Azure CLI/bash scripts) alongside PowerShell-based solutions.
- Review all tool documentation to ensure Linux users are not excluded from automation and monitoring workflows.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/troubleshoot-volumes.md
...in/articles/azure-netapp-files/troubleshoot-volumes.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates a Windows bias by consistently prioritizing SMB/Active Directory (Windows-centric) errors and resolutions before NFS/Linux scenarios. Troubleshooting steps and examples frequently reference Windows tools (e.g., PowerShell, Set-ADComputer) and concepts (Active Directory, Microsoft Entra Domain Services) without providing equivalent Linux/Unix commands or alternatives. Where Linux/NFS is mentioned, it is often secondary or less detailed. PowerShell is used for directory operations without showing Linux-native alternatives (e.g., ldapmodify, samba-tool).
Recommendations
- Provide Linux/Unix command-line examples (e.g., using ldapmodify, samba-tool, or kadmin) alongside PowerShell commands for managing AD/Kerberos attributes.
- Structure error tables to alternate or parallelize SMB (Windows) and NFS (Linux) issues, rather than always listing Windows/SMB first.
- Include troubleshooting steps and tools relevant to Linux environments (e.g., systemd, kinit, nsupdate) wherever Windows tools are referenced.
- Expand on NFS/Linux-specific troubleshooting, such as using Linux logs, systemctl, and open-source LDAP/Kerberos tools.
- Where possible, provide parity in detail and actionable steps for both Windows and Linux administrators.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/understand-path-lengths.md
...articles/azure-netapp-files/understand-path-lengths.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows/SMB path length details, providing Windows-specific configuration steps (such as registry edits and Group Policy), and showing Windows dialog screenshots. Linux/NFS examples are present but less detailed, with fewer practical configuration or troubleshooting steps. Windows tools and patterns (drive letter mapping, UNC paths, registry changes) are described in depth, while equivalent Linux/NFS client configuration and troubleshooting are not covered as thoroughly.
Recommendations
- Add Linux/NFS client configuration examples, such as mounting options and troubleshooting path length errors.
- Provide parity in screenshots and error dialogs for Linux environments (e.g., terminal output for path length errors).
- Include instructions for extending or querying NFS path limits using Linux tools and configuration files.
- Balance the order of presentation so that NFS/Linux information is given equal prominence to SMB/Windows details.
- Mention Linux equivalents for Windows tools (e.g., alternatives to Group Policy for enforcing limits, or using fstab for mounting).
- Clarify cross-platform limitations and workarounds for both Windows and Linux clients, not just Windows.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/use-dfs-n-and-dfs-root-consolidation-with-azure-netapp-files.md
...s-n-and-dfs-root-consolidation-with-azure-netapp-files.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows environments. All examples, instructions, and tooling references are exclusively for Windows Server, PowerShell, and Windows GUI tools. There are no Linux or cross-platform examples, and the documentation does not mention or address Linux clients, tools, or alternatives. Windows terminology and patterns are used throughout, and Windows tools are always presented first and exclusively.
Recommendations
- Acknowledge in the introduction that DFS Namespaces is a Windows-centric technology, but clarify any possible Linux client or integration scenarios (e.g., using SMB mounts from Linux).
- Provide guidance or references for accessing DFS-N namespaces from Linux clients (e.g., using smbclient, mount.cifs, or other SMB tools on Linux).
- If possible, include Linux command-line examples for mounting SMB shares exposed via DFS-N, or at least mention that Linux clients can access these shares using standard SMB tools.
- Mention any limitations or considerations when using DFS-N with non-Windows clients, such as differences in referral handling or UNC path support.
- Add a section or note on how to manage DNS records using Linux tools (e.g., `nsupdate`, `dig`, or editing BIND zone files) for organizations not using Windows DNS servers.
- Where PowerShell is used, clarify that these steps are for Windows environments, and suggest alternatives or workarounds for cross-platform or hybrid environments if applicable.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/authenticate-application.md
.../main/articles/azure-relay/authenticate-application.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a Windows bias by focusing primarily on .NET (C#) code samples, referencing the Azure portal UI (which is most familiar to Windows users), and providing sample applications only for .NET, Java, and JavaScript, with the highlighted code exclusively in C#. There are no explicit Linux or cross-platform command-line examples (e.g., Bash), and the 'Next steps' section lists PowerShell before Azure CLI, which is more common on Linux. There is no mention of Linux-specific tools, nor are there instructions for running the sample on Linux or macOS.
Recommendations
- Add explicit instructions and code samples for running the authentication flow on Linux and macOS, including any prerequisites or differences.
- Provide Bash or cross-platform shell examples for common tasks (e.g., using Azure CLI for authentication and role assignment).
- Include code samples in additional languages (e.g., Python) that are popular on Linux.
- When listing tools or commands, mention Azure CLI before or alongside PowerShell, as CLI is more common on Linux.
- Clarify that the sample applications can be run on Linux (if true), and provide any necessary steps or troubleshooting tips for non-Windows environments.
- Reference Linux package managers or installation instructions for required SDKs or tools.
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
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. All instructions for creating the project and managing dependencies are given using Visual Studio GUI steps, with no mention of cross-platform alternatives such as .NET Core/SDK CLI tools or Visual Studio Code. There are no Linux-specific instructions or examples, and the workflow is tailored to Windows development environments.
Recommendations
- Provide alternative instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') which works on Linux, macOS, and Windows.
- Mention and provide examples for using Visual Studio Code or other cross-platform editors.
- Clarify whether the code and dependencies are compatible with .NET Core/5+/6+ and not just .NET Framework.
- Include instructions for installing the NuGet package via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay') in addition to the Visual Studio GUI.
- Explicitly state cross-platform compatibility and provide any Linux-specific notes if necessary.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-config.md
.../articles/azure-resource-manager/bicep/bicep-config.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing on Visual Studio Code (a cross-platform editor but with a Windows-centric workflow) and referencing Azure PowerShell and AzureCLI in credential precedence, with PowerShell listed before CLI in examples. There are no explicit Linux or macOS-specific instructions, nor are there examples using Linux-native editors or shell commands for creating or managing the configuration file.
Recommendations
- Add explicit examples for creating and editing the bicepconfig.json file using Linux-native tools (e.g., nano, vim, or command-line touch/cat).
- When discussing credential precedence, clarify the cross-platform availability of AzureCLI and Azure PowerShell, and consider listing AzureCLI first as it is more commonly used on Linux.
- Include screenshots or instructions for creating the configuration file in editors popular on Linux/macOS (e.g., VS Code on Linux, Vim, or even gedit).
- Mention that all instructions apply equally to Linux/macOS unless otherwise noted, and provide any OS-specific caveats if they exist.
- Ensure that references to tools or commands (such as Visual Studio Code or PowerShell) are balanced with Linux/macOS equivalents or alternatives.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/ip-firewall-virtual-networks.md
...n/articles/azure-relay/ip-firewall-virtual-networks.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation demonstrates Windows bias by referencing deployment instructions specifically for Azure Resource Manager via a PowerShell link, without mentioning or providing equivalent CLI/Bash/Linux instructions. No Linux-specific tools or examples are provided, and the only automation/deployment path referenced is PowerShell, which is primarily a Windows tool. There are no explicit Linux or cross-platform command-line examples.
Recommendations
- Add Azure CLI (az) examples for deploying the Resource Manager template, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash shell examples for common tasks, such as using curl or jq to interact with Azure REST APIs.
- When referencing deployment instructions, provide links for both PowerShell and Azure CLI, and mention them together (e.g., 'To deploy the template, follow the instructions for Azure Resource Manager using PowerShell or Azure CLI').
- Explicitly state that the instructions apply to all platforms, and clarify any platform-specific steps if necessary.
- Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/private-link-service.md
...blob/main/articles/azure-relay/private-link-service.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a clear Windows bias. All command-line examples for automating private endpoint creation use Azure PowerShell, with no equivalent Azure CLI, Bash, or Linux shell examples. The validation steps explicitly instruct users to create a Windows virtual machine, with no mention of Linux VMs or cross-platform alternatives. The only command-line validation example uses Windows-centric instructions. There is no guidance for Linux users, and the only automation tooling referenced is PowerShell.
Recommendations
- Add Azure CLI examples alongside (or before) PowerShell examples for all automation steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- In the validation section, provide instructions for creating both Windows and Linux virtual machines, or use neutral language (e.g., 'Create a virtual machine') with links to both Windows and Linux VM creation guides.
- Show command-line validation examples (such as nslookup) in both Windows Command Prompt/PowerShell and Linux shell (bash) formats.
- Mention Linux tools and patterns (such as Bash scripting, Azure CLI, and Linux VM setup) wherever Windows tools are referenced.
- Ensure screenshots and portal instructions are platform-neutral, or clarify that the Azure portal is accessible from any OS.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-api-overview.md
...s/blob/main/articles/azure-relay/relay-api-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page shows a Windows bias by listing .NET Framework (Windows-only) and WCF Relay (Windows-specific technology) before cross-platform alternatives. There is no mention of Linux-specific usage, examples, or tools, and the .NET Framework library is described in detail without clarifying its Windows-only nature. No Linux command-line or environment-specific guidance is provided, and examples focus on Windows technologies and patterns.
Recommendations
- Explicitly mention platform compatibility for each API/library, including which are cross-platform and which are Windows-only.
- Add Linux-specific usage notes and examples, such as how to use the .NET Standard library on Linux and how to run Node.js modules on Linux.
- Provide parity in examples and guidance for Linux environments, including installation, configuration, and troubleshooting steps.
- Avoid listing Windows-only technologies (e.g., WCF Relay) before cross-platform options, or clearly separate them.
- Include references to Linux tools and patterns where applicable, such as systemd for service management or Linux networking concepts.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-get-started.md
...e-relay/relay-hybrid-connections-dotnet-get-started.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) for all development steps, without mentioning cross-platform alternatives or providing Linux-specific instructions. There are no examples or guidance for developing or running the .NET applications on Linux (e.g., using VS Code, JetBrains Rider, or the dotnet CLI). The prerequisites and instructions implicitly assume a Windows environment.
Recommendations
- Add instructions for setting up the development environment on Linux, including installing the .NET SDK and using editors like VS Code or JetBrains Rider.
- Provide examples for creating, building, and running the .NET console applications using the dotnet CLI, which is cross-platform.
- Update the prerequisites section to mention Linux and macOS as supported platforms for .NET development, and provide relevant installation links.
- Include screenshots or terminal output from Linux environments to demonstrate parity.
- Clarify that Visual Studio is not required, and that the tutorial can be completed on Linux using alternative tools.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-port-settings.md
.../blob/main/articles/azure-relay/relay-port-settings.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page focuses exclusively on Windows Communication Foundation (WCF) bindings and classes, which are Windows-centric technologies. There are no examples or references to Linux-compatible tools, frameworks, or usage patterns. The documentation assumes the use of Windows tools and does not provide guidance for Linux users or alternative cross-platform approaches.
Recommendations
- Include examples or references for Linux-compatible frameworks (e.g., Java, Python, Node.js) that can interact with Azure Relay.
- Mention cross-platform alternatives to WCF, such as REST APIs or other supported protocols.
- Provide guidance on configuring ports and security for Azure Relay on Linux systems, including firewall and network configuration examples.
- Clarify which features or bindings are Windows-only and suggest alternatives for Linux environments.
- Add links to cross-platform SDKs or documentation for Azure Relay usage outside of Windows.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md
...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 â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a strong Windows bias. All development is performed using Visual Studio (Windows-only), and all examples are based on .NET Framework (not .NET Core/5+/6+), which is primarily supported on Windows. There are no instructions or examples for Linux or cross-platform development environments. The use of Windows-specific tools (Visual Studio, Web Platform Installer) is pervasive, and there are no mentions of alternatives for Linux (e.g., VS Code, JetBrains Rider, or command-line tooling). No PowerShell or CMD scripts are shown, but the entire workflow assumes a Windows environment.
Recommendations
- Provide equivalent instructions for Linux users, including how to set up the development environment using cross-platform tools like VS Code or JetBrains Rider.
- Include .NET Core or .NET 6+ examples, which are cross-platform, instead of only .NET Framework.
- Document how to install the Azure SDK and required dependencies on Linux (using apt, yum, or direct downloads).
- Add command-line examples for project creation, building, and running (using dotnet CLI), not just Visual Studio UI steps.
- Mention and provide guidance for running the sample applications on Linux and macOS.
- Clarify which steps are Windows-specific and provide alternatives where possible.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-what-is-it.md
...ocs/blob/main/articles/azure-relay/relay-what-is-it.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. The WCF Relay feature is described as legacy and is tightly coupled to Windows technologies (WCF, .NET Framework), with all examples and quick starts for WCF Relay focused on Windows-centric tools and frameworks. The Hybrid Connections feature is more cross-platform, with examples for .NET, Node.js, and Java, but the documentation consistently lists .NET/.NET Framework examples first, and there are no explicit Linux or cross-platform command-line examples (e.g., Bash, curl, or Linux service setup). There is no mention of Linux-specific tools, nor are there instructions or examples for Linux environments, especially for the WCF Relay section.
Recommendations
- Add explicit Linux quick starts and examples, such as using Bash, curl, or Linux-based services for Hybrid Connections.
- Include instructions for setting up and running Azure Relay clients and listeners on Linux environments.
- Provide parity in example ordering (e.g., alternate listing Node.js or Java examples first, or group by platform).
- Clarify which features are Windows-only (WCF Relay) and which are cross-platform, and provide guidance for Linux users on alternatives.
- Add a table or section comparing Windows and Linux support for each feature, including any limitations or workarounds.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-functions-files.md
.../azure-resource-manager/bicep/bicep-functions-files.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides examples that are heavily oriented toward PowerShell scripts (e.g., .ps1 files, AzurePowerShell deployment scripts) and does not include equivalent examples for Linux shell scripts (e.g., .sh files, Bash). There are no references to Linux tools or patterns, and all script-related examples assume a Windows/PowerShell context. No Linux or cross-platform examples are provided.
Recommendations
- Add examples that use Bash or shell scripts (e.g., .sh files) alongside PowerShell examples, especially in sections demonstrating script loading.
- When referencing deployment scripts, include both 'AzurePowerShell' and 'AzureCLI' (with Bash) resource kinds to show parity.
- Explicitly mention that file paths and encodings are cross-platform, and provide notes or examples for Linux/macOS users.
- Where possible, alternate the order of examples or provide parallel examples for both Windows and Linux environments.
- Clarify that Bicep functions work with files created or edited on any OS, and note any OS-specific considerations (such as line endings or file permissions).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-cli.md
...ain/articles/azure-resource-manager/bicep/bicep-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style paths (e.g., c:\jsontemplates) in all file path examples, mentioning Windows paths before Linux equivalents, and referencing Windows tools (Azure PowerShell, Visual Studio Code) before or instead of Linux alternatives. There are no explicit Linux shell examples (e.g., bash), and Linux-style paths are only mentioned in a few places, often after the Windows version. Installation and usage guidance references Windows-centric tools and patterns, and Linux users may find it less approachable.
Recommendations
- Provide Linux/macOS path examples (e.g., /home/user/jsontemplates) alongside or before Windows paths in all relevant code blocks.
- Include bash/zsh shell command examples where appropriate, not just Azure CLI and PowerShell.
- When referencing installation instructions, ensure parity between Windows and Linux, and link to both Azure CLI and native package manager (apt, yum, brew) installation guides.
- When describing file system locations (e.g., cache paths), list Linux/macOS paths before or alongside Windows paths, not after.
- Avoid using only Windows-specific shortcuts (e.g., SHIFT+ALT+F in VS Code) and mention the Linux/macOS equivalents.
- Add explicit notes or tabs for Linux/macOS users where behavior or commands differ.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-functions-parameters-file.md
...ource-manager/bicep/bicep-functions-parameters-file.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias, especially in the 'readEnvironmentVariable' section. All examples for setting environment variables use PowerShell syntax and reference .NET/Windows APIs. There are no examples for Linux or macOS shells (e.g., Bash), and Windows methods are mentioned exclusively and first. This may confuse or exclude users working on non-Windows platforms.
Recommendations
- Add equivalent examples for setting environment variables in Bash (Linux/macOS), e.g., export testEnvironmentVariable="Hello World!".
- Mention both Windows (PowerShell/CMD) and Linux/macOS (Bash/Zsh) methods for setting environment variables, and present them together or in parallel sections.
- Reference cross-platform documentation for environment variables, not just Windows/.NET APIs.
- Clarify that Bicep and its parameter files are cross-platform and that environment variable handling depends on the user's OS/shell.
- Where possible, avoid assuming PowerShell as the default shell; provide parity for Linux/macOS users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/create-resource-group.md
.../azure-resource-manager/bicep/create-resource-group.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment commands. However, PowerShell (a Windows-centric tool) is always presented after the Azure CLI, and there is no mention of Bash, Linux shell scripting, or cross-platform command-line environments. The PowerShell examples use the Az module, which is primarily used on Windows, and there are no explicit Linux-specific instructions or troubleshooting notes. The documentation assumes parity between Azure CLI and PowerShell but does not address Linux users directly or provide guidance for common Linux workflows.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux users.
- Add Bash shell scripting examples or usage notes for Linux users, especially for multi-line commands.
- Include troubleshooting notes or prerequisites for running Azure CLI on Linux (e.g., installation links, authentication differences).
- Mention that PowerShell Core is available cross-platform, but clarify that the Az module examples are most familiar to Windows users.
- Consider providing a Linux-first example in at least one section to balance the order of presentation.
- Add a short section or note about using Bicep and deployment commands in WSL (Windows Subsystem for Linux) for users on Windows who prefer a Linux environment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-to-resource-group.md
...ure-resource-manager/bicep/deploy-to-resource-group.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides deployment command examples for both Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux-specific usage or shell environments (e.g., Bash). The CLI example is cross-platform, but the PowerShell example is Windows-centric. There are no Linux shell-specific instructions, nor is there guidance for using Bicep with Bash or other Linux tools. References to Cloud Shell are present but not elaborated upon, and the documentation does not clarify that Azure CLI works natively on Linux and macOS.
Recommendations
- Add explicit Bash/Linux shell examples alongside Azure CLI commands, clarifying cross-platform compatibility.
- Note that Azure CLI is available on Windows, Linux, and macOS, and provide installation or usage links for Linux users.
- Include a section or note on using Bicep with Linux-native tools and environments.
- Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux users (e.g., Azure CLI).
- Expand the Cloud Shell section to explain its cross-platform nature and how both CLI and PowerShell can be accessed from any OS.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/data-types.md
...in/articles/azure-resource-manager/bicep/data-types.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page is generally cross-platform, but it contains a notable Windows bias in the 'Integers' section, where only PowerShell is mentioned as an example of a deployment tool with integer range limitations. No mention is made of Linux or cross-platform equivalents (such as Azure CLI or Bash), and no Linux-specific examples or caveats are provided. This may lead Linux users to believe the limitation is exclusive to PowerShell or Windows environments.
Recommendations
- When referencing deployment tools (such as in the integer range limitation), mention both Windows (PowerShell) and Linux/cross-platform tools (such as Azure CLI, Bash, or Cloud Shell).
- If a limitation is specific to PowerShell, clarify that and provide information about behavior on Linux tools (e.g., Azure CLI).
- Wherever possible, provide examples or notes relevant to both Windows and Linux users, or explicitly state when behavior is platform-agnostic.
- Consider adding a table or section comparing behaviors across common deployment environments (PowerShell, Azure CLI, Bash) for clarity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/decompile.md
...ain/articles/azure-resource-manager/bicep/decompile.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting Azure CLI and Azure PowerShell examples, with PowerShell (a Windows-centric tool) given its own section. There are no explicit Linux/macOS shell examples (e.g., Bash), and the use of Visual Studio Code (a cross-platform tool but often associated with Windows) is emphasized. The documentation does not mention or show Linux-specific shell commands or workflows, nor does it address platform-specific differences or considerations. The ordering of examples (CLI, then PowerShell, then Portal) also puts Windows tools before Linux-native equivalents.
Recommendations
- Add explicit Bash/Linux shell examples for exporting and decompiling templates, e.g., using Bash redirection and file paths.
- Clarify that Azure CLI commands work on all platforms and provide sample commands using Bash syntax (e.g., with single quotes, Linux file paths).
- Mention and show how to use the Bicep CLI directly in Linux/macOS terminal environments.
- Balance the order of examples so that Linux/Bash and Windows/PowerShell are presented equally or alternate their order.
- Explicitly state cross-platform compatibility and call out any platform-specific differences or requirements.
- Consider adding a table or section summarizing commands for Windows (PowerShell), Linux (Bash), and macOS.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-to-tenant.md
...icles/azure-resource-manager/bicep/deploy-to-tenant.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples and commands before or alongside Azure CLI, referencing Windows-centric tools (PowerShell), and using PowerShell syntax in permission assignment steps. There is no explicit mention of Linux environments, nor are Linux-specific instructions or examples provided. The use of Azure CLI does help with cross-platform parity, but the prominence and order of PowerShell examples and references to Windows tools suggest a Windows-first approach.
Recommendations
- Ensure Azure CLI examples are presented first, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links or instructions for those platforms.
- Where PowerShell is referenced, clarify that Azure PowerShell is available on Linux/macOS, or provide Bash script equivalents where possible.
- Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or differences.
- Review all command-line examples to ensure they are not Windows-centric (e.g., avoid using backticks for line continuation in PowerShell, which is not standard in Bash).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-what-if.md
...rticles/azure-resource-manager/bicep/deploy-what-if.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples alongside Azure CLI, often listing PowerShell before CLI or with equal prominence. All command-line examples are either Azure CLI or PowerShell, with no mention of Bash, Linux shell scripting, or native Linux tools. Installation and usage instructions focus on PowerShell and Azure CLI, which, while cross-platform, are more familiar to Windows users. There is no explicit Linux shell (bash/zsh) or macOS-specific guidance, and PowerShell is treated as a first-class citizen, reinforcing a Windows-centric workflow.
Recommendations
- Add explicit Bash/Linux shell examples for all command-line operations, especially for scripting and programmatic evaluation.
- Clarify that Azure CLI is cross-platform and provide Linux/macOS installation instructions or links.
- When listing tools or examples, lead with Azure CLI (as it is more common on Linux/macOS) before PowerShell.
- Include notes or sections for using these commands in native Linux/macOS environments, addressing any differences (e.g., file paths, environment variables).
- Mention and link to relevant Linux-native editors (e.g., Vim, nano) or scripting approaches where appropriate.
- Review and adjust language to avoid implying PowerShell is the default or preferred shell, especially in cross-platform contexts.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-bicep-configure-dev.md
...manager/bicep/deployment-script-bicep-configure-dev.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a bias toward Windows and PowerShell by providing all deployment and upload examples using Azure PowerShell scripts, referencing Windows-style file paths, and omitting equivalent Bash or Azure CLI examples for common tasks such as uploading files. The Docker section also uses Windows drive letters and folder mapping syntax, with no explicit Linux or macOS instructions. While Azure CLI and Bash are mentioned for container images and script content, the operational instructions and tooling focus primarily on PowerShell and Windows-centric workflows.
Recommendations
- Provide Bash/Azure CLI equivalents for all PowerShell deployment and upload scripts, especially for tasks like deploying Bicep files and uploading scripts to Azure Storage.
- Include Linux/macOS-specific Docker volume mount examples (e.g., using /home/user/docker:/data) alongside Windows examples.
- When referencing file paths or drive letters, clarify platform differences and provide cross-platform examples.
- Balance the order of presentation so that Azure CLI/Bash and PowerShell/Windows instructions are given equal prominence, or group them clearly by platform.
- Explicitly mention platform compatibility and any differences in workflow for Linux/macOS users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/export-bicep-portal.md
...es/azure-resource-manager/bicep/export-bicep-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure PowerShell and Azure CLI as alternatives to the Azure portal for exporting ARM templates, but does not provide explicit Linux-specific examples or mention Bash/shell usage. Azure PowerShell is mentioned alongside Azure CLI, but there is no parity in showing Linux command-line workflows or emphasizing cross-platform tools. The absence of Linux-specific instructions or screenshots, and the order of mentioning PowerShell (a Windows-centric tool) before CLI or REST API, suggests a mild Windows bias.
Recommendations
- Add explicit examples using Azure CLI in Bash or shell environments to demonstrate Linux parity.
- When listing alternatives, mention Azure CLI and REST API before Azure PowerShell to avoid Windows-first ordering.
- Include screenshots or instructions that show the process on Linux systems, if applicable.
- Clarify that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Where PowerShell is referenced, note that PowerShell Core is also available cross-platform, or provide equivalent Bash commands.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md
.../main/articles/azure-resource-manager/bicep/install.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation shows moderate Windows bias. Visual Studio (Windows-only) is presented as a primary authoring tool alongside Visual Studio Code, and PowerShell/Windows installer/Windows package managers (Chocolatey, Winget) are described in greater detail and with more installation options than their Linux/macOS equivalents. Windows-specific tools and patterns (e.g., PowerShell scripts, registry edits, Windows environment variables) are used and described in depth, while Linux and macOS installation instructions are more concise and less varied. In several sections, Windows options are listed before Linux/macOS, and PowerShell is the only scripting language shown for manual installation on Windows.
Recommendations
- Present Linux and macOS installation options before or alongside Windows options in all lists and tables to avoid 'windows_first' ordering.
- Expand Linux and macOS installation sections to include more package manager options (e.g., apt, yum, snap for Linux), mirroring the variety offered for Windows (e.g., Chocolatey, Winget).
- Provide Bash or shell script equivalents for all PowerShell examples, especially for manual installation and PATH modification.
- Where possible, use cross-platform language and avoid Windows-specific terminology (e.g., use 'home directory' instead of '%UserProfile%').
- Highlight cross-platform editors and tools (e.g., Visual Studio Code) before Windows-only tools (e.g., Visual Studio).
- Ensure troubleshooting and advanced sections include Linux/macOS-specific guidance, not just Windows/PowerShell.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/installation-troubleshoot.md
...re-resource-manager/bicep/installation-troubleshoot.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools and patterns (e.g., 'where bicep', %USERPROFILE% paths, PATH variable instructions for Windows only), omitting Linux/macOS equivalents (such as 'which bicep', $HOME/.azure/bin), and not providing cross-platform guidance. There are no Linux or macOS-specific troubleshooting steps or examples.
Recommendations
- Include Linux/macOS equivalents for all command-line instructions (e.g., use 'which bicep' for Linux/macOS, and specify the typical Azure CLI Bicep path as $HOME/.azure/bin).
- Provide instructions for modifying the PATH environment variable on Linux/macOS (e.g., editing .bashrc, .zshrc, or .profile).
- Clearly label platform-specific steps and provide parallel instructions for each supported OS.
- Add screenshots or descriptions relevant to Linux/macOS environments where applicable.
- Review all sections to ensure Linux/macOS users are equally supported in troubleshooting scenarios.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/key-vault-parameter.md
...es/azure-resource-manager/bicep/key-vault-parameter.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all command-line operations, but PowerShell examples are consistently listed after Azure CLI. However, there is a notable reference to a Windows-specific scenario ('WinRM on a Windows VM') in the introduction, with no equivalent Linux example or mention. The documentation also references PowerShell and .NET in the 'More information' section before mentioning Node.js, and does not provide any Linux-specific guidance or examples, such as using Bash scripting or Linux-based deployment scenarios.
Recommendations
- Add Linux-focused examples or references, such as deploying to Linux VMs or using Linux-specific tools/scripts.
- Include a Linux VM quickstart template reference alongside the Windows VM example in the introduction.
- Ensure parity in the order of tool presentation (e.g., alternate between Azure CLI and PowerShell, or mention Bash scripting where relevant).
- Expand the 'More information' section to include examples using Bash, Python, or other common Linux tools.
- Explicitly state that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Where possible, provide screenshots or walkthroughs using a Linux shell environment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-no-loc-expr-outside-params.md
...anager/bicep/linter-rule-no-loc-expr-outside-params.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides deployment guidance and troubleshooting specifically for Azure PowerShell commands (e.g., New-AzDeployment), which are most commonly used on Windows. There are no examples or mentions of cross-platform tools such as Azure CLI, nor are there Linux-specific deployment patterns or considerations. The only deployment tool discussed is PowerShell, and it is mentioned before any Linux-equivalent tools (which are not mentioned at all).
Recommendations
- Add equivalent Azure CLI (az deployment ...) examples and guidance, which is cross-platform and widely used on Linux and macOS.
- Mention that Azure CLI does not have the same parameter name conflict as PowerShell, or document any differences.
- Where PowerShell-specific advice is given, provide parallel instructions for Bash/Azure CLI users.
- Consider reordering or balancing the documentation so that cross-platform tools are mentioned alongside or before Windows-specific tools.
- Explicitly state that the guidance applies to all platforms, and clarify any platform-specific differences.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate-blueprint.md
...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell-based export instructions and linking to a PowerShell-specific guide for exporting blueprint definitions. There is no mention of Linux or cross-platform tools (such as Azure CLI) for the export step, and no Linux-specific or cross-platform command examples are provided.
Recommendations
- Provide Azure CLI examples for exporting blueprint definitions, as Azure CLI is cross-platform and widely used on Linux.
- Update links and references to include both PowerShell and Azure CLI documentation, or clarify that the instructions apply to all platforms.
- Explicitly mention that migration steps can be performed on Linux, macOS, and Windows, and provide equivalent commands or guidance for non-Windows environments.
- Ensure that all code samples and instructions are platform-agnostic or have clear alternatives for Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate.md
.../main/articles/azure-resource-manager/bicep/migrate.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and workflows (such as Azure PowerShell and Visual Studio Code) are mentioned alongside or before cross-platform options, and there are no explicit Linux-specific examples or CLI instructions. Keyboard shortcuts are provided for Windows and macOS, but Linux is only mentioned as sharing the Windows shortcut. There is no mention of Linux-native editors or shell environments, and examples using Azure CLI are not prioritized over PowerShell.
Recommendations
- Provide explicit Linux examples and instructions, especially for command-line operations (e.g., show Azure CLI commands before PowerShell).
- Include Linux-native editor alternatives (such as Vim, Emacs, or JetBrains IDEs) or at least acknowledge their use.
- When referencing keyboard shortcuts, clarify Linux-specific variations if they exist, and avoid grouping Linux with Windows unless they are truly identical.
- Ensure that all tools and workflows mentioned (such as exporting resources or running deployments) include parity for Linux users, with clear instructions.
- Where possible, use Azure CLI as the primary example, as it is cross-platform, and mention PowerShell as an alternative.
- Add a section or callout highlighting any platform-specific limitations or differences, so Linux users are aware of potential issues.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/msbuild-bicep-file.md
...les/azure-resource-manager/bicep/msbuild-bicep-file.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a clear Windows bias. Windows/PowerShell commands and paths are used exclusively or appear first in nearly all examples, including project setup, directory navigation, and build instructions. Linux and macOS equivalents are rarely mentioned, and when present (e.g., in package references), they are not shown in code or command-line examples. The use of Windows-style paths (C:\, backslashes) and exclusive reliance on PowerShell for shell commands further reinforces the bias. There are no bash or Linux shell equivalents for common tasks such as directory creation, file deletion, or running MSBuild/dotnet commands.
Recommendations
- Provide parallel Linux/macOS examples for all command-line instructions, using bash syntax and POSIX-style paths (e.g., /home/user/msBuildDemo).
- Show how to run MSBuild and dotnet commands on Linux/macOS, including any differences in command names (e.g., 'msbuild' vs 'MSBuild.exe').
- Include Linux/macOS versions of project file snippets, especially for the <PackageReference> to Azure.Bicep.CommandLine.linux-x64 and path examples.
- When referencing environment variables or file paths, use cross-platform conventions or show both Windows and Linux/macOS variants.
- Add a tabbed or side-by-side format for all code and shell examples, allowing users to select their OS.
- For cleanup instructions, provide the equivalent bash command (e.g., 'rm -rf ~/msBuildDemo') alongside the PowerShell example.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/modules.md
.../main/articles/azure-resource-manager/bicep/modules.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation shows evidence of Windows bias primarily in the discussion of deployment tools and patterns. Azure PowerShell is mentioned before Azure CLI and the Azure portal when discussing deployment options for template specs. Additionally, PowerShell scripts are referenced as an example of artifacts that can be embedded in Bicep modules, with no mention of Bash or shell scripts. There are no explicit Linux or cross-platform command-line examples, and the only scripting language referenced is PowerShell.
Recommendations
- When listing deployment tools, mention Azure CLI before or alongside Azure PowerShell, and provide parity in examples.
- When referencing script artifacts, include Bash or shell scripts as examples alongside PowerShell scripts.
- Add explicit Azure CLI examples where deployment commands are discussed, especially for Linux users.
- Review the order of tool mentions to avoid always listing Windows tools first.
- Consider including a section or note about cross-platform compatibility and best practices for Linux/macOS users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-safe-dereference.md
...re-resource-manager/bicep/operator-safe-dereference.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where Azure PowerShell and Visual Studio Code (a tool often associated with Windows) are mentioned before or instead of Linux-native alternatives. There are no explicit Linux CLI examples, and the guidance to use Azure CLI is coupled with Azure PowerShell, with no Linux-specific instructions or parity. The Bicep code example itself is platform-neutral, but the surrounding guidance assumes a Windows-centric workflow.
Recommendations
- Provide explicit Linux and macOS instructions for deploying Bicep files, including terminal commands using Azure CLI.
- Mention and link to Linux-native editors (such as Vim, Emacs, or VS Code on Linux) for creating Bicep files.
- Ensure that Azure CLI (which is cross-platform) is given equal or higher prominence than Azure PowerShell in deployment instructions.
- Add a section or note clarifying that all examples and tools are available and supported on Linux, with links to relevant installation guides.
- Where possible, include screenshots or terminal output from Linux environments to demonstrate parity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-spread.md
...ticles/azure-resource-manager/bicep/operator-spread.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page references Azure CLI and Azure PowerShell together for running examples, but lists Azure PowerShell (a Windows-centric tool) before Azure CLI, which is cross-platform. The guidance for creating Bicep files only mentions Visual Studio Code, which is available on Linux but is often associated with Windows development. There are no explicit Linux shell or deployment examples, and no mention of Linux-native tools or workflows. No Linux-specific instructions or parity examples are provided.
Recommendations
- List Azure CLI before Azure PowerShell when suggesting deployment tools, as Azure CLI is more platform-neutral.
- Explicitly mention that all examples can be run on Linux, macOS, and Windows, and provide a Linux shell (bash) example for deploying Bicep files.
- Include instructions or links for using Bicep with Linux-native editors (e.g., Vim, Emacs) or command-line workflows.
- Clarify that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for non-Windows users.
- Ensure that all tool references and workflows are presented in a platform-neutral order and language.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/parameter-files.md
...ticles/azure-resource-manager/bicep/parameter-files.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing deployment examples and file path conventions primarily for Windows environments. Azure PowerShell is featured prominently, and all PowerShell examples use Windows-style paths (e.g., C:\MyTemplates\...). There are no Linux/macOS-specific examples, nor any mention of Bash, shell scripting, or Linux file paths. Visual Studio Code is referenced as the editor, but no cross-platform CLI or scripting guidance is provided for Linux users.
Recommendations
- Add Linux/macOS examples for Azure CLI and PowerShell, using POSIX-style file paths (e.g., /home/user/templates/storage.bicep).
- Include Bash or shell scripting examples alongside PowerShell, especially for deployment commands.
- Explicitly mention that Azure CLI and Bicep CLI are cross-platform, and provide installation and usage notes for Linux/macOS.
- Clarify that Visual Studio Code and Bicep extension are available on Linux/macOS, and provide relevant links.
- Where file paths are shown, provide both Windows and Linux/macOS variants, or use environment-agnostic placeholders.
- Add a note or section on deploying from Linux environments, including any differences or considerations.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/private-module-registry.md
...zure-resource-manager/bicep/private-module-registry.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation shows a moderate Windows bias. In command examples, Azure PowerShell (a Windows-centric tool) is consistently presented before Azure CLI, and PowerShell syntax is given equal or greater prominence than the cross-platform Azure CLI. There are no Bash or Linux shell examples, and the local cache path is described for Windows first, with Linux and Mac following. The documentation assumes use of Azure CLI or PowerShell for credentials, with no mention of Bash scripting or Linux-native workflows.
Recommendations
- Present Azure CLI examples before Azure PowerShell, as Azure CLI is cross-platform and more common for Linux users.
- Add Bash shell script examples where appropriate, especially for common tasks like publishing or restoring modules.
- When listing file paths, consider listing Linux or Mac paths first or presenting all platforms in parallel tables or lists.
- Explicitly mention that Azure CLI commands work on Linux, Mac, and Windows, and provide guidance for Linux-native workflows.
- Where possible, avoid Windows-centric terminology (e.g., %USERPROFILE%) without also providing the equivalent for Linux/Mac.
- Consider including a section or callout for Linux users, highlighting any differences or tips for using Bicep and Azure Container Registry on Linux.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md
...icep/quickstart-create-bicep-use-visual-studio-code.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation shows a moderate Windows bias. While it is focused on Visual Studio Code (which is cross-platform), it consistently presents Azure CLI and Azure PowerShell as the only deployment options, with PowerShell examples given equal prominence to CLI. There are no explicit Linux/macOS-specific instructions or terminal examples, and the workflow assumes familiarity with right-click context menus and UI patterns more common on Windows. The mention of Visual Studio (distinct from VS Code) also reinforces a Windows-centric perspective.
Recommendations
- Add explicit instructions or notes for Linux/macOS users, such as using the integrated terminal in VS Code or relevant keyboard shortcuts.
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users, listing CLI examples before PowerShell.
- Include screenshots or callouts showing the process on Linux/macOS (e.g., using the terminal instead of right-click context menus).
- Avoid mentioning Visual Studio (the Windows-only IDE) in the main flow; if referenced, clearly distinguish it from VS Code and link only as an alternative.
- Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path syntax) where relevant.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-loops.md
...icles/azure-resource-manager/bicep/quickstart-loops.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation consistently presents Windows-centric tools and workflows first or exclusively. Azure PowerShell is given equal prominence to Azure CLI, and Visual Studio Code is the only editor mentioned. There are no explicit Linux shell (bash) examples, and no mention of Linux-native editors or workflows. This may make Linux users feel like second-class citizens or require them to adapt Windows-oriented instructions.
Recommendations
- Present Azure CLI (which is cross-platform and often preferred on Linux/macOS) examples before PowerShell, or clarify that CLI is cross-platform while PowerShell is more common on Windows.
- Include bash/zsh shell variable syntax in CLI examples (e.g., export resourceGroupName=...) and clarify that CLI commands work on Linux/macOS terminals.
- Mention alternative editors such as Vim, Emacs, or JetBrains IDEs, or at least clarify that Visual Studio Code is available on Linux/macOS.
- Add a note or section on running Bicep deployments from Linux/macOS, including any prerequisites or differences.
- Where PowerShell is shown, explicitly state that it is primarily for Windows users, and link to Linux/macOS equivalents.
- Ensure that all instructions and scripts are tested and presented in a way that is friendly to Linux/macOS users, not just Windows.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-template-specs.md
...urce-manager/bicep/quickstart-create-template-specs.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, and by referencing Windows tools and patterns (such as PowerShell and backslash line continuations) before or instead of Linux equivalents. There are no explicit Linux/macOS shell examples, and the CLI examples use Windows paths and conventions, which may not work on Linux/macOS systems.
Recommendations
- Provide both Windows and Linux/macOS file path examples (e.g., C:\templates\main.bicep and ~/templates/main.bicep) in all CLI and PowerShell commands.
- When showing Azure CLI examples, use POSIX-style paths and line continuations (forward slashes and \ or \ for Windows, / for Linux/macOS).
- Explicitly mention that the examples work on both Windows and Linux/macOS, and highlight any differences (such as variable assignment syntax in Bash vs PowerShell).
- Add tabs or callouts for Bash (Linux/macOS) shell usage where appropriate, especially for Azure CLI commands.
- Avoid using only Windows-specific tools or patterns (such as PowerShell) as the primary or first example; alternate or present Bash/Linux examples first in some sections.
- Clarify in notes or prerequisites that Visual Studio Code and the Bicep extension are cross-platform, and provide installation links for Linux/macOS if available.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-deployment-stacks.md
...e-manager/bicep/quickstart-create-deployment-stacks.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell is featured prominently throughout, including in prerequisites and code tabs. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every example may signal a bias toward Windows users. Visual Studio Code is listed as the recommended editor, which is cross-platform, but there is no mention of Linux-specific shell environments or editors. The documentation does not provide explicit Linux shell examples (e.g., bash), nor does it mention Linux-specific installation steps or considerations. The ordering of examples sometimes places PowerShell before CLI, and PowerShell is referenced in the prerequisites before CLI.
Recommendations
- Add explicit bash/Linux shell examples where appropriate, especially for CLI commands.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any Linux-specific notes if needed (e.g., file path formats, environment setup).
- In the prerequisites, mention that Azure CLI and Visual Studio Code are cross-platform, and provide installation links for Linux and macOS as well as Windows.
- Consider providing examples using native Linux tools (e.g., nano, vim) for editing Bicep files, or at least mention their use.
- Ensure that CLI examples are presented first, as CLI is platform-neutral, and PowerShell is Windows-centric.
- Add a note that PowerShell Core is available on Linux and macOS, if PowerShell examples are retained.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/visual-studio-code.md
...les/azure-resource-manager/bicep/visual-studio-code.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Azure CLI and Azure PowerShell as the primary command-line tools for interacting with Bicep and Azure resources. In several places, PowerShell is mentioned alongside or before CLI, and examples are always given for both, but there is no mention of Bash, Linux-specific shells, or Linux-native tools. The use of Visual Studio Code (cross-platform) is appropriate, but the command-line examples and tool recommendations are Windows-centric, with no explicit Linux or macOS guidance or examples. The documentation does not provide parity for Linux users in terms of shell commands, package management, or troubleshooting.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Provide Bash or shell examples where command-line usage is shown, especially for common tasks (e.g., using az in Bash).
- When referencing PowerShell, clarify that PowerShell Core is available on Linux and macOS, or provide Bash equivalents.
- Include Linux/macOS-specific troubleshooting tips or installation notes, such as using apt, yum, or Homebrew for installing tools.
- Ensure that any references to file paths, keyboard shortcuts, or context menus clarify platform differences (e.g., Ctrl vs Cmd, path separators).
- Add a section or callout for Linux/macOS users to ensure parity in setup and usage.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-private-module-registry.md
...ce-manager/bicep/quickstart-private-module-registry.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation consistently provides examples using Azure CLI and Azure PowerShell, with no mention of native Linux shells (e.g., bash) or scripting environments. Visual Studio Code and Visual Studio are recommended as editors, with no mention of Linux-preferred alternatives. PowerShell examples are given equal prominence to Azure CLI, and Windows tools (Visual Studio, PowerShell) are referenced throughout, while Linux-specific workflows, editors, or shell commands are absent.
Recommendations
- Add explicit bash/zsh shell examples for all CLI commands, showing usage in a typical Linux environment (e.g., export environment variables, use $HOME paths).
- Mention and provide examples for using editors commonly preferred on Linux, such as Vim, Emacs, or alternatives to Visual Studio/Visual Studio Code.
- Clarify that Azure CLI is cross-platform and show command-line examples in a Linux terminal context (e.g., using single quotes, Linux-style paths).
- De-emphasize PowerShell as a primary tool by listing Azure CLI (which is cross-platform) first and PowerShell second, or in a separate section.
- Include a note or section on using the Bicep CLI directly from bash or other Linux shells, especially for users who do not use PowerShell.
- Ensure screenshots and instructions do not assume a Windows environment (e.g., file paths, UI elements).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/resource-dependencies.md
.../azure-resource-manager/bicep/resource-dependencies.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates bias towards Windows by exclusively mentioning Visual Studio Codeâa tool most commonly associated with Windowsâwhen discussing visualization of dependencies. No Linux-native editors or tools (such as Vim, Emacs, or command-line alternatives) are referenced. There are no examples or instructions for Linux users, nor is there mention of how to visualize dependencies outside of Visual Studio Code. The documentation implicitly assumes the reader is using Windows or Windows-centric tooling.
Recommendations
- Include instructions or references for visualizing Bicep dependencies using Linux-native editors or command-line tools.
- Mention cross-platform alternatives to Visual Studio Code, such as Vim, Emacs, or JetBrains IDEs, and clarify their support for Bicep visualization.
- Add a note about the availability of Visual Studio Code on Linux and macOS, or provide parity by listing equivalent steps for those platforms.
- Consider referencing CLI-based visualization tools (if available) for users who prefer terminal workflows, common on Linux.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-spec-convert.md
...re-resource-manager/templates/template-spec-convert.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only PowerShell-based automation for converting portal templates to template specs, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The only script provided is a PowerShell script, and there are no Linux/macOS-specific instructions or examples. This creates a bias toward Windows users and environments.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for Linux/macOS users.
- Explicitly state platform compatibility for the PowerShell script (e.g., if it works in PowerShell Core on Linux/macOS).
- Mention and link to cross-platform tools or scripts if available.
- Add a note or section for Linux/macOS users, clarifying how they can perform the migration (e.g., using Azure CLI, Cloud Shell, or PowerShell Core).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/template-specs.md
...rticles/azure-resource-manager/bicep/template-specs.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and in some cases provides PowerShell-only guidance (e.g., deploying with .bicepparam files is not supported in PowerShell). There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The focus on PowerShell and lack of explicit Linux/Bash examples or notes may make the documentation less accessible for Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) examples first to avoid Windows-first bias.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash/zsh shell command examples where relevant.
- Add notes or sections for Linux users, including any OS-specific considerations (e.g., file paths, environment variables, shell syntax).
- Where PowerShell is referenced, clarify its availability on Linux and macOS, or provide equivalent Bash scripting examples.
- Review and update any statements or features that are PowerShell-only to clarify cross-platform support and provide alternatives if available.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/create-custom-provider.md
...rce-manager/custom-providers/create-custom-provider.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but the PowerShell sections rely on ARMClient, a tool that is Windows-centric and not natively available on Linux. There are no examples using common Linux-native tools (such as curl or httpie) for REST operations, and no mention of how to perform the PowerShell steps on Linux or via cross-platform alternatives. This creates a bias towards Windows users in the PowerShell sections and omits Linux-native workflows for REST calls.
Recommendations
- Add Linux-native examples for REST operations, such as using curl or httpie, especially in sections where ARMClient is recommended.
- Clarify whether ARMClient can be used on Linux (e.g., via .NET Core or Mono), or suggest cross-platform alternatives.
- In the PowerShell sections, note that PowerShell 7 is cross-platform and provide instructions for installing and using it on Linux and macOS.
- Consider including Bash script examples for key operations, or at least mention how the Azure CLI commands can be run on Linux/macOS.
- Wherever a Windows-specific tool is recommended, provide a Linux equivalent or explicitly state the limitations.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/create-storage-customer-managed-key.md
...ed-applications/create-storage-customer-managed-key.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, referencing Visual Studio Code (a cross-platform but Windows-associated editor) as the primary tool, and omitting explicit Linux/macOS shell examples for key steps. The portal-based instructions are platform-neutral, but command-line guidance is Windows-centric, and there are no Bash or Linux-specific notes or troubleshooting tips.
Recommendations
- Present Azure CLI (which is cross-platform) instructions before or alongside PowerShell, especially for build and deployment steps.
- Explicitly mention that Visual Studio Code is available on Linux and macOS, or suggest alternative editors (e.g., Vim, nano) for Linux users.
- Add Bash/Linux shell command examples for all steps where PowerShell is shown, and clarify any OS-specific differences.
- Include troubleshooting notes or links relevant to Linux/macOS users (e.g., file permissions, path conventions).
- Ensure that all prerequisite tools (Azure CLI, Bicep, editors) have installation instructions or links for Linux/macOS as well as Windows.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md
...aged-applications/deploy-service-catalog-quickstart.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. In most sections, Azure PowerShell (which is Windows-centric) is presented before Azure CLI (which is cross-platform and more common on Linux). Instructions for opening terminals default to PowerShell and Visual Studio Code, and PowerShell-specific syntax (such as the backtick for line continuation and escaping) is explained in detail, while Bash/Linux equivalents are covered later. There is a strong focus on PowerShell commands and patterns, and no mention of native Linux shells or editors (e.g., Bash, nano, vim) outside of the Azure CLI context. The documentation does not provide Linux-specific troubleshooting or environment notes, and the overall structure and examples are slightly more tailored to Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI (Bash) first, as it is more cross-platform and widely used on Linux and macOS.
- Explicitly mention and provide examples for opening Bash terminals on Linux and macOS, not just in the context of Visual Studio Code or Git Bash.
- Include notes or tips for Linux users, such as common editors (nano, vim) or shell differences, especially when discussing environment setup.
- Balance the depth of explanation for PowerShell and Bash syntax (e.g., line continuation, escaping) to ensure Linux users receive equal guidance.
- Reference Linux-native tools or workflows where appropriate, and avoid assuming Visual Studio Code or PowerShell as the default environment.
- Consider adding a short section or callout for Linux/macOS users, highlighting any platform-specific considerations or troubleshooting steps.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/publish-bicep-definition.md
...nager/managed-applications/publish-bicep-definition.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples and terminology are presented before Azure CLI/Bash equivalents throughout the page, and PowerShell-specific features (such as splatting) are explained in detail. Instructions for opening terminals reference PowerShell and Visual Studio Code, which are more commonly used on Windows. There is little explicit mention of Linux environments, and no Linux-specific tooling or patterns (such as native shell scripting, package managers, or alternative editors) are discussed.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples so that neither is always presented first; consider leading with Azure CLI/Bash in some sections.
- Add explicit instructions for Linux users, such as using native terminals (e.g., GNOME Terminal, Konsole) and referencing common Linux shell environments.
- Include notes on installing required tools (Azure CLI, Bicep, VS Code) on Linux distributions, with links to Linux-specific installation guides.
- Mention alternative editors (e.g., Vim, nano) for users who may not use Visual Studio Code.
- Avoid PowerShell-specific terminology (like 'splatting') without providing equivalent Bash/Linux shell explanations.
- Clarify that all CLI commands are cross-platform and provide troubleshooting tips for Linux-specific issues (e.g., file permissions, case sensitivity).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/tutorial-create-managed-app-with-custom-provider.md
...ns/tutorial-create-managed-app-with-custom-provider.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is used exclusively for scripting storage uploads, with no Bash or Linux shell equivalents provided. Windows/PowerShell tooling is presented first and in detail, while Linux alternatives are omitted. The use of Windows-specific tools (PowerShell cmdlets like Connect-AzAccount, New-AzResourceGroup, etc.) is prominent, and there is no mention of cross-platform or Linux-compatible approaches for these steps. Azure CLI is used for deployment, but the initial artifact upload relies solely on PowerShell, which is not native to Linux environments.
Recommendations
- Provide Bash/Azure CLI examples for uploading the application package to Azure Storage, alongside or before PowerShell examples.
- Explicitly mention cross-platform compatibility and clarify which steps can be performed on Linux/macOS.
- Add notes or links to documentation for Linux users, including installation and usage of Azure CLI and azcopy.
- Where PowerShell is used, offer equivalent Bash or Azure CLI commands to ensure Linux parity.
- Review all scripting sections to ensure both Windows and Linux users are supported equally.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/azure-services-resource-providers.md
...anager/management/azure-services-resource-providers.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page demonstrates some Windows bias. It references Windows-specific tools (e.g., PowerShell) and APIs (e.g., Windows Azure Service Management API), and provides PowerShell examples alongside Azure CLI and Python. The mention of 'Azure Serial Console for Windows' and 'WindowsIoT' as services further reinforces the Windows-centric approach. In the 'Find resource provider' section, PowerShell is presented before Python, and the registration warning references Windows Azure Service Management API without mentioning Linux alternatives.
Recommendations
- Add explicit Linux/Bash examples alongside PowerShell, especially in 'Find resource provider' and other command-line sections.
- Reference cross-platform APIs or tools where possible, or clarify platform-specific limitations.
- When listing services or tools, avoid Windows-first ordering; present Linux and cross-platform options equally.
- In registration and security warnings, mention Linux/Unix equivalents or clarify that the advice applies to all platforms.
- For services like 'Azure Serial Console for Windows' and 'WindowsIoT', provide links or notes about Linux alternatives or clarify platform support.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/create-private-link-access-commands.md
...ager/management/create-private-link-access-commands.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples, but PowerShell is featured equally and sometimes before Linux-native tools. There are no explicit Linux shell (bash) or scripting examples, and PowerShell is a Windows-centric tool. References to PowerShell and its cmdlets may bias the documentation toward Windows users. REST API examples are platform-neutral, but there are no bash or Linux-specific scripting examples or notes. In the 'Add private endpoint' section, PowerShell is listed before CLI, and there is no mention of Linux-specific guidance.
Recommendations
- Add explicit bash/shell scripting examples for Linux users alongside PowerShell examples.
- Ensure that Azure CLI examples are always listed before PowerShell, as CLI is cross-platform.
- Include notes or sections highlighting any Linux-specific considerations or troubleshooting.
- Where PowerShell is referenced, clarify that Azure CLI is recommended for Linux/macOS users.
- Add links to Linux-specific documentation or tutorials where relevant.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/includes/tags.md
...les/azure-resource-manager/management/includes/tags.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI in every example demonstrates a 'powershell_heavy' and 'windows_tools' bias. Additionally, PowerShell is always presented immediately after Azure CLI, which can be interpreted as a 'windows_first' ordering, especially since no explicit Linux shell (such as Bash) or scripting examples are provided. There are no Linux-specific or cross-platform shell scripting examples, and the documentation does not mention or demonstrate usage from a Linux environment beyond the CLI, which is cross-platform.
Recommendations
- Add explicit Bash or shell scripting examples for Linux users, especially for scenarios where scripting is common.
- Clarify in the documentation that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Consider including examples using other cross-platform tools (e.g., REST API via curl, Python SDK) to provide parity for non-Windows users.
- If PowerShell is included, note that PowerShell Core is cross-platform, or provide both Windows PowerShell and Bash equivalents where possible.
- Reorder or randomize the presentation of CLI and PowerShell examples, or group them under a 'Command-line' section to avoid implicit prioritization.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resources-rest.md
...e-resource-manager/management/manage-resources-rest.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and making REST API calls. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some cases, PowerShell-specific patterns (such as Invoke-WebRequest) are used without mentioning Linux-native alternatives (e.g., curl or httpie in bash). Additionally, links to further deployment instructions reference Visual Studio Code and PowerShell, which are more commonly associated with Windows environments. There are no explicit Linux-only examples or mentions of Linux-native scripting environments beyond the use of curl.
Recommendations
- Provide bash and curl-only examples (without Azure CLI) for authentication and REST calls, to support Linux and macOS users who may not use PowerShell.
- When listing tabs for code examples, consider listing Azure CLI (bash) first, as it is cross-platform, and PowerShell second.
- Include references to Linux-native tools (e.g., httpie, wget) where appropriate.
- Add a section or callout explicitly stating that all REST API operations can be performed from Linux/macOS terminals using standard tools.
- When referencing further documentation, balance links to PowerShell and Visual Studio Code with links to Linux-friendly tools and editors.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/microsoft-resources-move-regions.md
...manager/management/microsoft-resources-move-regions.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by using Windows-style file paths (e.g., c:\export), referencing only Windows file system conventions, and omitting Linux/macOS equivalents. Both Azure PowerShell and Azure CLI examples use Windows paths, and there are no explicit Linux/macOS examples or notes about cross-platform usage. The documentation also links to deployment instructions that reference PowerShell, reinforcing a Windows-centric approach.
Recommendations
- Provide Linux/macOS examples using appropriate file paths (e.g., /home/user/export or ./export).
- Add notes clarifying that Azure CLI and PowerShell are cross-platform, and show how to run them on Linux/macOS.
- When giving file path parameters, show both Windows and Linux/macOS formats side by side.
- Link to deployment instructions that cover Bash or generic CLI usage, not just PowerShell.
- Explicitly mention any platform-specific considerations or differences in behavior.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/classic-model-move-limitations.md
...ent/move-limitations/classic-model-move-limitations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure PowerShell before Azure CLI when listing move operations, which suggests a Windows-first bias. There are no explicit Linux or cross-platform shell examples, and no mention of Bash or Linux-specific guidance. The examples and instructions focus on REST API calls and PowerShell, with no parity for Linux users.
Recommendations
- List Azure CLI before or alongside Azure PowerShell when mentioning supported tools.
- Provide explicit Bash/Azure CLI command examples for common operations, not just REST API or PowerShell.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes or sections addressing Linux/macOS users to ensure parity in guidance.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/cloud-services-extended-support.md
...nt/move-limitations/cloud-services-extended-support.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure PowerShell before Azure CLI and does not provide explicit Linux-specific examples or guidance. The mention of Azure PowerShell (commonly associated with Windows environments) before Azure CLI, and the lack of Linux or Bash-specific instructions, indicates a Windows-first bias. There are no Linux command-line examples or references to Linux tools.
Recommendations
- List Azure CLI before Azure PowerShell when presenting cross-platform options, or mention both together to avoid implying a preference.
- Provide explicit Linux/Bash examples for common operations, such as using Azure CLI commands in a Bash shell.
- Clarify that all operations can be performed from Linux, macOS, or Windows, and link to platform-specific instructions if available.
- Avoid implying that PowerShell is the default or primary method, especially for cross-platform documentation.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/request-limits-and-throttling.md
...ce-manager/management/request-limits-and-throttling.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided in detail, including both direct REST calls and Az module cmdlets, with additional debugging tips. These PowerShell examples appear before Azure CLI examples, and the only referenced scripting language outside of C# is PowerShell. There are no Bash/cURL or Linux-native scripting examples, and the PowerShell examples assume a Windows-centric workflow. The Azure CLI examples, while present, are less detailed and come after the PowerShell section.
Recommendations
- Add Bash/cURL examples for retrieving response headers, as these are common on Linux and macOS.
- Present Azure CLI examples before or alongside PowerShell examples to avoid the impression of Windows-first bias.
- Include examples using common Linux tools (e.g., grep, jq) to parse headers from REST API responses.
- Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- If referencing PowerShell, clarify that PowerShell Core is also available cross-platform, or provide examples using both Windows PowerShell and PowerShell Core.
- Ensure that all code snippets and debugging instructions are available for both Windows and Linux environments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/preview-features.md
.../azure-resource-manager/management/preview-features.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides examples for the Azure Portal, Azure CLI, and Azure PowerShell. However, it shows a bias towards Windows environments by including extensive Azure PowerShell examples (a Windows-centric tool) and referencing PowerShell cmdlets throughout. The PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being primarily used on Windows. There is no mention of Bash, shell scripting, or Linux-native tools, and no explicit Linux-specific guidance. The documentation also refers to the Azure Portal, which is cross-platform, but the command-line examples are limited to Azure CLI and PowerShell, with PowerShell being a Windows-first tool.
Recommendations
- Add explicit Bash or shell scripting examples for Linux users, especially for automation scenarios.
- Clarify that Azure CLI is cross-platform and highlight its use on Linux/macOS.
- De-emphasize PowerShell as a primary automation tool unless parity is provided for Linux users (e.g., PowerShell Core).
- Include a note or section about using Azure CLI in Bash on Linux, and provide sample commands with typical Linux shell usage (e.g., piping, jq for JSON parsing).
- If PowerShell is mentioned, clarify that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Consider adding REST API curl examples, which are universally available on Linux.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocate-evaluate.md
...azure-resource-manager/management/relocate-evaluate.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows/Azure bias by exclusively referencing Azure-specific tools and workflows, and by providing only PowerShell-based or Azure Portal instructions (e.g., for moving public IPs), without mentioning Linux CLI equivalents or cross-platform tools. There are no examples or guidance for Linux users, nor are Linux-native tools or scripts referenced. The documentation assumes the use of Azure and Windows-centric management patterns throughout.
Recommendations
- Include equivalent Azure CLI (az) commands alongside or instead of PowerShell/Portal instructions, as Azure CLI is cross-platform and widely used on Linux.
- When referencing automation or scripting, provide examples in both PowerShell and Bash (or Python), or explicitly mention that scripts can be written in any language supported by the user's environment.
- Reference cross-platform tools (such as Azure CLI, Terraform, or Ansible) for discovery and automation, not just Azure Portal or PowerShell.
- When linking to documentation (e.g., for moving public IPs), ensure that both PowerShell and CLI (az) instructions are included or linked.
- Explicitly state that all procedures can be performed from Linux, macOS, or Windows, and provide guidance for non-Windows users where appropriate.
- Consider including a section or callout for Linux-specific considerations, especially for teams that may not use Windows-based tooling.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-app-service.md
...anager/management/relocation/relocation-app-service.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), mentioning Kudu and FTP credentials (commonly used in Windows workflows), and providing links to PowerShell-based cloning guides as the only 'Next steps'. Examples and terminology (such as session affinity and Kudu) are presented with Windows conventions first or exclusively. There is a lack of explicit Linux or cross-platform command-line examples (e.g., Bash, Azure CLI), and Linux-specific considerations (such as file permissions, case sensitivity, or deployment patterns) are not addressed.
Recommendations
- Include Linux/Bash examples alongside or before PowerShell examples, especially for tasks like app cloning and backup/restore.
- Reference Azure CLI commands in addition to PowerShell for resource management and deployment steps.
- Clarify that Kudu and FTP credentials are available and relevant for both Windows and Linux App Service plans, or provide Linux-specific alternatives.
- Discuss Linux-specific considerations, such as file system case sensitivity, permissions, and deployment patterns (e.g., zip deploy, container-based workflows).
- Balance references to Windows paths (e.g., %HOME%\site) with Linux equivalents (e.g., $HOME/site), and explain any differences in environment variables or file system structure.
- Add links to Linux-focused documentation or guides in the 'Next steps' section.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-container-registry.md
...management/relocation/relocation-container-registry.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by frequently providing PowerShell examples (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Bash or Linux shell alternatives. Windows/PowerShell commands are often mentioned before or instead of cross-platform Azure CLI commands, and some steps reference Windows-centric tools (e.g., unzipping a .zip file without specifying platform-agnostic methods). Linux-specific instructions, such as Bash scripts or command-line patterns, are underrepresented or missing in several key workflow steps.
Recommendations
- Provide equivalent Bash or Linux shell examples for all PowerShell commands (e.g., show how to enumerate repositories/tags and import images using Azure CLI and Bash).
- List Azure CLI (cross-platform) commands before PowerShell commands when both are available, or present them side-by-side.
- Explicitly mention Linux/macOS methods for tasks like unzipping files, scripting, and file manipulation.
- Avoid using Windows-specific tools or terminology exclusively; ensure all tooling and instructions are platform-agnostic or have clear alternatives.
- Add notes or sections clarifying any platform-specific differences in workflow, especially for automation and scripting.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-firewall.md
...e-manager/management/relocation/relocation-firewall.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides step-by-step instructions for relocating Azure Firewall using the Azure Portal and PowerShell, but does not include examples or guidance for Linux users or cross-platform CLI tools. PowerShell is featured as the only command-line automation method, and references to creating firewall policies or migrating configurations are linked to PowerShell-specific guides. There are no Bash, Azure CLI, or Linux shell examples, nor is there mention of alternative tooling or scripting approaches for non-Windows environments.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all automation steps, including template export, modification, and deployment.
- Include Bash shell script samples for Linux users where applicable.
- Reference cross-platform documentation and tools, such as Azure CLI, before or alongside PowerShell.
- Ensure links to migration and policy creation guides include Azure CLI and REST API options, not just PowerShell.
- Explicitly state that all steps can be performed from Linux, macOS, or Windows, and provide platform-agnostic instructions where possible.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-functions.md
...-manager/management/relocation/relocation-functions.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific concepts (such as the %HOME% path variable) and mentioning Azure PowerShell alongside Azure CLI as deployment options, without providing parity for Linux-specific tools or examples. The examples and instructions do not include Linux shell equivalents, and Windows terminology appears before or instead of Linux alternatives. There is also a lack of explicit Linux-based deployment or scripting examples, and no mention of Linux-specific patterns or considerations beyond a brief note about mounting shares.
Recommendations
- Add Linux shell (bash) examples alongside or before PowerShell examples for deployment and scripting tasks.
- Replace or supplement Windows path variables (e.g., %HOME%) with Linux equivalents (e.g., $HOME) and clarify cross-platform differences.
- Explicitly mention Linux tools and workflows (such as Bash scripts, SSH, or Linux-based CI/CD pipelines) where relevant.
- Ensure that instructions and terminology are platform-neutral or provide both Windows and Linux variants.
- Highlight any Linux-specific considerations or best practices for Azure Functions, especially for file storage, authentication, and deployment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-private-link.md
...nager/management/relocation/relocation-private-link.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary automation option before Azure CLI, and does not provide explicit Linux-specific instructions or examples. There is no mention of Bash, Linux shell, or cross-platform scripting, and the examples and tool references (PowerShell, Azure portal) are more familiar to Windows users. Linux users may find the guidance less approachable due to the lack of parity in examples and tool recommendations.
Recommendations
- Provide explicit Linux/Bash examples alongside PowerShell, especially for command-line operations.
- List Azure CLI (which is cross-platform) before PowerShell when suggesting automation tools.
- Include references to Linux-native tools or shell environments where relevant.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample commands.
- Ensure that all steps and screenshots are platform-agnostic or provide alternatives for both Windows and Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-hub.md
...-manager/management/relocation/relocation-event-hub.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and referencing Windows-centric tools (Azure PowerShell, Get-AzLocation) without offering equivalent Linux or cross-platform CLI examples. The PowerShell tab is present, but there is no Azure CLI tab or bash/shell example for Linux users. Where command-line instructions are given, they are exclusively for PowerShell, and links to Azure CLI are only mentioned in passing, not demonstrated. This may hinder Linux users or those preferring cross-platform tools from following the guide effectively.
Recommendations
- Add an Azure CLI tab alongside the PowerShell and portal tabs in all relevant sections, with full CLI command examples for each step.
- Where region codes are obtained via PowerShell (Get-AzLocation), provide the equivalent Azure CLI command (az account list-locations) and example output.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide instructions for downloading and using the CLI.
- Ensure screenshots and instructions are not exclusively portal/Windows-centric; include CLI output and Linux terminal screenshots where appropriate.
- Review all references to automation and scripting to ensure parity between PowerShell and CLI/bash approaches.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-key-vault.md
...-manager/management/relocation/relocation-key-vault.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell-based instructions for all command-line operations, with no equivalent Azure CLI (cross-platform) or Bash examples. PowerShell is featured as the only scripting option, and all automation steps outside the portal are shown using PowerShell cmdlets, which are primarily used on Windows. There are no Linux/macOS-specific instructions or CLI examples, and PowerShell is presented before any mention of Azure CLI. The only mention of Azure CLI is in a passing reference for configuring service endpoints, with no actual CLI commands or walkthroughs provided.
Recommendations
- Add Azure CLI examples (az commands) for all PowerShell-based steps, including exporting and deploying templates, and managing resources.
- Present Azure CLI and PowerShell examples side-by-side or in tabs, ensuring parity for Linux/macOS users.
- Explicitly mention that PowerShell can be used cross-platform, but highlight Azure CLI as the recommended tool for Linux/macOS.
- Include Bash shell script examples where automation is discussed, or reference Bash scripting for Linux users.
- Ensure that references to tools and commands are not Windows-centric; provide equal visibility to cross-platform tools.
- Review and update the documentation to avoid assuming the reader is using Windows or PowerShell by default.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-storage-account.md
...er/management/relocation/relocation-storage-account.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. All CLI examples are provided exclusively using Azure PowerShell, with no mention of Azure CLI (cross-platform) or Bash/Shell scripting alternatives. The PowerShell instructions are presented as the only command-line option, and there are no Linux-specific or cross-platform examples for exporting, modifying, or deploying templates. This may disadvantage users on Linux or macOS, who typically use Azure CLI or Bash.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, including exporting, modifying, and deploying Resource Manager templates.
- Include Bash/Shell script snippets where appropriate, especially for tasks like file manipulation and automation.
- Explicitly mention that AzCopy and Azure CLI are cross-platform tools, and provide usage instructions for Linux/macOS environments.
- Reorder or parallelize examples so that PowerShell and CLI/Bash instructions are presented side-by-side or in tabs, rather than PowerShell-only.
- Reference installation and usage guides for Azure CLI on Linux/macOS, and clarify that all steps can be performed on non-Windows platforms.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-virtual-network-nsg.md
...anagement/relocation/relocation-virtual-network-nsg.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides detailed instructions for relocating an Azure NSG using the Azure Portal and PowerShell, with all CLI examples and automation steps relying exclusively on PowerShell cmdlets. There are no examples or guidance for Linux users, such as using Azure CLI (az), Bash, or cross-platform editors. Windows tools like Notepad are referenced, and the PowerShell approach is presented as the sole scripting method, which may disadvantage users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell steps, including authentication, resource export, template editing, deployment, and cleanup.
- Reference cross-platform text editors (e.g., VS Code, nano, vim) instead of or alongside Notepad.
- Explicitly mention that both PowerShell and Azure CLI are supported, and provide tabs for each where applicable.
- Ensure that instructions for obtaining region codes and other metadata include Azure CLI commands.
- Review and update prerequisites and process steps to avoid assuming a Windows environment or toolset.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/resource-providers-and-types.md
...rce-manager/management/resource-providers-and-types.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page exhibits mild Windows bias. The Azure portal is referenced as the primary GUI, and the PowerShell section appears before Azure CLI and Python. The portal is a web application but historically associated with Windows environments. The documentation mentions the 'Windows Azure Service Management API' and does not reference Linux-specific tools or shell environments (e.g., Bash, zsh). There are no examples using Bash scripts, REST calls via curl, or Linux-native automation tools. PowerShell is given prominence, and there is no mention of cross-platform PowerShell Core or its usage on Linux/macOS. The CLI examples are present and parity is generally maintained, but the ordering and terminology favor Windows.
Recommendations
- Add explicit Bash or shell script examples using curl for REST API operations.
- Clarify that Azure PowerShell and Azure CLI are cross-platform, and provide installation/usage notes for Linux/macOS.
- Mention and provide examples for PowerShell Core on Linux/macOS, not just Windows PowerShell.
- Reorder sections so that Azure CLI (which is more popular on Linux/macOS) appears before PowerShell.
- Avoid references to 'Windows Azure Service Management API' unless necessary, or clarify its relevance to all platforms.
- Include notes or links for Linux users about authentication and environment setup (e.g., using environment variables, az login, etc.).
- Where screenshots are shown, clarify that the Azure portal is web-based and accessible from any OS.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-mission-critical-workload.md
...ce-manager/management/tag-mission-critical-workload.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits mild Windows bias by listing Azure PowerShell (a Windows-centric tool) before Azure CLI and other cross-platform automation tools in the 'How to apply Azure tags' section. PowerShell is mentioned explicitly, and no Linux-specific shell examples (e.g., Bash) or platform notes are provided. The ordering and emphasis may suggest a preference for Windows/PowerShell environments.
Recommendations
- List Azure CLI before Azure PowerShell, as CLI is cross-platform and widely used on Linux.
- Provide explicit Bash/Linux shell examples for tag application, or clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Add notes or examples for Linux users, such as using Bash scripts or integrating with Linux automation tools.
- Ensure parity in guidance for both Windows and Linux environments, possibly including screenshots or step-by-step instructions for each platform.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-cli.md
...rticles/azure-resource-manager/templates/deploy-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. While the main examples use Azure CLI (which is cross-platform), there are several instances 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 alternatives are not always provided or are described second. There is little explicit mention of Linux tools or patterns, and some examples (such as variable assignment and array formatting) are Windows-centric.
Recommendations
- Ensure all shell-specific instructions are provided for both Windows (CMD/PowerShell) and Linux (Bash) users, with equal prominence.
- When describing parameter formatting or variable assignment, give Bash/Linux examples first or side-by-side with Windows examples.
- Explicitly mention that Azure CLI is cross-platform and provide links or notes about using it on Linux/macOS.
- Include troubleshooting or usage notes relevant to Linux environments (e.g., file permissions, path formats).
- Add more examples that use Linux/Bash syntax, especially for variable assignment, parameter passing, and scripting.
- Avoid assuming Windows as the default environment; clarify instructions for both platforms where differences exist.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tls-support.md
...icles/azure-resource-manager/management/tls-support.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Windows versions and tools first, focusing on .NET Framework and Visual Studio (Windows-only technologies), and providing guidance and troubleshooting links that are specific to PowerShell and WinHTTP (Windows components). There are no examples or recommendations for Linux environments, nor are Linux tools or patterns mentioned.
Recommendations
- Add explicit guidance for Linux users, such as how to check and enforce TLS 1.2 usage on common Linux distributions.
- Include examples using Linux command-line tools (e.g., OpenSSL, curl, wget) to verify TLS versions.
- Mention Linux equivalents to Windows tools like Fiddler (e.g., Wireshark, tcpdump) for inspecting TLS connections.
- Provide instructions for configuring TLS settings in popular Linux frameworks and runtimes (e.g., Python, Java, Node.js) on Linux.
- Balance references to .NET/Visual Studio with examples for cross-platform frameworks and editors (e.g., VS Code, JetBrains IDEs).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-properties.md
...es/azure-resource-manager/templates/copy-properties.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific resources (e.g., a VM deployment template for Windows), mentioning Azure PowerShell before Azure CLI, and omitting explicit Linux-focused examples or links. The only example template provided is for deploying a Windows VM, and the 'Next steps' section directs users to PowerShell deployment instructions without equal emphasis on CLI or Linux-native tools.
Recommendations
- Include example templates for Linux VM deployments (e.g., link to a 'vm-linux-copy-datadisks' template alongside the Windows one).
- When referencing deployment tools, mention Azure CLI before or alongside Azure PowerShell, and provide links to both deployment guides.
- Add explicit statements or examples for deploying ARM templates from Linux/macOS environments, including Bash/CLI commands.
- Ensure parity in 'Next steps' by linking to both PowerShell and CLI deployment documentation.
- Review and balance the order of tool mentions to avoid implying Windows is the default or preferred platform.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-variables.md
...les/azure-resource-manager/templates/copy-variables.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. In the 'Copy limits' section, Azure PowerShell is listed before Azure CLI, and the 'Next steps' section links only to a PowerShell deployment guide, omitting Linux-specific or cross-platform deployment instructions. There are no explicit Linux or Bash examples, and no mention of Linux-specific tools or workflows for ARM template deployment.
Recommendations
- Add explicit Bash or shell examples for deploying ARM templates, alongside PowerShell examples.
- In sections listing supported tools (e.g., 'Copy limits'), mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Include links to documentation for deploying ARM templates using Azure CLI and REST API, not just PowerShell.
- Clarify that both Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users.
- Where possible, provide parity in example scripts and command-line instructions for both Windows and Linux environments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/create-visual-studio-deployment-project.md
...r/templates/create-visual-studio-deployment-project.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation is heavily biased toward Windows users by exclusively using Visual Studio (a Windows-centric IDE) and PowerShell scripts for deployment. All examples and workflows assume the use of Visual Studio and PowerShell, with no mention of Linux, macOS, or cross-platform alternatives. There are no CLI, Bash, or VS Code examples, nor any guidance for non-Windows environments. The only deployment scripts referenced are PowerShell-based, and all project creation and management steps are Visual Studio GUI-centric.
Recommendations
- Add equivalent instructions for creating and deploying resource group projects using cross-platform tools such as Visual Studio Code, Azure CLI, and ARM/Bicep templates.
- Provide Bash or Azure CLI script examples for deployment, in addition to or instead of PowerShell scripts.
- Mention and link to cross-platform alternatives for users on Linux or macOS, such as using VS Code with Azure extensions.
- Clearly state the Windows-specific nature of the Visual Studio workflow at the top, and guide non-Windows users to alternative documentation.
- Include a section or callout for Linux/macOS users, outlining supported workflows and tools.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/data-types.md
...rticles/azure-resource-manager/templates/data-types.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation references PowerShell specifically when discussing integer parameter limits, without mentioning Linux equivalents such as Azure CLI. No Linux-specific tools or examples are provided, and the only command-line tool mentioned is PowerShell, which is Windows-centric.
Recommendations
- When discussing SDK or command-line tool limitations, mention both PowerShell and Azure CLI, and provide information about their respective behaviors on Windows, Linux, and macOS.
- Include examples or notes for Linux users, such as how to deploy ARM templates using Azure CLI.
- Avoid referencing only Windows tools unless there is a clear technical reason; provide parity in tool references and examples.
- Consider a table or section comparing behaviors across PowerShell, Azure CLI, and other SDKs to ensure cross-platform clarity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-to-resource-group.md
...resource-manager/templates/deploy-to-resource-group.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, but PowerShell examples are consistently shown before CLI examples in multi-step deployment sections. PowerShell is a Windows-centric tool, and its prominence may suggest a Windows-first bias. There is no mention of Linux-specific shells or scripting environments (e.g., Bash), nor are there explicit Linux command-line examples or notes about cross-platform usage. The documentation does not reference Linux tools or patterns, and the use of PowerShell as a primary example can be seen as a bias toward Windows users.
Recommendations
- Present Azure CLI (which is cross-platform) examples before PowerShell examples to avoid suggesting a Windows-first workflow.
- Explicitly mention that Azure CLI commands work in Bash, Cloud Shell, and other Linux environments.
- Add Bash-specific notes or examples where appropriate, especially for scripting or automation scenarios.
- Clarify that PowerShell Core is cross-platform if referencing PowerShell, or provide links to instructions for using PowerShell on Linux/macOS.
- Ensure parity in troubleshooting and tool references for both Windows and Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-to-subscription.md
...e-resource-manager/templates/deploy-to-subscription.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment commands, but PowerShell is consistently presented as the second option after Azure CLI. There are no explicit Linux shell (bash) examples, nor are there any references to Linux-specific tools or scripting environments. The use of PowerShell (which is traditionally associated with Windows, though now cross-platform) is prominent, and there is no mention of Linux-native scripting or automation approaches. The documentation does not clarify that Azure CLI commands are cross-platform, nor does it provide bash-specific guidance or troubleshooting.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
- Add bash-specific examples or notes, especially for parameter passing and environment variable usage, to address common Linux shell scenarios.
- Include troubleshooting tips or links for common issues encountered on Linux (e.g., line endings, quoting differences).
- Consider providing examples using native Linux tools (e.g., curl for REST API calls) where relevant.
- Reorder sections or alternate the order of CLI and PowerShell examples to avoid implicit prioritization of Windows tools.
- Clarify that PowerShell Core is available on Linux and macOS, if PowerShell examples are retained.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-what-if.md
...les/azure-resource-manager/templates/deploy-what-if.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and terminology are presented first and in greater detail than Azure CLI equivalents. Output samples and explanations use PowerShell syntax and conventions, and the installation instructions for Azure PowerShell are more prominent than those for Azure CLI. The use of PowerShell-specific tools and patterns (e.g., `$results = ...`, `foreach ($change in $results.Changes)`) is emphasized, while Linux-specific considerations (such as shell differences, color handling, or alternative scripting) are not addressed.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples so that CLI is presented first in some sections.
- Provide equivalent output samples using Azure CLI syntax, especially for text output and programmatic inspection.
- Include notes on running Azure CLI commands in Linux/macOS environments, such as shell differences and color handling.
- Add Bash or shell scripting examples for programmatic evaluation of what-if results (e.g., using jq to parse JSON output).
- Clarify that both PowerShell and CLI are cross-platform, and explicitly mention Linux/macOS compatibility.
- Ensure installation instructions for Azure CLI are as detailed and prominent as those for PowerShell.
- Avoid using only PowerShell conventions (e.g., `$variable`, `foreach`) in output and code samples; provide CLI/Bash alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-modes.md
...s/azure-resource-manager/templates/deployment-modes.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by presenting the PowerShell example before the Azure CLI example in the 'Set deployment mode' section. PowerShell is a Windows-centric tool, and its precedence over Azure CLI (which is cross-platform and more commonly used on Linux/macOS) suggests a Windows-first approach. Additionally, there are no explicit Linux shell (e.g., Bash) or platform-agnostic deployment examples, nor is there mention of Linux-specific considerations or tools. The documentation also references file paths in a Windows format (e.g., c:\MyTemplates\storage.json) in the PowerShell example, further reinforcing the Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell script examples or at least clarify that Azure CLI commands work on Linux/macOS terminals.
- Use platform-neutral file paths in examples (e.g., ./MyTemplates/storage.json) or provide both Windows and Linux path formats.
- Explicitly mention that both Azure CLI and PowerShell are supported on all major platforms, and link to guidance for Linux/macOS users.
- Consider adding a short section or note for Linux/macOS users to ensure parity and inclusivity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/resource-extensions.md
...zure-resource-manager/templates/resource-extensions.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page references Windows resources and links before Linux equivalents (e.g., 'features for Windows' is mentioned first), and does not provide Linux-specific examples or highlight Linux tools. The tutorials and extension references do not clarify Linux support or provide parity in examples.
Recommendations
- List Linux and Windows resources in parallel or alternate order to avoid Windows-first bias.
- Explicitly mention and link to Linux extension documentation wherever Windows extensions are referenced.
- Provide Linux-specific examples or tutorials alongside Windows ones, especially for common post-deployment scenarios.
- Clarify in each extension or tutorial whether it applies to Windows, Linux, or both.
- Include references to Linux tools and patterns (e.g., shell scripts, cloud-init) where relevant.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-tutorial-linked-template.md
...nager/templates/deployment-tutorial-linked-template.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page demonstrates a bias toward Windows environments by providing PowerShell scripts as the primary method for template storage and deployment, with Azure CLI examples presented only after PowerShell. The instructions for storing templates in Azure Storage use only PowerShell, and the 'Try-it' Cloud Shell guidance is tailored to PowerShell users. There is also a reliance on Windows-centric tools and patterns, with minimal Linux-specific guidance except for a brief note about the 'date' command in macOS.
Recommendations
- Provide equivalent Azure CLI and/or Bash scripts for all steps, especially for storing templates in Azure Storage, not just for deployment.
- Present Azure CLI and Bash examples alongside PowerShell, or allow users to select their preferred environment at the start of each section.
- Include Linux/macOS-specific notes and troubleshooting tips where command syntax or behavior differs, not just for the 'date' command.
- Avoid language such as 'right-click to paste' which is Windows-centric; instead, use platform-neutral instructions.
- Ensure that all 'Try-it' and Cloud Shell instructions clarify how to switch between Bash and PowerShell environments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/key-vault-parameter.md
...zure-resource-manager/templates/key-vault-parameter.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation consistently presents both Azure CLI and PowerShell examples for all operations, but PowerShell (a Windows-centric tool) is given equal prominence and is referenced throughout. The introductory sections and links reference Windows scenarios (e.g., VM certificate install for Windows), and there is no mention of Linux-specific tools or shell patterns (such as Bash, zsh, or Linux-native scripting). References to PowerShell and Windows-centric deployment patterns are present, while Linux or cross-platform alternatives are not highlighted or explained.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
- Add Bash/zsh script examples for Linux users, especially for parameter file manipulation and deployment.
- Include references or links to Linux-specific documentation or quickstarts (e.g., deploying to Linux VMs, using Linux-native tools).
- Clarify that PowerShell Core is available on Linux/macOS, or recommend Azure CLI as the default for non-Windows environments.
- Add notes or sections that address Linux deployment scenarios, such as using SSH keys or Linux VM configuration with Key Vault secrets.
- Ensure that example links and quickstarts are not Windows-specific unless necessary, or provide Linux equivalents.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/overview.md
.../articles/azure-resource-manager/templates/overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias. While it mentions both PowerShell and Bash for deployment scripts, the only concrete tooling example for testing (arm-ttk) is a PowerShell script, and the authoring tools highlighted are Visual Studio and Visual Studio Code, both of which are more Windows-centric (though VS Code is cross-platform). In the CI/CD section, Azure DevOps and Visual Studio project pipelines are emphasized, which are often associated with Windows workflows. PowerShell is mentioned before Bash, and there are no explicit Linux-specific examples or tool recommendations. The deployment options list Azure CLI and PowerShell, but PowerShell is mentioned before Bash in the extensibility section.
Recommendations
- Provide explicit Linux/bash examples or references alongside PowerShell, especially for testing and scripting (e.g., mention Bash-based test kits or how to use arm-ttk in Linux environments).
- Highlight cross-platform or Linux-native authoring tools (such as vim, nano, or JetBrains IDEs) or clarify that Visual Studio Code is cross-platform.
- In the CI/CD section, mention other popular CI/CD systems (such as GitHub Actions, Jenkins, or GitLab CI) with Linux runners, and provide links to relevant guides.
- When listing deployment options, alternate the order or explicitly state that both Azure CLI and PowerShell are cross-platform, and provide example commands for both.
- Where PowerShell is mentioned, ensure Bash is given equal prominence and provide sample Bash scripts or references.
- If possible, include screenshots or walkthroughs from Linux environments (e.g., Azure Cloud Shell in Bash mode).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/parameter-files.md
...es/azure-resource-manager/templates/parameter-files.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page provides deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool. The PowerShell example appears after the CLI example, but there is no explicit Linux shell example (e.g., Bash), nor is there mention of Linux file path conventions. The Visual Studio tip is also Windows-specific. There is no mention of Linux editors or deployment patterns.
Recommendations
- Add explicit Bash/Linux shell examples for deploying with parameter files, using Linux-style file paths (e.g., /home/user/storage.parameters.json).
- Clarify that Azure CLI works cross-platform and provide Linux/macOS file path examples alongside Windows ones.
- Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio for parameter file management.
- Where PowerShell is referenced, note that PowerShell Core is available on Linux/macOS, and provide examples with Linux file paths.
- Avoid Windows-centric file paths in generic examples, or provide both Windows and Linux/macOS variants.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs-deploy-linked-template.md
...ger/templates/template-specs-deploy-linked-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits several signs of Windows bias. File paths are given in Windows format (e.g., c:\Templates\deployTS\azuredeploy.json) without mention of Linux alternatives. PowerShell examples and instructions are presented before Azure CLI, and troubleshooting notes specifically reference Windows PowerShell issues. There are no explicit Linux shell examples, nor are Linux file path conventions or considerations discussed.
Recommendations
- Provide Linux/macOS file path examples alongside Windows paths (e.g., /home/user/Templates/deployTS/azuredeploy.json).
- Alternate the order of PowerShell and CLI examples, or present them side-by-side to avoid implicit prioritization.
- Include troubleshooting notes relevant to Linux/macOS environments, not just Windows PowerShell.
- Explicitly state that both Windows and Linux are supported, and mention any platform-specific considerations.
- Add Bash shell examples for variable assignment and command usage where appropriate.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-template-specs.md
...-manager/templates/quickstart-create-template-specs.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page exhibits several Windows-centric biases. File paths in all examples use Windows-style (C:\Templates\...), with no mention of Linux or macOS equivalents. PowerShell is presented as a primary tool alongside Azure CLI, and references to Azure PowerShell are frequent, including in prerequisites and role assignment tutorials. There are no Linux shell (bash) or macOS-specific instructions, nor are Linux file paths or environment differences addressed. Known issues are only called out for Windows PowerShell, and the documentation assumes a Windows environment throughout.
Recommendations
- Provide Linux/macOS file path examples (e.g., /home/user/Templates/createStorageV1.json) alongside Windows paths.
- Explicitly mention that Azure CLI commands work on Linux/macOS and show sample commands using bash syntax where appropriate.
- Include notes or tabs for Linux/macOS environments, especially for file operations and environment setup.
- Reference role assignment tutorials using Azure CLI or bash, not only PowerShell.
- Call out any cross-platform differences or issues, not just Windows-specific ones.
- Ensure screenshots and instructions in the portal are not Windows-specific (e.g., avoid showing Windows file dialogs only).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md
...emplates/quickstart-create-templates-use-the-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by recommending Visual Studio Code and Visual Studio (both Windows-centric tools) for ARM template development, and by mentioning Azure PowerShell and Azure CLI for deployment, with PowerShell listed first. There are no explicit Linux examples or mentions of Linux-specific tools or workflows. The guidance assumes a Windows environment and does not address Linux users' needs or alternative editors and shells.
Recommendations
- List Azure CLI before Azure PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Visual Studio Code is available on Linux and macOS, and suggest alternative editors (e.g., Vim, Emacs, nano) for Linux users.
- Include a note or section on how to deploy ARM templates using the Azure CLI from a Linux terminal.
- Avoid recommending Visual Studio (which is Windows-only) as the primary editor; instead, focus on cross-platform tools.
- Add Linux-specific instructions or screenshots where relevant, or clarify that the portal experience is identical across platforms.
- Ensure parity in tool recommendations by including Bash and Linux shell examples where command-line deployment is discussed.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/secure-template-with-sas-token.md
...ce-manager/templates/secure-template-with-sas-token.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all steps, but the PowerShell examples use Windows-style paths (e.g., c:\Templates\azuredeploy.json) and are presented before the Azure CLI/Bash examples in each section. There are no explicit Linux/macOS-specific notes or examples, and the CLI section only briefly mentions Bash in Cloud Shell, without addressing local Linux environments or common Linux file paths. This structure subtly prioritizes Windows/PowerShell users and may cause confusion for Linux users.
Recommendations
- Alternate the order of PowerShell and CLI examples or present them side-by-side to avoid consistently prioritizing Windows/PowerShell.
- In CLI examples, provide explicit Linux/macOS shell commands and file path examples (e.g., /home/user/Templates/azuredeploy.json) to improve clarity for Linux users.
- Add notes or callouts for Linux/macOS users regarding any differences in command syntax, environment variables, or file paths.
- Consider including a table summarizing command differences or prerequisites for Windows, Linux, and macOS environments.
- Ensure that all references to file paths and shell commands are platform-agnostic or provide platform-specific alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-expressions.md
...ure-resource-manager/templates/template-expressions.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell (Windows-centric) command-line examples for deploying ARM templates. There are no examples using cross-platform tools like Azure CLI or bash scripts, and the resource deployment examples use 'AzurePowerShell' as the script kind. Linux or cross-platform equivalents are not mentioned or shown, and PowerShell is referenced before any other tool.
Recommendations
- Add equivalent Azure CLI (az) command-line examples for deploying templates and passing parameters, alongside or before PowerShell examples.
- Include examples using 'AzureCLI' as the deployment script kind in ARM templates, not just 'AzurePowerShell'.
- Explicitly mention that ARM templates and their deployment can be managed from Linux, macOS, and Windows, and provide bash or shell script examples where appropriate.
- Reorder examples or provide parallel examples so that Linux/cross-platform tools are not always secondary to Windows/PowerShell.
- Clarify when a tool or pattern is Windows-specific, and offer alternatives for other platforms.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs-create-linked.md
...urce-manager/templates/template-specs-create-linked.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows file paths (e.g., c:\Templates\...), presenting PowerShell examples and terminology before Azure CLI, and omitting explicit Linux/macOS file path examples. The instructions and examples assume a Windows environment, with no mention of Linux-specific considerations or shell usage.
Recommendations
- Provide Linux/macOS file path examples (e.g., /home/user/Templates/linkedTS/azuredeploy.json) alongside Windows paths.
- Explicitly mention that the instructions apply to all platforms, and clarify any OS-specific differences.
- Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
- Include notes or tabs for Bash or other common Linux shells where variables or commands differ.
- Avoid using Windows-specific terminology (e.g., 'local computer' with Windows paths) without also referencing Linux/macOS equivalents.
- Add troubleshooting notes for Linux/macOS if there are known issues, not just for Windows PowerShell.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-specs.md
...les/azure-resource-manager/templates/template-specs.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently presents Azure PowerShell and Azure CLI examples side-by-side, but PowerShell is always listed first and referenced as a primary tool. There are no explicit Linux-specific instructions, nor are there examples using Bash, native Linux shell scripting, or Linux-specific tooling. The documentation assumes familiarity with PowerShell patterns (e.g., variable assignment, parameter passing) and does not mention platform differences, such as file paths or shell environments. No examples are given for deploying template specs using Bash scripts, nor is there guidance for Linux users regarding prerequisites or environment setup.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI (which is cross-platform) first to avoid implicit Windows prioritization.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash script examples for common workflows.
- Add a section on environment setup for Linux users, including installation instructions for Azure CLI and notes on file path conventions.
- Where PowerShell syntax is shown, provide equivalent Bash or shell scripting examples for variable assignment and command chaining.
- Clarify that PowerShell examples are primarily for Windows users, and encourage Linux users to use Azure CLI.
- Include troubleshooting tips or notes for Linux-specific issues (e.g., file permissions, shell quoting).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-functions.md
...e-manager/templates/template-tutorial-add-functions.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation shows a mild Windows bias. In the prerequisites, 'Azure PowerShell' is mentioned before Azure CLI, and PowerShell is listed as an option alongside Azure CLI, which is more cross-platform. In the deployment section, PowerShell instructions are presented before Azure CLI, and the example uses PowerShell-specific syntax. There are no explicit Linux shell (bash) examples, and the verification and cleanup steps rely on the Azure Portal UI, which is platform-agnostic but does not provide CLI alternatives.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide installation links for both.
- Add bash shell examples for running Azure CLI commands, showing both Windows (cmd/PowerShell) and Linux/macOS (bash) syntax for environment variables and command usage.
- Where possible, provide CLI commands for verification and cleanup steps, not just portal instructions.
- Avoid implying that Visual Studio Code is required; mention it as a recommended editor but also suggest alternatives available on Linux.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-parameters.md
...-manager/templates/template-tutorial-add-parameters.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI examples, and provides no explicit Linux/macOS shell (e.g., Bash) instructions or screenshots. While Azure CLI is cross-platform, there are no Linux-specific notes, nor are there any examples using native Linux tools or terminal environments. The clean-up section only describes using the Azure Portal (web UI), not command-line options, and the prerequisites mention Visual Studio Code but do not mention Linux editors or shells.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI examples, or present Azure CLI (the more cross-platform tool) first.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh).
- Add Linux/macOS-specific notes or screenshots where relevant (e.g., for file paths or shell variables).
- In the prerequisites, mention popular Linux editors (e.g., vim, nano) and shells as alternatives to Visual Studio Code.
- For resource clean-up, provide Azure CLI commands to delete the resource group, in addition to the Azure Portal instructions.
- Where variables are used (e.g., $templateFile), clarify shell syntax differences between PowerShell and Bash.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-resource.md
...ce-manager/templates/template-tutorial-add-resource.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation presents Azure PowerShell instructions before Azure CLI, which can be perceived as a Windows-first bias. While Azure CLI is cross-platform and included, there are no explicit Linux/macOS-specific instructions or terminal usage examples. The verification and cleanup steps rely solely on the Azure Portal GUI, which is platform-agnostic but omits command-line alternatives that Linux users may prefer. No Linux-specific tools or shell examples (e.g., Bash scripting, use of environment variables in Bash) are provided.
Recommendations
- Present Azure CLI instructions before PowerShell, or at least in parallel, to avoid a Windows-first impression.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example terminal commands using Bash syntax (e.g., export, $HOME).
- Include instructions for verifying deployment and cleaning up resources using Azure CLI commands, not just the Azure Portal.
- Where variables are referenced (e.g., $templateFile), show both PowerShell and Bash syntax for setting them.
- Consider adding a short section or callout for Linux/macOS users, highlighting any differences or tips.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/test-toolkit.md
...icles/azure-resource-manager/templates/test-toolkit.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily PowerShell-centric, as the ARM template test toolkit is implemented as a set of PowerShell scripts. All usage examples, regardless of platform, require PowerShell (pwsh) to be installed and used. Windows instructions are presented first, and the Linux and macOS sections are nearly identical but still rely on PowerShell rather than native shell scripting. There are no examples or guidance for running the toolkit with native Linux tools (e.g., Bash, Python), and the documentation does not discuss Linux-specific patterns or troubleshooting beyond PowerShell. This creates a Windows/PowerShell bias, even though cross-platform PowerShell is available.
Recommendations
- Clearly state early in the documentation that the toolkit is PowerShell-based and required on all platforms.
- Provide native Linux (Bash) and macOS (zsh/bash) alternatives if possible, or explicitly note that only PowerShell is supported.
- If feasible, offer or link to a wrapper script or Docker container for Linux users who may not want to install PowerShell.
- Add troubleshooting tips for common Linux/macOS PowerShell issues (e.g., permissions, execution policy differences).
- Consider developing and documenting a cross-platform CLI or containerized version of the toolkit that does not require PowerShell.
- Reorder sections or provide a platform-neutral overview before diving into Windows-specific instructions.
- Highlight any Linux/macOS-specific dependencies (e.g., coreutils on macOS) in a dedicated prerequisites section.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-deployment-script.md
...nager/templates/template-tutorial-deployment-script.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a strong bias towards Windows and PowerShell. All deployment script examples use PowerShell exclusively, with no Bash or cross-platform scripting alternatives. The 'deploymentScripts' resource is shown only with 'AzurePowerShell' kind, and the script content is PowerShell-only. Even in the deployment steps, PowerShell is presented alongside CLI, but the core scripting and troubleshooting are PowerShell-centric. There is no mention or example of using Bash or other Linux-native tools for the deployment script, and PowerShell-specific patterns and escape rules are discussed in detail. This limits accessibility and parity for Linux users.
Recommendations
- Provide equivalent examples using 'AzureCLI' as the 'kind' for the 'deploymentScripts' resource, with Bash script content.
- Include Bash script examples for creating and adding certificates to Key Vault, demonstrating cross-platform compatibility.
- Discuss Bash/Linux-specific troubleshooting steps and file locations in the debugging section.
- Present CLI/Bash examples before or alongside PowerShell, not after or as an alternative.
- Clarify in the prerequisites and throughout the tutorial that both PowerShell and Bash/CLI are supported, and link to relevant documentation for both.
- Add notes about any limitations or differences between PowerShell and Bash deployment scripts in ARM templates.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-create-first-template.md
...r/templates/template-tutorial-create-first-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. Windows tools and patterns (e.g., PowerShell, Visual Studio Code, Windows file dialogs) are mentioned or shown first in most sections. PowerShell examples are consistently presented before Azure CLI (Bash) examples, and the instructions for file creation and navigation assume a Windows GUI workflow. While Azure CLI (with Bash) is supported and Linux installation is mentioned, there are no explicit Linux-native editor or terminal workflow examples, and the CLI instructions are written for Bash but lack parity in terms of Linux file management or editor usage.
Recommendations
- Present Azure CLI (Bash) examples before PowerShell, or at least alternate their order to avoid implicit prioritization.
- Include Linux-native editor options (e.g., Vim, nano, gedit) and show how to create and save files using terminal-based editors.
- Provide explicit instructions for Linux and macOS users for file creation and navigation, not just Windows GUI steps.
- Add screenshots or descriptions of the workflow on Linux (e.g., using a terminal, different file paths).
- Clarify that Visual Studio Code is cross-platform, and mention how to install and launch it on Linux.
- When referencing installation instructions, link to Linux and macOS options first or equally with Windows.
- Ensure that all PowerShell-specific notes (e.g., line continuation with backticks) are matched with Bash/Linux equivalents.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-deploy-vm-extensions.md
...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All examples and instructions focus exclusively on deploying a PowerShell script to a Windows VM using the Custom Script Extension. The template and scripts are Windows-specific, and there is no mention of Linux VMs, Bash scripts, or Linux equivalents. Windows tools and patterns (e.g., PowerShell, Install-WindowsFeature, IIS) are used throughout, and Linux options are omitted.
Recommendations
- Add parallel examples for deploying to Linux VMs using Bash scripts and the Custom Script Extension for Linux.
- Include a Linux quickstart template (e.g., 'Deploy a simple Linux VM') alongside the Windows template, and show how to edit it.
- Demonstrate how to install a web server (e.g., Apache or Nginx) on a Linux VM using a Bash script.
- Provide Linux command examples for retrieving the public IP address (e.g., using Azure CLI in Bash).
- Mention and link to the Linux extensions documentation and features.
- Structure the tutorial to present both Windows and Linux options, or clearly indicate that this tutorial is Windows-specific and link to a Linux-focused equivalent.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-export-template.md
...manager/templates/template-tutorial-export-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is mentioned before Azure CLI in prerequisites and deployment instructions, and PowerShell examples are presented before CLI equivalents. There are no explicit Linux shell examples (e.g., bash), nor are Linux-specific tools or patterns (such as scripting in bash or using Linux-native editors) discussed. The use of Visual Studio Code is cross-platform, but no mention is made of Linux-specific alternatives or considerations.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Include explicit bash shell examples for template deployment, especially for Linux users.
- Mention Linux-native editors (such as Vim, Nano, or Gedit) as alternatives to Visual Studio Code.
- Clarify that both Azure CLI and PowerShell are cross-platform, and provide installation guidance for Linux users.
- Add notes or sections highlighting Linux-specific workflows or troubleshooting steps.
- Ensure that screenshots and instructions referencing the Azure portal do not assume a Windows environment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-quickstart-template.md
...ger/templates/template-tutorial-quickstart-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation shows a moderate Windows bias. In the deployment section, Azure PowerShell (a Windows-centric tool) is presented before Azure CLI, and the PowerShell example is given first. There is also mention of Visual Studio Code as the editor, which is cross-platform but often associated with Windows. The instructions for cleaning up resources use the Azure Portal, which is platform-agnostic, but there are no explicit Linux-specific instructions or terminal examples. There are no Linux shell (bash) examples, and no mention of Linux-native editors or tools.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is more cross-platform and Linux-friendly) first.
- Explicitly mention that both Azure CLI and PowerShell are available on Linux, macOS, and Windows, and provide installation links for all platforms.
- Add bash shell examples for deploying templates, especially for Linux users.
- Mention alternative editors such as Vim, Nano, or Emacs for Linux users, or clarify that Visual Studio Code is available on Linux.
- Include a section or note highlighting any platform-specific differences or requirements.
- Provide resource cleanup instructions using the Azure CLI in addition to the Azure Portal.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-conditions.md
...-manager/templates/template-tutorial-use-conditions.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a clear Windows bias. It uses a Windows VM template as the primary example, provides only PowerShell deployment scripts (no Azure CLI or Bash equivalents), and references Windows tools and patterns (e.g., PowerShell, Windows VM Quickstart template) before or instead of Linux alternatives. Linux users are only briefly acknowledged (e.g., Bash in Cloud Shell), but no full Linux/CLI workflow is provided.
Recommendations
- Provide parallel Azure CLI (az) or Bash script examples for all deployment and cleanup steps, not just PowerShell.
- Include a Linux VM Quickstart template as an alternative or in addition to the Windows VM template.
- When referencing Cloud Shell, give equal prominence to Bash and PowerShell, and show both script types.
- Avoid using only Windows-specific terminology and tools (e.g., PowerShell, Windows VM) in examples and instructions.
- Add a section or callout for Linux/macOS users, outlining any differences or considerations.
- Ensure screenshots and walkthroughs are not exclusively based on Windows environments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-key-vault.md
...e-manager/templates/template-tutorial-use-key-vault.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows and PowerShell bias. All command-line examples for creating and deploying resources use Azure PowerShell scripts, with no equivalent Azure CLI (az) or Bash examples provided. The tutorial centers on deploying a Windows VM, and the only template referenced is for a Windows VM. There is no mention of Linux VM templates or how to use Key Vault secrets with Linux deployments. The instructions for connecting to the VM use RDP, a Windows-specific protocol, and do not mention SSH or Linux alternatives. Visual Studio Code is recommended as the editor, which is cross-platform, but all automation and scripting is Windows/PowerShell-centric.
Recommendations
- Provide equivalent Azure CLI (az) and Bash examples for all PowerShell scripts, especially for key vault creation, secret retrieval, and template deployment.
- Include a Linux VM deployment scenario alongside or instead of the Windows VM example, referencing a Linux quickstart template.
- Demonstrate how to connect to a Linux VM using SSH, and how to use Key Vault secrets for Linux admin credentials.
- When referencing password requirements, link to both Windows and Linux VM documentation.
- Explicitly state that the instructions apply to both Windows and Linux, or clarify when steps are OS-specific.
- Consider providing a toggle or tabs for PowerShell and CLI/Bash instructions throughout the tutorial.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-use-template-reference.md
.../templates/template-tutorial-use-template-reference.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation shows a slight Windows bias: Visual Studio Code is required as the editor (commonly used on Windows, though cross-platform), and file operations are described using GUI steps typical of Windows workflows. In deployment instructions, both PowerShell and Azure CLI (Bash) examples are provided, but PowerShell is mentioned first and in more detail. There is no mention of Linux-native editors or command-line file operations, and no explicit Linux-specific guidance for file handling or environment setup.
Recommendations
- Include instructions for opening and saving files using Linux command-line tools (e.g., curl, nano, vim) alongside Visual Studio Code.
- Explicitly mention that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for those platforms.
- Alternate the order of PowerShell and CLI examples, or present CLI (Bash) first to avoid Windows-first perception.
- Add a note clarifying that all steps can be performed on Linux, macOS, or Windows, and provide platform-specific tips where relevant.
- Provide screenshots or descriptions for Linux/macOS file dialogs or terminal commands where file upload/download is discussed.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/create-troubleshooting-template.md
...ger/troubleshooting/create-troubleshooting-template.md
High Priority
View Details â
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) before Azure CLI, and by referencing PowerShell-specific commands. There are no explicit Linux or Bash examples, and the instructions do not clarify parity or differences for Linux users. The guidance assumes familiarity with PowerShell, which is more common on Windows, and does not offer alternative command-line examples or considerations for Linux environments.
Recommendations
- Provide both Azure PowerShell and Azure CLI examples side by side, or clarify which is cross-platform.
- List Azure CLI (which is cross-platform and common on Linux) before Azure PowerShell, or at least equally.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
- If PowerShell is referenced, note that PowerShell Core is available cross-platform, or provide Bash equivalents.
- Add a section or note about running deployments from Linux or macOS, including any differences or prerequisites.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/deployment-quota-exceeded.md
...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI (with Bash shell) and PowerShell examples for managing deployment quotas. However, the PowerShell section is given equal prominence, and there is no mention of Linux-specific shell environments (e.g., zsh, fish) or Windows Command Prompt. The Bash examples are generic, but the PowerShell examples are Windows-centric. There is no explicit guidance for Linux users beyond Bash, and the documentation does not clarify cross-platform compatibility for the CLI commands.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and mention supported shells (e.g., Bash, zsh, fish).
- Add examples for other popular Linux shells if syntax differs, or clarify that Bash syntax is portable.
- Clarify that PowerShell Core is cross-platform, and provide guidance for running PowerShell commands on Linux/macOS if relevant.
- Consider adding a Windows Command Prompt example or explicitly state that PowerShell is the recommended Windows shell.
- Add a note about prerequisites for each environment (e.g., Azure CLI installation on Linux/macOS, PowerShell installation on non-Windows platforms).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/enable-debug-logging.md
...source-manager/troubleshooting/enable-debug-logging.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell (which is most commonly used on Windows) for enabling debug logging, with no equivalent method available for Azure CLI (the typical cross-platform/Linux tool). All actionable examples for enabling debug logging use PowerShell cmdlets, and the documentation explicitly states that debug logging cannot be enabled via Azure CLI. There are no references to Linux-specific tools, shell scripting, or platform-agnostic alternatives for the core debug logging functionality.
Recommendations
- Work with Azure engineering to add support for enabling debug logging via Azure CLI, or document any workarounds if available.
- If enabling debug logging is fundamentally unavailable in Azure CLI, clearly state this limitation and suggest alternative troubleshooting approaches for Linux users.
- Provide Bash or shell scripting examples where possible, especially for retrieving and managing deployment logs.
- Consider mentioning platform-agnostic tools or REST API methods for enabling debug logging, if available, to improve parity.
- Ensure that documentation does not assume PowerShell as the default and provides equal visibility to Linux/cross-platform workflows.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-not-found.md
...re-resource-manager/troubleshooting/error-not-found.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell and Azure CLI for command-line operations, with PowerShell (a Windows-centric tool) mentioned first. There are no explicit Linux shell (bash) examples or instructions, and the only command-line tools referenced are PowerShell and Azure CLI. The Azure portal is also referenced as a GUI tool, which is cross-platform but not a Linux-native experience. No Linux-specific troubleshooting steps, shell commands, or examples are provided.
Recommendations
- Provide bash shell examples for Azure CLI commands, especially for common troubleshooting steps.
- Mention Azure CLI before PowerShell, or present both equally, to avoid Windows-first ordering.
- Include explicit instructions or notes for users on Linux/macOS, such as verifying the current subscription context using bash.
- Reference cross-platform tools and workflows where possible, and clarify that Azure CLI is available on all platforms.
- If referencing PowerShell, also mention that Azure PowerShell is available on Linux/macOS, or provide equivalent bash commands.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-policy-requestdisallowedbypolicy.md
...ubleshooting/error-policy-requestdisallowedbypolicy.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for investigating policy errors, but the PowerShell section is more detailed, with additional explanation and advanced usage (e.g., ConvertTo-Json with Depth). There is no mention of Bash scripting or Linux-specific command-line patterns, and the PowerShell section appears after the Azure CLI section, but is more comprehensive. No explicit Linux tools or shell examples are provided.
Recommendations
- Add Bash shell scripting examples for users on Linux/macOS, especially for parsing JSON output from Azure CLI.
- Ensure CLI and PowerShell sections are equally detailed, or provide advanced CLI usage (e.g., using jq to parse JSON).
- Explicitly mention that Azure CLI commands work cross-platform, and provide sample commands for common Linux shells.
- Consider adding a note or section for troubleshooting using REST API calls with curl, which is common on Linux.
- Review the PowerShell section to ensure parity with CLI examples, avoiding unnecessary detail imbalance.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-register-resource-provider.md
...er/troubleshooting/error-register-resource-provider.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed examples for Azure CLI and Azure PowerShell, with PowerShell examples given equal prominence to CLI. However, there are no explicit Linux shell (bash) examples, and the CLI examples are not specifically shown in a Linux context. PowerShell is a Windows-centric tool, and its inclusion without bash or Linux shell equivalents may bias the documentation towards Windows users. Additionally, the order of sections places Azure CLI first, but the lack of explicit Linux shell examples and the presence of PowerShell may still indicate a subtle Windows bias.
Recommendations
- Add explicit bash/Linux shell examples for all Azure CLI commands, clarifying that Azure CLI is cross-platform and can be run in bash.
- Include notes or tabs for bash and PowerShell to show parity and help users on both platforms.
- Consider adding troubleshooting steps or examples using native Linux tools or scripting patterns where relevant.
- Clarify in the introduction that Azure CLI commands are cross-platform and provide guidance for both Windows and Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/error-resource-quota.md
...source-manager/troubleshooting/error-resource-quota.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for checking quotas, but the PowerShell example is given equal prominence, despite PowerShell being primarily associated with Windows. There are no explicit Linux shell (bash) examples, and the Azure CLI example is not clearly marked as cross-platform. The documentation does not mention or show how to perform these actions using native Linux tools or in a Linux context, and the portal instructions are platform-neutral but do not address Linux-specific workflows.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide bash-specific context or examples where appropriate.
- Add a note or section highlighting how Linux users can install and use Azure CLI, and clarify that PowerShell is optional and not required on Linux.
- Consider providing bash script examples or mentioning common Linux shell environments to ensure parity.
- If PowerShell is mentioned, clarify its cross-platform availability, or de-emphasize it in favor of the more universal Azure CLI.
- Ensure that any screenshots or portal instructions do not assume a Windows environment (e.g., file paths, UI differences).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-bicep-deployment.md
...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell examples alongside Azure CLI, and by referencing Windows-centric tools and workflows (e.g., Visual Studio Code, PowerShell, and Cloud Shell) without mentioning Linux-specific alternatives. PowerShell is given equal prominence to Azure CLI, and there are no Bash or Linux shell examples. The use of Visual Studio Code, while cross-platform, is often associated with Windows workflows. There are no explicit Linux or macOS-specific instructions, nor are there references to native Linux editors or shells.
Recommendations
- Add explicit Bash/Linux shell examples for all Azure CLI commands, demonstrating usage in a typical Linux terminal.
- Clarify that Visual Studio Code is cross-platform, and mention alternative editors (e.g., Vim, nano) for Linux users.
- Include instructions for installing and using the Azure CLI and Bicep tools on Linux systems.
- Avoid presenting PowerShell examples with equal prominence to Azure CLI; instead, default to Azure CLI (which is cross-platform) and provide PowerShell as an optional tab.
- Mention that all commands can be run from Bash on Linux/macOS, and provide troubleshooting tips for common Linux-specific issues (e.g., file permissions, line endings).
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/concept-connection-string.md
...in/articles/azure-signalr/concept-connection-string.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation page primarily uses .NET-centric and Windows-oriented configuration patterns (such as appsettings.json, dotnet user-secrets, and double-underscore environment variable conventions) without providing explicit Linux/Unix examples or mentioning Linux-native tools. The only CLI example is Azure CLI, which is cross-platform, but all configuration and code examples assume a .NET/Windows development environment. There are no bash, shell, or Linux-specific configuration examples, and the secret management tools referenced are .NET/Windows-first.
Recommendations
- Add explicit Linux/Unix shell examples for setting environment variables (e.g., export Azure__SignalR__ConnectionString=...) and managing secrets.
- Mention and provide examples for Linux-native secret management tools (such as using environment variables in bash, or integrating with Linux keyrings or Azure Key Vault CLI).
- Clarify that the .NET secret manager and appsettings.json are not exclusive to Windows, but also provide parity examples for Node.js, Python, or Java apps on Linux.
- When listing configuration options, avoid assuming a Windows-first environment; present cross-platform approaches first or in parallel.
- Include a section or callout for configuring connection strings in common Linux deployment scenarios (e.g., Docker containers, systemd services, or Kubernetes pods).
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-concept-serverless-development-config.md
...gnalr/signalr-concept-serverless-development-config.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a bias towards Windows by primarily referencing Azure Portal (a web UI often associated with Windows-centric workflows), omitting explicit Linux or cross-platform command-line examples for configuration and deployment, and mentioning CORS configuration limitations for Linux Consumption plans only as a note. There are no Bash, CLI, or Linux-native tool examples for common tasks such as CORS configuration, deployment, or authentication setup. The guidance for enabling CORS in the cloud refers only to the Azure Portal UI, and the workaround for Linux plans is to use Azure API Management, without showing how to use Azure CLI or ARM templates. All code samples are in C# (a language more common on Windows), and there are no examples for Bash, PowerShell, or Linux shell environments.
Recommendations
- Add Azure CLI and/or Azure PowerShell examples for common configuration tasks (e.g., enabling CORS, setting authentication) alongside or before portal-based instructions.
- Provide explicit instructions or scripts for configuring CORS and authentication on Linux (Consumption and other plans), using cross-platform tools.
- Include deployment examples using Bash or cross-platform shell scripts, not just references to the Azure Portal.
- Ensure that any limitations or differences for Linux plans are clearly documented with actionable alternatives (e.g., ARM/Bicep templates, CLI commands).
- Add code samples in additional languages (e.g., JavaScript, Python) where possible, and clarify that C# is used for demonstration but alternatives exist.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-reverse-proxy-overview.md
.../azure-signalr/signalr-howto-reverse-proxy-overview.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a bias towards Windows/Azure-native tools by exclusively referencing Azure Application Gateway and Azure API Management as reverse proxy solutions, without mentioning or providing examples for popular Linux-based reverse proxies such as NGINX or Apache. No Linux-specific configuration examples or guidance are provided, and the only reverse proxy examples are Azure-centric, which are more commonly used in Windows environments. This may leave Linux users without clear guidance for integrating Azure SignalR with widely-used open-source reverse proxies.
Recommendations
- Add configuration examples for popular Linux-based reverse proxies such as NGINX and Apache, including sample config snippets for HOST header rewriting and WebSocket/SSE support.
- Explicitly mention Linux-compatible reverse proxy solutions alongside Azure-native options, and provide links to relevant documentation.
- Ensure that Linux examples are presented with parity to Azure-native/Windows tools, either by alternating order or by grouping all supported reverse proxies together.
- Include troubleshooting tips or caveats specific to Linux environments (e.g., SELinux, systemd socket activation, common pitfalls with NGINX/Apache and WebSockets).
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-move-across-regions.md
...les/azure-signalr/signalr-howto-move-across-regions.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure portal and Azure PowerShell, with all command-line examples using PowerShell syntax and Windows-specific tools (e.g., Notepad). There are no examples for Linux users (e.g., Azure CLI, Bash, or cross-platform editors), and PowerShell is presented as the only scripting option, which may disadvantage users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI (az) command examples for exporting, editing, and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Replace or supplement references to Windows-specific tools like Notepad with cross-platform editors (e.g., 'use your preferred text editor such as nano, vim, or Visual Studio Code').
- Explicitly mention that the PowerShell examples are for Windows and provide Bash/Linux alternatives where possible.
- Reorder or parallelize sections so that Azure CLI and PowerShell instructions are presented side-by-side or with equal prominence.
- Add a note at the beginning clarifying that the instructions apply to all platforms and that both PowerShell and CLI options are available.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-overview.md
...s/blob/main/articles/azure-signalr/signalr-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
aspnet_heavy
Summary
The documentation page exhibits a bias toward Windows by focusing primarily on ASP.NET Core and ASP.NET (which are traditionally associated with Windows development), mentioning them exclusively as server-side options. There are no examples or mentions of Linux-specific frameworks, tools, or deployment scenarios. The documentation does not provide parity for Linux users, such as examples using Node.js, Python, or Java server-side implementations, nor does it mention cross-platform development or deployment considerations.
Recommendations
- Include examples and references for using Azure SignalR Service with cross-platform frameworks such as Node.js, Python, or Java on Linux.
- Mention and link to documentation for deploying SignalR applications on Linux servers or containers.
- Balance the server-side language and framework discussion by highlighting non-.NET options and their compatibility with Azure SignalR Service.
- Add explicit statements or sections clarifying that Azure SignalR Service is platform-agnostic and can be used with both Windows and Linux environments.
- Provide sample code snippets or tutorials for Linux-based development and deployment scenarios.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-troubleshoot-guide.md
...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation shows a bias toward Windows environments. Troubleshooting steps and examples reference Windows-specific tools (e.g., Fiddler, Performance Monitor), Visual Studio UI, and .NET/ASP.NET patterns. There are no Linux-specific equivalents or instructions for common tasks like debugging, viewing network traffic, or monitoring server metrics. Linux and cross-platform scenarios are not addressed, and Windows tools are mentioned exclusively or before any alternatives.
Recommendations
- Provide Linux equivalents for Windows tools mentioned, such as suggesting Wireshark or tcpdump for network traffic analysis, and dotnet-trace or PerfView (on Linux) for diagnostics.
- Include instructions for enabling and viewing logs, debugging, and monitoring on Linux-based deployments (e.g., using journalctl, systemd, or container logs).
- When referencing Visual Studio or Windows UI steps (e.g., 'Uncheck Just My Code'), add corresponding steps for VS Code, JetBrains Rider, or command-line debugging tools.
- When mentioning Fiddler, also mention cross-platform alternatives like mitmproxy or Wireshark.
- For performance monitoring, reference tools like top, htop, or dotnet-counters for Linux environments.
- Add explicit notes or sections for Linux users, ensuring parity in troubleshooting guidance and code samples.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-troubleshoot-method.md
...les/azure-signalr/signalr-howto-troubleshoot-method.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. Windows tools (Fiddler, web.config, Windows Phone 8) are mentioned before or more prominently than Linux equivalents. Some examples and logging instructions (web.config, Windows Phone 8 tracing) are Windows-specific, while Linux alternatives (tcpdump) are present but less emphasized. There are missing Linux-specific examples for some logging/tracing scenarios, and overall, Windows-centric patterns appear first or exclusively in several sections.
Recommendations
- Ensure Linux tools (e.g., tcpdump, journalctl, syslog) are mentioned with equal prominence and ordering as Windows tools like Fiddler.
- Provide explicit Linux/macOS examples for enabling server-side and client-side logging, including configuration file samples for common Linux hosting scenarios.
- Avoid Windows-only references (e.g., Windows Phone 8, web.config) or supplement with Linux equivalents (e.g., appsettings.json, environment variables).
- Add troubleshooting steps and examples for Linux environments, such as using systemd logs, container logs, or Linux desktop clients.
- Review all links and referenced guides to ensure Linux parity in diagnostic and troubleshooting instructions.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-use.md
.../blob/main/articles/azure-signalr/signalr-howto-use.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows environments, particularly in the legacy ASP.NET SignalR section. It exclusively uses PowerShell/Package Manager Console commands for SDK installation and references the 'web.config' file for configuration, both of which are Windows-centric tools and patterns. There are no Linux/macOS equivalents or cross-platform alternatives provided, and no mention of using the .NET CLI for package installation in the legacy section. The ASP.NET Core section is more neutral, using 'dotnet' CLI commands, but the legacy section lacks Linux parity.
Recommendations
- For SDK installation in the legacy ASP.NET SignalR section, provide cross-platform .NET CLI commands (e.g., 'dotnet add package') alongside or instead of PowerShell/Package Manager Console commands.
- Mention configuration alternatives for non-Windows environments, such as using environment variables or appsettings.json, instead of only referencing 'web.config'.
- Explicitly state that the instructions apply to Windows and provide guidance or links for Linux/macOS users where applicable.
- Review all code and configuration samples to ensure they are platform-agnostic or provide platform-specific alternatives as needed.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-functions-java.md
...ure-signalr/signalr-quickstart-azure-functions-java.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation references the Azure Storage Emulator, which is a Windows-only tool, without mentioning or prioritizing its cross-platform replacement, Azurite. There are no explicit Linux/macOS-specific instructions or examples for setting up storage emulation or environment variables, and the only emulator mentioned is not available on Linux. This may confuse or block Linux users. The overall instructions are mostly cross-platform, but the storage setup step is Windows-biased.
Recommendations
- Replace references to 'Azure Storage Emulator' with 'Azurite', which is cross-platform and recommended by Microsoft for local storage emulation.
- Provide explicit instructions or links for installing and running Azurite on Linux and macOS, not just Windows.
- Clarify that the quickstart works on all platforms by ensuring all tools and steps are available and documented for Linux/macOS.
- If any commands or environment variable settings differ between platforms (e.g., export vs. set), provide both examples.
- Review and update any screenshots or UI references that may be Windows-specific to ensure parity.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias by listing PowerShell instructions before CLI/Bash equivalents, providing detailed PowerShell examples, and referencing Windows-centric tools (e.g., Git Bash via Git for Windows) in the prerequisites. While Azure CLI (cross-platform) examples are present, the structure and language prioritize Windows and PowerShell users, and Linux-native tools or shells are not mentioned.
Recommendations
- Alternate the order of PowerShell and CLI sections or present CLI (Bash) instructions first in some sections to avoid always prioritizing Windows tools.
- Explicitly mention support for Linux and macOS in the prerequisites, including native Bash shells (e.g., Ubuntu Terminal, macOS Terminal) rather than only referencing Git Bash for Windows.
- Add notes clarifying that Azure CLI commands work natively on Linux and macOS, not just in Git Bash on Windows.
- Ensure parity in detail and explanation between PowerShell and CLI sections.
- Where possible, provide examples or troubleshooting tips specific to Linux environments (e.g., common permission issues, package managers for installing Azure CLI).
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-vsan.md
...docs/blob/main/articles/azure-vmware/configure-vsan.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation demonstrates a Windows bias by exclusively using PowerShell cmdlets for all configuration tasks, referencing Windows tooling and patterns (such as 'Run command' and cmdlets) without mentioning Linux CLI or automation equivalents. Where OS-specific prerequisites are mentioned, Windows is listed before Linux. There are no Linux shell examples or guidance for performing these tasks outside the Azure portal or PowerShell context.
Recommendations
- Provide equivalent Linux CLI or automation examples (e.g., using Azure CLI, Bash scripts, or REST API calls) for all configuration tasks.
- Mention and link to Linux-based tools or methods where possible, not just PowerShell cmdlets.
- When listing OS prerequisites or instructions, alternate or parallelize Windows and Linux information to avoid Windows-first ordering.
- Clarify if the 'Run command' and cmdlets can be invoked from Linux environments, and provide guidance if so.
- Add explicit Linux-focused sections or callouts to ensure parity and inclusivity for Linux administrators.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-dotnet.md
...in/articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a strong Windows bias. It exclusively references Visual Studio (a Windows-centric IDE), .NET Framework (not .NET Core/.NET 5+), and provides only PowerShell/NuGet Package Manager Console commands for package installation. There are no instructions or examples for Linux users (e.g., using VS Code, JetBrains Rider, or CLI tools), nor are there any bash or cross-platform command examples. The prerequisites and workflow assume a Windows environment throughout.
Recommendations
- Add instructions for Linux and macOS users, including using .NET Core or later (which is cross-platform) instead of .NET Framework.
- Provide alternative steps for using VS Code or JetBrains Rider, and for running the application via the dotnet CLI.
- Include bash/zsh shell commands for package installation (e.g., 'dotnet add package') alongside PowerShell examples.
- Clarify which steps are Windows-specific and offer equivalent Linux/macOS workflows where possible.
- Mention cross-platform compatibility and test the sample on Linux to ensure parity.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/architecture-api-management.md
...n/articles/azure-vmware/architecture-api-management.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and the Azure portal as primary management tools, with no mention of Linux-native tools (such as Azure CLI on Linux, Bash scripting, or cross-platform automation). The examples and management patterns are described in a way that assumes a Windows-centric workflow, and there are no Linux-specific instructions or parity in tool recommendations.
Recommendations
- Include Azure CLI (az) examples alongside or before PowerShell examples to provide parity for Linux users.
- Explicitly mention that API Management and Azure VMware Solution can be managed from Linux, macOS, and Windows environments.
- Provide Bash scripting examples or references for common management tasks.
- Clarify that automation can be performed using cross-platform tools (e.g., Azure CLI, REST API, Terraform) and not just PowerShell.
- Add a section or callout highlighting cross-platform compatibility and best practices for Linux-based DevOps workflows.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/architecture-hub-and-spoke.md
...in/articles/azure-vmware/architecture-hub-and-spoke.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based jump boxes (Windows 10 or Windows Server), recommending Active Directory-integrated DNS and domain controllers (Windows-centric), and omitting Linux-based alternatives or examples for jump boxes, DNS, or identity. There are no Linux or open-source equivalents mentioned for jump box VMs, DNS, or identity management, and the only OS-specific example is Windows.
Recommendations
- Include Linux-based jump box examples (e.g., Ubuntu or CentOS VMs) alongside or before Windows examples.
- Mention and provide guidance for deploying DNS servers on Linux (e.g., BIND, dnsmasq) as alternatives to Active Directory-integrated DNS.
- Discuss identity options that are not Windows-centric, such as integrating with LDAP or other open-source identity providers.
- When referencing RDP and SSH, clarify that SSH is typically used for Linux VMs and provide instructions/examples for both.
- Ensure that all OS-specific recommendations (e.g., for jump boxes, DNS, identity) are presented in a cross-platform manner, or explicitly state that both Windows and Linux are supported with relevant links.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/architecture-migrate.md
...lob/main/articles/azure-vmware/architecture-migrate.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric migration scenarios (such as SQL Server and Always On configurations) in the 'Next Steps' section, and by referencing Windows tools (e.g., SQL Server) without equivalent Linux migration examples. There is no mention of Linux-specific migration scenarios or tools, and the only reference to Linux (KVM) is brief and not elaborated with examples or guidance.
Recommendations
- Add migration examples and guidance for common Linux workloads (e.g., Oracle, MySQL, Apache) to balance the focus on Windows workloads.
- Include Linux-specific migration scenarios in the 'Next Steps' section, such as migrating KVM-based VMs or Linux application servers.
- Provide parity in documentation by offering Linux command-line examples or references where Windows/SQL Server examples are given.
- Mention and link to tools and best practices relevant to Linux migrations, not just Windows-centric tools.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/backup-azure-netapp-files-datastores-vms.md
...ure-vmware/backup-azure-netapp-files-datastores-vms.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the VMware vSphere client and vCenter web client interfaces, which are primarily used in Windows environments. There are no examples or instructions for performing backup operations using Linux-based tools, CLIs, or automation scripts. All step-by-step instructions assume a GUI workflow typical of Windows administrators, and there is no mention of Linux command-line alternatives or cross-platform automation options.
Recommendations
- Provide equivalent instructions for performing backup operations using Linux-based tools, such as the Azure CLI, PowerShell Core (cross-platform), or REST API calls from a Linux shell.
- Include examples of how to automate backup and restore tasks using scripts that can be run on Linux systems.
- Mention and document any supported Linux-compatible management interfaces or third-party tools.
- Clarify whether the vSphere client and vCenter web client are accessible from Linux environments (e.g., via browser) and provide any necessary setup instructions.
- Ensure that all prerequisites and workflows are described in a platform-agnostic way, or provide parallel instructions for both Windows and Linux users.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/bitnami-appliances-deployment.md
...articles/azure-vmware/bitnami-appliances-deployment.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by instructing users to connect to the VM via RDP and linking only to Windows-specific connection instructions. There are no examples or guidance for connecting from Linux or macOS clients (e.g., using SSH or RDP clients on those platforms). The documentation also references Windows tools and patterns (RDP, Windows Azure portal instructions) before any Linux alternatives, and omits Linux/macOS connection workflows.
Recommendations
- Add instructions for connecting to the VM from Linux and macOS clients, including SSH and RDP alternatives (e.g., using Remmina, rdesktop, or native SSH clients).
- Include links to Azure documentation for connecting to Linux VMs, not just Windows VMs.
- When referencing RDP, clarify that it is available on multiple platforms and provide platform-agnostic instructions.
- Provide parity in examples and screenshots for Linux/macOS users where applicable.
- Explicitly mention that Bitnami appliances are Linux-based and that SSH is the primary method for remote access, with instructions for all major OSes.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-azure-elastic-san.md
...n/articles/azure-vmware/configure-azure-elastic-san.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by prioritizing Azure portal and PowerShell/CLI tools, with no mention of Linux-specific tools or workflows. All procedural examples and instructions are centered around the Azure portal or PowerShell/CLI, which are more commonly used in Windows environments. There are no Linux-specific command-line examples, nor is there guidance for Linux administrators or integration with Linux-based management tools.
Recommendations
- Include Linux-specific command-line examples (e.g., using Azure CLI on Linux, or relevant Linux shell commands) alongside or instead of PowerShell examples.
- Mention and provide guidance for Linux-based workflows and tools where applicable, such as using Bash scripts or integrating with Linux automation tools.
- Ensure that instructions for creating and managing Elastic SAN resources are platform-agnostic or provide parity for both Windows and Linux users.
- Explicitly state that the Azure CLI can be used from Linux, and provide example commands in Bash syntax.
- Add troubleshooting steps or notes relevant to Linux environments, such as SELinux considerations, iSCSI initiator setup on Linux, or network configuration differences.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-dns-azure-vmware-solution.md
...es/azure-vmware/configure-dns-azure-vmware-solution.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page provides detailed PowerCLI (PowerShell-based) examples for verifying DNS forwarder configuration, with no equivalent Linux or cross-platform CLI examples. All command-line instructions use PowerShell modules, and there is no mention of Linux-native tools (e.g., dig, nslookup, curl) or how to perform verification from a Linux environment. The only CLI workflow is Windows-centric, and Windows tools are mentioned exclusively and before any Linux alternatives (which are absent).
Recommendations
- Add equivalent Linux CLI examples for verifying DNS forwarder functionality, such as using dig or nslookup from a Linux VM connected to the NSX-T DNS Forwarder.
- Mention that PowerCLI is available on Linux (PowerShell Core), or provide instructions for installing and using PowerCLI on Linux/macOS if applicable.
- Include a section or note on how to perform DNS lookups from a Linux-based VM or management station, demonstrating parity with the PowerCLI workflow.
- Where possible, use generic or cross-platform tools (e.g., REST API calls with curl, or platform-agnostic SDKs) in examples, or provide both Windows and Linux variants.
- Explicitly state that the verification steps can be performed from both Windows and Linux environments, and clarify any platform-specific requirements.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-external-identity-source-nsx-t.md
...ure-vmware/configure-external-identity-source-nsx-t.md
High Priority
View Details â
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 as the LDAP provider, requiring Windows-specific infrastructure (domain controllers, AD Certificate Services), and omitting any examples or guidance for Linux-based LDAP servers (such as OpenLDAP). All terminology, screenshots, and instructions are tailored to Windows environments, with no mention of Linux tools or alternative LDAP implementations.
Recommendations
- Include examples and instructions for configuring NSX with Linux-based LDAP servers (e.g., OpenLDAP), including certificate management and connection setup.
- Add guidance for generating and managing certificates using Linux tools (such as OpenSSL) and third-party CAs, not just Windows AD CS.
- Provide parity in prerequisites and role assignment sections by referencing Linux LDAP server equivalents and their configuration steps.
- Update screenshots and terminology to be inclusive of both Windows and Linux LDAP environments.
- Clarify that NSX supports third-party LDAP servers and provide links or references to official documentation for non-Windows LDAP integration.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-virtual-trusted-platform-module.md
...re-vmware/configure-virtual-trusted-platform-module.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by emphasizing Windows security features (e.g., BitLocker, Windows credential protection) and mentioning Windows guest OS versions before Linux. There are no Linux-specific examples or tools referenced, and the security benefits are described primarily in Windows-centric terms. The documentation does not provide Linux-specific guidance or examples for configuring or using vTPM, nor does it mention Linux disk encryption tools or Linux-specific attestation workflows.
Recommendations
- Add Linux-specific examples and guidance for configuring and using vTPM, including steps for enabling vTPM on Linux VMs.
- Mention and describe Linux disk encryption solutions (e.g., LUKS, dm-crypt) that can leverage vTPM, alongside BitLocker.
- Provide parity in describing security benefits for both Linux and Windows, including how vTPM and Secure Boot protect Linux systems.
- List Linux guest OS versions before or alongside Windows versions in prerequisites.
- Reference Linux attestation tools or workflows, if applicable, and provide links to relevant Linux documentation.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-vmware-cloud-director-service-azure-vmware-solution.md
...re-vmware-cloud-director-service-azure-vmware-solution.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation consistently references the Azure portal (a web-based tool, but often associated with Windows-centric workflows) and does not provide any Linux-specific examples or command-line alternatives. All credential and management steps are described using the Azure portal UI, with no mention of Linux CLI tools (e.g., Azure CLI, PowerShell Core on Linux, or SSH-based workflows). There are no Linux shell commands or examples for tasks such as transferring the OVA, deploying the VM, or verifying connectivity. The only command-line example is 'transporter-status.sh', but its usage context is minimal and not contrasted with any Windows-specific commands. The documentation assumes a GUI-first, Azure-portal-centric workflow, which can be less accessible or familiar to Linux-focused administrators.
Recommendations
- Add Linux CLI examples for interacting with Azure VMware Solution resources, such as using Azure CLI to retrieve credentials, manage NSX, or deploy OVAs.
- Provide alternative workflows for downloading and transferring the OVA using Linux tools (e.g., wget, scp, or az CLI).
- Include Linux shell commands for verifying network connectivity (e.g., using curl, ping, or netcat) to the VMware Cloud Director service.
- Mention that all steps can be performed from Linux environments, and clarify any platform-specific requirements or differences.
- If PowerShell is required, reference PowerShell Core (which is cross-platform) and provide equivalent bash/zsh commands where possible.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-traffic-manager-balance-workloads.md
...ure-vmware/deploy-traffic-manager-balance-workloads.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft IIS Servers as backend pool members, using Windows-centric terminology (e.g., vSphere, NSX, IIS), and omitting any Linux-based examples or instructions. There are no examples or guidance for deploying Linux web servers (such as Apache or Nginx) as backend pool members, nor are there any Linux-specific verification or troubleshooting steps. All screenshots and configuration steps assume a Windows-based environment.
Recommendations
- Include examples using Linux-based web servers (e.g., Apache, Nginx) as backend pool members alongside or instead of IIS.
- Provide Linux command-line examples for verification steps (e.g., using curl, dig, or traceroute) to check endpoint status and DNS resolution.
- Mention that backend pool members can be any OS, not just Windows, and provide guidance for configuring common Linux distributions.
- Add screenshots or instructions for managing Linux VMs in the Azure VMware Solution environment.
- Balance references to Windows tools (IIS, vSphere) with Linux equivalents or note cross-platform alternatives.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-vmware-cloud-director-availability-in-azure-vmware-solution.md
...e-cloud-director-availability-in-azure-vmware-solution.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Azure VMware Solution and the use of Azure portal Run commands, which are Windows-centric tools. There are no Linux or cross-platform CLI examples, nor any mention of Linux-based deployment or management patterns. The instructions and examples exclusively reference Azure portal and Run commands, which are typically accessed from Windows environments, and do not provide parity for Linux administrators or those using non-Windows automation tools.
Recommendations
- Provide equivalent Linux CLI or shell script examples for deploying and managing VMware Cloud Director Availability.
- Include instructions for using cross-platform tools (e.g., Azure CLI, PowerShell Core, REST API) from Linux or macOS environments.
- Clarify whether Run commands can be executed from non-Windows systems and, if so, provide examples.
- Add documentation sections or links for Linux administrators, including automation via Ansible, Bash, or other common Linux tools.
- Ensure that prerequisites and troubleshooting steps mention Linux-compatible methods (e.g., uploading OVAs, configuring DNS) alongside Windows approaches.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-zerto-disaster-recovery.md
...rticles/azure-vmware/deploy-zerto-disaster-recovery.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation displays a moderate Windows bias. While it notes that core Zerto components (ZVMA, vRA) run on Linux, the only explicit OS-specific instructions or details are for the Windows-based Zerto Cloud Appliance (ZCA). The ZCA (Windows VM) is described in greater detail than the Linux appliances, and Windows services are named, while Linux equivalents are not. No Linux command-line or deployment examples are provided, and there is no mention of Linux-based management or troubleshooting tools. The documentation does not provide parity in examples or operational details for Linux users.
Recommendations
- Provide explicit Linux-based deployment and management examples for Zerto components (e.g., ZVMA, vRA), including command-line instructions or references.
- Describe Linux service names and management patterns for Zerto appliances, similar to how Windows services are detailed for ZCA.
- Ensure that troubleshooting and log collection instructions are available for Linux-based appliances, not just for Windows.
- When listing components, present Linux and Windows options in parallel, rather than focusing on Windows tools and services.
- Add links to Linux-specific documentation (e.g., ZVMA log collection, service management) where available.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/includes/vcenter-access-identity-description.md
...vmware/includes/vcenter-access-identity-description.md
High Priority
View Details â
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, mentioning Windows tools and patterns (Active Directory) before any Linux equivalents, and omitting examples or guidance for Linux-based identity sources or user management. There are no examples or mentions of integrating with Linux-based directory services (such as OpenLDAP) or using Linux tools for identity management.
Recommendations
- Add examples and guidance for configuring user accounts and groups using Linux-based identity sources, such as OpenLDAP or FreeIPA.
- Include instructions for integrating vCenter Server with non-Windows LDAP/LDAPS servers, highlighting any differences or considerations.
- Present both Windows and Linux options in parallel when discussing identity management, rather than focusing solely on Windows Server Active Directory.
- Clarify any platform-specific limitations or requirements for identity source integration, and provide troubleshooting steps for Linux environments.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/install-cloud-backup-virtual-machines.md
.../azure-vmware/install-cloud-backup-virtual-machines.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal 'Run command' interface and PowerShell-like cmdlet names (e.g., Install-NetAppCBSA), with no mention of Linux CLI, shell, or automation alternatives. All operational steps are described using GUI or Windows-centric tools, and there are no Linux-specific instructions or parity examples. The documentation assumes the user is operating in a Windows or Azure GUI environment, omitting any guidance for Linux administrators or those using native Linux tools.
Recommendations
- Provide equivalent Linux CLI or shell-based installation and management instructions, such as using Azure CLI, Bash scripts, or REST API calls.
- Include examples for automating installation and upgrades using Linux tools (e.g., az CLI, curl, or Ansible).
- Clarify whether the 'Run command' interface is accessible and fully functional from Linux environments, and if so, provide explicit instructions.
- Add a section or callout for Linux administrators, highlighting any differences or additional steps required.
- Ensure that any PowerShell or Windows-specific cmdlets are accompanied by Linux-friendly alternatives where possible.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/integrate-azure-native-services.md
...ticles/azure-vmware/integrate-azure-native-services.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page primarily describes Azure native monitoring and management tools with a focus on Windows-centric features and terminology. Windows-specific artifacts (e.g., registry, services) are mentioned before Linux equivalents, and there is a lack of concrete Linux command-line examples or tool references. While Linux is briefly acknowledged, the guidance and examples are minimal compared to Windows, and there are no PowerShell examples, but the overall pattern is Windows-first.
Recommendations
- Provide parallel Linux examples and workflows alongside Windows instructions, especially for agent installation and configuration.
- Explicitly mention Linux monitoring capabilities (e.g., monitoring Linux daemons, log files) with concrete examples.
- Include Linux command-line examples (e.g., shell commands for agent installation, log collection) where relevant.
- Balance references to Windows-specific artifacts (e.g., registry, services) with Linux equivalents (e.g., systemd services, /etc files).
- Add screenshots or diagrams that show both Windows and Linux VM monitoring scenarios.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/migrate-sql-server-always-on-availability-group.md
...are/migrate-sql-server-always-on-availability-group.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented towards Windows environments, specifically Windows Server Failover Clustering and SQL Server on Windows. All examples, procedures, and prerequisites assume a Windows-based SQL Server deployment. There are no mentions of Linux-based SQL Server deployments, nor are there any examples or guidance for users running SQL Server on Linux. All clustering and migration steps reference Windows tools and patterns (e.g., Windows Server Failover Cluster, SSMS), and all external links are to Windows-centric documentation.
Recommendations
- Add guidance and examples for migrating SQL Server Always On Availability Groups running on Linux (supported since SQL Server 2017).
- Include Linux-specific prerequisites, such as required packages, cluster manager (e.g., Pacemaker), and OS-level considerations.
- Provide equivalent migration steps using Linux tools and commands (e.g., using sqlcmd, Pacemaker commands, or Linux-based management tools).
- Reference official Microsoft and VMware documentation for SQL Server on Linux and Linux clustering solutions.
- Clarify early in the article that the documented procedure is for Windows-based deployments, and link to Linux guidance if available.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/native-first-party-principle-security.md
.../azure-vmware/native-first-party-principle-security.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation prioritizes Windows-centric tools and workflows. Azure PowerShell is presented as the primary scripting example, and the Azure CLI (which is cross-platform) is only mentioned after PowerShell. There are no explicit Linux-specific instructions or examples, and the use of PowerShell commands may alienate Linux users who are more familiar with Bash or other Linux-native tools.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash shell context for Linux users.
- Add a section or callout for Linux users, clarifying that all required actions can be performed from Linux environments using Azure CLI.
- Where possible, provide Bash script examples or guidance for common Linux shells.
- Avoid referring to PowerShell as the default or primary scripting method unless there is a specific technical reason.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/protect-azure-vmware-solution-with-application-gateway.md
...protect-azure-vmware-solution-with-application-gateway.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a strong Windows bias. All backend web server configuration examples use Windows Server 2016 with IIS, and all automation is shown exclusively with PowerShell commands. There are no Linux-based examples (e.g., Apache or Nginx), nor are there any Bash or cross-platform shell commands. The documentation refers to Windows-specific tools and patterns (IIS, PowerShell) and does not mention Linux alternatives. This may give the impression that only Windows-based web servers are supported or recommended.
Recommendations
- Add parallel examples using Linux VMs (e.g., Ubuntu or CentOS) with Apache or Nginx as the web server.
- Include Bash shell commands for installing and configuring web servers on Linux (e.g., apt install apache2, echo commands to create index.html).
- Explicitly state that both Windows and Linux backend VMs are supported by Azure Application Gateway.
- Where PowerShell is used, provide equivalent Bash or shell commands for Linux users.
- Balance screenshots and configuration steps to show both Windows and Linux environments where possible.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/restore-guest-files-folders.md
...n/articles/azure-vmware/restore-guest-files-folders.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows environments. It exclusively describes and provides steps for restoring files from VMDKs on Windows guest OS, with no equivalent steps or examples for Linux guests. Linux is explicitly marked as unsupported for guest file restore, and only a manual workaround is mentioned. All credential and restore path examples are Windows-specific (e.g., UNC paths, 'Administrator' account). No Linux tools, commands, or patterns are referenced.
Recommendations
- Add explicit instructions or a separate section for restoring files from VMDKs attached to Linux guest OS, even if only manual methods are supported.
- Provide Linux-specific examples for mounting VMDKs and copying files (e.g., using 'mount', 'losetup', or 'guestmount').
- Include credential requirements and restore path examples relevant to Linux (e.g., using SSH, specifying Linux file paths).
- Clarify any feature gaps and, if possible, provide a roadmap or alternatives for Linux guest support.
- Avoid using only Windows terminology and tools (e.g., UNC paths, 'Administrator' account) in general instructions; provide Linux equivalents where possible.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/set-up-backup-server-for-azure-vmware-solution.md
...ware/set-up-backup-server-for-azure-vmware-solution.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation demonstrates a strong Windows bias. All setup and usage instructions for Azure Backup Server are based on deploying and operating on Windows Server VMs. There are no examples or guidance for deploying Azure Backup Server on Linux, nor are there any references to Linux tools or command-line instructions. Powershell is used for configuration checks, and Windows-specific tools and patterns (such as ReFS, Windows Update, and domain join requirements) are mentioned exclusively. Linux is only referenced in the context of application-consistent backups, not as a platform for running Azure Backup Server.
Recommendations
- Clarify early in the documentation whether Azure Backup Server is supported on Linux. If not, explicitly state this to set expectations.
- If Linux support is available or planned, provide equivalent setup, installation, and configuration instructions for Linux-based VMs.
- Include Linux-specific examples for disk attachment, storage pool configuration, and backup/restore operations, using Linux tools and commands.
- When referencing command-line operations, provide both Powershell (Windows) and Bash (Linux) equivalents where applicable.
- Mention Linux filesystem requirements and supported filesystems if Linux is supported.
- If only Windows is supported, add a section explaining why and suggest alternative backup solutions for Linux environments.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/sql-server-hybrid-benefit.md
...ain/articles/azure-vmware/sql-server-hybrid-benefit.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
Despite the title and description mentioning Linux subscriptions, the documentation content and examples focus almost exclusively on Windows Server and SQL Server workloads, tools, and migration scenarios. There are no concrete examples, migration guides, or configuration steps for Linux workloads or Linux-based hybrid benefit usage. All 'Next steps' links and detailed sections are centered on Microsoft SQL Server and Windows Server technologies, with no Linux equivalents provided.
Recommendations
- Add concrete examples and migration guides for Linux workloads using Azure Hybrid Benefit, such as migrating RHEL, SUSE, or Ubuntu VMs to Azure VMware Solution.
- Include configuration steps or links for enabling Azure Hybrid Benefit with Linux subscriptions, similar to the detailed SQL Server/Windows Server sections.
- Provide parity in 'Next steps' by adding Linux-focused guides (e.g., 'Migrate Linux VM to Azure VMware Solution', 'Enable Azure Hybrid Benefit for Linux workloads').
- Mention Linux tools and patterns (e.g., cloud-init, SSH, Linux clustering solutions) where relevant, not just Windows-specific technologies.
- Ensure Linux is not only mentioned in the introduction but is represented throughout the documentation with actionable guidance.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/tutorial-access-private-cloud.md
...articles/azure-vmware/tutorial-access-private-cloud.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively describes creating and using a Windows VM as the jump box for accessing the Azure VMware Solution private cloud. All instructions, screenshots, and references are for Windows, with no mention of Linux alternatives or examples. The guidance for connecting to the VM links only to Windows-specific documentation, and there is no discussion of using Linux VMs, SSH, or Linux-based browsers/tools.
Recommendations
- Add a parallel section describing how to create a Linux VM as a jump box, including screenshots and field values.
- Provide instructions and links for connecting to a Linux VM (e.g., using SSH from the Azure portal or a local terminal).
- Include examples of accessing vCenter Server and NSX Manager from a Linux VM (e.g., using Firefox or Chrome on Linux).
- Mention that either Windows or Linux VMs can be used as jump boxes, and discuss pros/cons or considerations for each.
- Ensure that all steps and screenshots have Linux equivalents where applicable, or note any limitations.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/use-hcx-run-commands.md
...lob/main/articles/azure-vmware/use-hcx-run-commands.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell-style cmdlets (e.g., Restart-HcxManager, Set-HcxScaledCpuAndMemorySetting) and the Azure portal UI, both of which are Windows-centric tools and patterns. There are no Linux shell/CLI examples, nor are Linux-native tools or workflows mentioned. The documentation assumes familiarity with PowerShell and Windows paradigms, and does not provide parity for Linux users.
Recommendations
- Provide equivalent Linux shell (bash/CLI) commands or scripts for each operation, if supported.
- Mention and document any Linux-native tools or APIs that can be used to perform the same tasks.
- If only PowerShell is supported, clarify this limitation explicitly and provide guidance for Linux users (e.g., using PowerShell Core on Linux).
- Reorder or supplement examples so that Linux and Windows approaches are presented equally, not Windows-first.
- Include screenshots or walkthroughs using cross-platform tools where possible.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/using-run-command.md
...s/blob/main/articles/azure-vmware/using-run-command.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing PowerShell cmdlets as the mechanism for Run Command operations, without mentioning or providing examples for Linux shells or tools. There are no Bash, shell script, or Linux-native command examples, and the term 'cmdlet' (specific to PowerShell) is used throughout. This may give the impression that Run Command is only accessible or relevant to Windows/PowerShell users, and does not address Linux administrators' needs.
Recommendations
- Clarify whether Run Command supports only PowerShell or if Bash/shell scripts are also supported. If Linux shells are supported, provide equivalent examples using Bash or shell scripts.
- Use more neutral terminology such as 'script' or 'command' instead of 'cmdlet' where possible, or clarify that 'cmdlet' refers to PowerShell and mention Linux equivalents if available.
- Add explicit instructions or examples for Linux users, including how to use Run Command with Linux VMs or environments, and how to view execution status for Linux-based scripts.
- If Run Command is Windows/PowerShell-only by design, state this limitation clearly at the beginning of the documentation to set expectations for Linux users.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-custom-domain.md
.../main/articles/azure-web-pubsub/howto-custom-domain.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell/Windows examples are presented before Bash/Linux equivalents (e.g., in the Health API verification section, PowerShell is the first tab). The use of 'curl.exe' and 'PS C:\>' prompt in examples further emphasizes Windows-centric instructions. There are no explicit Linux-specific instructions or screenshots, and the Azure Portal screenshots do not clarify cross-platform parity. The documentation does not mention Linux tools or workflows outside of the Bash/cURL example, and Windows patterns (such as PowerShell) are prioritized.
Recommendations
- Present Bash/Linux examples before or alongside PowerShell/Windows examples, or randomize their order to avoid implicit prioritization.
- Include explicit instructions or notes for Linux users, such as command-line differences, certificate management, and DNS configuration.
- Add Linux-specific screenshots or clarify that the Azure Portal UI is platform-agnostic.
- Avoid using Windows-specific prompts (e.g., 'PS C:\>') in generic examples; use neutral prompts or include both Windows and Linux prompts.
- Mention cross-platform compatibility for all command-line instructions and tools.
- Where relevant, provide guidance for Linux-native certificate creation and management.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-move-across-regions.md
...articles/azure-web-pubsub/howto-move-across-regions.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing detailed instructions and examples exclusively for Azure PowerShell, which is most commonly used on Windows. It references Windows-specific tools (e.g., Notepad for editing JSON files) and omits equivalent Linux/macOS command-line examples (such as Azure CLI or cross-platform editors). The PowerShell workflow is presented as the only scripting alternative to the portal, with no mention of Linux-friendly options. The order of presentation also puts Windows-centric methods before any cross-platform alternatives.
Recommendations
- Add Azure CLI examples for all steps currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Replace or supplement 'notepad' with cross-platform editors (e.g., 'nano', 'vim', 'code') or generic instructions for editing JSON files.
- Explicitly mention that PowerShell Core is available cross-platform, or clarify the instructions for Linux/macOS users.
- Provide bash shell command equivalents for resource group and template management.
- Reorder sections or provide parallel instructions so that Linux/macOS users do not feel secondary to Windows users.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-secure-rotate-access-key.md
...les/azure-web-pubsub/howto-secure-rotate-access-key.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation page primarily describes rotating access keys via the Azure portal, a web-based tool, and mentions the Azure CLI only as a future option. There are no command-line examples, and no Linux-specific instructions or parity with Windows tools. The Azure portal is often associated with Windows workflows, and there is no mention of Linux shells or automation approaches.
Recommendations
- Add Azure CLI examples for rotating access keys, including command-line instructions that work on both Windows and Linux.
- Explicitly mention that the Azure portal is web-based and platform-agnostic to avoid the perception of Windows bias.
- When Azure CLI support is available, provide both PowerShell and Bash (Linux/macOS) command examples.
- Include notes or links for automating key rotation using cross-platform tools (e.g., Bash scripts, Azure CLI in Linux environments).
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md
...icles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides credential setup instructions for both Linux/macOS and Windows, but Windows instructions (cmd) are presented after Linux/macOS (bash). There are no PowerShell examples, but the Windows example uses cmd syntax. The rest of the documentation uses bash commands for installation and usage, which are suitable for Linux/macOS and also work in Windows environments with WSL or Git Bash, but there are no explicit instructions or examples for PowerShell or native Windows environments beyond setting environment variables. There is a slight bias toward bash/Linux in command examples, and Windows users may need more guidance for running Node.js scripts and npm commands in native Windows terminals.
Recommendations
- Add PowerShell examples for setting environment variables and running commands, as many Windows users prefer PowerShell over cmd.
- Clarify that bash commands can be run in Windows using WSL, Git Bash, or similar tools, and provide native Windows alternatives where appropriate.
- Ensure parity in examples by providing both Linux/macOS and Windows (cmd and PowerShell) instructions for all steps, not just environment variable setup.
- Explicitly mention any Windows-specific considerations for running Node.js/npm commands (e.g., path differences, administrative permissions).
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-serverless-iot.md
...n/articles/azure-web-pubsub/tutorial-serverless-iot.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The tutorial demonstrates some Windows bias, primarily in the tooling and troubleshooting sections. The documentation references the Azure Storage Emulator, which is a Windows-only tool, as the recommended solution for local storage emulation. There is no mention of Linux alternatives (such as Azurite) or cross-platform instructions for storage emulation. The troubleshooting note for the Event Hub trigger only references the Storage Emulator and links to Windows-centric documentation. While most CLI and function examples are cross-platform, the absence of Linux-specific guidance for local development and emulation is notable.
Recommendations
- Explicitly mention Azurite as the recommended cross-platform storage emulator for local development, and provide installation and usage instructions for Linux/macOS.
- Update troubleshooting notes to reference both Storage Emulator (Windows) and Azurite (Linux/macOS), with appropriate links.
- Ensure all tool recommendations and troubleshooting steps include Linux/macOS equivalents or alternatives.
- Where possible, clarify that all CLI commands and function tools work on both Windows and Linux, and highlight any platform-specific caveats.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/about-azure-vm-restore.md
...cs/blob/main/articles/backup/about-azure-vm-restore.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the method to recreate VMs after restoring encrypted disks, and by linking only to Windows-specific encrypted VM documentation (including Microsoft Entra ID scenarios). There are no Linux-specific examples, instructions, or links for restoring encrypted Linux VMs, nor are Linux tools or command-line patterns mentioned. The restore process for encrypted VMs is described only for Windows, and PowerShell is presented as the default tool.
Recommendations
- Add equivalent instructions and examples for restoring encrypted Linux VMs, including references to Linux-specific documentation.
- Mention and provide examples using Linux command-line tools (such as Azure CLI or Bash scripts) for VM recreation after disk restore.
- Ensure that links to encrypted VM restore scenarios include both Windows and Linux guides.
- Avoid presenting Windows/PowerShell as the only or primary method; instead, provide parity by listing Linux methods alongside Windows methods.
- Clarify in each scenario whether the instructions apply to both Windows and Linux VMs, or provide separate sections for each OS.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/active-directory-backup-restore.md
...ain/articles/backup/active-directory-backup-restore.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, specifically Windows Server domain controllers. All examples and procedures reference Windows tools (PowerShell, ntdsutil.exe), Windows-specific concepts (Directory Services Restore Mode, tombstone lifetime for Windows Server), and do not mention or provide guidance for Linux-based domain controllers or cross-platform scenarios. The documentation assumes the use of Windows Server and does not offer Linux equivalents, examples, or considerations.
Recommendations
- Explicitly state that the guidance is for Windows-based Active Directory and clarify whether Azure Backup supports Linux-based domain controllers (such as Samba AD DC).
- If Linux-based Active Directory domain controllers (e.g., Samba) are supported, provide equivalent backup and restore procedures, including Linux command-line examples and tools.
- Include a section comparing Windows and Linux domain controller backup/restore scenarios, highlighting any differences and limitations.
- Mention cross-platform considerations for hybrid environments where both Windows and Linux domain controllers may exist.
- If Linux is not supported, add a note explaining this and suggest alternative backup strategies for Linux-based AD environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/archive-tier-support.md
...docs/blob/main/articles/backup/archive-tier-support.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page lists PowerShell as a supported client before CLI, and provides no explicit Linux or cross-platform examples. The only command-line interface mentioned by name is PowerShell, which is Windows-centric, while the Azure CLI (which is cross-platform) is listed after PowerShell. There are no Linux-specific instructions, screenshots, or examples, and no mention of Bash or Linux tools. This suggests a Windows-first and PowerShell-heavy bias, with missing Linux parity in examples and guidance.
Recommendations
- Provide explicit Linux/Bash/Azure CLI examples alongside or before PowerShell examples, ensuring parity.
- Include screenshots or walkthroughs using Azure CLI on Linux or macOS, not just the Azure portal or PowerShell.
- Clarify that Azure CLI is cross-platform and provide links or instructions for Linux users.
- If there are any differences in behavior or prerequisites on Linux, document them clearly.
- Consider reordering the 'Supported clients' section to list Azure CLI before PowerShell, or group them together as 'Command-line tools'.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/automation-backup.md
...re-docs/blob/main/articles/backup/automation-backup.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell first when listing automation methods and in scenario explanations. Practical examples and workflow descriptions focus on PowerShell and Azure Automation Runbooks, with no explicit Linux shell (Bash) or cross-platform CLI examples provided. While Azure CLI is mentioned, there are no concrete Bash/Linux shell command examples, and the automation scenarios default to Windows-centric tools and patterns.
Recommendations
- Provide explicit Bash/Linux shell examples alongside or before PowerShell examples in all automation scenarios.
- When listing automation methods, alternate the order or list CLI/Bash before PowerShell to avoid Windows-first bias.
- Include sample scripts and workflows using Azure CLI in Bash for common tasks such as configuring backups, exporting data, and automating responses.
- Highlight cross-platform tools (e.g., Ansible, Terraform) with practical Linux-based examples, not just links.
- Clarify that all automation methods are supported on both Windows and Linux, and add notes or sections for Linux users where appropriate.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-backup-glossary.md
...ocs/blob/main/articles/backup/azure-backup-glossary.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The Azure Backup glossary page demonstrates a Windows bias in several ways. Windows-specific technologies and tools (such as VSS, DPM, MABS, MARS agent, System State backup, and references to Windows clients) are mentioned frequently and often before or instead of Linux equivalents. The only explicit mention of Linux is in the context of application-consistent backups, where 'pre or post scripts for Linux' is briefly noted, but no further detail or links are provided. There are references to Azure PowerShell and ARM templates, but Linux-native tools or workflows are not highlighted. There are no Linux-specific backup scenarios, tools, or examples, and the glossary omits terms or links relevant to Linux backup practices.
Recommendations
- Add Linux-specific backup terms and scenarios, such as describing how Azure Backup interacts with Linux VMs, file systems, and application consistency (e.g., pre/post scripts, fsfreeze, etc.).
- Provide equal detail and links for Linux backup mechanisms as are given for Windows (e.g., link to documentation on Linux application-consistent backups, Linux agent installation, and recovery processes).
- Include references to Linux-native tools and commands where relevant, and ensure that examples and explanations are not Windows-centric.
- When describing features like VSS, also mention and link to Linux equivalents or approaches, and avoid presenting Windows tools first or exclusively.
- Add glossary entries for Linux-specific backup agents, scripts, or integration points if applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-data-lake-storage-backup-configure-quickstart-arm-bicep.md
...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides only PowerShell-based deployment instructions for both ARM and Bicep templates, specifically referencing Azure Cloud Shell and the New-AzResourceGroupDeployment cmdlet. There are no examples using Azure CLI, Bash, or Linux-native tooling. The deployment steps are written with a Windows/PowerShell-first perspective, and there is no mention of Linux or cross-platform alternatives.
Recommendations
- Add Azure CLI (az deployment group create) examples for deploying both ARM and Bicep templates, alongside or before PowerShell examples.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide Bash/CLI instructions.
- Ensure that all scripts and commands are cross-platform or provide platform-specific alternatives (e.g., Bash for Linux/macOS, PowerShell for Windows).
- Update the documentation to avoid implying PowerShell is the default or only supported method for deployment.
- Where possible, use generic terms like 'run the following command' instead of 'run the following PowerShell script', unless only PowerShell is supported.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-data-lake-storage-backup-support-matrix.md
...ackup/azure-data-lake-storage-backup-support-matrix.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page references PowerShell and the Azure portal as primary configuration methods, with only a brief mention of Azure CLI. There are no explicit Linux or cross-platform command examples, and the ordering of tools (Azure portal, PowerShell, then Azure CLI) suggests a Windows-first bias. No Linux-specific tools, shell commands, or considerations are provided.
Recommendations
- Provide explicit, step-by-step examples using Azure CLI for all major operations (configuration, restore, management), and ensure these are presented alongside or before PowerShell examples.
- Include Linux/macOS shell command examples where relevant, especially for scripting or automation scenarios.
- Reorder tool mentions to avoid always listing PowerShell before Azure CLI; consider grouping Azure CLI and PowerShell together as 'command-line options' or alternating their order.
- Add a section or notes highlighting parity and any differences between Windows and Linux environments for backup operations.
- Ensure that screenshots, code snippets, and troubleshooting steps are platform-agnostic or include both Windows and Linux variants.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup-concept.md
...kup/azure-kubernetes-service-cluster-backup-concept.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits subtle Windows bias. In the 'Next steps' section, Azure PowerShell is listed before Azure CLI for backup operations, and both backup and restore examples reference PowerShell, which is more commonly used on Windows. There are no explicit Linux shell (bash) or cross-platform command-line examples, and no mention of Linux-specific tools or patterns. The documentation assumes use of the Azure portal and PowerShell, which may not be the primary tools for Linux users. There are no explicit bash or shell script examples, and the documentation does not clarify cross-platform parity for command-line operations.
Recommendations
- Ensure all command-line examples are provided for both Azure CLI (bash/shell) and Azure PowerShell, with CLI examples listed first or equally.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
- Add bash/shell script examples for common operations (e.g., installing the Backup Extension, enabling Trusted Access) alongside PowerShell examples.
- Where the Azure portal is referenced, clarify that it is web-based and platform-agnostic.
- Review the order of tool mentions in the 'Next steps' section to avoid implying Windows-first workflows.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup.md
...cles/backup/azure-kubernetes-service-cluster-backup.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the only CLI alternative to the 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 configuration or management. The documentation does not mention or provide parity for Linux users, who typically use Azure CLI and Bash scripts for automation.
Recommendations
- Add Azure CLI examples for all backup and restore operations, including installation of the Backup extension, creation of Backup vaults, policies, and backup configuration.
- Reference Azure CLI as an alternative to PowerShell in the introduction and 'Next steps' sections, ensuring both Windows and Linux users are addressed.
- Include Bash script samples for deploying backup hooks and managing AKS backups, in addition to the existing kubectl example.
- Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux environments.
- Ensure screenshots and instructions do not assume use of Windows-only tools or UI patterns.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-file-data.md
...re-docs/blob/main/articles/backup/back-up-file-data.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented towards Windows environments. All instructions, terminology, and referenced tools (e.g., MABS console, Volume Shadow Copy Service, Data Deduplication, SAN hardware snapshots) are Windows-specific. There are no examples, instructions, or notes for Linux systems, nor any mention of Linux client support, agent installation, or recovery scenarios. This creates a strong Windows bias and leaves Linux administrators without guidance.
Recommendations
- Add explicit sections or notes describing support for Linux machines, including any limitations or prerequisites.
- Provide step-by-step examples for backing up and recovering file data from Linux servers/clients, including agent installation and configuration.
- Mention Linux-specific considerations (e.g., supported file systems, required packages, SELinux/AppArmor notes, etc.).
- If Linux is not supported, clearly state this early in the prerequisites.
- Reference Linux equivalents for Windows features (e.g., alternatives to VSS, deduplication, etc.), or clarify if such features are unavailable.
- Include screenshots or CLI examples relevant to Linux where applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-architecture.md
...-docs/blob/main/articles/backup/backup-architecture.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. Backup scenarios and tooling are described primarily for Windows environments, with the MARS agent and DPM/MABS servers only supporting Windows. Linux support is either absent or mentioned only to note its lack of support. Examples, agent descriptions, and architecture diagrams focus on Windows tools and workflows, with no equivalent Linux guidance or parity in backup methods for on-premises machines.
Recommendations
- Add explicit sections describing backup options for on-premises Linux machines, including supported agents, workflows, and limitations.
- If Linux is not supported for certain backup scenarios (e.g., MARS agent), clarify alternative solutions or recommend third-party/complementary Azure services for Linux backup.
- Provide Linux-centric examples and diagrams where applicable, such as backup of Azure Linux VMs, and ensure parity in feature tables.
- Mention Linux tools and patterns (e.g., CLI commands, cron-based scheduling, integration with native Linux backup utilities) alongside Windows/Powershell equivalents.
- Review all 'next steps' and scenario lists to include Linux-focused guidance and links, not just Windows and Windows-centric tools.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-about-mars.md
...s/blob/main/articles/backup/backup-azure-about-mars.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively describes backup and recovery scenarios for Windows systems, referencing Windows-specific features (e.g., VSS, USN change journal, System State) and does not mention Linux support or provide Linux examples. All instructions, terminology, and supported scenarios are Windows-centric, with no parity or guidance for Linux environments.
Recommendations
- Clearly state in the introduction and support matrix whether the MARS agent supports Linux systems. If not, provide alternative solutions or links for Linux backup to Azure.
- If Linux support is available or planned, add equivalent Linux examples, instructions, and supported scenario tables.
- Avoid using only Windows-specific terminology (e.g., VSS, System State) without clarifying their scope or providing Linux equivalents.
- Ensure that any diagrams, screenshots, or walkthroughs include Linux where applicable, or explicitly note platform limitations.
- Mention and link to Azure backup solutions for Linux (such as Azure Backup Server, Azure VM backup for Linux, or third-party options) to guide Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server-troubleshoot.md
...ckup/backup-azure-alternate-dpm-server-troubleshoot.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure Backup Server and Data Protection Manager (DPM), which are Windows-based tools. There are no examples or troubleshooting steps for Linux-based backup solutions, and the language assumes the use of Windows Server or Windows Client. No Linux equivalents or cross-platform considerations are mentioned.
Recommendations
- Include troubleshooting steps or references for Linux-based backup solutions, such as Azure Backup integration with Linux servers.
- Clarify in the introduction that the guidance is specific to Windows environments, and provide links to Linux-specific documentation if available.
- Add examples or notes for users managing backups on Linux systems, or explicitly state if Azure Backup Server does not support Linux.
- Ensure parity by mentioning Linux tools and workflows where applicable, or by providing a comparison table of supported platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server.md
...n/articles/backup/backup-azure-alternate-dpm-server.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively describes recovery using Azure Backup Server and Data Protection Manager (DPM), which are Windows-only tools. All instructions and screenshots reference the Windows GUI and workflow, with no mention of Linux equivalents, CLI options, or cross-platform alternatives. There are no Linux-specific examples or guidance, and the documentation assumes a Windows environment throughout.
Recommendations
- Add information about recovering data from Linux servers or workloads, if supported by Azure Backup.
- Include CLI-based recovery steps (e.g., using Azure CLI, az backup commands, or PowerShell Core on Linux) if available.
- Explicitly state platform limitations (e.g., 'Azure Backup Server and DPM are Windows-only; for Linux workloads, use XYZ method').
- Provide parity in examples and screenshots for Linux environments, or link to relevant Linux recovery documentation.
- Mention and link to alternative backup and recovery solutions for Linux, such as Azure Backup for Linux VMs, and provide guidance for those scenarios.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-cloud-as-tape.md
...n/articles/backup/backup-azure-backup-cloud-as-tape.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing System Center Data Protection Manager (DPM), a Windows-only tool, and linking to a 'backup-windows-with-mars-agent' guide as the next step. There are no Linux-specific tools, examples, or instructions provided, nor are Linux backup scenarios mentioned. The documentation implicitly assumes a Windows environment and does not address Linux users or their needs.
Recommendations
- Include equivalent Linux backup solutions (e.g., Azure Backup integration with Linux servers, or mention of Azure Backup Server support for Linux).
- Provide Linux-specific examples and screenshots for backup and retention policy configuration.
- Add links to documentation for backing up Linux machines with Azure Backup.
- Avoid referencing only Windows tools (like DPM) without mentioning Linux alternatives or clarifying platform support.
- Ensure that 'Next steps' includes guides for both Windows and Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-exchange-server.md
...articles/backup/backup-azure-backup-exchange-server.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively describes backup procedures using System Center DPM, a Windows-only tool, and focuses on Microsoft Exchange (also Windows-only). All examples, instructions, and screenshots reference Windows interfaces and tools (e.g., DPM Administrator Console, Eseutil.exe, PowerShell). There are no Linux equivalents, alternative cross-platform tools, or even mentions of Linux-based Exchange alternatives. The documentation assumes a Windows environment throughout.
Recommendations
- Clearly state early in the documentation that the described solution is Windows-only and not applicable to Linux environments.
- If possible, provide references or links to cross-platform or Linux-compatible backup solutions for email servers (e.g., using Azure Backup with Linux servers, or alternatives for backing up Postfix/Dovecot).
- Include a comparison table or section outlining the lack of Linux support and suggesting next steps for Linux users.
- Avoid implying that the solution is generally applicable to all environments; specify the Windows focus in the title and introduction.
- If any part of Azure Backup supports Linux workloads, add a 'See also' or 'Related content' section with links to those resources.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-import-export.md
...n/articles/backup/backup-azure-backup-import-export.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily biased toward Windows environments. All instructions, prerequisites, and tools (such as the MARS agent, AzureOfflineBackupDiskPrep utility, and Azure PowerShell) are Windows-specific. There are no examples or guidance for Linux systems, nor is there mention of Linux compatibility or alternatives. The workflow assumes use of Windows-only tools and patterns, such as elevated command prompts, BitLocker, and Internet Explorer/Microsoft Edge.
Recommendations
- Clearly state in the prerequisites and introduction whether Linux is supported or not. If not, provide a link to Linux-compatible workflows or alternatives.
- If Linux is supported, add parallel instructions and examples for Linux systems, including command-line equivalents (e.g., Bash scripts, az CLI usage) and supported disk encryption methods.
- Mention Linux tools and patterns (such as mounting disks, using Linux-compatible browsers, or alternative disk preparation utilities) where appropriate.
- If the MARS agent and AzureOfflineBackupDiskPrep utility are Windows-only, explicitly call this out and provide guidance for Linux users (e.g., using Azure Data Box or other supported methods).
- Avoid referencing Windows tools (e.g., PowerShell, BitLocker, Internet Explorer) exclusively; when possible, provide cross-platform alternatives or note platform limitations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-server-import-export.md
...les/backup/backup-azure-backup-server-import-export.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows environments. All instructions, tools, and workflows are centered around Windows-based products (DPM, MABS), and utilities (AzureOfflineBackupDiskPrep.exe), with prerequisites such as Microsoft Edge/Internet Explorer, BitLocker, and Azure PowerShell. There are no Linux equivalents, examples, or mentions of cross-platform alternatives. The documentation assumes the use of Windows servers and clients throughout.
Recommendations
- Provide explicit statements about Linux support or lack thereof for DPM/MABS offline seeding workflows.
- If Linux is not supported, clarify this early in the documentation to set expectations.
- If any steps can be performed on Linux (e.g., preparing disks, copying data), provide equivalent Linux commands and tools (such as using dd, cryptsetup for encryption, or Azure CLI).
- Mention and link to any Linux-compatible backup solutions for Azure, if available.
- If the AzureOfflineBackupDiskPrep utility is Windows-only, suggest or develop a cross-platform version or script.
- Avoid requiring Windows-specific browsers (Edge/IE11) and instead recommend cross-platform browsers where possible.
- Include a comparison table or section outlining OS support for the described workflow.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sharepoint-mabs.md
...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments. All instructions, examples, and tooling references assume Windows servers, Windows command-line tools (CMD, Registry Editor), and Windows-specific paths and permissions. There are no examples or guidance for Linux-based SharePoint deployments, nor for using Linux-native tools or patterns. The documentation does not mention Linux compatibility or alternatives, and all administrative tasks are described with Windows-centric terminology and steps.
Recommendations
- Explicitly state platform requirements and limitations (e.g., if MABS only supports Windows-based SharePoint farms, clarify this early in the documentation).
- If Linux support is possible, provide equivalent instructions for Linux environments, including command-line examples, file paths, and permissions.
- Mention whether SharePoint on Linux (e.g., via containers) is supported or not, and provide guidance for such scenarios if applicable.
- Where possible, offer cross-platform alternatives for monitoring, notifications, and backup/restore operations (e.g., using REST APIs, CLI tools, or scripts that work on Linux).
- Add a section comparing Windows and Linux support, or explicitly state that only Windows is supported if that is the case.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sharepoint.md
...main/articles/backup/backup-azure-backup-sharepoint.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
powershell_heavy
windows_first
Summary
The documentation is heavily biased towards Windows environments. It exclusively references System Center Data Protection Manager (DPM), a Windows-only tool, and provides no mention of Linux-based backup solutions or cross-platform alternatives. The only automation example referenced is via PowerShell, and there are no Linux command-line or tool examples. All instructions and screenshots are based on Windows tools and UI, with no parity for Linux users.
Recommendations
- Include information about cross-platform or Linux-compatible backup solutions for SharePoint, if available (e.g., Azure Backup Server on Linux, or third-party tools).
- Provide equivalent Linux command-line examples (e.g., Bash scripts, Azure CLI) for backup and restore operations, where possible.
- Mention and link to any Linux-based documentation or tools that can be used for similar backup scenarios.
- If DPM is required and only available on Windows, clearly state this limitation at the beginning of the article and suggest alternatives for Linux environments.
- Add automation examples using Azure CLI or REST API, not just PowerShell.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sql.md
...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily biased toward Windows environments. It exclusively references Data Protection Manager (DPM), a Windows-only tool, and all examples, screenshots, and instructions are based on the Windows GUI. There are no Linux equivalents or examples, and Linux-based backup tools or scenarios are not mentioned. The only automation reference is to PowerShell, further reinforcing the Windows-centric approach.
Recommendations
- Include information about Linux-based backup solutions for SQL Server (such as Azure Backup integration with Linux servers or third-party tools).
- Provide parallel instructions or links for backing up SQL Server on Linux to Azure, if supported.
- Mention limitations or alternatives for users running SQL Server on Linux.
- Add automation examples using cross-platform tools (such as Azure CLI or REST API), not just PowerShell.
- Clarify early in the article that the documented workflow is specific to Windows/DPM, and point Linux users to relevant resources.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-data-protection-use-rest-api-create-update-postgresql-policy.md
...rotection-use-rest-api-create-update-postgresql-policy.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates Windows bias primarily through repeated references to PowerShell objects as the default or primary way to conceptualize and configure backup policies. The only non-REST API tool mentioned is PowerShell, with no mention of Linux-native tools, CLI, or Bash scripting. The phrase 'default PowerShell object' is used to describe the policy structure, suggesting a Windows-centric approach. There are no Linux-specific examples, nor is there guidance for Linux users on how to perform equivalent operations outside of REST or PowerShell.
Recommendations
- Add Azure CLI examples for creating and managing backup policies, as the CLI is cross-platform and widely used on Linux.
- Replace or supplement references to 'default PowerShell object' with neutral or cross-platform terminology, such as 'policy definition' or 'policy JSON object'.
- Explicitly mention that all REST API operations can be performed from any platform, and provide sample Bash/cURL commands for Linux users.
- If scripting examples are included, provide both PowerShell and Bash/cURL equivalents.
- Include a section or note for Linux/macOS users, clarifying supported tools and providing links to relevant cross-platform documentation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql-overview.md
...es/backup/backup-azure-database-postgresql-overview.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively recommending the use of the pgAdmin GUI tool for database operations, without mentioning or providing examples for Linux-native or cross-platform command-line tools such as psql. All screenshots and workflow steps are centered around the Azure Portal and pgAdmin, which are more commonly used on Windows. There are no examples using Linux CLI tools, and the documentation does not mention or prioritize Linux or cross-platform alternatives. This can make it less accessible for Linux users or those who prefer command-line workflows.
Recommendations
- Add equivalent examples using the psql command-line tool for tasks such as granting privileges, connecting to the database, and creating users/databases.
- Include instructions and screenshots for performing operations via the Azure CLI (az), which is cross-platform, alongside or before GUI-based instructions.
- Explicitly mention that pgAdmin is available on Linux and macOS, and provide installation links for those platforms.
- Wherever possible, provide both GUI (pgAdmin/Azure Portal) and CLI (psql/Azure CLI) instructions in parallel.
- Highlight any platform-specific differences or prerequisites for Linux users, such as firewall configuration or client installation steps.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dpm-introduction.md
.../main/articles/backup/backup-azure-dpm-introduction.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented towards Windows environments. All examples, prerequisites, and instructions assume the use of Windows tools (e.g., PowerShell, .NET Framework, .exe installers) and the DPM server itself, which is a Windows-only product. There are no examples or instructions for Linux environments, and Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
- Explicitly state that DPM is a Windows-only product early in the documentation to set expectations for cross-platform users.
- If Azure Backup supports Linux workloads via other agents or methods, provide links or references to those alternatives for Linux users.
- Where possible, mention Linux backup options (such as Azure Backup for Linux VMs or MARS agent alternatives) and link to their documentation.
- If any steps (such as downloading vault credentials or configuring storage) are relevant to both Windows and Linux, provide parallel Linux examples or clarify platform applicability.
- Add a section summarizing backup options for non-Windows workloads to help guide Linux administrators.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-encrypted-vm-troubleshoot.md
...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary CLI example for configuring permissions, without mentioning Linux alternatives such as Azure CLI or Bash. No Linux-specific instructions or examples are provided for troubleshooting or automation, and Windows tooling (PowerShell) is mentioned before any cross-platform solutions.
Recommendations
- Include equivalent Linux/Unix instructions using Azure CLI and Bash where PowerShell is referenced.
- Add explicit examples for configuring Key Vault permissions and restoring VMs using Azure CLI commands.
- Ensure troubleshooting steps and automation guidance are platform-neutral or provide both Windows and Linux options.
- Review linked pages to confirm Linux parity in referenced step-by-step instructions.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-exchange-mabs.md
...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows environments, specifically Microsoft Exchange Server and Azure Backup Server (MABS), which are Windows-only products. All instructions, screenshots, and tool references (such as Eseutil.exe, Ese.dll, and file paths like C:\Program Files\...) are Windows-centric. There are no examples, notes, or guidance for Linux-based Exchange alternatives or backup scenarios, nor any mention of Linux-compatible tools or commands.
Recommendations
- Clarify early in the documentation that MABS and Exchange Server are Windows-only products, and explicitly state platform requirements.
- If Azure Backup supports Linux workloads, provide parallel documentation or links for backing up Linux-based mail servers (e.g., Postfix, Dovecot) using Azure Backup.
- Where possible, mention Linux equivalents for backup and recovery (such as using Azure Backup Agent for Linux or third-party tools).
- Include a section on limitations or alternatives for Linux users, and direct them to relevant resources.
- Avoid hardcoding Windows file paths and tools without noting platform constraints.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-manage-mars.md
.../blob/main/articles/backup/backup-azure-manage-mars.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only backup solution. All instructions, screenshots, and tool references are for Windows environments (e.g., MARS console, Windows file paths, use of %ProgramFiles%, and Windows-specific antivirus configuration). There are no Linux or cross-platform examples, nor any mention of Linux equivalents or alternative approaches for non-Windows systems. This creates a strong Windows bias and excludes Linux administrators from relevant guidance.
Recommendations
- Clearly state at the beginning of the documentation that MARS Agent is only supported on Windows, and provide links to Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI/agent-based solutions for Linux).
- Where possible, include a comparison table or section that outlines backup and recovery options for both Windows and Linux, with links to relevant documentation for Linux.
- If any features or workflows are available for Linux (e.g., via Azure CLI, REST API, or other agents), provide equivalent examples and instructions.
- Avoid using Windows-specific terminology (such as %ProgramFiles%) without clarification, or provide Linux path equivalents where relevant.
- Add a 'Linux support' or 'Cross-platform considerations' section to clarify platform limitations and direct Linux users to appropriate resources.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitoring-built-in-monitor.md
...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority
View Details â
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 management guides specifically for Windows Server. There are no explicit Linux backup tool examples or instructions, and Windows tools are mentioned exclusively when discussing backup item visibility and naming conventions.
Recommendations
- Include examples and instructions for monitoring Linux-based backup workloads, such as Azure Backup for Linux VMs or native Linux backup agents.
- Reference Linux-compatible backup tools and workflows alongside Windows tools, ensuring parity in documentation.
- Add links to Linux-specific management guides and clarify any differences in monitoring or notification capabilities for Linux workloads.
- When discussing naming conventions or limitations, specify if these apply to Linux workloads or provide Linux-specific guidance if different.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-database.md
...blob/main/articles/backup/backup-azure-sql-database.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All examples, instructions, and tooling references are Windows-centric, including exclusive use of Windows service accounts, PowerShell scripts, Windows file paths, and SSMS (SQL Server Management Studio). There is no mention of Linux-based SQL Server VMs, nor any Linux-specific instructions or parity for backup configuration, permissions, or troubleshooting.
Recommendations
- Add explicit support and instructions for SQL Server on Linux VMs, including any differences in extension installation, service accounts, and permissions.
- Provide Linux command-line examples (e.g., Bash scripts, use of sqlcmd on Linux) alongside PowerShell examples.
- Document the location of configuration files and logs for Linux-based SQL Server VMs.
- Clarify whether the AzureBackupWindowsWorkload extension or an equivalent is available for Linux, and if not, state the limitation clearly.
- Include troubleshooting steps and permission-setting instructions for Linux environments (e.g., using chown/chmod, systemd service accounts).
- Ensure that all file path examples are provided in both Windows and Linux formats where applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-files-from-vm.md
.../articles/backup/backup-azure-restore-files-from-vm.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions, tools, and troubleshooting steps are consistently presented before Linux equivalents. Windows-specific tools (e.g., registry edits, Windows Explorer, .NET requirements) are described in detail, while Linux instructions are sometimes less detailed or presented after Windows. PowerShell is referenced as a primary automation method, and some troubleshooting (e.g., registry changes) is only described for Windows. Linux examples are present but often less emphasized or detailed.
Recommendations
- Present Linux and Windows instructions in parallel or in clearly separated, equally detailed sections, rather than always listing Windows first.
- Provide Linux troubleshooting steps with the same level of detail as Windows (e.g., registry edits for Windows vs. config file changes for Linux).
- Include Linux automation examples (e.g., Bash scripts or CLI commands) alongside PowerShell references.
- Ensure that all screenshots and examples are balanced between Windows and Linux environments.
- Mention Linux tools and patterns (e.g., file managers, mount utilities) with the same prominence as Windows tools.
- Where possible, avoid language that implies Windows is the default or primary platform.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-system-state.md
...n/articles/backup/backup-azure-restore-system-state.md
High Priority
View Details â
Detected Bias Types
windows_only
windows_tools
missing_linux_example
windows_first
Summary
The documentation is exclusively focused on restoring System State for Windows Server using Azure Backup. All instructions, examples, and tools referenced (MARS agent, Windows Server Backup, wbadmin, Win RE) are specific to Windows environments. There are no references to Linux equivalents, nor any mention of how to perform similar operations on Linux servers. The documentation assumes the reader is using Windows and does not provide parity for Linux users.
Recommendations
- Add a section or a separate article for restoring system state or equivalent on Linux servers using Azure Backup, if supported.
- Include Linux-specific tools and commands (e.g., rsync, tar, dd, or native Linux backup/restore utilities) where applicable.
- If Azure Backup supports Linux VM backup and restore, provide step-by-step instructions for Linux, including screenshots and command-line examples.
- Clearly indicate at the beginning of the article that the instructions are Windows-specific, and provide links to Linux documentation if available.
- Ensure that future documentation covers both Windows and Linux scenarios, or explicitly states platform limitations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-key-secret.md
...ain/articles/backup/backup-azure-restore-key-secret.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell cmdlets, and file paths are given in Windows format (e.g., C:\ paths). There are no examples using Bash, Azure CLI, or cross-platform scripting. Even when Linux VMs are mentioned, the instructions still use PowerShell, which is not the default or most common shell on Linux. There is no guidance for users who may be working from a Linux or macOS environment.
Recommendations
- Provide equivalent examples using Azure CLI (az commands) and Bash scripting, which are native to Linux and cross-platform environments.
- Use platform-agnostic file paths or show both Windows and Linux path formats in examples.
- Explicitly mention and provide steps for performing the same operations from Linux/macOS, including prerequisites such as installing Azure CLI.
- Reorganize sections so that instructions for Linux and Windows are presented with equal prominence, or group platform-specific instructions clearly.
- Add notes clarifying which steps are platform-specific and provide alternatives where necessary (e.g., for downloading blobs or manipulating JSON files).
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-rbac-rs-vault.md
...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. It explicitly references Windows-specific backup tools (Azure Backup agent client UI, System Center Data Protection Manager UI, Azure Backup Server UI) and on-premises Windows Server/client registration, without mentioning Linux equivalents or cross-platform backup agents. Windows tools and scenarios are mentioned exclusively in several places, and there are no examples or guidance for Linux-based backup management or registration. The documentation does not provide parity for Linux server backup scenarios or mention Linux-specific tools or processes.
Recommendations
- Include references to Linux backup agents and management tools where applicable, such as Azure Backup for Linux VMs or third-party Linux backup solutions.
- Add examples and guidance for registering and managing backups for Linux servers, including any differences in role assignments or permissions.
- Mention Linux equivalents alongside Windows tools (e.g., if referencing Azure Backup agent for Windows, also reference Azure Backup for Linux or other supported Linux backup mechanisms).
- Ensure that on-premises backup scenarios cover both Windows and Linux environments, and clarify any platform-specific limitations or requirements.
- Review tables and descriptions to explicitly state support for Linux workloads and provide links to relevant documentation for Linux backup management.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-scdpm-troubleshooting.md
.../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows tools and patterns (e.g., 'net stop dpmra', NT AUTHORITY\SYSTEM, MARS agent), and does not provide any Linux-specific troubleshooting steps or examples. There are no mentions of Linux equivalents, nor are any Linux commands or environments addressed, despite the potential for cross-platform backup scenarios.
Recommendations
- Add troubleshooting steps and examples relevant to Linux environments, if Data Protection Manager or Azure Backup Server supports Linux workloads.
- Include Linux command-line equivalents (e.g., systemctl or service commands) alongside Windows commands like 'net stop/start'.
- Mention Linux-specific agents, permissions, and error messages where applicable.
- Clarify in the introduction or prerequisites if the product or documentation is Windows-only; if not, ensure Linux parity in all examples and troubleshooting steps.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-security-feature.md
.../main/articles/backup/backup-azure-security-feature.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
powershell_heavy
Summary
The documentation is heavily biased towards Windows environments. It exclusively discusses Microsoft-centric backup tools (MABS, DPM, MARS), which are Windows-only. All examples, workflows, and troubleshooting steps reference Windows tools and interfaces, with no mention of Linux equivalents or support. There are no Linux-specific instructions, commands, or scenarios, and the documentation does not clarify Linux support or alternatives. Even PowerShell commands are referenced without Bash or Linux CLI equivalents.
Recommendations
- Clearly state in the introduction whether Linux workloads are supported by these security features and, if not, provide links to Linux backup documentation.
- If Linux support exists, add equivalent examples and workflows for Linux, including CLI commands (e.g., Bash, az CLI) and Linux agent usage.
- Include troubleshooting steps and error messages relevant to Linux environments.
- Mention Linux backup tools (such as Azure Backup for Linux, if available) alongside Windows tools, and provide parity in feature descriptions.
- For PowerShell commands, provide equivalent Bash or shell commands where possible.
- Add a comparison table summarizing feature availability and steps for both Windows and Linux platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vm-migrate-enhanced-policy.md
...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
High Priority
View Details â
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 migration support, mentioning PowerShell before CLI, and omitting explicit Linux shell examples. The only command-line reference is to Azure CLI and PowerShell, with no Bash or Linux-specific instructions or screenshots. The portal instructions and screenshots are platform-neutral, but command-line guidance is not inclusive of Linux users.
Recommendations
- Add explicit Bash/Linux shell examples for CLI commands, showing usage in a Linux terminal.
- When mentioning command-line tools, list Azure CLI before PowerShell or present both together to avoid Windows-first ordering.
- Include notes or examples for Linux users, such as installation instructions for Azure CLI on Linux and any OS-specific considerations.
- Clarify that Azure CLI is cross-platform and provide sample commands in both Windows (PowerShell) and Linux (Bash) contexts.
- Add screenshots or terminal output examples from Linux environments where relevant.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vm-file-recovery-troubleshoot.md
...s/backup/backup-azure-vm-file-recovery-troubleshoot.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows troubleshooting steps and tools (such as File Explorer, 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 external links or summarized briefly. Windows scenarios are frequently presented before Linux equivalents, and some error resolutions provide only Windows-specific guidance or examples. Linux instructions are less detailed, sometimes missing direct command-line examples or GUI walkthroughs.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux scenarios, including relevant commands (e.g., mount, fdisk, lsblk, iscsiadm) and screenshots where applicable.
- Include Linux troubleshooting examples directly in the documentation, rather than referring to external links.
- Present Windows and Linux guidance in parallel, ensuring neither is consistently prioritized or described first.
- List Linux tools and patterns (e.g., GNOME Disks, CLI utilities) alongside Windows tools when discussing disk management and recovery.
- Add Linux-specific error codes and their resolutions where only Windows errors are currently described.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md
...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias by mentioning Windows-specific tools (Volume Shadow Copy Service - VSS) before Linux equivalents (fsfreeze) when describing backup consistency mechanisms. References to VM Agent and snapshot extension link only to Windows documentation, with no Linux-specific links or examples. There are no Linux command-line or tool examples, and Linux backup patterns (such as pre/post scripts) are only mentioned as a reason not to use crash-consistent backups, without further guidance.
Recommendations
- Provide equal prominence to Linux tools (e.g., fsfreeze) alongside Windows tools (VSS), including links to relevant Linux documentation.
- Include examples or references for both Windows and Linux VM Agent and snapshot extension documentation.
- Add Linux-specific backup scenarios, including guidance on using pre/post scripts and how crash-consistent backups interact with common Linux workloads.
- Ensure that any tool or pattern mentioned for Windows is matched with its Linux equivalent, and vice versa, to maintain parity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-encryption.md
...ob/main/articles/backup/backup-azure-vms-encryption.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page shows evidence of Windows bias. PowerShell is the only command-line example provided for identifying a VM's associated key vault, with no equivalent Linux/CLI example. In the section on ADE, Windows tools (BitLocker) are mentioned before Linux equivalents (dm-crypt). There are no explicit Linux shell or Azure CLI examples for common tasks, and the only code snippet for identifying key vaults uses PowerShell, which is more familiar to Windows users.
Recommendations
- Provide equivalent Azure CLI and/or Bash examples alongside PowerShell commands, especially for tasks like identifying a VM's associated key vault.
- When describing encryption technologies, mention Linux (dm-crypt) and Windows (BitLocker) tools in parallel, not always listing Windows first.
- Ensure that all automation and scripting instructions are available for both Windows (PowerShell) and Linux (Bash/CLI) users.
- Add explicit Linux-focused examples or callouts where workflows or commands differ.
- Review screenshots and UI instructions to ensure they are not overly Windows-centric (e.g., referencing right-clicks or UI elements that may differ on Linux).
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-extended-zones.md
...ain/articles/backup/backup-azure-vms-extended-zones.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation primarily focuses on Azure Portal-based workflows, which are platform-agnostic. However, in the 'Install the VM agent' section, Windows instructions are presented first, with explicit references to Windows-specific tools (MSI installer, C:\ paths, right-click context menus), while Linux instructions are less detailed and lack concrete command examples. No Linux command-line examples (e.g., Bash, az CLI) are provided anywhere in the document, and there are no references to Linux-specific tools or troubleshooting steps. This results in a subtle Windows bias, especially for users managing Linux VMs.
Recommendations
- Provide Linux instructions before or alongside Windows instructions in the 'Install the VM agent' section, including concrete command-line examples (e.g., using apt, yum, or zypper to install the agent).
- Add az CLI and/or Bash examples for key operations (e.g., enabling backup, monitoring jobs, cleaning up resources) to ensure parity for users who prefer or require command-line workflows, especially on Linux.
- Include Linux-specific troubleshooting tips (e.g., checking agent status with systemctl, log file locations) where relevant.
- Avoid Windows-centric language such as 'right-click', 'Properties', or explicit references to C:\ paths unless mirrored with Linux equivalents.
- Consider a dedicated section or callouts for Linux administrators to highlight any differences or best practices.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-introduction.md
.../main/articles/backup/backup-azure-vms-introduction.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas. Windows-specific tools (such as VSS) are described in detail and mentioned before Linux equivalents. PowerShell is referenced for restore operations, with no equivalent Linux CLI or automation example. Linux backup consistency relies on custom scripting, but no concrete Linux script example is provided, whereas Windows backup is described as automatic via VSS. Overall, Windows tools and patterns are presented as the default, with Linux support appearing as an afterthought.
Recommendations
- Provide Azure CLI or Bash examples for backup and restore operations alongside PowerShell, especially for tasks like restoring managed disks.
- Include concrete Linux pre/post script samples for achieving application-consistent backups, not just a link to another article.
- When describing backup consistency mechanisms, give equal detail to Linux (e.g., describe the 'freeze' tool and how it is used, not just mention it in passing).
- Present Windows and Linux instructions/examples in parallel, rather than always listing Windows first.
- Where possible, avoid language that implies Windows is the default or primary platform; instead, clarify parity and differences explicitly.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-instant-restore-capability.md
...n/articles/backup/backup-instant-restore-capability.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
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 (e.g., Azure CLI or Bash scripting). All command-line examples use PowerShell, which is primarily associated with Windows environments. There is no mention of Linux-specific tools or workflows, and no parity for Linux administrators.
Recommendations
- Add equivalent Azure CLI examples for configuring snapshot retention and other operations, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that the operations can be performed from Linux environments using Azure CLI or Bash, and provide sample commands.
- Where PowerShell is referenced, clarify if the steps are also supported in PowerShell Core on Linux, or provide alternative instructions.
- Ensure that screenshots and UI instructions do not assume a Windows environment.
- Include a section or note addressing Linux users and their typical workflows, ensuring parity in guidance and tooling.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-encryption.md
...re-docs/blob/main/articles/backup/backup-encryption.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by mentioning BitLocker (a Windows tool) before DM-Crypt (the Linux equivalent) in the context of Azure Disk Encryption. There are no explicit Linux command-line examples or references to Linux-specific backup workflows, and the only detailed example for in-guest encryption references BitLocker for Windows, with DM-Crypt for Linux mentioned secondarily and without further explanation. No Linux shell or tool usage is shown, and the documentation does not provide parity in examples or guidance for Linux users.
Recommendations
- Provide equal prominence to Linux tools such as DM-Crypt by mentioning them alongside BitLocker, not after.
- Include explicit examples or references for Linux backup scenarios, such as using Linux command-line tools or scripts.
- Add links to Linux-specific documentation for DM-Crypt and Azure Disk Encryption on Linux.
- Ensure that any workflow or process described for Windows (e.g., BitLocker usage) is also described for Linux, with step-by-step guidance or references.
- Consider including a table or section comparing Windows and Linux encryption approaches in Azure Backup to highlight parity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-add-storage.md
...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority
View Details â
Detected Bias Types
windows_only
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All instructions, screenshots, and tools referenced are specific to Windows Server (e.g., Server Manager, ReFS, PowerShell cmdlets). There is no mention of Linux support, nor are there any Linux-specific instructions or examples. The documentation assumes the user is operating in a Windows ecosystem and does not address cross-platform scenarios.
Recommendations
- Clarify early in the documentation whether Azure Backup Server and Modern Backup Storage are Windows-only solutions, or if there is any Linux support or equivalent.
- If Linux is supported, provide parallel instructions and examples for Linux environments, including command-line equivalents and supported filesystems.
- If Linux is not supported, explicitly state this limitation at the beginning of the article to set user expectations.
- Where possible, mention cross-platform alternatives or Azure-native backup solutions that support Linux workloads.
- Avoid using only Windows-specific tools and terminology (e.g., Server Manager, PowerShell) without noting their platform limitations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-files-applications-azure-stack.md
...s/backup/backup-mabs-files-applications-azure-stack.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing Microsoft Azure Backup Server, which is a Windows-based tool. All instructions and screenshots are based on the Azure Backup Server console, with no mention of Linux-based backup solutions, command-line alternatives, or cross-platform considerations. There are no examples or guidance for Linux VMs or filesystems, and the workflow assumes a Windows-centric administrative experience.
Recommendations
- Include explicit instructions or references for backing up files and applications from Linux-based Azure Stack VMs, such as using Azure Backup agent for Linux or other supported methods.
- Provide command-line examples (e.g., Bash scripts, CLI commands) for Linux environments alongside or in addition to GUI-based instructions.
- Mention any Linux-compatible backup tools or agents supported by Azure Stack, and clarify any limitations or differences in feature support.
- Add screenshots or walkthroughs for Linux scenarios, if supported, to ensure parity with Windows examples.
- Clearly state in the prerequisites or introduction if the documented workflow is only supported for Windows VMs, and link to Linux-specific backup guidance if available.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-sharepoint-azure-stack.md
.../articles/backup/backup-mabs-sharepoint-azure-stack.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily oriented towards Windows environments. All examples, tools, and instructions assume Windows servers, Windows command-line tools (CMD, Registry Editor), and Windows-specific services (VSS Writer, DCOM, NT AUTHORITY\SYSTEM). There are no Linux equivalents, nor any mention of Linux-based SharePoint deployments or Azure Backup Server support for Linux. The documentation presumes the use of Windows domains, file paths, and administrative patterns unique to Windows.
Recommendations
- Explicitly state platform requirements and limitations at the top of the documentation, clarifying if Linux is unsupported.
- If Linux support is possible, add equivalent instructions, examples, and tool references for Linux environments.
- Where possible, use cross-platform terminology and avoid Windows-specific jargon unless necessary.
- Provide a comparison table of supported OSes for MABS and SharePoint backup scenarios.
- Include notes or links to Linux backup solutions if MABS is Windows-only, to guide Linux users to alternatives.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-sql-azure-stack.md
...ob/main/articles/backup/backup-mabs-sql-azure-stack.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented toward Windows environments, specifically Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and workflows assume a Windows GUI and SQL Server running on Windows. There are no examples, instructions, or even mentions of Linux-based SQL Server or command-line alternatives (e.g., Bash, CLI). The documentation does not address Linux users or provide parity for cross-platform scenarios.
Recommendations
- Explicitly state in the prerequisites and introduction that MABS is a Windows-only tool, and clarify support for Linux-based SQL Server (if any).
- If Linux-based SQL Server on Azure Stack is supported, provide parallel instructions or note the differences/workarounds for Linux environments.
- Include command-line examples (e.g., using Azure CLI, Bash scripts, or cross-platform tools) where possible, not just GUI walkthroughs.
- Mention and link to Linux-native backup solutions or Azure Backup alternatives for Linux SQL Server, if MABS is not supported.
- Ensure that any references to system accounts, file paths, or permissions include Linux equivalents or note their absence.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks-cli.md
.../blob/main/articles/backup/backup-managed-disks-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias. While the main focus is on Azure CLI (which is cross-platform), variable assignment examples use PowerShell syntax (e.g., $DiskId = ...), which is specific to Windows and not valid in Bash or other Linux shells. There are no explicit Bash/Linux shell examples, nor are there notes about cross-platform differences. The 'Next steps' section lists Azure portal and PowerShell before CLI, reinforcing a Windows-first pattern. There is also a link to PowerShell-specific documentation for assigning permissions, but no equivalent Bash/Linux guidance.
Recommendations
- Replace PowerShell variable assignment examples (e.g., $DiskId = ...) with Bash-compatible syntax (e.g., DiskId=...) or provide both.
- Add explicit Bash/Linux shell examples alongside PowerShell where variables or scripting are involved.
- In 'Next steps', list CLI before PowerShell to avoid Windows-first ordering.
- Provide links to Linux/Bash-specific documentation for tasks like assigning permissions, or clarify that the CLI commands work identically on Linux/macOS.
- Add a note at the top clarifying that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks.md
...docs/blob/main/articles/backup/backup-managed-disks.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation primarily describes how to back up Azure Managed Disks using the Azure portal, with only brief references to scripting alternatives. When scripts are mentioned, PowerShell is listed before Azure CLI, and there are no explicit Linux-specific examples or guidance. The 'Next steps' section also lists PowerShell before CLI, and there is no mention of Bash or Linux shell scripting. The documentation assumes familiarity with Windows-centric tools and patterns, which may disadvantage Linux users.
Recommendations
- When referencing scripting options, list Azure CLI before or alongside PowerShell, and provide parity in examples for both.
- Explicitly mention that Azure CLI can be used from Linux, macOS, and Windows, and provide Bash shell examples where relevant.
- Add links or sections for Linux users, such as 'How to back up Azure Managed Disks using Azure CLI on Linux'.
- Ensure that all references to scripts or automation include both PowerShell and Bash/CLI examples, not just PowerShell.
- Avoid Windows-first ordering when listing tools or approaches; alternate or group by platform.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-overview.md
...zure-docs/blob/main/articles/backup/backup-overview.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page for Azure Backup demonstrates a Windows bias by prominently mentioning Windows-specific backup agents (MARS, DPM, MABS) and tools before Linux equivalents, and by providing examples and links that focus on Windows workloads. Linux backup scenarios are referenced only in passing (e.g., 'Windows/Linux VMs'), with no detailed Linux-specific examples or tool guidance. There is a lack of parity in describing Linux backup options, agents, or best practices compared to the detailed coverage of Windows tools.
Recommendations
- Add explicit examples and guidance for backing up Linux systems, including supported Linux distributions and file systems.
- Include Linux-specific agent/tool names, installation instructions, and links to relevant documentation.
- Present Windows and Linux backup scenarios in parallel, ensuring equal detail and visibility for both platforms.
- Highlight any differences or limitations for Linux backup (e.g., application consistency, file-level restore) to help users plan accordingly.
- Provide sample commands or scripts for Linux environments (e.g., shell commands, cron job integration) alongside PowerShell/Windows examples.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-reports-email.md
...docs/blob/main/articles/backup/backup-reports-email.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by exclusively referencing Office 365/Outlook (a Microsoft/Windows-centric email solution) and the Azure portal for configuration, with no mention of Linux-native tools, open-source alternatives, or cross-platform command-line approaches. All examples and troubleshooting steps are tailored to the Azure portal and Office 365, and there is no guidance for users who may prefer or require Linux-based email solutions or automation tools. The documentation also presents the Azure portal (a GUI) as the primary method, which is more familiar to Windows users, and only secondarily mentions ARM templates, with no mention of CLI or scripting alternatives common in Linux environments.
Recommendations
- Provide examples or guidance for configuring email delivery using Linux-native tools (e.g., sendmail, Postfix, or mailx) or open-source alternatives to Office 365.
- Include Azure CLI or Azure PowerShell examples for automation, and ensure parity between PowerShell and Bash/CLI instructions.
- Mention and link to documentation for integrating with non-Microsoft email providers (such as Gmail, SendGrid, or SMTP servers) for users who do not use Office 365.
- Add troubleshooting steps relevant to Linux environments, such as checking logs or permissions for Linux-based automation tools.
- Ensure that all platform-specific instructions are clearly labeled, and provide equivalent steps for both Windows and Linux users where possible.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-from-azure-vm-blade.md
...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented toward Windows-based SQL Server VMs. It exclusively references the AzureBackupWindowsWorkload extension, NT Service accounts, and Windows-specific service accounts. There are no examples or instructions for SQL Server on Linux VMs, nor any mention of Linux-specific tools or differences. The documentation implicitly assumes SQL Server is running on Windows, and does not address Linux scenarios.
Recommendations
- Add explicit guidance for backing up SQL Server running on Linux-based Azure VMs, including any differences in supported features or required extensions.
- Mention and document any Linux-specific backup agents or extensions, or clarify if Azure Backup does not support SQL Server on Linux VMs.
- Include examples or callouts for Linux users, such as differences in service accounts, permissions, or extension installation.
- If Azure Backup does not support SQL Server on Linux, state this clearly at the beginning of the article.
- Ensure parity in documentation by providing Linux and Windows instructions side-by-side where applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/modify-vm-policy-cli.md
...docs/blob/main/articles/backup/modify-vm-policy-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows environments by using a Windows-style file path (C:\temp2\Policy.json) in the Azure CLI example and not providing a Linux/macOS equivalent. There are no examples or notes for Linux users regarding file paths or command usage, and the documentation implicitly assumes a Windows environment.
Recommendations
- Provide both Windows and Linux/macOS file path examples when referencing files in CLI commands (e.g., C:\temp2\Policy.json and /tmp/Policy.json).
- Add a note clarifying that file paths should be adapted to the user's operating system.
- Include explicit Linux/macOS CLI examples or mention that the Azure CLI commands are cross-platform.
- Avoid using only Windows-specific conventions in cross-platform documentation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-on-availability-groups.md
...les/backup/backup-sql-server-on-availability-groups.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation page focuses exclusively on SQL Server Always On Availability Groups in Azure VMs, implicitly assuming a Windows environment. There are no examples, instructions, or mentions of Linux-based SQL Server deployments, nor any Linux-specific backup tooling or patterns. All references to backup extensions, registration, and failover are written from the perspective of Windows VMs, with no guidance for Linux users. The documentation also omits any mention of cross-platform compatibility or differences, and does not provide parity for Linux SQL Server scenarios.
Recommendations
- Add explicit guidance for SQL Server AG deployments on Linux, including any limitations or differences in Azure Backup support.
- Provide Linux-specific examples for registering AG nodes, configuring backups, and handling failover, using relevant Linux tools and commands.
- Clarify whether the Azure Backup workload extension is supported on Linux SQL Server VMs, and if not, document alternative backup strategies for Linux.
- Include a section comparing Windows and Linux support for SQL Server AG backups in Azure, highlighting any feature gaps or required steps.
- Ensure that all instructions and diagrams mention both Windows and Linux scenarios where applicable, and avoid assuming a Windows-only environment.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-the-mabs-server.md
...cs/blob/main/articles/backup/backup-the-mabs-server.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily biased toward Windows environments. All backup and recovery procedures rely on Windows-specific tools (e.g., PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, VSS, Windows Explorer), and all example commands and scripts are for Windows. There are no Linux equivalents or cross-platform instructions, and the documentation assumes the use of Windows-based SQL Server and file paths. No mention is made of Linux support, alternative tools, or how to perform these tasks on non-Windows systems.
Recommendations
- Clearly state in the prerequisites or introduction if MABS is only supported on Windows. If so, explain why and link to alternatives for Linux users.
- If any components (such as SQL Server) can be hosted on Linux, provide equivalent Linux commands and procedures for backup and restore.
- For each example using Windows-specific tools (e.g., PowerShell, mountvol.exe, diskshadow.exe), provide Linux equivalents or note their absence.
- Where file paths or shares are referenced (e.g., C:\ paths, UNC shares), include Linux path examples if supported.
- If VSS (Volume Shadow Copy Service) or Windows Previous Versions are used, mention Linux alternatives (e.g., LVM snapshots, rsync, etc.) or clarify that these features are not available on Linux.
- Add a section explicitly addressing cross-platform support and limitations, so Linux administrators know what is and isn't possible.
- If MABS is strictly Windows-only, suggest alternative backup solutions for Linux environments (e.g., Azure Backup for Linux, third-party tools).
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-vm-from-vm-pane.md
...n/articles/backup/backup-sql-server-vm-from-vm-pane.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation focuses exclusively on backing up SQL Server VMs using the Azure portal UI, with no mention of Linux-specific tools, commands, or considerations. All examples and screenshots are oriented toward the Windows/SQL Server environment, and there is no discussion of Linux-based SQL Server VMs or command-line alternatives (e.g., Bash, Linux CLI). The related content references Azure CLI and REST API, but the main instructions and UI are Windows-centric.
Recommendations
- Add explicit instructions or notes for backing up SQL Server on Linux-based Azure VMs, including any differences in the process or prerequisites.
- Include examples using Bash or Linux shell commands where applicable, especially if there are CLI-based alternatives.
- Mention any Linux-specific considerations (e.g., permissions, file system differences) when configuring backup.
- Ensure screenshots and UI references clarify if they apply to both Windows and Linux SQL Server VMs, or provide Linux-specific visuals if the experience differs.
- List Linux and cross-platform options alongside Windows options, not just in related content but in the main instructional flow.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix.md
...ocs/blob/main/articles/backup/backup-support-matrix.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows backup scenarios and tools (MARS, DPM, MABS) throughout, often listing Windows support and features first or exclusively. Linux support is frequently noted as 'not supported' or is only available via indirect or limited methods (e.g., file-consistent backup for Linux VMs via DPM/MABS, custom scripts for app-consistency). There are no Linux-specific examples, and Windows tools are referenced without Linux equivalents. The documentation assumes familiarity with Windows-centric backup patterns and does not provide parity in Linux guidance.
Recommendations
- Provide Linux-specific backup examples and workflows where possible, especially for Azure VM and on-premises scenarios.
- List Linux support and features alongside Windows in all tables and descriptions, rather than as afterthoughts or exclusions.
- Include Linux-native tools and commands (e.g., shell scripts, cron jobs, rsync, etc.) where relevant, or clarify their (lack of) support explicitly.
- Offer guidance or references for Linux users seeking backup solutions outside the MARS/DPM/MABS ecosystem, including third-party or Azure-native alternatives.
- Ensure that any mention of Windows tools or features is balanced with Linux equivalents or clear statements about platform limitations.
- Add more detail and links for configuring app-consistent backups on Linux, not just referencing 'custom scripts'.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-manage.md
...b/main/articles/backup/blob-backup-configure-manage.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page primarily describes backup configuration and management using the Azure portal, with references to Azure PowerShell, Azure CLI, and REST API in the 'Related content' section. However, throughout the main guide, there are no explicit CLI or Linux-oriented examples, and PowerShell is mentioned before CLI in the related links. The step-by-step instructions and screenshots are focused on the Azure portal, which is platform-neutral but often more familiar to Windows users. There is no mention of Linux-specific tools, shell commands, or parity guidance for users on Linux systems.
Recommendations
- Add explicit Azure CLI examples alongside PowerShell references, especially in sections describing backup and restore operations.
- Provide sample commands for common Linux shells (bash/zsh) where applicable, such as role assignment or backup configuration.
- Ensure that CLI instructions are presented before or alongside PowerShell instructions to avoid Windows-first bias.
- Include notes or links to Linux-specific documentation or troubleshooting guides for Azure Backup.
- Clarify that all operations can be performed from Linux, macOS, or Windows, and highlight any platform-specific considerations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/disk-backup-overview.md
...docs/blob/main/articles/backup/disk-backup-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits a mild Windows bias. Windows-specific technologies (e.g., Volume Shadow Copy Service, Windows Server Failover Cluster) are mentioned before or more prominently than Linux equivalents. There are no Linux-specific backup consistency mechanisms or tools referenced, and no explicit Linux command-line or scripting examples are provided. The documentation assumes familiarity with Windows patterns and does not provide parity in Linux-specific guidance or examples.
Recommendations
- Include Linux-specific backup consistency mechanisms (e.g., LVM snapshots, fsfreeze) alongside mentions of VSS.
- Provide explicit examples or references for Linux environments, such as how to prepare Linux VMs for crash-consistent or application-consistent backups.
- Mention Linux clustering technologies (e.g., Pacemaker, Corosync) when referencing Windows Server Failover Cluster.
- Add Linux command-line or scripting examples (e.g., using Azure CLI on Linux) where relevant.
- Ensure that Linux and Windows scenarios are given equal prominence and detail in all relevant sections.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-telemetry.md
...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows, referencing only the Microsoft Azure Backup Server (MABS) console, which is a Windows application. All instructions and screenshots are for the Windows GUI, with no mention of Linux equivalents, CLI commands, or cross-platform alternatives. There is no guidance for managing telemetry settings on Linux systems, nor any mention of PowerShell or Windows-specific tools, but the overall context and examples are exclusively Windows-centric.
Recommendations
- Clarify platform support: Explicitly state whether MABS and telemetry management are available on Linux or only on Windows.
- If Linux is supported, provide equivalent instructions for managing telemetry settings on Linux, including CLI commands or configuration file edits.
- Include cross-platform guidance or alternatives, such as REST API or scripting options, if available.
- Add a section comparing Windows and Linux management options, or explicitly note limitations for non-Windows platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/install-mars-agent.md
...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority
View Details â
Detected Bias Types
windows_only
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exclusively describes installation and usage of the MARS agent for Windows machines, with all instructions, screenshots, and prerequisites focused on Windows environments. There are no examples, instructions, or mentions of Linux support or Linux equivalents. Windows tools (such as PowerShell, .NET Framework, and Windows-specific installer files) are referenced throughout, and the only scripting example provided is for PowerShell. The page title, customer intent, and all steps reinforce a Windows-centric approach, with no Linux parity.
Recommendations
- Clearly state in the introduction whether the MARS agent is Windows-only, and if so, provide links or guidance for Linux backup solutions (e.g., Azure Backup for Linux VMs, Azure Backup Server, or third-party tools).
- If Linux support exists, add equivalent installation and usage instructions for Linux, including command-line examples, package requirements, and screenshots.
- Provide parity in scripting examples by including Bash or shell script alternatives alongside PowerShell.
- Reference Linux backup patterns and tools where appropriate, and avoid implying that Azure Backup is only for Windows by updating customer intent and summary sections.
- If the MARS agent is not available for Linux, clarify this limitation and direct Linux users to supported alternatives.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-afs-backup.md
...re-docs/blob/main/articles/backup/manage-afs-backup.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation primarily focuses on managing Azure Files backups using the Azure Portal, with only a brief mention of Azure PowerShell, Azure CLI, and REST API as alternative management methods. The PowerShell link is listed before CLI, and there are no direct examples or instructions for Linux users or Linux-specific tools. All screenshots and step-by-step instructions are portal-based, which is platform-agnostic, but the lack of parity in command-line examples (especially for Linux/CLI) and the ordering of PowerShell before CLI suggest a subtle Windows bias.
Recommendations
- Provide explicit Azure CLI examples alongside or immediately after PowerShell examples, especially for common tasks such as creating, modifying, or deleting backup policies.
- Ensure that Azure CLI and REST API links are given equal prominence to PowerShell, and consider listing CLI before PowerShell to avoid Windows-first ordering.
- Include at least one end-to-end Linux/CLI workflow for managing Azure Files backups, with sample commands and expected outputs.
- Add a section or callout for Linux users, highlighting any platform-specific considerations or best practices.
- Review and update cross-references to ensure that Linux and CLI documentation is as comprehensive and discoverable as Windows/PowerShell content.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-bicep-file.md
...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a strong Windows bias. All deployment and cleanup examples use Azure PowerShell scripts exclusively, with no mention of Azure CLI or Bash equivalents. The Bicep template provisions only Windows VMs, and the instructions reference Windows-specific tools and patterns (e.g., PowerShell, Remove-AzResourceGroup). There are no Linux VM options or Linux command-line examples provided.
Recommendations
- Add Azure CLI and/or Bash examples for deploying and cleaning up resources, alongside PowerShell.
- Include a Linux VM option in the Bicep template (e.g., allow selection of a Linux image and admin SSH key).
- Ensure that references to tools and commands are cross-platform, or provide parallel instructions for Linux/macOS users.
- Update the documentation to mention both Windows and Linux scenarios where applicable, and avoid assuming a Windows-only environment.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-portal.md
...cs/blob/main/articles/backup/quick-backup-vm-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows VM creation first, providing more detailed and step-by-step instructions for Windows VM agent installation (including a direct download link and file verification steps), and mentioning Windows-specific tools and paths. Linux instructions are less detailed, lack explicit command-line examples, and are presented after the Windows instructions. There are no Linux-specific screenshots or examples, and the initial VM creation link points to a Windows-specific guide.
Recommendations
- Provide parallel Linux examples and links (e.g., link to both Windows and Linux VM creation guides).
- Include explicit Linux command-line examples for agent installation (e.g., apt, yum, or zypper commands).
- Add Linux-specific screenshots or UI references where applicable.
- Present Windows and Linux instructions with equal detail and in parallel sections, rather than Windows first.
- Avoid referencing Windows-specific tools or file paths without Linux equivalents.
- Ensure all optional and troubleshooting steps are covered for both platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-backup-vault.md
...-docs/blob/main/articles/backup/manage-backup-vault.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell before CLI when discussing scripting and automation, and by not providing any Linux-specific examples or guidance. All command-line references are generic or PowerShell-centric, with no mention of Linux shell usage, nor any screenshots or instructions tailored for Linux users. The page assumes the Azure portal as the main interface, which is cross-platform, but scripting examples and tool mentions favor Windows environments.
Recommendations
- Provide explicit examples for both Azure CLI (bash/shell) and PowerShell when mentioning scripting or automation, and ensure CLI examples are given equal prominence.
- Include notes or sections on how Linux users can perform equivalent operations, especially for tasks like moving resources, managing vaults, and troubleshooting.
- Add screenshots or command snippets that show usage from Linux terminals (e.g., bash) where relevant.
- When referencing tools and scripts, clarify compatibility and provide sample scripts for both Windows (PowerShell) and Linux (bash/CLI).
- Review all command references to ensure they are not Windows-centric and update documentation to reflect cross-platform parity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-monitor-sql-database-backup.md
.../articles/backup/manage-monitor-sql-database-backup.md
High Priority
View Details â
Detected Bias Types
windows_heavy
missing_linux_example
windows_tools
Summary
The documentation focuses exclusively on managing and monitoring SQL Server databases on Azure VMs, implicitly assuming Windows as the underlying OS. There are no examples, instructions, or notes for SQL Server on Linux VMs, nor any mention of Linux-specific tools or scenarios. All references to SQL Server management, backup, and recovery are Windows-centric, and the use of the Azure portal is described with screenshots and steps that are only applicable to Windows-based SQL Server deployments.
Recommendations
- Explicitly state whether the instructions apply to both Windows and Linux-based SQL Server VMs, or clarify if only Windows is supported.
- Add sections or notes describing how to manage and monitor SQL Server on Linux VMs, including any differences in backup agent installation, extension registration, or portal experience.
- Provide Linux-specific examples, such as using Bash, Linux file paths, or relevant Linux tools for troubleshooting and management.
- If certain features are not supported on Linux, clearly document these limitations.
- Include links to documentation for SQL Server on Linux in Azure VMs, if available.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/monitoring-and-alerts-overview.md
...main/articles/backup/monitoring-and-alerts-overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell as a primary non-portal client and listing it before the Azure CLI. There are no explicit Linux-specific examples or references to Linux shells or tools. While Azure CLI is mentioned, it is always after PowerShell, and no sample commands or workflows are provided for Linux users. The documentation does not address Linux-specific monitoring or reporting scenarios, nor does it provide parity in examples or guidance for Linux administrators.
Recommendations
- Provide explicit Linux/Unix shell examples (e.g., Bash) alongside or before PowerShell examples.
- Ensure Azure CLI examples are given equal prominence and detail as PowerShell, including sample commands for common tasks.
- Mention cross-platform compatibility and highlight any differences or considerations for Linux users.
- Include references to Linux-native tools or workflows where appropriate (e.g., integration with syslog, cron jobs, or Linux-based automation).
- Review the ordering of tool mentions to avoid always listing Windows tools first.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box-dpm-mabs.md
...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority
View Details â
Detected Bias Types
windows_only
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All instructions, examples, and supported platforms are exclusively for Windows Server (2016/2019) and Windows-based tools (DPM, MABS). The setup and troubleshooting sections rely on Windows-specific tools (e.g., PSExec, regedit, Windows command prompt, PowerShell modules), and there are no Linux equivalents or mentions of cross-platform alternatives. No Linux distributions or commands are referenced, and the workflow assumes a Windows administrative environment throughout.
Recommendations
- Clearly state early in the documentation that only Windows platforms are supported, if that is a product limitation. If not, add explicit support information for Linux and other platforms.
- If DPM/MABS or the MARS agent can be used on Linux, provide equivalent Linux instructions, including commands for mounting NFS shares, managing certificates, and interacting with Azure (e.g., using Azure CLI instead of PowerShell).
- Where PowerShell is used, provide Azure CLI equivalents for cross-platform compatibility.
- Replace or supplement Windows-only tools (e.g., PSExec, regedit) with cross-platform alternatives or document how to perform equivalent tasks on Linux.
- If Linux is not supported, add a note in the 'Supported platforms' section to clarify this and, if possible, link to alternative solutions for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box.md
.../main/articles/backup/offline-backup-azure-data-box.md
High Priority
View Details â
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 support. All examples, prerequisites, and troubleshooting steps use Windows-specific tools (PowerShell, MARS Agent, Windows command prompt, PsExec, Windows Registry, Control Panel). There are no Linux equivalents or instructions, and the documentation does not clarify whether Linux is unsupported or simply omitted.
Recommendations
- Explicitly state platform support at the beginning of the document. If Linux is not supported, clarify this to avoid confusion.
- If Linux support exists or is planned, provide equivalent instructions for Linux environments, including commands for Bash, Linux-compatible tools, and Linux-specific troubleshooting.
- Where possible, use cross-platform Azure CLI examples in addition to or instead of PowerShell.
- Mention Linux tools and patterns (e.g., mounting NFS shares, managing certificates, uninstalling packages) alongside Windows tools.
- Add a section addressing common questions about non-Windows support and alternatives.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/move-to-azure-monitor-alerts.md
...b/main/articles/backup/move-to-azure-monitor-alerts.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation references PowerShell and the Azure portal as primary management interfaces, with no mention of Linux-specific tools or CLI usage. It assumes familiarity with PowerShell and Windows-centric workflows, and does not provide Linux or cross-platform command-line examples. Notification configuration is stated as only available via the Azure portal, and there is no discussion of Linux automation or scripting options.
Recommendations
- Add Azure CLI examples for common alert management and backup operations, as the CLI is cross-platform and widely used on Linux.
- Explicitly mention Linux support and provide guidance for Linux administrators, including how to monitor or manage alerts using Bash scripts or automation tools.
- Clarify if PowerShell Core (cross-platform) is supported, and provide examples using it if so.
- Where possible, avoid language that assumes a Windows environment (e.g., 'portal/PowerShell/the CLI clients') and ensure parity in examples and instructions for both Windows and Linux users.
- If certain features are only available via the Azure portal, note any workarounds or alternative monitoring/notification integrations that Linux users might employ.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/pre-backup-post-backup-scripts.md
...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows file paths, tools, and conventions (e.g., 'Drive:', 'cscript', and backslash paths). There are no examples or instructions for Linux systems, and all scripting and configuration guidance assumes a Windows environment.
Recommendations
- Add explicit guidance and examples for configuring pre-backup and post-backup scripts on Linux-based protected computers, if supported.
- Include Linux path formats (e.g., /opt/dpm/Scripting) and script execution methods (e.g., bash, sh) alongside Windows examples.
- Mention Linux-compatible scripting languages and tools (e.g., Bash, Python) and how to invoke them.
- Clarify whether MABS supports Linux agents for scripting, and if not, state this limitation clearly.
- Ensure that all XML configuration examples show both Windows and Linux path and script invocation formats where applicable.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/query-backups-using-azure-resource-graph.md
...les/backup/query-backups-using-azure-resource-graph.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as the first automation client for Azure Resource Graph, referencing a PowerShell-specific quickstart before the Azure CLI or SDK equivalents. There are no explicit Linux shell (bash) or cross-platform CLI examples, and the only automation tools mentioned are PowerShell, Azure CLI, and Python SDK, with PowerShell given prominence. No Linux-specific guidance or parity is provided.
Recommendations
- List Azure CLI examples and documentation links before or alongside PowerShell to avoid Windows-first ordering.
- Provide explicit bash/Azure CLI sample commands for running ARG queries, especially for Linux users.
- Mention cross-platform tools (e.g., Azure CLI, Python SDK) before or equally with PowerShell.
- Clarify that all automation clients (PowerShell, CLI, SDK) are cross-platform, and provide links to Linux installation guides.
- Consider adding a section or note for Linux/macOS users, highlighting any differences or tips for their environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/private-endpoint-configure-vault-backup-server.md
...ckup/private-endpoint-configure-vault-backup-server.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented toward Windows environments, specifically Microsoft Azure Backup Server (MABS) and the MARS agent, which are Windows-only tools. All examples, screenshots, and instructions assume use of the Azure Portal GUI or Windows-based DNS management. There are no references to Linux equivalents, CLI commands, or cross-platform backup agents. The only DNS host file example links to a Windows-based DNS guide, and there are no PowerShell or CLI scripts, but the overall workflow is Windows-centric.
Recommendations
- Add explicit notes clarifying that MABS and MARS agent are Windows-only, and suggest Linux-compatible alternatives (e.g., Azure CLI, AzCopy, or third-party backup solutions) where possible.
- Provide parallel instructions or references for configuring private endpoints and DNS using Azure CLI, which is cross-platform.
- Include Linux-based DNS configuration examples (e.g., editing /etc/hosts, using BIND for DNS forwarding) alongside or after Windows examples.
- If possible, add guidance for backing up Linux servers to Azure using supported tools, and how private endpoints would be configured in those scenarios.
- Link to documentation for Linux backup solutions and their integration with Azure Backup, if supported.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-cli.md
...cles/backup/quick-backup-azure-files-vault-tier-cli.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page, while focused on Azure CLI (which is cross-platform), shows evidence of Windows bias. It includes a command output with a Windows file path (C:\Users\testuser\Downloads\...), references PowerShell and the Azure portal before mentioning Linux or macOS alternatives, and does not provide explicit Linux shell output or examples. The prerequisites section mentions Docker for macOS/Windows but does not clarify native Linux installation. There are no explicit Linux shell examples or screenshots, and the only command output shown is from a Windows environment.
Recommendations
- Provide example command outputs from both Linux and Windows environments, or use a neutral shell prompt (e.g., $ or #) instead of a Windows path.
- Explicitly mention native Linux installation steps for Azure CLI, not just Docker for macOS/Windows.
- Include Linux-specific notes or troubleshooting tips where relevant.
- When referencing alternative tools (PowerShell, Azure portal), list them in an order that does not prioritize Windows tools (e.g., 'Azure CLI, Azure PowerShell, or Azure portal').
- Add screenshots or terminal snippets from Linux environments to demonstrate parity.
- Clarify that all CLI commands work identically on Linux, macOS, and Windows, and provide links to Linux-specific documentation where appropriate.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-terraform.md
...ackup/quick-backup-azure-files-vault-tier-terraform.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows-first bias by mentioning Azure PowerShell alongside Azure CLI for authentication, despite Terraform only supporting Azure CLI. PowerShell is referenced multiple times (including in 'Next steps') before or alongside Azure CLI, and there are no explicit Linux/macOS-specific instructions or examples. The documentation assumes familiarity with Windows tools and patterns, such as PowerShell, without providing parity for Linux users.
Recommendations
- Clearly state that Azure CLI is cross-platform and preferred for Terraform authentication, and de-emphasize PowerShell in this context.
- Provide explicit Linux/macOS command-line examples (e.g., bash/zsh) where relevant, especially for directory and file operations.
- In 'Next steps', list Azure CLI and REST API options before PowerShell to avoid Windows-first ordering.
- Add a note or section for Linux/macOS users, clarifying that all Terraform and Azure CLI commands work natively on those platforms.
- Remove or clarify any PowerShell references that are not directly relevant to Terraform workflows.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-database-portal.md
...cles/backup/quick-backup-postgresql-database-portal.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation demonstrates a bias towards Windows environments by primarily referencing PowerShell scripts for privilege assignment and automation, with only brief and secondary mentions of Linux-native tools (e.g., psql, pgAdmin). PowerShell is presented as the default or primary method, and alternatives are not equally detailed. There is also a lack of explicit Linux shell or cross-platform CLI examples, and no Bash or Linux command-line instructions are provided.
Recommendations
- Provide equivalent examples using Linux-native tools such as psql and Bash scripts for privilege assignment and automation, alongside PowerShell.
- Ensure that instructions for both PowerShell and Linux/Unix environments are presented with equal prominence and detail.
- Where PowerShell scripts are referenced, include downloadable or copy-paste-ready Bash/psql equivalents.
- Explicitly mention cross-platform compatibility and clarify which steps or scripts are platform-agnostic.
- Add screenshots or walkthroughs using Azure CLI and psql on Linux, not just Azure Portal or PowerShell.
- Review and update all sections to ensure Linux users are not required to adapt Windows-centric instructions themselves.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-arm.md
.../backup/quick-backup-postgresql-flexible-server-arm.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias. All deployment and restore examples use PowerShell, with no Azure CLI, Bash, or Linux-native instructions provided. The prerequisites and next steps reference PowerShell tools and modules exclusively, and there is no mention of Linux or cross-platform alternatives. This may hinder accessibility for Linux or macOS users.
Recommendations
- Add Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Provide Bash shell script examples alongside PowerShell scripts.
- In prerequisites, mention both Azure PowerShell and Azure CLI, with installation links for each.
- In 'Next steps', include links to restoring using Azure CLI or portal, not just PowerShell.
- Explicitly state that the instructions are cross-platform, or clarify platform-specific steps where necessary.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-bicep.md
...ackup/quick-backup-postgresql-flexible-server-bicep.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a clear Windows bias by providing only PowerShell deployment instructions and referencing the Azure PowerShell module as a prerequisite. There are no examples or instructions for deploying the Bicep template using cross-platform tools such as Azure CLI, nor are there any Linux/macOS-specific notes or parity. The guidance for restoring backups also links only to a PowerShell-based article.
Recommendations
- Add Azure CLI deployment instructions for the Bicep template, as Azure CLI is cross-platform and widely used on Linux and macOS.
- List both PowerShell and CLI as options in the prerequisites, and provide installation links for both.
- Update the deployment section to include both PowerShell and CLI examples, or at least mention that the CLI can be used with a reference link.
- Ensure that any 'Next steps' or further reading links include CLI-based or portal-based alternatives, not just PowerShell.
- Wherever possible, avoid language that assumes a Windows shell (e.g., 'right-click the shell window'), or provide equivalent instructions for other platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-cli.md
.../backup/quick-backup-postgresql-flexible-server-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page, while focused on Azure CLI (which is cross-platform), exhibits Windows bias in several ways. It references PowerShell and Windows object manipulation patterns first and in detail, and uses Windows-style file paths (e.g., '.\OSSPolicy.json') in CLI examples. The explanation of modifying policy templates emphasizes PowerShell object usage before discussing the CLI/file-based approach, and does not provide explicit Linux/Unix shell equivalents or path examples. There are no Linux-specific examples or notes about running the CLI commands on Linux or macOS.
Recommendations
- Provide Linux/Unix shell command examples alongside or instead of Windows-style examples, especially for file paths (e.g., use './OSSPolicy.json' instead of '.\OSSPolicy.json').
- When discussing object manipulation, avoid assuming PowerShell as the default and clarify that Linux/macOS users should use file-based approaches.
- Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and provide notes or tips for users on different platforms.
- If referencing PowerShell, also reference Bash or other common Linux shells where appropriate, or provide links to equivalent guidance.
- Consider reordering explanations to avoid presenting Windows/PowerShell approaches first, or clearly separate platform-specific guidance.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-template.md
.../blob/main/articles/backup/quick-backup-vm-template.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All deployment and cleanup examples use Azure PowerShell scripts, with no Azure CLI (bash) or Linux shell equivalents provided. The template referenced is for a Windows VM, and the PowerShell approach is presented first and in detail, while Azure CLI and REST API are only mentioned in passing. There are no Linux-specific instructions or examples, and Windows tools and patterns are used exclusively throughout the page.
Recommendations
- Add equivalent Azure CLI (bash) examples for deploying the ARM template, including parameter input and resource group creation.
- Provide cleanup instructions using Azure CLI commands, not just PowerShell.
- Reference and/or provide a template for deploying a Linux VM with backup, or clarify how to adapt the template for Linux.
- When listing deployment options, mention Azure CLI and the portal before or alongside PowerShell, not after.
- Link directly to Linux/CLI quickstart guides where available.
- Ensure that monitoring and backup job instructions include both PowerShell and CLI options.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-terraform.md
...blob/main/articles/backup/quick-backup-vm-terraform.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively demonstrates backing up a Windows virtual machine in Azure using Terraform, with no mention or example of Linux VM equivalents. The description, checklist, and verification steps all focus on Windows VMs, and the 'Next steps' section directs users to further Windows VM resources. There is no parity for Linux VM scenarios, nor any guidance for Linux-specific backup considerations.
Recommendations
- Add parallel examples and instructions for backing up Linux virtual machines in Azure using Terraform.
- Update the checklist and verification steps to include Linux VM resource names and backup commands.
- Provide guidance on differences in backup configuration or recovery for Linux VMs, such as OS disk types, authentication, or agent requirements.
- Balance 'Next steps' links to include articles about Azure Linux VMs and their backup procedures.
- Consider renaming the article or clearly indicating its Windows-specific scope if Linux parity is not intended.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-blob-vaulted-backup-cli.md
.../main/articles/backup/quick-blob-vaulted-backup-cli.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing 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 restore section lists Azure PowerShell before Azure CLI and REST API. There are no explicit Linux-specific instructions or examples, and the documentation does not mention Linux tools or shell environments.
Recommendations
- Provide explicit Bash/Linux shell examples alongside or before PowerShell examples.
- Ensure links for key tasks (e.g., creating a Backup vault) include both Azure CLI and PowerShell options, with CLI (cross-platform) listed first.
- Add notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
- Avoid referencing PowerShell-specific guides in CLI-focused documentation unless parity is maintained.
- Include troubleshooting or environment setup instructions for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-kubernetes-backup-bicep.md
.../main/articles/backup/quick-kubernetes-backup-bicep.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a clear Windows bias by exclusively providing deployment instructions using Azure PowerShell, referencing Windows-specific interaction patterns (e.g., right-click to paste in shell), and omitting equivalent Azure CLI or Bash examples. The prerequisites and deployment steps focus on PowerShell, with no mention of Linux-native tools or workflows, despite Bicep and Azure CLI being cross-platform.
Recommendations
- Add Azure CLI and Bash examples for deploying the Bicep template, ensuring Linux and macOS users are equally supported.
- Update instructions to use platform-neutral language for shell interactions (e.g., 'paste the code into your terminal'), or provide platform-specific notes.
- Mention both Azure PowerShell and Azure CLI as options in the prerequisites and deployment sections.
- Order examples so that cross-platform tools (Azure CLI, Bash) are presented before or alongside PowerShell.
- Explicitly state that all steps can be performed on Linux, macOS, or Windows, and link to relevant cross-platform installation guides.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/register-public-access-vault-backup-server.md
...s/backup/register-public-access-vault-backup-server.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively describes the process for Microsoft Azure Backup Server (MABS), which is a Windows-only product. All instructions, UI references, and screenshots are specific to the Windows environment, with no mention of Linux equivalents or cross-platform alternatives. There are no Linux commands, tools, or workflows provided, and the documentation assumes the user is operating in a Windows GUI context.
Recommendations
- If Linux support is available for similar backup scenarios (e.g., via Azure Backup Agent or other tools), add equivalent Linux instructions and examples.
- Explicitly state early in the documentation that MABS is Windows-only, and provide links to Linux backup solutions if applicable.
- Where possible, include PowerShell and CLI examples alongside GUI instructions, and mention if/when these are only available on Windows.
- Add a section or note addressing Linux users, guiding them to appropriate documentation for their platform.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-all-files-volume-mars.md
.../main/articles/backup/restore-all-files-volume-mars.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily biased towards Windows environments. All instructions and screenshots reference the Microsoft Azure Backup snap-in, which is a Windows-specific tool. There are no examples, instructions, or mentions of Linux systems, nor any cross-platform or Linux alternatives. The documentation assumes the user is operating in a Windows environment and does not address Linux users or provide parity in guidance.
Recommendations
- Add explicit statements about platform support, clarifying whether the MARS Agent and these instructions are Windows-only or if Linux is supported.
- If Linux is supported, provide equivalent step-by-step instructions for restoring files on Linux systems, including relevant commands and screenshots.
- Mention and link to Linux-compatible backup and restore tools (such as Azure CLI, azcopy, or other Azure Backup solutions for Linux) if MARS Agent is not available for Linux.
- Ensure that any platform-specific limitations or differences are clearly documented at the beginning of the article.
- Consider adding a comparison table or section that outlines feature parity and differences between Windows and Linux restore processes.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-backup-server-vmware.md
.../articles/backup/restore-azure-backup-server-vmware.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on the Microsoft Azure Backup Server (MABS) Administrator Console, which is a Windows-only tool. All procedures and screenshots are based on the Windows GUI. Individual file restore (ILR) is only supported for Windows Server VMs, with no mention of Linux VM support or equivalent Linux file-level recovery workflows. Registry key modifications are described using Windows Registry paths, and there are no Linux-specific instructions, examples, or considerations.
Recommendations
- Include explicit statements about the support (or lack thereof) for Linux VMs, especially for individual file recovery. If unsupported, clarify this early in the documentation.
- If Linux VM file-level recovery is supported, provide equivalent step-by-step instructions and screenshots for Linux VMs, or link to relevant Linux recovery documentation.
- Mention and document any Linux tools, commands, or workflows that can be used in conjunction with MABS for Linux VM recovery.
- When describing configuration changes (e.g., increasing parallel restores), note whether these are only applicable to Windows environments and provide Linux alternatives if available.
- Consider adding a comparison table summarizing feature parity (or gaps) between Windows and Linux VM recovery scenarios.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-encrypted-virtual-machines.md
...les/backup/restore-azure-encrypted-virtual-machines.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is mentioned as the primary method for creating a VM from restored disks, with no equivalent CLI or Linux-native example provided. The OS disk swap note links only to Windows-specific documentation. Linux-specific guidance is relegated to a separate step, and lacks detailed, step-by-step instructions or examples. Windows tools and patterns (such as PowerShell and OS disk swap) are referenced before or instead of Linux equivalents.
Recommendations
- Provide Azure CLI and/or Bash examples for restoring and recreating VMs from restored disks, alongside PowerShell.
- Include links to Linux-specific documentation for OS disk swap and VM restore operations.
- Offer detailed, step-by-step instructions for restoring encrypted Linux VMs, including ADE extension reinstallation and configuration.
- Ensure that Linux and Windows procedures are presented with equal prominence and detail throughout the documentation.
- When referencing tools or commands, mention both Windows and Linux options together, or in parallel sections.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-ase-backup-support-matrix.md
.../main/articles/backup/sap-ase-backup-support-matrix.md
High Priority
View Details â
Detected Bias Types
windows_explicit_exclusion
linux_only_examples
missing_windows_example
Summary
The documentation page is strongly Linux-centric, explicitly stating that only SAP ASE databases running on Azure Linux VMs are supported for backup, with Windows configurations listed as unsupported. All example scripts and operational instructions use Linux tools (bash, sudo, shell scripts), with no PowerShell, Windows command-line, or Windows tool examples provided. Azure CLI/PowerShell support is explicitly marked as unavailable, and there are no references to Windows-specific patterns or tools.
Recommendations
- Clarify the roadmap for Windows support, if any, or provide a rationale for Linux-only support to help Windows users understand the limitation.
- If Windows support is planned, add equivalent examples and instructions for Windows environments (e.g., PowerShell scripts, Windows command-line usage).
- Explicitly mention alternative backup strategies for SAP ASE on Windows VMs, if available, or link to relevant documentation.
- Consider adding a section that addresses common questions from Windows users, including migration guidance or interoperability notes.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-ase-database-about.md
...cs/blob/main/articles/backup/sap-ase-database-about.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits subtle Windows bias by referencing Windows-specific VM creation links, omitting explicit Linux examples, and not clarifying cross-platform parity for backup and restore operations. There are no PowerShell-heavy sections, but the only explicit VM creation link points to a Windows VM guide, and there are no Linux-specific instructions or examples. The documentation does not mention Linux tools or provide Linux-first guidance, despite SAP ASE being commonly deployed on Linux.
Recommendations
- Add explicit examples and links for both Windows and Linux VM creation and management, ensuring Linux parity.
- Clarify that the backup and restore procedures apply equally to Linux-based Azure VMs, or provide any Linux-specific prerequisites or differences.
- Include Linux-specific instructions or screenshots where relevant, such as running the preregistration script on Linux (e.g., using Bash in Azure Cloud Shell).
- Where VM restore options are discussed, provide links to both Windows and Linux VM creation guides.
- Explicitly state supported operating systems for the Azure Backup plugin for ASE, and highlight any OS-specific considerations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-instances-restore.md
...articles/backup/sap-hana-database-instances-restore.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Azure portal workflows and PowerShell/CLI scripts for permission management, without providing explicit Linux shell examples or guidance. The use of terms like 'PowerShell or CLI script' and the absence of Linux-specific commands or tools (such as bash scripts or Linux-native utilities) suggests a preference for Windows-centric administration patterns. Additionally, the documentation does not clarify how to perform key steps (like disk mounting or permission assignment) on Linux VMs, which are common for SAP HANA deployments.
Recommendations
- Add explicit Linux shell (bash) examples for disk mounting and permission assignment, alongside PowerShell/CLI instructions.
- Clarify how to perform restore operations using Linux-native tools and commands, especially for SAP HANA running on Linux VMs.
- Ensure that references to scripting (e.g., 'PowerShell or CLI script') are accompanied by both Windows and Linux command examples.
- Include screenshots or step-by-step instructions for Linux environments in addition to Azure portal workflows.
- Review terminology to avoid Windows-first language and ensure equal visibility for Linux administration patterns.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/selective-disk-backup-restore.md
.../main/articles/backup/selective-disk-backup-restore.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides extensive examples for Azure CLI and PowerShell, with PowerShell (a Windows-centric tool) featured as a primary automation method. There are no explicit Linux shell (bash) or cross-platform scripting examples, and PowerShell is presented as the only scripting alternative to the CLI. Windows-specific tools and terminology (e.g., drive letters, BitLocker) are mentioned before Linux equivalents, and Linux-specific instructions are limited to brief notes about required utilities (lsblk, lsscsi) rather than full examples. There are no bash or Linux-native command examples for configuring or managing selective disk backup, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
- Add bash/Linux shell script examples for common operations (e.g., using Azure CLI in bash scripts, handling output with jq, etc.).
- Provide Linux-native automation examples alongside PowerShell, such as bash scripts for configuring selective disk backup.
- When discussing OS-specific requirements (e.g., BitLocker for Windows, dm-crypt for Linux), present Linux and Windows information in parallel rather than Windows-first.
- Include troubleshooting steps and examples for common Linux distributions, not just notes about required utilities.
- Clarify that PowerShell Core is cross-platform, but also provide bash alternatives for users who prefer native Linux tooling.
- Ensure that all CLI examples are shown in a way that is copy-paste friendly for both Windows (cmd/PowerShell) and Linux (bash) environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/set-system-state-backup-policy.md
...icles/backup/scripts/set-system-state-backup-policy.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides a PowerShell script for managing system state backup policies with the MARS agent, which is a Windows-centric tool. All instructions, examples, and referenced modules are specific to Windows environments, with no mention of Linux equivalents, alternative scripting languages, or cross-platform approaches. The page assumes the user is on Windows and does not address Linux users or provide parity for non-Windows platforms.
Recommendations
- Include equivalent instructions or scripts for Linux environments, if supported, using Bash or other common Linux tools.
- Explicitly state platform requirements and limitations at the beginning of the documentation.
- If the MARS agent is Windows-only, suggest Linux alternatives for backup management (e.g., Azure Backup for Linux, or other supported agents).
- Provide links or references to Linux documentation for similar backup policy management tasks.
- Consider adding a comparison table of backup solutions for Windows and Linux, highlighting feature parity and differences.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/disable-soft-delete-for-file-shares.md
.../backup/scripts/disable-soft-delete-for-file-shares.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides command-line examples using armclient with Windows-style paths (e.g., '.\rqbody-disableSoftDelete.json'), which are specific to Windows and PowerShell. There are no Linux or macOS shell examples, nor is there guidance for using armclient on non-Windows platforms. The mention of PowerShell and Azure CLI is only in a link, not in the main content. This creates a bias toward Windows users and may confuse or exclude Linux/macOS users.
Recommendations
- Provide equivalent Linux/macOS shell examples, using forward slashes (e.g., './rqbody-disableSoftDelete.json') and bash syntax.
- Explicitly state that armclient is cross-platform (if it is), or provide alternative tools/commands for Linux/macOS.
- Add a section or callout for Linux/macOS users, showing how to install and use armclient on those platforms.
- When referencing file paths or commands, show both Windows and Linux/macOS variants side-by-side.
- Consider including Azure CLI or REST API examples directly in the documentation, not just as a link.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/set-file-folder-backup-policy.md
...ticles/backup/scripts/set-file-folder-backup-policy.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides a PowerShell script sample and instructions for managing backup policies using the MARS agent, which is a Windows-specific tool. There are no examples, instructions, or references for Linux environments, nor are Linux-compatible tools or scripting languages mentioned. The documentation assumes a Windows context throughout.
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, etc.) if supported.
- Clarify platform prerequisites and limitations at the top of the page.
- If the MARS agent is Windows-only, explicitly state this and link to Linux backup solutions.
- Provide parity in documentation structure and detail for Linux users, including example commands and automation patterns.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sql-support-matrix.md
...e-docs/blob/main/articles/backup/sql-support-matrix.md
High Priority
View Details â
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 listed as supported, with Linux explicitly stated as unsupported. All examples and tooling references (e.g., PowerShell) are Windows-centric, with no mention of Linux equivalents or parity. The backup configuration is only supported via the Azure portal or PowerShell, and CLI is not supported, further reinforcing Windows bias.
Recommendations
- Clearly indicate plans or timelines for Linux support, if any, or provide rationale for its absence.
- Add Linux support where feasible, including examples and instructions for common Linux distributions running SQL Server in Azure VMs.
- Support Azure CLI for backup configuration to enable cross-platform management, and provide CLI examples alongside PowerShell.
- Where features are Windows-only, explicitly state alternatives or workarounds for Linux users.
- Review all tooling and example sections to ensure parity and visibility for Linux administrators.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-sql-saphana-in-azure-vm.md
...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides detailed instructions for the Azure Portal and Azure PowerShell, both of which are Windows-centric tools. There are no examples or instructions for Linux-native tools (e.g., Azure CLI, Bash scripting), nor is there mention of Linux command-line equivalents. PowerShell is presented as the only scripting/automation method, and no Linux-first or cross-platform guidance is provided.
Recommendations
- Add Azure CLI examples for all operations (delete, undelete, restore, resume backup) alongside PowerShell examples.
- Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide Bash shell command examples.
- If certain operations are not supported in Azure CLI, state this clearly and provide alternative guidance for Linux users.
- Reorder sections or provide parallel tabs for Azure CLI and PowerShell to ensure Linux users are not an afterthought.
- Include screenshots or walkthroughs using the Azure CLI in a Linux terminal where possible.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-azure-file-share.md
...b/main/articles/backup/soft-delete-azure-file-share.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing a PowerShell script for undeleting file shares and not providing equivalent examples or scripts for Linux environments (e.g., Bash, Azure CLI). The term 'script' is used without clarifying its platform, but the linked script is PowerShell-based. There are no Linux or cross-platform command-line examples, and the documentation does not mention or prioritize Linux tools or workflows.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for undeleting file shares and other operations, and link to them alongside the PowerShell script.
- Explicitly state when a script is PowerShell-specific, and offer guidance for Linux/macOS users.
- Include examples using Azure CLI, which is cross-platform, for all major operations (undelete, disable soft delete, etc.).
- Review all documentation links and ensure that Linux and macOS users are supported with clear, platform-agnostic instructions.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/threat-detection-configure-monitor-tutorial.md
.../backup/threat-detection-configure-monitor-tutorial.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by only referencing Microsoft-centric tools and workflows (Azure Portal, Microsoft Defender for Cloud, Microsoft Sentinel) without mentioning or providing parity for Linux-specific tools, command-line interfaces, or automation methods. There are no examples or guidance for Linux users (e.g., using Azure CLI, Bash, or Linux-based automation), and all instructions are oriented around GUI workflows typical for Windows administrators.
Recommendations
- Add examples using Azure CLI and/or Azure PowerShell for enabling and monitoring threat detection, ensuring both Windows and Linux users can follow along.
- Explicitly mention that the Azure Portal and Defender for Cloud are cross-platform, and clarify any platform-specific requirements or limitations.
- Provide sample scripts or automation steps that can be run from Linux environments (e.g., Bash scripts, az CLI commands) for all major operations described.
- Include a section or callout addressing Linux VM backup scenarios, and note any differences or considerations for Linux VMs.
- Where screenshots are provided, consider including CLI output or code snippets as alternatives for users who do not use the Azure Portal.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/transport-layer-security.md
.../blob/main/articles/backup/transport-layer-security.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exclusively discusses enabling TLS 1.2 for Azure Backup on Windows systems, with detailed registry and .NET Framework configuration steps. There are no instructions, examples, or references for Linux systems or cross-platform scenarios. All troubleshooting and configuration guidance is Windows-centric, and Windows tools (registry, KB articles) are mentioned exclusively.
Recommendations
- Add a dedicated section for enabling and verifying TLS 1.2 on Linux systems, including relevant configuration files (e.g., OpenSSL, system-wide TLS settings).
- Provide command-line examples for Linux (e.g., using openssl, curl, or systemctl) to verify TLS support.
- Include troubleshooting steps and common issues for Linux environments.
- Reference Azure Backup client requirements and TLS configuration for Linux agents, if available.
- Ensure parity in examples and guidance for both Windows and Linux users, presenting both platforms side-by-side where possible.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-postgresql-backup.md
...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation demonstrates a bias toward Windows by providing PowerShell scripts as the primary or only example for granting privileges to database users. There is no equivalent example for Linux users (e.g., bash shell, psql commands), and PowerShell is mentioned before alternatives like PG admin or PSQL. This can make it harder for Linux users to follow the tutorial, especially in environments where PowerShell is not available.
Recommendations
- Add explicit Linux/Unix examples for granting privileges, such as using psql commands or bash scripts.
- When referencing PowerShell, always provide equivalent steps for Linux (e.g., using psql or shell scripts) and mention them together.
- Avoid presenting Windows/PowerShell methods first; instead, list both Windows and Linux approaches side by side or in parallel sections.
- Clarify that PG admin and PSQL are cross-platform tools and provide example commands for both.
- Review all steps to ensure that Linux users can complete the tutorial without needing access to PowerShell.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-sql-backup.md
...-docs/blob/main/articles/backup/tutorial-sql-backup.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on SQL Server running on Azure VMs with Windows OS. It exclusively references Windows-specific components (such as AzureBackupWindowsWorkload extension, NT Service accounts, and SQLIaaSExtension), and does not mention or provide guidance for SQL Server on Linux VMs. There are no Linux-specific instructions, examples, or troubleshooting steps, and all tooling and extension references are Windows-centric.
Recommendations
- Add explicit guidance for SQL Server running on Linux VMs, including prerequisites, supported backup scenarios, and any differences in process.
- Provide Linux-specific examples and screenshots where applicable, such as using the Azure portal or CLI to discover and back up SQL Server databases on Linux VMs.
- Document the equivalent Linux extensions or agents (if available), or clarify if the described backup solution is not supported for Linux.
- Include troubleshooting steps and permission requirements relevant to Linux environments (e.g., service accounts, file permissions, SQL authentication).
- Clearly state OS limitations or support matrix at the beginning of the tutorial to set expectations for users running SQL Server on Linux.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/upgrade-mars-agent.md
...e-docs/blob/main/articles/backup/upgrade-mars-agent.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
powershell_heavy
Summary
The documentation exclusively describes upgrading the MARS agent on Windows environments, referencing Windows-specific tools (Remote Desktop, DPM Console), graphical wizards, and agent installers. There are no Linux examples, nor any mention of Linux-compatible procedures or tools. All instructions assume a Windows server context and Windows administrative patterns.
Recommendations
- Clarify in the introduction that the MARS agent is only supported on Windows, if that is the case. If Linux support exists or is planned, add equivalent instructions for Linux environments.
- If Linux support is not available, explicitly state this to avoid confusion for cross-platform administrators.
- Where possible, provide parity for Linux by referencing Azure Backup solutions or agents available for Linux, and link to their documentation.
- Avoid using Windows-specific terminology (e.g., Remote Desktop, DPM Console) without noting platform limitations.
- Add a section comparing Windows and Linux backup agent options in Azure, to help users choose the right solution for their OS.
Baremetal Infrastructure
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/concepts-baremetal-infrastructure-overview.md
...tructure/concepts-baremetal-infrastructure-overview.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation page primarily describes Azure BareMetal Infrastructure in a platform-neutral way, but it exhibits subtle Windows bias. It references Windows-centric tools and patterns (such as Active Directory and DNS), and does not provide Linux-specific operational examples or management guidance. The only OSes explicitly listed are RHEL and SLES, but there are no examples or instructions for Linux users. Windows tools and patterns (e.g., Azure portal, Active Directory) are mentioned before or instead of Linux equivalents.
Recommendations
- Add Linux-specific operational examples, such as using SSH for access, or Linux-native management tools and scripts.
- Provide parity in instructions for managing BareMetal instances via Linux command-line tools (e.g., Azure CLI on Linux, Bash scripting), not just via the Azure portal.
- Mention and provide guidance for integrating with Linux-based identity and directory services (such as LDAP or FreeIPA) alongside or instead of Active Directory.
- Include examples of configuring networking, storage, and backup/recovery solutions using Linux tools and conventions.
- Explicitly state support for other Linux distributions if available, and provide guidance for their use.
Baremetal Infrastructure
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/workloads/nc2-on-azure/about-nc2-on-azure.md
...structure/workloads/nc2-on-azure/about-nc2-on-azure.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing on Windows Server and SQL Server licensing benefits, providing detailed instructions for obtaining Extended Security Updates (ESU) for Windows, and referencing Windows-specific product terms. While Linux is briefly mentioned in the context of Azure Hybrid Benefit, there are no concrete examples, instructions, or equivalent details for Linux workloads, tools, or licensing. The documentation also highlights Windows-specific cost benefits and support processes without Linux parity.
Recommendations
- Provide equivalent details for Linux workloads, such as supported Linux distributions, licensing options, and any cost-saving programs (e.g., Azure Hybrid Benefit for Linux).
- Include instructions or references for obtaining extended support or updates for Linux VMs, if available, similar to the ESU process for Windows.
- Mention Linux-specific scenarios, tools, or migration paths where relevant, ensuring Linux is not only referenced as an afterthought.
- Balance the discussion of cost benefits and licensing by including Linux examples and links to Linux product terms or support resources.
- If certain features or benefits are Windows-only, explicitly state this and clarify Linux alternatives or limitations.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-faq.md
...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits a Windows bias by frequently referencing Windows tools, workflows, and terminology before or instead of Linux equivalents. For example, browser support is described in terms of Windows and Mac, with no mention of Linux. Keyboard layout instructions are provided only for Windows, and RDP (a Windows protocol) is discussed in detail, while SSH (commonly used on Linux) receives less focus. There are no examples or instructions tailored for Linux users, such as how to set keyboard layouts or use native SSH clients on Linux.
Recommendations
- Include Linux-specific instructions and examples where relevant, such as how to set keyboard layouts on popular Linux distributions.
- When discussing browser support, explicitly mention Linux and supported browsers on that platform.
- Provide parity in native client connection instructions, including examples for both RDP (Windows) and SSH (Linux/macOS).
- Avoid assuming the user is on Windows; use platform-neutral language or provide parallel instructions for Windows, Linux, and macOS.
- When referencing Microsoft Entra authentication, include links or notes for Linux VM scenarios, not just Windows.
- Where possible, balance the discussion of RDP (Windows) and SSH (Linux/macOS) to reflect cross-platform usage.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-developer.md
...ocs/blob/main/articles/bastion/quickstart-developer.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation shows a moderate Windows bias. Windows is consistently mentioned before Linux (e.g., in VM creation links and port requirements). Keyboard shortcut guidance is Windows-centric, with only a brief Mac note for connecting to Windows VMs. There are no Linux-specific connection examples, troubleshooting tips, or keyboard shortcut guidance. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.
Recommendations
- Alternate the order of Windows and Linux references, or list Linux first in some sections to balance visibility.
- Provide Linux-specific connection guidance, including keyboard shortcuts and troubleshooting tips for common Linux desktop environments.
- Include examples and screenshots for connecting to Linux VMs, not just Windows.
- Clarify any differences in user experience when connecting to Linux VMs (e.g., clipboard, audio, keyboard mapping).
- Ensure that all instructions and examples are provided for both Windows and Linux VMs, including any platform-specific caveats.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configuration-settings.md
...s/blob/main/articles/bastion/configuration-settings.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) as a primary scripting/configuration method, often before Azure CLI. There are no explicit Linux shell or Bash script examples, and no mention of Linux-specific tools or workflows. The examples and links for configuration are focused on the Azure portal and PowerShell, with Azure CLI included but not emphasized. No Linux-native guidance or parity is provided.
Recommendations
- Add explicit Bash/Linux shell examples for all configuration steps, especially for users managing Azure resources from Linux environments.
- Ensure Azure CLI examples are given equal prominence to PowerShell, and consider listing CLI before PowerShell where possible, as CLI is cross-platform.
- Include references to Linux-native tools or workflows where relevant (e.g., using Bash scripts, cloud-init, or SSH key management on Linux).
- Where possible, clarify that Azure CLI commands work on all platforms and provide sample commands in a Linux shell context.
- Add a section or note for Linux administrators highlighting any differences or considerations when configuring Azure Bastion from Linux systems.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/configure-host-scaling.md
...s/blob/main/articles/bastion/configure-host-scaling.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page focuses exclusively on using the Azure portal for host scaling and mentions PowerShell as an alternative method, with no reference to Linux-specific tools or CLI commands. Windows/PowerShell is mentioned as the only alternative to the portal, and there are no examples or guidance for Linux users (e.g., Azure CLI, Bash).
Recommendations
- Add equivalent instructions for configuring host scaling using Azure CLI (az bastion update), which is cross-platform and commonly used on Linux.
- Include examples using Bash or shell scripting for automation on Linux systems.
- Explicitly mention that PowerShell is available cross-platform, but also provide Azure CLI examples to ensure Linux parity.
- Consider reordering alternative methods so that CLI (cross-platform) options are mentioned before or alongside PowerShell.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/connect-ip-address.md
...-docs/blob/main/articles/bastion/connect-ip-address.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing RDP (a Windows protocol) in both the portal and native client sections, listing RDP before SSH, and omitting explicit Linux-focused examples or screenshots. There are no Linux-specific instructions, such as connecting from a Linux terminal or using Linux-native tools. All command-line examples use Azure CLI but are generic, with no mention of Linux authentication patterns or SSH key management. The documentation does not address Linux users' needs directly.
Recommendations
- Provide Linux-specific examples, such as connecting from a Linux terminal using SSH with Azure Bastion.
- Include screenshots or instructions that show connecting to Linux VMs (e.g., using SSH) in the Azure portal.
- List SSH (Linux) examples before RDP (Windows) examples, or present them in parallel to avoid Windows-first bias.
- Mention Linux authentication methods, such as using private key files and their typical locations on Linux systems.
- Clarify that the Azure CLI commands work on all platforms and provide any Linux-specific notes if needed.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-portal.md
...s/blob/main/articles/bastion/quickstart-host-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows VM creation first, listing Windows port (3389) before Linux (22), and providing keyboard shortcut guidance only for Windows VMs (including Mac-to-Windows shortcut mapping). There are no Linux-specific connection details, shortcut keys, or troubleshooting tips, and the audio output section does not clarify Linux support. The documentation does mention Linux VM creation, but examples and guidance are predominantly Windows-centric.
Recommendations
- Alternate the order of Windows and Linux VM references to avoid implicit prioritization.
- Provide Linux-specific connection instructions, including SSH client usage and relevant keyboard shortcuts for Linux VMs.
- Clarify audio output support for Linux VMs and provide troubleshooting steps if applicable.
- Include examples and tips for connecting from Linux and Mac clients to Linux VMs, not just Windows.
- Ensure parity in troubleshooting and usage notes for both Windows and Linux VM scenarios.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/work-remotely-support.md
...cs/blob/main/articles/bastion/work-remotely-support.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing PowerShell as a primary configuration method and referencing RDP (a Windows protocol) before SSH. There are no explicit Linux-focused examples or mentions of Linux tools, and the ordering and language suggest a Windows-first approach.
Recommendations
- Add explicit Linux-focused examples, such as using SSH from Linux/macOS terminals.
- Provide step-by-step instructions for configuring Azure Bastion from a Linux environment, including relevant CLI commands.
- Mention Linux-native tools (e.g., OpenSSH, terminal applications) alongside PowerShell and RDP.
- Ensure that SSH connectivity and Linux VM management are described with equal prominence to Windows/RDP scenarios.
- Reorder examples and tool mentions so that Linux and Windows approaches are presented with parity.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-about.md
...Docs/azure-docs/blob/main/articles/bastion/vm-about.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features and documentation before or instead of Linux equivalents. For example, the 'Copy and paste' section links only to a Windows VM guide, with no mention of Linux VMs. There is no explicit mention of Linux tools, SSH, or Linux-specific workflows in the main sections, and Windows terminology (such as RDP) is prioritized.
Recommendations
- Add parallel Linux examples and documentation links wherever Windows-specific features are described (e.g., provide a 'Copy and paste - Linux VMs' link or section).
- Ensure that SSH and Linux VM connection methods are mentioned alongside RDP and Windows methods in all relevant sections.
- Reference Linux tools and workflows (such as OpenSSH, SCP, or SFTP) where file transfer or remote access is discussed.
- Review all sections to ensure Linux parity in feature descriptions, troubleshooting, and FAQ links.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/whats-new.md
...ocs/azure-docs/blob/main/articles/bastion/whats-new.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page shows a subtle Windows bias: Windows-specific features (RDP, Entra ID for RDP) are listed before Linux equivalents (SSH), and the terminology and links (e.g., RDP, session recording) are Windows-centric. There is no mention of Linux remote desktop protocols or tools, and Linux examples are less prominent or missing.
Recommendations
- Ensure Linux-related features (such as SSH, Linux remote desktop protocols) are mentioned with equal prominence and detail as Windows features.
- Provide explicit examples and documentation links for Linux remote access scenarios, such as connecting to Linux VMs using Bastion.
- Include references to Linux-native tools (e.g., xrdp, VNC, SSH clients) where appropriate, and clarify parity between Windows and Linux support.
- Alternate the order of feature announcements to avoid consistently listing Windows features first.
- Add a section or table comparing Windows and Linux Bastion capabilities for transparency.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/vm-upload-download-native.md
...lob/main/articles/bastion/vm-upload-download-native.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates Windows bias by presenting Windows/RDP instructions and tools (MSTSC, Copy/Paste) first and in more detail, while Linux/SSH instructions are secondary and less detailed. There are no explicit Linux-native file manager examples, and the documentation assumes familiarity with Windows workflows. Linux users are directed to use SCP via the tunnel command, but no GUI or alternative Linux-native methods are discussed.
Recommendations
- Provide Linux-native client examples (e.g., using Remmina, KRDC, or rdesktop for RDP file transfer) alongside Windows examples.
- Present Linux and Windows instructions in parallel sections or with equal prominence.
- Include explicit Linux file transfer workflows (e.g., using Nautilus, Dolphin, or command-line tools) for both RDP and SSH.
- Avoid assuming the use of Windows-native tools (like MSTSC and Copy/Paste) as the default workflow.
- Add screenshots or step-by-step guides for Linux users, similar to those provided for Windows.
- Clarify any limitations or differences in file transfer support between platforms.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/accounts.md
...ftDocs/azure-docs/blob/main/articles/batch/accounts.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools and patterns, such as the Azure portal and Batch Management .NET library, without mentioning Linux equivalents or cross-platform command-line options (e.g., Azure CLI, Azure PowerShell, REST API). No Linux-specific examples or guidance are provided for creating or managing Batch accounts, and the order of presentation favors Windows tools first.
Recommendations
- Include examples for creating and managing Batch accounts using cross-platform tools like Azure CLI and REST API.
- Mention Azure PowerShell and Azure CLI alongside .NET and portal options, and provide links to relevant documentation.
- Add explicit guidance or examples for Linux users, such as shell commands or scripts.
- Ensure that references to management tools are presented in a neutral or parallel order (e.g., 'You can use the Azure portal, Azure CLI, Azure PowerShell, or .NET SDK...').
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-aad-auth-management.md
.../blob/main/articles/batch/batch-aad-auth-management.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively providing .NET (C#) examples, referencing only the Azure portal (which is often Windows-centric in its UI instructions), and using Windows-specific terminology such as 'Windows Azure Service Management API.' There are no examples or guidance for Linux users, such as using cross-platform SDKs, command-line tools (e.g., Azure CLI), or alternative authentication flows suitable for non-Windows environments.
Recommendations
- Include examples using cross-platform tools such as Azure CLI or Azure PowerShell (which is available on Linux and macOS) for application registration and permission assignment.
- Provide code samples in additional languages (e.g., Python, Java) that are commonly used on Linux.
- Clarify that the Azure portal is accessible from any OS, and consider providing equivalent instructions for using the Azure CLI or REST API for app registration and permission management.
- Avoid Windows-specific terminology where possible (e.g., refer to 'Azure Service Management API' instead of 'Windows Azure Service Management API').
- Add a section or callout specifically addressing Linux/macOS developers, outlining any differences or additional steps required.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-applications-to-pool-nodes.md
...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits Windows bias by referencing Windows-specific file types and installation patterns (e.g., .exe, .msi) as primary examples, without providing equivalent Linux examples (such as .sh scripts or .deb/.rpm packages). There are no Linux-specific tools, commands, or file types mentioned, and the examples assume a Windows environment. This may lead Linux users to feel unsupported or unclear about how to adapt the instructions for their platforms.
Recommendations
- Include Linux-specific examples alongside Windows ones, such as installing .deb or .rpm packages, or running shell scripts (.sh) in start tasks.
- Mention Linux tools and patterns (e.g., using bash scripts, apt/yum/zypper for package installation) wherever Windows tools (.msi, .exe) are referenced.
- Provide explicit examples of start task command lines for both Windows (cmd/PowerShell) and Linux (bash/sh).
- Clarify that the methods described apply to both Windows and Linux nodes, and note any platform-specific considerations.
- Add a section or table summarizing common installation patterns for both Windows and Linux environments.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-container-isolation-task.md
.../main/articles/batch/batch-container-isolation-task.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by describing Windows-specific paths and mount patterns in detail, listing Windows host/container paths first and exclusively in the main table, and omitting explicit Linux path examples. There are no Linux-specific code or path examples, and the documentation assumes familiarity with Windows drive letters and conventions.
Recommendations
- Add a table or section showing equivalent Linux host and container paths for each Azure Batch data path, using Linux filesystem conventions (e.g., /mnt/batch/tasks/applications).
- Provide Linux-specific examples and explanations, including how to mount paths in Linux containers and what the default Linux paths are.
- Ensure that code samples and explanations are balanced, showing both Windows and Linux scenarios where applicable.
- Avoid listing Windows paths and patterns first or exclusively; present both platforms in parallel for clarity and parity.
- Clarify any platform-specific differences in behavior, such as mount modes or default directories, in a dedicated comparison section.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-cli-templates.md
...e-docs/blob/main/articles/batch/batch-cli-templates.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation shows evidence of Windows bias in several areas. File path examples for uploading and downloading files use Windows-style paths (e.g., 'c:\source_videos\*.mp4') without providing Linux or macOS equivalents. The CLI file transfer commands only show Windows paths, and there are no explicit Linux shell examples or mentions of Linux-specific patterns for file operations. While the documentation does mention Linux in the context of VM pools and package installation, user-facing examples and instructions for local operations are Windows-centric.
Recommendations
- Provide parallel examples using Linux/macOS file paths (e.g., '~/source_videos/*.mp4' or '/home/user/source_videos/*.mp4') alongside Windows examples in all CLI command snippets.
- Explicitly mention that the Azure CLI and Batch CLI extension are cross-platform and supported on Windows, Linux, and macOS, including in the installation section.
- Add notes or callouts where file paths are used, clarifying the syntax differences between Windows and Unix-like systems.
- Include at least one end-to-end example workflow using Linux/macOS conventions (e.g., bash shell, forward slashes in paths) to demonstrate parity.
- Review all screenshots, code snippets, and instructions to ensure they are platform-agnostic or provide alternatives for both Windows and Linux users.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-custom-images.md
...e-docs/blob/main/articles/batch/batch-custom-images.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by consistently mentioning Windows (RDP) before Linux (SSH) when describing how to connect to VMs, providing only Windows-specific .NET SDK code samples (with 'batch.node.windows amd64' as the node agent SKU), and omitting explicit Linux-focused code examples or command-line walkthroughs. Additionally, there is no example of using Linux tools or scripts to create or manage images/pools, and the REST API example does not clarify Linux-specific values for nodeAgentSkuId.
Recommendations
- Provide parallel Linux-focused code samples (e.g., using 'batch.node.ubuntu' or other Linux nodeAgentSkuId values) alongside Windows examples in SDK and REST API sections.
- When describing how to connect to VMs, alternate or equally prioritize Linux (SSH) and Windows (RDP) instructions.
- Include explicit Linux command-line examples (e.g., using Bash/CLI) for preparing VMs, creating snapshots, and images.
- Clarify the nodeAgentSkuId values for common Linux distributions in REST API and SDK examples.
- Add references to Linux-specific documentation and tools where appropriate, not just Windows or generic Azure tools.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-job-prep-release.md
...ocs/blob/main/articles/batch/batch-job-prep-release.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Windows command-line examples (using 'cmd /c', Windows environment variables, and Windows file paths), referencing Windows tools and patterns, and omitting any Linux or cross-platform equivalents. The code samples and output use Windows-style paths and commands, with no mention of Bash, Linux shell scripting, or POSIX environment variables. This may hinder Linux users from easily adapting the guidance to their environment.
Recommendations
- Provide equivalent Linux/Bash command-line examples alongside Windows examples, using Bash syntax, Linux environment variables, and POSIX file paths.
- Clearly indicate cross-platform support for job preparation and release tasks, and document any platform-specific considerations.
- Update code samples to show how to specify command lines for both Windows and Linux nodes, possibly using conditional logic or configuration.
- Include sample output using Linux-style paths and commands to illustrate parity.
- Reference Linux tools (e.g., 'rm', 'echo', shell scripts) and patterns where appropriate, and avoid assuming Windows as the default platform.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/managed-identity-pools.md
...ocs/blob/main/articles/batch/managed-identity-pools.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation shows evidence of Windows bias, primarily by presenting Windows/PowerShell examples before Linux/Bash equivalents, and referencing Windows tools and documentation first. The .NET example is also Windows-centric, and the Instance Metadata Service link points to the Windows-specific page. Linux is included, but often after Windows, and with less detail.
Recommendations
- Present Linux/Bash examples before or alongside Windows/PowerShell examples, or alternate their order in each section.
- Link to both Windows and Linux versions of the Instance Metadata Service documentation, or use a platform-neutral link.
- Include code examples using cross-platform tools (e.g., Azure CLI, REST API) and ensure parity in detail and explanation for both Windows and Linux.
- When referencing SDKs or libraries, clarify their cross-platform support and provide at least one example using a Linux-friendly language or tool.
- Avoid defaulting to Windows terminology or tools (e.g., PowerShell, .NET) without also providing Linux alternatives (e.g., Bash, Python).
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-parallel-node-tasks.md
.../blob/main/articles/batch/batch-parallel-node-tasks.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways. The primary code sample for the .NET SDK uses a Windows VM image (MicrosoftWindowsServer) and node agent, with no equivalent Linux example provided. The only full code walkthrough is in C#/.NET, which is most commonly used on Windows. The referenced GitHub sample is also a C# console application, reinforcing Windows-centric tooling. Although the REST API example uses Ubuntu, it is less detailed and not accompanied by a Linux-focused SDK sample or workflow. There are no Linux shell or Python examples, and Windows tools and patterns are mentioned first or exclusively throughout the page.
Recommendations
- Add equivalent .NET SDK code samples for Linux pools (e.g., using Ubuntu images and batch.node.ubuntu agent SKU).
- Provide Python SDK examples, which are popular on Linux, showing pool creation and task submission with Linux VM images.
- Include Linux shell (bash) or CLI examples for common operations, such as pool creation and task submission.
- Reference Linux-focused sample projects on GitHub, or add new ones if they do not exist.
- When listing VM images in examples, alternate or show both Windows and Linux options.
- Ensure that REST API examples are as detailed and complete for Linux as for Windows.
- Mention Linux tools and patterns (e.g., bash scripting, cron jobs) where relevant, not just Windows/PowerShell.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
...tDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias. All code samples, configuration snippets, and walkthroughs exclusively use Windows tools (MS-MPI, cmd.exe, Windows Server images) and Batch .NET, with no equivalent Linux or cross-platform examples. Linux and Intel MPI are only mentioned in passing or in notes, and no concrete Linux-based code or setup instructions are provided. The sample application and setup instructions are entirely Windows-centric, and the only referenced code sample for Linux is external and not integrated into the main documentation.
Recommendations
- Provide parallel Linux-based examples using Python or Bash, Intel MPI, and Ubuntu or other Linux VM images.
- Include code snippets for creating pools with Linux images and installing Intel MPI via a StartTask using Bash.
- Show how to configure and run multi-instance tasks using Linux command lines (e.g., using mpirun or mpiexec for Intel MPI) in addition to Windows/MS-MPI.
- Add a Linux-specific walkthrough for building, packaging, and running an MPI application (e.g., using gcc/mpicc and Python).
- Reference and integrate the Batch Linux MPI code sample directly in the main documentation, not just as a tip.
- Ensure that all sections (requirements, setup, execution, troubleshooting) have both Windows and Linux instructions/examples side by side.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-compute-intensive-sizes.md
...n/articles/batch/batch-pool-compute-intensive-sizes.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Linux and Windows guidance, but there is a noticeable Windows bias. Windows examples and tools (e.g., PowerShell, Remote Desktop, Microsoft MPI) are often mentioned first or in more detail. The Windows example for installing GPU drivers is more step-by-step and includes a full command line, while the Linux example is less detailed and omits a direct command for driver installation. The Windows MPI example uses PowerShell and RDP, but there is no equivalent Linux MPI example. Windows-specific tools and patterns (e.g., MSI installers, RDP, PowerShell) are referenced without Linux equivalents.
Recommendations
- Ensure Linux and Windows examples are equally detailed and parallel in structure. For example, provide explicit Linux shell commands for driver installation, not just references.
- When listing OS-specific sections or tables, alternate the order or present Linux first in some cases to avoid 'windows_first' bias.
- For every Windows example (e.g., installing Microsoft MPI with PowerShell), provide a Linux equivalent (e.g., installing Intel MPI or OpenMPI with apt or yum).
- Reference Linux tools and patterns (e.g., SSH, bash scripts) wherever Windows tools (e.g., RDP, PowerShell) are mentioned.
- Expand the Linux MPI example to match the detail level of the Windows example, including explicit commands and configuration steps.
- Review for parity in troubleshooting and next steps sections, ensuring both OSes are equally represented.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-update-properties.md
...ob/main/articles/batch/batch-pool-update-properties.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by providing only a C# SDK example that uses a Windows VM image (MicrosoftWindowsServer) and a Windows node agent SKU. There are no equivalent examples for Linux VM images, Linux node agent SKUs, or usage of Linux-specific tools. The only concrete code sample is Windows-centric, and Linux alternatives are neither mentioned nor demonstrated.
Recommendations
- Add equivalent examples for updating a pool with a Linux VM image (e.g., Ubuntu or CentOS) and the corresponding Linux node agent SKU in both C# and REST API sections.
- Explicitly mention Linux VM image options alongside Windows in descriptive text and code comments.
- Provide at least one example using a Linux-based tool or scripting environment (e.g., Azure CLI on Linux, Bash scripting) to update pool properties.
- Ensure that documentation references to VM images and node agent SKUs include both Windows and Linux options equally.
- Review all code snippets and ensure parity between Windows and Linux scenarios, including authentication and environment variable handling where relevant.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-rendering-storage-data-movement.md
...rticles/batch/batch-rendering-storage-data-movement.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as cmdkey, net use, and Windows-style azcopy syntax) are presented in detail, with full command-line examples and configuration snippets. Linux equivalents (e.g., mounting Azure Files via CIFS, or using azcopy with Linux syntax) are either missing or only briefly mentioned. The section on Azure Files is explicitly focused on Windows, with no Linux mounting example provided. In the azcopy section, only the Windows command-line syntax is shown, and the Linux usage is not illustrated. Overall, Windows approaches are described first and in more depth, while Linux alternatives are less detailed or omitted.
Recommendations
- Provide parallel Linux examples for all Windows-specific instructions, especially for mounting Azure Files (e.g., using mount.cifs in a job preparation task).
- Include azcopy command-line examples using Linux syntax (e.g., azcopy cp source dest) and shell conventions.
- Ensure that for every Windows tool or command (e.g., cmdkey, net use), the Linux equivalent (e.g., mount, cifs-utils) is presented with equal detail.
- Reorganize sections to present Linux and Windows options with parity, or clearly separate them to avoid implicit prioritization.
- Expand the blobfuse section with more concrete Linux job/task configuration examples, similar to the detailed Windows Azure Files mounting example.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-sig-images.md
...zure-docs/blob/main/articles/batch/batch-sig-images.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as RDP, PowerShell) are often mentioned before or more prominently than their Linux equivalents. Some examples and instructions are Windows-centric or list Windows tooling first, and there is a lack of parity in Linux-specific examples or guidance, especially for common administrative tasks.
Recommendations
- Ensure that Linux and Windows instructions are presented with equal prominence and in parallel where possible (e.g., 'Connect via RDP (Windows) or SSH (Linux)' should be consistently paired in all relevant sections).
- Provide Linux-specific examples and commands alongside PowerShell, such as Bash/CLI equivalents, especially in sections listing how to retrieve supported images or manage resources.
- When referencing tools (e.g., RDP, PowerShell), always mention the Linux alternatives (e.g., SSH, Bash) at the same time, not as an afterthought.
- Add explicit Linux-focused walkthroughs for tasks like preparing a VM, mounting disks, and verifying pool nodes, not just generic or Windows-first instructions.
- Review all code snippets and ensure that, for every Windows/PowerShell example, a Linux/Bash/CLI equivalent is provided.
- In portal instructions, clarify SSH login steps for Linux as thoroughly as RDP steps for Windows, including any differences in credential setup or troubleshooting.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-dependencies.md
...cs/blob/main/articles/batch/batch-task-dependencies.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a strong Windows bias by exclusively using Windows command-line syntax (cmd.exe) in all code examples and referencing Windows tools. There are no Linux/bash equivalents or examples, and the documentation does not mention cross-platform considerations. This may mislead users into thinking Azure Batch is Windows-only or make it harder for Linux users to adapt the examples.
Recommendations
- Provide equivalent examples using bash/sh syntax (e.g., 'bash -c "echo taskA"') alongside the Windows 'cmd.exe' examples.
- Explicitly mention that Azure Batch supports both Windows and Linux compute nodes, and clarify any platform-specific behaviors.
- Add a section or note on how to adapt task commands for Linux pools, including differences in shell invocation and script handling.
- Ensure that all code snippets and sample projects include both Windows and Linux variants where applicable.
- Avoid using only Windows-specific tools or patterns (like 'cmd.exe') in documentation intended for a cross-platform audience.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md
...s/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Visual Studio (Windows-only), using Windows-specific UI instructions, and relying on PowerShell/NuGet Package Manager Console for package installation. There are no examples or guidance for Linux or cross-platform development environments (e.g., VS Code, JetBrains Rider, or CLI-based workflows). The documentation does not mention or provide parity for Linux users, such as using the .NET CLI or alternative editors.
Recommendations
- Add instructions for creating and managing .NET projects using the cross-platform .NET CLI (e.g., 'dotnet new console', 'dotnet add package').
- Mention and provide examples for using cross-platform editors like Visual Studio Code or JetBrains Rider.
- Clarify that Visual Studio is only required if using Windows-specific features, and provide Linux/macOS alternatives.
- Include screenshots or descriptions relevant to Linux/macOS environments.
- Provide a section or callout for Linux/macOS users, outlining any differences or additional steps.
- Ensure that PowerShell/NuGet Package Manager Console commands are accompanied by equivalent Bash or shell commands where possible.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output-file-conventions.md
...n/articles/batch/batch-task-output-file-conventions.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a strong Windows bias. All code samples are in C# and reference the .NET File Conventions library, with no mention of Linux, cross-platform, or non-Windows development environments. The instructions and code samples assume use of Visual Studio (a Windows-centric IDE), and there are no examples or guidance for using the library or conventions from Linux environments, with other languages, or via command-line tools. References to the Azure Storage client library are specific to .NET, and there is no mention of Linux-compatible alternatives or how to implement the conventions in Linux-based Batch pools.
Recommendations
- Add explicit guidance and code samples for using the File Conventions standard from Linux environments, such as with .NET Core on Linux, or with other languages (e.g., Python, Java).
- Include instructions for setting up and running the sample project on Linux (e.g., using VS Code, JetBrains Rider, or command-line .NET SDK), not just Visual Studio.
- Mention and provide examples for using Azure CLI, Azure Storage Explorer (which is cross-platform), or REST APIs to interact with persisted output files.
- Clarify that the File Conventions standard can be implemented in any language/environment, and link to or provide sample implementations for Linux users.
- Add a section or callout explicitly addressing Linux Batch pool scenarios and any platform-specific considerations.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output.md
...ure-docs/blob/main/articles/batch/batch-task-output.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits Windows bias by providing examples and instructions that reference Windows-specific patterns (such as .exe files and Windows command syntax) without offering equivalent Linux examples. The only explicit example of running a custom file movement solution uses Windows executables, and there is no mention of Linux shell scripts or tools. The page also references .NET and C# libraries first, with no mention of cross-platform alternatives or parity for Linux users.
Recommendations
- Provide equivalent Linux examples alongside Windows examples, such as using shell scripts (.sh) and Linux command syntax.
- Mention Linux tools (e.g., Bash, rsync, curl) for custom file movement solutions.
- Clarify that the Batch File Conventions library is only for .NET, and suggest cross-platform approaches or libraries for other languages and platforms.
- Include sample commands for both Windows and Linux nodes when describing how to invoke custom scripts or executables.
- Add a sample project or code snippets for Linux environments in the 'Next step' section.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output-files.md
...cs/blob/main/articles/batch/batch-task-output-files.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples are in C# and use Windows-style commands (e.g., 'cmd /v:ON /c'), with no Linux shell equivalents provided. File paths use backslashes by default, with only a brief note for Linux users to change slashes. The only sample project is a Visual Studio solution for .NET, and all tooling references (e.g., NuGet, Visual Studio) are Windows-centric. There are no Linux or cross-platform code samples, nor are there instructions for using Linux tools or SDKs. The documentation also refers to Windows tools and patterns first and exclusively.
Recommendations
- Provide equivalent Linux shell (bash) command examples for task commands, alongside the Windows 'cmd' examples.
- Include code samples in additional languages commonly used on Linux (e.g., Python, Java), and demonstrate use of the Azure SDK for these languages.
- Show file path examples using both Windows (backslash) and Linux (forward slash) conventions, not just a note.
- Offer instructions for using cross-platform editors (e.g., VS Code) and package managers (e.g., pip for Python, Maven for Java) in addition to Visual Studio and NuGet.
- Add a Linux-based sample project or instructions for running the sample on Linux, including any required setup.
- Explicitly mention and demonstrate how to use the Batch service API from Linux environments, not just Windows.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-user-accounts.md
...e-docs/blob/main/articles/batch/batch-user-accounts.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates several forms of Windows bias. Windows tools and patterns (e.g., RDP, DPAPI, 'cmd.exe', 'cmd /c') are mentioned before or instead of Linux equivalents. In code examples, Windows-specific commands are used (such as 'cmd.exe /c echo') without providing Linux shell equivalents (like '/bin/bash -c'). The .NET example for named user accounts is split into Windows and Linux, but only the Windows example includes a full command line for running a task under a named user account. Linux-specific instructions are less prominent, and Linux command examples are missing in several places. Additionally, Windows tools (e.g., DPAPI) are referenced without mentioning Linux alternatives.
Recommendations
- For every example using Windows-specific commands (e.g., 'cmd.exe /c echo'), provide a Linux equivalent (e.g., '/bin/bash -c "echo hello"').
- When referencing Windows tools like DPAPI, mention Linux alternatives for secret management (e.g., GnuPG, file permissions, or other Linux-native approaches).
- Ensure that Linux and Windows instructions/examples are presented with equal prominence and in parallel where possible, rather than Windows first.
- Add explicit Linux code examples for running tasks under named user accounts, including command lines using bash/sh.
- In introductory sections, mention SSH and Linux access patterns before or alongside RDP and Windows.
- Review all code snippets and update them to include both Windows and Linux command-line examples where applicable.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/create-pool-ephemeral-os-disk.md
...b/main/articles/batch/create-pool-ephemeral-os-disk.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary method for programmatically querying VM capabilities (specifically 'EphemeralOSDiskSupported'), without providing equivalent Linux or cross-platform CLI examples. The mention of PowerShell cmdlets and the lack of Azure CLI, Bash, or other Linux-native tooling examples suggest a preference for Windows tools and patterns. Additionally, Windows-specific tools are mentioned before any Linux alternatives, which are absent.
Recommendations
- Add Azure CLI and Bash examples for querying VM capabilities, such as checking 'EphemeralOSDiskSupported', alongside the PowerShell example.
- Explicitly mention cross-platform tools (e.g., Azure CLI) and provide usage instructions for both Windows and Linux environments.
- Ensure that code and command-line examples are balanced between Windows and Linux, or presented in a platform-neutral way.
- Reference Linux documentation and tools where appropriate, and avoid assuming PowerShell as the default scripting environment.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/credential-access-key-vault.md
...lob/main/articles/batch/credential-access-key-vault.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong Windows bias. All code examples are provided exclusively in PowerShell, with no equivalent Bash or Linux shell commands. Windows-specific tools and patterns (such as PowerShell cmdlets, .msi installers, and references to Windows Management Framework) are used throughout, and there is no mention of how to perform these tasks on Linux Batch nodes. The documentation assumes a Windows environment by default, and Linux alternatives are not discussed or linked.
Recommendations
- Provide equivalent Bash or Azure CLI examples for all major steps, including certificate creation, service principal setup, and Key Vault access.
- Mention and demonstrate how to install necessary tools (e.g., Azure CLI) on Linux Batch nodes, rather than only referencing PowerShell and .msi installers.
- Explicitly state support for both Windows and Linux Batch nodes, and provide parallel instructions or callouts for Linux users.
- Reference Linux tools (e.g., openssl for certificate generation) and show how to authenticate and access Key Vault from Linux scripts.
- Reorder sections or provide tabs so that Linux and Windows instructions are presented with equal prominence.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/jobs-and-tasks.md
.../azure-docs/blob/main/articles/batch/jobs-and-tasks.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation exhibits a mild Windows bias. In several places, Windows tools and patterns (e.g., 'cmd.exe', 'robocopy', 'setup.exe', MSI installers) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. The command-line examples place Windows syntax before Linux, and Windows-specific tools are suggested without Linux alternatives. There are no PowerShell-specific examples, but the overall pattern favors Windows terminology and tools.
Recommendations
- When providing command-line examples, alternate the order or present Linux examples first in some cases.
- Where Windows tools like 'robocopy', 'setup.exe', or MSI are mentioned, also mention common Linux equivalents (e.g., 'cp', 'rsync', '.sh' scripts, '.deb' or '.rpm' packages).
- Explicitly state that both Windows and Linux nodes are supported, and provide parallel examples for both platforms where possible.
- If referencing Windows environment variable syntax, also provide the Linux syntax in equal prominence.
- Where application packaging is discussed, mention Linux-native packaging and installation methods alongside Windows ones.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/low-priority-vms-retirement-migration-guide.md
...s/batch/low-priority-vms-retirement-migration-guide.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for automating migration to Spot VMs. However, PowerShell is called out as the only alternative to CLI for automation, and is presented before the Azure portal (UI) method. There are no explicit Linux shell or Bash-specific examples, and PowerShell is highlighted as a primary automation method, which may bias towards Windows users. Additionally, the PowerShell section uses Windows-style command syntax and context variables, with no mention of Linux equivalents or cross-platform PowerShell usage.
Recommendations
- Add Bash shell script examples for common migration tasks, especially for validation and automation, to provide parity with PowerShell.
- Clarify that Azure CLI is fully cross-platform and can be used on Windows, Linux, and macOS, and consider listing it as the primary automation method.
- If PowerShell is included, specify that Azure PowerShell can also be run on Linux/macOS (with PowerShell Core), or provide explicit Bash alternatives.
- Where possible, avoid presenting Windows-centric tools (like PowerShell) before platform-agnostic or Linux-native tools.
- Add troubleshooting and validation examples using Bash/CLI pipelines (e.g., using jq or grep with az batch pool show) to help Linux users.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/manage-private-endpoint-connections.md
.../articles/batch/manage-private-endpoint-connections.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell examples before Azure CLI, referencing the Az PowerShell module prominently, and using PowerShell-specific syntax. The Azure portal instructions are also more familiar to Windows users. While Azure CLI examples are provided, they appear after the PowerShell section, and there is no explicit mention of Linux or Bash environments.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell to emphasize platform neutrality.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash syntax where appropriate.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for cross-platform usage.
- If possible, include screenshots or terminal output from Linux environments to reinforce parity.
- Review and balance the prominence of Windows-specific tools and terminology throughout the documentation.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/monitor-application-insights.md
...ob/main/articles/batch/monitor-application-insights.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a strong Windows bias. Windows-specific tools (Visual Studio, WindowsServer VM images, cmd.exe) are mentioned exclusively or before any Linux equivalents. The only package installation example is given in PowerShell, and there are no Linux or cross-platform alternatives provided for key steps such as environment setup, package installation, or VM configuration. The documentation does not address how to use Application Insights with Azure Batch on Linux pools, nor does it provide Linux shell commands or mention .NET Core cross-platform compatibility.
Recommendations
- Add Linux-based prerequisites, such as instructions for installing .NET SDK on Ubuntu or other distributions.
- Provide equivalent Linux shell (bash) commands for NuGet package installation (e.g., 'dotnet add package').
- Include examples and configuration steps for deploying Application Insights on Azure Batch pools running Linux VMs (e.g., Ubuntu images).
- Mention and demonstrate how to run the sample code on .NET Core/.NET 6+ for cross-platform compatibility.
- Show how to use Linux-native tools and commands for staging files and running tasks (e.g., using bash scripts instead of cmd.exe).
- Clarify which features or libraries are Windows-only (e.g., Microsoft.ApplicationInsights.WindowsServer) and suggest alternatives or limitations for Linux.
- Add screenshots or walkthroughs for monitoring Linux-based compute nodes in the Azure portal.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/nodes-and-pools.md
...azure-docs/blob/main/articles/batch/nodes-and-pools.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation shows a mild Windows bias. Windows tools and patterns (such as .exe, .cmd, .bat, and PowerShell scripts) are mentioned first and in more detail than Linux equivalents. Container support examples focus on Windows Server images, and Docker on Linux is only briefly referenced. There are no explicit Linux shell or scripting examples, and Windows remote access (RDP) is mentioned before Linux (SSH). References to Windows-specific tools and patterns are more prominent, and Linux alternatives are less detailed or omitted.
Recommendations
- Provide Linux shell script examples (e.g., .sh, bash) alongside or before Windows script examples.
- When discussing remote access, mention SSH for Linux nodes before or equally with RDP for Windows nodes.
- In container support sections, include explicit examples and instructions for using Docker on Linux nodes, not just Windows.
- Ensure that Linux tools and patterns (such as mounting disks, using bash scripts, etc.) are described with the same level of detail as Windows equivalents.
- Add links to Linux-specific documentation (e.g., 'Provision Linux compute nodes in Azure Batch pools') in relevant sections, not just as a reference.
- Review all sections to ensure Linux and Windows parity in examples, tool mentions, and ordering.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/pool-endpoint-configuration.md
...lob/main/articles/batch/pool-endpoint-configuration.md
High Priority
View Details â
Detected Bias Types
windows_first
paired_examples
no_cli_examples
no_linux_tools
Summary
The documentation presents both Windows (RDP) and Linux (SSH) scenarios in parallel, with each example given for both platforms. However, Windows/RDP examples are consistently presented before Linux/SSH examples, and all code samples use high-level SDKs (C# for Windows, Python for Linux) rather than platform-native tools or CLI commands. There are no examples using Powershell, but also no Linux shell or CLI (e.g., Bash, az CLI) examples. The documentation does not mention or recommend platform-specific tools for either OS, but the ordering and language may subtly prioritize Windows.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Add examples using platform-native tools: Powershell for Windows, Bash or az CLI for Linux.
- Include explicit instructions or code samples for configuring endpoints using CLI commands on both platforms.
- Mention platform-specific considerations or troubleshooting steps for both Windows and Linux environments.
- Ensure that terminology and guidance is equally detailed for both OS types, and avoid language that assumes Windows as the default.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-portal.md
...e-docs/blob/main/articles/batch/quick-create-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively demonstrates creating a pool of Windows compute nodes and provides only Windows-specific command-line examples (e.g., using 'cmd', 'set', 'timeout'). There is no mention of Linux-based pools or equivalent Linux shell commands, and the steps for creating pools and tasks are tailored solely to Windows environments.
Recommendations
- Include instructions and screenshots for creating a pool of Linux compute nodes (e.g., using Ubuntu or CentOS images).
- Provide parallel Linux shell command examples for tasks (e.g., using 'bash -c "env; sleep 90"' instead of 'cmd /c "set AZ_BATCH & timeout /t 90 > NUL"').
- Explicitly mention that Azure Batch supports both Windows and Linux pools, and highlight any differences or considerations.
- Where possible, present both Windows and Linux examples side-by-side, or allow the user to select their preferred OS context.
- Update the narrative to avoid assuming Windows as the default, and ensure Linux users are equally supported throughout the quickstart.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
.../azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates a subtle Windows bias by recommending Visual Studio Code as the editor (which is often associated with Windows, though cross-platform), referencing the Visual Studio Code debugger and its launch.json for parameter passing, and concluding with a link to PowerShell-based management. There are no explicit Linux-specific instructions, examples, or references to Linux-native tools or editors. All command-line instructions are generic, but the only editor/debugger guidance is for Visual Studio Code, and the only alternative management tool mentioned is PowerShell.
Recommendations
- Add explicit instructions or tips for running and debugging the Node.js application on Linux and macOS, such as using terminal commands or editors like Vim, Emacs, or GNOME Builder.
- Provide equivalent examples for configuring command-line parameters in popular Linux-based editors or IDEs (e.g., JetBrains WebStorm, Atom, or using plain terminal).
- Include a section or link for managing CDN resources using Azure CLI (which is cross-platform and popular on Linux), not just PowerShell.
- When referencing editors or tools, clarify their cross-platform availability and suggest alternatives for Linux users.
- Ensure screenshots and file path examples use neutral or Linux-style paths (e.g., forward slashes) where possible.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-template.md
...docs/blob/main/articles/batch/quick-create-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by primarily featuring the Azure Portal (a GUI tool most familiar to Windows users) and referencing Azure PowerShell as the first alternative deployment method. There are no explicit Linux or cross-platform CLI examples, and the only command-line tool mentioned by name is PowerShell. The Azure CLI is mentioned, but only after PowerShell and without any example. There are no Linux shell (bash) or cross-platform scripting examples, nor is there guidance for Linux users.
Recommendations
- Add explicit Azure CLI (az) command examples for deploying the ARM template, with step-by-step instructions.
- Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform parity.
- Include bash shell scripting examples for Linux users.
- Mention and link to Linux-friendly tools (such as Cloud Shell, which is available in the browser and supports both bash and PowerShell).
- Clarify that all deployment methods (Portal, PowerShell, CLI, REST) are cross-platform, and provide links or instructions for each.
- Avoid listing PowerShell before CLI unless there is a technical reason; alternate or randomize order to avoid perceived bias.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/security-best-practices.md
...cs/blob/main/articles/batch/security-best-practices.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page generally aims for OS neutrality, but there are subtle signs of Windows bias. Windows-specific tools (e.g., PowerShell) are mentioned before or instead of Linux equivalents for certain operations, such as discovering supported images. The section on TLS configuration provides detailed guidance and links for Windows but omits equivalent Linux guidance. There are no Linux-specific examples or references to Linux-native tools (e.g., Bash, Linux configuration files), and where remote access is discussed, RDP (Windows) is mentioned before SSH (Linux).
Recommendations
- When referencing tools for discovering supported images, include Linux-native options (e.g., Azure CLI with Bash) alongside or before PowerShell.
- Provide equivalent guidance and links for configuring SSL/TLS on Linux, not just Windows.
- Where remote access is discussed, mention SSH (for Linux) before or alongside RDP (for Windows), and provide links to relevant Linux documentation.
- Add Linux-specific examples or callouts where OS-level configuration is required, such as patching, security hardening, or disk encryption.
- Review the order of OS mentions to ensure Linux is not consistently secondary to Windows.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/simplified-node-communication-pool-no-public-ip.md
...tch/simplified-node-communication-pool-no-public-ip.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias in troubleshooting sections by presenting Windows (PowerShell) commands before Linux equivalents, and by providing more detailed Windows command examples. In the 'Troubleshooting' section, the Windows PowerShell command (Test-NetConnection) is listed first, with the Linux command (nc) given second and without explanation. There are no Bash or Linux CLI examples for other operations (e.g., ARM deployment, REST API usage), and the portal instructions do not mention cross-platform CLI tools (e.g., Azure CLI) as a primary method.
Recommendations
- Present Linux and Windows command examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
- Provide equivalent Bash/Linux CLI commands (e.g., curl for REST API, az CLI for resource management) in all relevant sections, not just PowerShell.
- Expand troubleshooting steps to include Linux-native tools (e.g., dig for DNS, traceroute, etc.) with explanations.
- Instruct users on using Azure CLI and Bash for pool creation and management, not just the Azure portal or ARM templates.
- Ensure that all code snippets and screenshots are platform-agnostic or provide variants for both Windows and Linux environments.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/certificates-and-key-vault.md
...ervices-extended-support/certificates-and-key-vault.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the only command-line example for creating Key Vaults, requiring certificates 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 is there mention of Linux-compatible certificate formats or tools.
Recommendations
- Add Azure CLI examples for creating Key Vaults and uploading certificates, alongside PowerShell.
- Include instructions for generating and converting certificates using OpenSSL, which is standard on Linux.
- Mention and support certificate formats commonly used on Linux (such as PEM or CRT), and provide guidance for converting to .PFX if required.
- List Linux deployment tools and workflows (e.g., Azure CLI, VS Code) alongside Visual Studio.
- Ensure that all steps and screenshots have Linux parity, or note any platform-specific differences.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-family-2-3-4-retirement.md
...port/cloud-services-guestos-family-2-3-4-retirement.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily Windows-centric. All examples and instructions reference Windows Server OS families, PowerShell scripts, and Windows development tools (Visual Studio, .NET Framework). There are no Linux equivalents or migration paths discussed, and the only script provided is for Azure PowerShell, with no mention of Azure CLI or Bash alternatives.
Recommendations
- Provide equivalent Azure CLI or Bash scripts for identifying affected services, as Azure CLI is cross-platform and widely used on Linux.
- Clarify whether Linux-based cloud services are affected, and if not, explicitly state this to avoid confusion.
- Include migration guidance for Linux-based workloads if applicable, or a note that this retirement only impacts Windows-based guest OS families.
- Mention cross-platform development tools (e.g., VS Code, .NET Core/6+) where possible, not just Visual Studio and .NET Framework.
- Reorder or supplement instructions so that cross-platform or Linux options are presented alongside or before Windows-specific tools.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/tutorial-parallel-dotnet.md
...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias by exclusively using Windows Server VM images for compute pools, referencing Windows-specific ffmpeg builds, and providing only Windows command-line examples (cmd /c, ffmpeg.exe). There are no Linux pool configuration examples, nor any Linux-compatible ffmpeg usage or shell commands. The tutorial does not mention how to adapt the workflow for Linux compute nodes, despite Azure Batch supporting both Windows and Linux environments.
Recommendations
- Add explicit instructions and code samples for creating Linux-based pools, including the appropriate BatchImageReference and node agent SKU for Ubuntu or other supported Linux distributions.
- Provide Linux-compatible ffmpeg application package references and download links (e.g., static Linux builds from ffmpeg.org).
- Include example task command lines using Linux shell syntax (e.g., bash, ./ffmpeg -i ...) alongside the Windows cmd examples.
- Clarify any differences in application package deployment or resource file handling between Windows and Linux nodes.
- Update screenshots and walkthroughs to show both Windows and Linux pool/job/task creation and monitoring where applicable.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for enabling diagnostic logs, with no equivalent Azure CLI, Bash, or cross-platform scripting examples. Additionally, it recommends Microsoft Azure Storage Explorer (a GUI tool primarily associated with Windows, though available cross-platform) for log access, without mentioning Linux-native or command-line alternatives. There are no Linux-specific instructions or parity in tooling or workflow.
Recommendations
- Add Azure CLI examples for all PowerShell workflows, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash or shell script examples where applicable, especially for tasks like downloading and processing logs.
- Mention and provide examples using cross-platform tools such as azcopy, Azure CLI storage commands, or open-source alternatives for accessing and exporting logs.
- Clarify that PowerShell Core is available cross-platform, if retaining PowerShell examples, and provide installation guidance for Linux/macOS.
- Ensure that any tool recommendations (such as Storage Explorer) are clearly marked as cross-platform, and suggest command-line alternatives for headless or server environments.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-troubleshoot-compression.md
...blob/main/articles/cdn/cdn-troubleshoot-compression.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Windows tools (Fiddler, IIS) for troubleshooting and configuration, and omitting Linux equivalents or examples. The guidance for server-side configuration is focused solely on Microsoft IIS, with no reference to common Linux web servers such as Apache or Nginx. Troubleshooting steps and tool recommendations are Windows-centric, and Linux alternatives are not provided.
Recommendations
- Include Linux-based troubleshooting tools such as curl, wget, or command-line examples for checking HTTP headers.
- Add instructions for configuring compression on popular Linux web servers (e.g., Apache: mod_deflate, Nginx: gzip/brotli modules).
- Mention cross-platform tools (e.g., Wireshark, Postman) alongside Fiddler.
- Provide examples and guidance for both Windows and Linux environments, ensuring parity in troubleshooting steps.
- Clarify that IIS-specific instructions apply only to Windows servers, and provide equivalent steps for Linux-based origins.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-map-content-to-custom-domain.md
.../main/articles/cdn/cdn-map-content-to-custom-domain.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides detailed instructions and code samples for performing tasks using the Azure portal (web UI) and Azure PowerShell. There are no examples or instructions for using Azure CLI (which is cross-platform and preferred by many Linux users), nor are there bash or shell script equivalents. All command-line automation is shown with PowerShell, which is a Windows-centric tool, despite its availability on Linux. This may disadvantage Linux users or those who prefer bash/CLI workflows.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line tasks, such as adding or removing custom domains.
- Include bash/shell script snippets where appropriate, especially for DNS record management or validation steps.
- Explicitly mention that PowerShell is available cross-platform, but recommend Azure CLI for Linux/macOS users.
- Ensure that any references to tools or scripts are balanced between Windows and Linux environments.
- Consider adding a 'Choose your environment' or 'Choose your tool' tab set for PowerShell, Azure CLI, and possibly REST API.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/create-profile-endpoint-template.md
.../main/articles/cdn/create-profile-endpoint-template.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and cleaning up resources, but PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, and PowerShell is presented as a primary automation method alongside the CLI, which may suggest a Windows bias. Additionally, there are no mentions of Linux-specific tools or workflows, and the PowerShell section appears before the Portal section, reinforcing the Windows-first pattern.
Recommendations
- Add explicit bash shell examples for Linux/macOS users, especially for common tasks like setting variables and running Azure CLI commands.
- Clarify that Azure CLI commands can be run on Windows, Linux, and macOS, and consider providing bash-specific syntax (e.g., export instead of read -p for variable assignment).
- If PowerShell is included, note that PowerShell Core is cross-platform, or clarify when examples are Windows-specific.
- Consider listing Azure CLI (bash) as the default or first automation method, as it is cross-platform and more common for Linux users.
- Mention or link to documentation for using ARM templates with Linux-native tools (e.g., bash scripts, cloud-init, etc.) if relevant.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/managed-identity.md
.../azure-docs/blob/main/articles/cdn/managed-identity.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively describing configuration steps using the Azure Portal GUI, which is most familiar to Windows users. There are no CLI-based examples (such as Azure CLI or Bash scripts) that would be more accessible to Linux users. No PowerShell commands are shown, but the lack of Linux-friendly command-line instructions and the assumption of GUI usage reflects a Windows-centric approach.
Recommendations
- Add Azure CLI examples for all configuration steps, including enabling managed identity and configuring Key Vault access policies.
- Include Bash script snippets where appropriate to automate tasks for Linux users.
- Explicitly mention that all steps can be performed using cross-platform tools (Azure CLI, REST API) and provide links or examples.
- Ensure parity by presenting CLI instructions before or alongside GUI instructions, not just after.
- Clarify that the Azure Portal is web-based and platform-agnostic, but supplement with command-line alternatives for users who prefer or require them.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/monitoring-and-access-log.md
...cs/blob/main/articles/cdn/monitoring-and-access-log.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides detailed configuration steps and examples exclusively using Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples or instructions for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. The focus on PowerShell and lack of Linux or cross-platform alternatives demonstrates a Windows bias in the operational guidance.
Recommendations
- Add equivalent configuration instructions and code samples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Include Bash script examples for common tasks, such as enabling diagnostic settings and exporting logs.
- Explicitly mention that Azure PowerShell is available on Linux and macOS, but recommend Azure CLI for Linux users.
- Reorder or parallelize example sections so that both PowerShell and CLI/Bash options are presented together, giving equal prominence.
- Add notes or links to official documentation for Azure CLI and Bash usage for monitoring and logging tasks.
Certification
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/certification/validate-device-edge-secured-core.md
...les/certification/validate-device-edge-secured-core.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively describes validation steps using Windows GUI tools and terminology, with no mention of Linux equivalents or command-line methods. All instructions and screenshots are Windows-specific, indicating a strong Windows bias and lack of Linux parity.
Recommendations
- Add equivalent validation steps for Linux devices, such as checking TPM version via tpm2-tools or system logs.
- Include command-line examples for both Windows (e.g., PowerShell) and Linux (e.g., Bash) to validate device security features.
- Mention how Edge Secured-core certification applies to non-Windows platforms, if applicable, or clarify platform limitations.
- Provide screenshots or output examples from Linux environments where similar security features can be verified.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-family-1-retirement.md
...-support/cloud-services-guestos-family-1-retirement.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong Windows bias. All technical examples, including the only script provided, use Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. The OS families discussed are exclusively Windows Server-based, and migration recommendations focus solely on Windows Server versions and .NET frameworks. There are no Linux-based guest OS options or examples, and Windows tools and patterns are referenced exclusively and before any Linux equivalents (which are not mentioned at all).
Recommendations
- Provide equivalent Azure CLI or Bash script examples for determining OS Family, ensuring cross-platform compatibility.
- Mention and link to documentation for Linux-based guest OS options if available, or clarify if only Windows OS families are supported.
- If Linux guest OS is not supported for this service, explicitly state this to avoid confusion.
- When referencing tools or scripts, present cross-platform options (e.g., Azure CLI, REST API) before or alongside Windows/PowerShell examples.
- Consider including a section addressing migration paths for workloads that could move to Linux-based services (such as Azure Virtual Machines with Linux OS) if relevant.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/configure-scaling.md
...s/cloud-services-extended-support/configure-scaling.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows. The 'Next steps' section lists PowerShell and Visual Studio (both Windows-focused) as deployment options, with no mention of Linux equivalents (such as Azure CLI or cross-platform editors like VS Code). The only code example link for queue storage uses a Windows environment variable tab by default. There are no explicit Linux or cross-platform command-line examples, and the portal screenshots and instructions do not address Linux users or alternative tooling.
Recommendations
- Add Azure CLI examples for scaling and deployment, as Azure CLI is cross-platform and widely used on Linux.
- Include references to cross-platform editors like Visual Studio Code, not just Visual Studio.
- Ensure that links to quickstarts or tutorials include Linux/macOS tabs or examples, not just Windows/PowerShell.
- Explicitly mention that the Azure portal is OS-agnostic, and clarify any steps that might differ on Linux.
- Balance the order of tool mentions (e.g., list Azure CLI before or alongside PowerShell) to avoid 'windows_first' bias.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-key-vault-virtual-machine.md
...s-extended-support/enable-key-vault-virtual-machine.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily Windows-centric: it only discusses the Key Vault VM extension for Windows, references the Windows certificate store, and provides no information or examples for Linux VMs or their certificate management. All instructions, settings, and terminology are specific to Windows environments, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
- Add information about the availability (or lack thereof) of the Key Vault VM extension for Linux VMs in Azure Cloud Services (extended support).
- If a Linux equivalent exists, provide parallel instructions and examples for Linux, including how certificates are stored and managed.
- Mention Linux certificate store locations and relevant configuration properties if supported.
- If only Windows is supported, explicitly state this early in the documentation to set expectations.
- Reference Linux tools, patterns, or Azure extensions where appropriate, and provide links to relevant documentation.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-prerequisite.md
...cloud-services-extended-support/deploy-prerequisite.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by frequently referencing PowerShell and Visual Studio as primary tools for deployment and configuration, with little or no mention of Linux equivalents or cross-platform alternatives. PowerShell is listed before Azure CLI, and Visual Studio is mentioned as a deployment tool without reference to cross-platform IDEs. There are no explicit Linux shell or CLI examples, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples, especially for common tasks like creating virtual networks and key vaults.
- Mention cross-platform or Linux-friendly tools (e.g., Visual Studio Code, Azure CLI) wherever Visual Studio or PowerShell are referenced.
- Ensure that all code snippets and instructions are platform-agnostic or include both Windows and Linux variants where applicable.
- Add explicit Linux shell (bash) examples for tasks currently only shown with PowerShell.
- Clarify when a tool or method is Windows-only, and suggest Linux-compatible alternatives.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-sdk.md
...articles/cloud-services-extended-support/deploy-sdk.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias in several ways: all command-line examples for key vault and certificate management use PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. The SDK code samples and extension configuration reference Windows-centric patterns (e.g., RDP, Microsoft.Windows.Azure.Extensions). Windows tools and terminology (PowerShell, RDP, .cspkg) are mentioned exclusively or before Linux equivalents, and there is no guidance for Linux users on how to perform these steps. The absence of Linux or cross-platform command-line examples and the prioritization of Windows-centric workflows indicate a significant bias toward Windows environments.
Recommendations
- Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for key vault and certificate management.
- Explicitly mention Linux support and provide instructions for Linux users, including how to install required SDKs and tools.
- Include references to Linux-friendly remote access extensions (such as SSH) alongside RDP, and clarify cross-platform options.
- Document how to generate and upload certificates from Linux environments (e.g., using OpenSSL and Azure CLI).
- Review terminology and tool references to ensure parity (e.g., mention both .cspkg and .zip formats, clarify their use on Linux).
- Add a section or callout for cross-platform deployment considerations, highlighting any differences or requirements for Linux users.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-alerts.md
...icles/cloud-services-extended-support/enable-alerts.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page primarily references Windows-centric tools and workflows, such as PowerShell and Visual Studio, and does not provide Linux-specific examples or mention Linux tools (e.g., Azure CLI, Bash scripting). The order of deployment options also lists Windows tools before cross-platform or Linux-friendly alternatives, and there are no explicit Linux examples or screenshots.
Recommendations
- Include Azure CLI examples for enabling monitoring and deploying Cloud Services, as Azure CLI is cross-platform and widely used on Linux.
- List deployment options in a neutral or alternating order (e.g., Azure portal, Azure CLI, PowerShell, Template, Visual Studio) to avoid Windows-first bias.
- Add explicit mention of Linux support and provide screenshots or instructions relevant to Linux users where applicable.
- Reference Bash scripting or other Linux-native automation options alongside PowerShell.
- Clarify that the Azure portal is accessible from any OS, and highlight any differences (if any) for Linux users.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-rdp.md
...articles/cloud-services-extended-support/enable-rdp.md
High Priority
View Details â
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 for managing the Remote Desktop extension use PowerShell, a Windows-centric tool, with no mention of Linux alternatives such as Azure CLI or Bash. The workflow assumes the use of RDP, which is natively a Windows protocol, and does not discuss Linux-compatible remote access methods (e.g., SSH, xrdp). The 'Next steps' section lists PowerShell and Visual Studio (both Windows-focused) before mentioning templates, and does not reference Linux-native tools or workflows.
Recommendations
- Add Azure CLI examples for managing the Remote Desktop extension, as Azure CLI is cross-platform and works on Linux.
- Include instructions or notes for connecting to Linux role instances, such as using SSH or xrdp, if supported.
- Mention Linux-compatible remote desktop clients and workflows for users on non-Windows platforms.
- Reorder 'Next steps' to present cross-platform options (Azure portal, Azure CLI, templates) before Windows-specific tools (PowerShell, Visual Studio).
- Clarify whether the Remote Desktop extension is applicable only to Windows role instances, and provide guidance for Linux instances if relevant.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-wad.md
...articles/cloud-services-extended-support/enable-wad.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page provides only PowerShell and ARM template examples for applying the Azure diagnostics extension, with all command-line instructions using PowerShell (a Windows-centric tool). There are no examples or instructions for Linux users (e.g., using Azure CLI, Bash, or cross-platform scripting), and Windows tools/patterns are mentioned exclusively and first. This creates a strong Windows bias and limits accessibility for Linux users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux users.
- Include Bash scripting examples where relevant, especially for file manipulation or automation.
- List cross-platform methods (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
- Ensure that all schema download and configuration steps have Linux-compatible alternatives.
- Review and update the 'Next steps' section to include Linux-friendly tools and workflows, such as Azure CLI and VS Code.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/in-place-migration-technical-details.md
...tended-support/in-place-migration-technical-details.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell as the primary or sole scripting interface for migration operations (e.g., abort/commit, retrieving deployments), with no explicit mention or examples for Linux users (such as Bash, Azure CLI, or cross-platform scripting). Where command-line tools are referenced, PowerShell is consistently listed before Azure CLI, and no Linux-specific workflows or examples are provided. This may make the documentation less accessible or clear for users on Linux or macOS platforms.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples for all migration operations, including abort, commit, and deployment retrieval.
- Explicitly mention that Azure CLI is cross-platform and supported on Linux/macOS, and provide equivalent commands.
- Where PowerShell is referenced for troubleshooting (e.g., retrying stuck operations), add Azure CLI and/or REST API alternatives.
- Include a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tools.
- Review all references to scripting and command-line tools to ensure parity and clarity for non-Windows users.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/override-sku.md
...ticles/cloud-services-extended-support/override-sku.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides explicit PowerShell examples and references to the Azure PowerShell module (New-AzCloudService), which is primarily a Windows-centric tool. There are no CLI (az cli), Bash, or Linux-native examples. The SDK example is in C#, a language most commonly associated with Windows development. No Linux-first or cross-platform command-line examples are provided.
Recommendations
- Add equivalent Azure CLI (az cli) examples for setting allowModelOverride, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash or shell script examples where appropriate, especially for automation scenarios.
- Mention cross-platform tools and approaches before or alongside PowerShell, rather than only providing PowerShell and C# examples.
- Clarify in the documentation that the PowerShell example is also available on Linux (if true), or provide guidance for Linux users.
- Consider adding SDK examples in languages popular on Linux, such as Python or Java, to improve parity.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-cscfg-file.md
...s/cloud-services-extended-support/schema-cscfg-file.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits Windows bias by referencing only Windows file paths (e.g., C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK), mentioning Visual Studio and .NET SDK tools without Linux equivalents, and omitting Linux-specific instructions or examples for locating or using the schema files. There are no Linux or cross-platform examples or guidance.
Recommendations
- Include Linux and macOS file paths for the Azure SDK schema installation location, or clarify cross-platform installation differences.
- Mention and provide examples for using cross-platform tools (such as Azure CLI or VS Code) for schema validation and configuration, not just Visual Studio.
- Add explicit instructions or notes for Linux users on how to obtain and use the .cscfg schema files.
- Ensure that any references to SDK tools or workflows are accompanied by Linux/macOS equivalents or alternatives.
- Consider providing a table or section that summarizes differences in usage or file locations between Windows and Linux environments.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/non-vnet-migration.md
.../cloud-services-extended-support/non-vnet-migration.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page focuses exclusively on migration steps using the Azure portal and references PowerShell for further migration steps, without mentioning or providing examples for Linux users or CLI tools such as Azure CLI. The 'Next steps' section lists PowerShell before any Linux-friendly alternatives, and there are no Linux-specific instructions or screenshots.
Recommendations
- Add equivalent migration instructions using Azure CLI, which is cross-platform and widely used on Linux.
- Include examples or links for Bash scripting or automation, not just PowerShell.
- In the 'Next steps' section, list Azure CLI and Linux-friendly options alongside or before PowerShell.
- Add a note clarifying that all steps can be performed on Linux using Azure CLI, and provide links to relevant documentation.
- Ensure screenshots and UI references are platform-agnostic or include notes for Linux users where appropriate.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/overview.md
...n/articles/cloud-services-extended-support/overview.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before alternatives, referencing PowerShell as a primary automation method, and omitting Linux-native tools or CLI examples. There are no explicit Linux or cross-platform command-line examples (e.g., Azure CLI, Bash), and the guidance does not mention Linux development environments or editors.
Recommendations
- Add Azure CLI examples alongside or before PowerShell for deployment and migration tasks, as Azure CLI is cross-platform and widely used on Linux.
- Mention and provide examples using cross-platform editors (e.g., VS Code) in addition to Visual Studio.
- Explicitly state that all deployment and management operations can be performed from Linux, macOS, and Windows, and link to relevant Linux documentation.
- Reorder tool listings to avoid always listing Windows tools first; alternate or group by platform-neutral and platform-specific tools.
- Provide Bash script examples where automation is discussed, or at least reference their availability.
- Ensure that all referenced links for deployment (e.g., 'deploy-powershell.md', 'deploy-visual-studio.md') have Linux equivalents or alternatives (e.g., 'deploy-cli.md', 'deploy-vscode.md').
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/post-migration-changes.md
...ud-services-extended-support/post-migration-changes.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Windows-centric tools in its examples and instructions. PowerShell is mentioned repeatedly as the primary automation and scripting tool, with no equivalent Bash, Azure CLI, or Linux shell examples provided. References to Visual Studio (a Windows-only IDE) and the lack of explicit Linux or cross-platform guidance further reinforce the bias. Azure CLI is mentioned only once, and always after PowerShell, while REST API is presented as a generic alternative rather than a first-class cross-platform option.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts alongside PowerShell, especially for retrieving deployment files and managing resources.
- Include explicit instructions or references for Linux/macOS users, such as using Azure CLI or REST API from non-Windows environments.
- Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio for deployment file updates.
- Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
- Add a section or note clarifying that all operations can be performed from Linux/macOS using CLI or REST API, and link to relevant documentation.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-cscfg-networkconfiguration.md
...-extended-support/schema-cscfg-networkconfiguration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation references PowerShell and template deployments as the only methods for configuring reserved IP allocation, without mentioning Linux-native tools (e.g., Azure CLI, Bash). There are no Linux or cross-platform command-line examples, and the only tool mentioned is PowerShell, which is traditionally associated with Windows. This may lead Linux users to believe that only Windows tools are supported or recommended.
Recommendations
- Include Azure CLI examples for all configuration tasks, especially for reserved IP allocation, to provide parity with PowerShell.
- Explicitly mention that Azure CLI and other cross-platform tools can be used from Linux, macOS, and Windows.
- Add Bash or shell script examples where appropriate.
- Clarify that PowerShell is available cross-platform, or provide links to documentation for using PowerShell on Linux if it remains the preferred method.
- Ensure that any references to deployment methods (e.g., 'template and PowerShell deployments') also mention equivalent Linux-friendly options.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-file.md
...s/cloud-services-extended-support/schema-csdef-file.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page references a Windows-specific file path for the Azure Diagnostics configuration schema and only mentions the .NET SDK installation directory on Windows. There are no Linux or cross-platform equivalents or examples provided, and the only tooling context is Windows-centric. This may lead Linux users to believe that the csdef schema and related tools are only available or supported on Windows.
Recommendations
- Add equivalent Linux file paths or clarify where the schema files can be found when using the Azure SDK on Linux.
- Mention cross-platform SDK installation methods (e.g., via dotnet CLI, package managers) and where schema files are located on non-Windows systems.
- Provide examples or notes for both Windows and Linux environments when referencing tooling, file locations, or SDK usage.
- Avoid referencing only Windows tools or directories; if Windows is mentioned, ensure Linux/macOS equivalents are also described.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-workerrole.md
...d-services-extended-support/schema-csdef-workerrole.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page shows a Windows bias through its exclusive use of Windows-centric terminology and patterns. It references Windows certificate stores (CurrentUser, LocalMachine, My, Root, etc.), environment variables in Windows format (%ROLEROOT%), and startup scripts as CMD/batch files in ANSI format. There are no examples or mentions of Linux equivalents, such as Linux certificate stores, environment variable syntax, or shell scripts. All examples and descriptions assume a Windows environment, with no guidance for Linux-based deployments.
Recommendations
- Add explicit examples and guidance for Linux-based worker roles, including shell script (sh/bash) startup tasks and Linux file formats.
- Document Linux equivalents for certificate store locations and names, or clarify platform-specific differences.
- Use cross-platform environment variable syntax (e.g., $ROLEROOT for Linux) and clarify how paths and variables are handled on Linux.
- Where Windows-specific terms are used (e.g., CMD files, %ROLEROOT%), provide Linux alternatives or note platform differences.
- Include a section or table summarizing platform-specific behaviors and configuration requirements for both Windows and Linux worker roles.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/states.md
...ain/articles/cloud-services-extended-support/states.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing PowerShell and Visual Studio (Windows-centric tools) as primary deployment methods, with no mention of Linux-native tools or CLI examples. PowerShell is referenced before more cross-platform options like ARM templates, and there is no explicit guidance for Linux users or parity in deployment instructions.
Recommendations
- Add Azure CLI deployment instructions and links, as Azure CLI is cross-platform and widely used on Linux.
- Include examples or references for deploying Cloud Services (extended support) from Linux environments.
- Mention Linux-compatible editors (e.g., VS Code) alongside Visual Studio.
- Reorder deployment options to present cross-platform methods (Azure portal, Azure CLI, ARM templates) before Windows-specific tools (PowerShell, Visual Studio).
- Explicitly state that deployment can be performed from both Windows and Linux systems, and provide guidance for each.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/swap-cloud-service.md
.../cloud-services-extended-support/swap-cloud-service.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows PowerShell (Get-AzRole) as the only CLI example for checking role status, mentioning Visual Studio and PowerShell as deployment options without Linux equivalents, and omitting Azure CLI or Bash examples. No Linux-specific tools or workflows are described, and Windows tools are mentioned before or instead of cross-platform alternatives.
Recommendations
- Add Azure CLI examples (e.g., 'az' commands) for checking role status and performing swaps, as Azure CLI is cross-platform.
- Include Bash or shell script examples where relevant, especially for REST API usage.
- Mention cross-platform IDEs (such as VS Code) alongside Visual Studio, or clarify Visual Studio's availability on Windows only.
- List deployment options in a neutral or alternating order (e.g., Azure portal, ARM template, Azure CLI, PowerShell, Visual Studio) to avoid Windows-first ordering.
- Explicitly state that PowerShell examples are Windows-specific and provide equivalent commands for Linux/macOS users.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/cloud-shell-predictive-intellisense.md
...les/cloud-shell/cloud-shell-predictive-intellisense.md
High Priority
View Details â
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 using PowerShell cmdlets and patterns. There are no examples or mentions of equivalent features or workflows for Bash or other Linux shells, despite Azure Cloud Shell supporting Bash. The editor instructions also assume PowerShell usage. This creates a bias toward Windows/PowerShell users and does not address Linux/Bash users' needs.
Recommendations
- Add equivalent examples and instructions for Bash users in Azure Cloud Shell, such as how to enable, configure, or disable predictive suggestions in Bash (e.g., using bash-completion, fish shell, or zsh with plugins).
- Mention and link to documentation about command-line completion and prediction features available in Bash or other Linux shells supported by Cloud Shell.
- Clarify early in the documentation that the described features are specific to PowerShell, and provide guidance or links for users who are using Bash.
- Include instructions for editing Bash profile files (e.g., .bashrc, .bash_profile) if relevant, and how to persist configuration changes for Bash users.
- Balance the documentation by presenting Bash/Linux shell options and tools alongside PowerShell/Windows tools where possible.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/features.md
.../azure-docs/blob/main/articles/cloud-shell/features.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation, while describing a Linux-based environment, frequently highlights PowerShell and Windows-centric tools and patterns. PowerShell features (such as the Azure drive and cmdlets) are given dedicated sections and detailed explanations, while Bash/Linux equivalents are not. Several Microsoft/Windows-oriented tools (e.g., Exchange Online PowerShell, Microsoft Graph PowerShell, SqlServer PowerShell modules) are listed prominently. In tool listing and examples, PowerShell is often mentioned before Bash, and some features (like the Azure drive) are only available in PowerShell, with no Linux/Bash equivalent described.
Recommendations
- Provide Bash/Linux equivalents for features highlighted in PowerShell (e.g., describe how to navigate Azure resources using Azure CLI in Bash, if possible).
- Balance the order of presentation: mention Bash and PowerShell together, or alternate which is listed first.
- Include more Linux-native tools and workflows in the 'Other Microsoft services' and 'Database tools' sections, or clarify if certain features are PowerShell-only.
- Add explicit Bash/Linux examples for common tasks, not just PowerShell cmdlets.
- Clearly indicate when a feature is exclusive to PowerShell and suggest Linux/Bash alternatives where possible.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/faq-troubleshooting.md
.../blob/main/articles/cloud-shell/faq-troubleshooting.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation shows some Windows bias, particularly in the order and emphasis of examples and tools. Windows browsers and PowerShell are mentioned first or exclusively in several sections, and Windows-specific tools (e.g., PowerShell, Microsoft Edge) are referenced more prominently than Linux equivalents. Linux is included, but often after Windows and macOS, and with less detail.
Recommendations
- Ensure Linux examples and tools are presented with equal prominence and detail as Windows and macOS. For example, mention Linux browsers and keyboard shortcuts first or in parallel.
- When referencing browser developer tools, include explicit instructions for Firefox and Linux browsers, not just Edge and Chrome.
- In sections where PowerShell is discussed, provide Bash or other shell equivalents where possible, or clarify when features are PowerShell-specific.
- Avoid using Windows tools or terminology (e.g., 'PowerShell provider', 'Azure: drive') without noting their platform specificity and providing Linux/Bash alternatives or explanations.
- Review the order of OS mentions in lists and examples to avoid always listing Windows first.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/get-started/classic.md
.../blob/main/articles/cloud-shell/get-started/classic.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents both Azure CLI (Bash) and Azure PowerShell examples, but there is a subtle Windows bias. PowerShell (traditionally Windows-centric) is given equal prominence to Bash, and in some sections, PowerShell-specific features (like the Azure drive and context navigation) are described in detail without Linux/Bash equivalents. The 'Next steps' section lists PowerShell before CLI, and some PowerShell examples use Windows-style paths and concepts. There are no explicit Linux-only examples or references to native Linux tools.
Recommendations
- Ensure Bash/Azure CLI examples are presented first, or alternate their order to avoid implicit prioritization.
- Where PowerShell-specific features (like the Azure drive) are mentioned, provide equivalent Bash/Linux navigation tips or explicitly state if no equivalent exists.
- Include references to native Linux tools or workflows where appropriate, such as using 'ls' or 'find' in Bash to explore the environment.
- In the 'Next steps' section, alternate or randomize the order of PowerShell and CLI links, or group them together as 'Choose your shell: PowerShell or Bash/CLI'.
- Explicitly mention that Cloud Shell supports both Linux (Bash) and Windows (PowerShell) environments, and clarify any differences in capabilities.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/persisting-shell-storage.md
.../main/articles/cloud-shell/persisting-shell-storage.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive), with no equivalent Bash or Linux shell commands. It references PowerShell cmdlets and does not mention or demonstrate how to perform the same tasks in Bash, even though Azure Cloud Shell supports both Bash and PowerShell environments. This creates a bias toward Windows/PowerShell users and leaves Linux/Bash users without guidance.
Recommendations
- Add equivalent Bash command examples (e.g., using Azure CLI commands like 'az storage share show', 'az storage share delete', or 'clouddrive' commands available in Bash Cloud Shell).
- Explicitly mention that Cloud Shell supports both Bash and PowerShell, and provide parallel instructions for both environments.
- Avoid using only PowerShell cmdlets when describing common tasks; always provide Linux/Bash alternatives.
- Review the documentation for other places where Windows-centric terminology or tools are used, and ensure Linux parity.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/release-notes.md
...e-docs/blob/main/articles/cloud-shell/release-notes.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page exhibits a moderate Windows bias. Azure PowerShell and Windows-centric tools are consistently highlighted alongside Azure CLI, and PowerShell versioning is called out in every release note. The only explicit mention of keyboard shortcuts prioritizes Windows (Ctrl+V) before Linux (Ctrl+Shift+V), and links and references often default to PowerShell tabs or Windows tools. Linux-specific tools and patterns are mentioned less frequently and with less detail, though there are some references to Linux (e.g., Azure Linux, Inspektor Gadget).
Recommendations
- Provide Linux/Bash examples and tool updates with equal prominence as PowerShell.
- When mentioning keyboard shortcuts or UI features, list Linux and Windows options together or alternate the order.
- Include links to Linux/Bash documentation and tabs, not just PowerShell.
- Highlight Linux-native tools and changes with the same frequency and detail as Windows/PowerShell tools.
- Explicitly mention Linux compatibility or differences for major features and updates.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/how-to-use-private-endpoint-storage.md
...loud-shell/vnet/how-to-use-private-endpoint-storage.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a bias towards Windows by exclusively using Azure Portal (a GUI tool often associated with Windows workflows) for all steps, without providing any command-line examples (such as Azure CLI or Bash scripts) that are common in Linux environments. There are no Linux-specific instructions or parity for users who may prefer or require command-line automation, and the documentation does not mention cross-platform tools until after the portal steps, if at all.
Recommendations
- Add Azure CLI (az) command-line examples for each major step, such as disabling public access, creating the private endpoint, and configuring DNS. These commands work on both Linux and Windows.
- Include Bash script snippets for automation, which are especially useful for Linux users.
- Explicitly mention that the Azure Portal is cross-platform, but also provide guidance for users who prefer not to use a GUI.
- Ensure that any references to tools or workflows are balanced between GUI (Portal), PowerShell, and CLI/Bash.
- Consider adding a section or callout for Linux users, highlighting any differences or additional steps required.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/overview.md
...e-docs/blob/main/articles/cloud-shell/vnet/overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page references PowerShell remoting as a primary management method and does not provide explicit examples or mention of Linux-native tools (e.g., SSH, Bash scripting) beyond a brief mention of SSH. There are no Linux-specific command-line examples or references to Bash, and the focus on PowerShell remoting and tools may suggest a Windows-centric approach.
Recommendations
- Include explicit examples of using Linux-native tools (e.g., Bash, SSH, scp, sftp) from Cloud Shell to manage resources.
- Mention Bash scripting and Linux command-line utilities alongside PowerShell remoting in the benefits and usage sections.
- Add Linux-focused scenarios or use cases, such as connecting to Linux VMs or managing resources with Bash.
- Ensure that any references to command-line management are balanced between Windows (PowerShell) and Linux (Bash/SSH) tools.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/troubleshooting.md
...blob/main/articles/cloud-shell/vnet/troubleshooting.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses the Azure portal (a web GUI) for all troubleshooting steps, without providing any CLI-based alternatives (such as Azure CLI or PowerShell Core commands). This approach implicitly favors users familiar with Windows-centric workflows and does not address Linux-first or cross-platform users who may prefer or require command-line instructions. No Linux-specific tools or examples are mentioned, and there is no parity for users who may be automating or scripting these tasks.
Recommendations
- Add equivalent Azure CLI command examples for each portal-based step, especially for resource provider registration, role assignments, and resource inspection.
- Explicitly mention that all steps can be performed using Azure CLI or PowerShell Core, and provide links or references to relevant command-line documentation.
- Where screenshots are provided for the portal, consider adding CLI output examples or command snippets for Linux/macOS users.
- Ensure that terminology and instructions do not assume a GUI-first workflow, and clarify that all actions can be performed cross-platform.
- If any step is only possible via the portal, explicitly state this and provide a rationale.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/analytics/logs/call-summary-log-schema.md
...ces/concepts/analytics/logs/call-summary-log-schema.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_example
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias in its sample data and examples. Specifically, the only explicit operating system shown in the sample call summary logs is 'Windows 10.0.17763 Arch: x64', while other OS examples are either 'null', 'Redacted', or non-Windows (Darwin/Android) but appear later. There are no Linux-specific examples or mentions, and Windows is the first and only desktop OS explicitly named in the P2P call example. No Linux tools, patterns, or instructions are referenced anywhere in the page.
Recommendations
- Include sample call summary logs with Linux endpoints, showing realistic Linux osVersion strings (e.g., 'Ubuntu 20.04 x86_64', 'Debian 11.2 x86_64').
- Explicitly mention Linux as a supported platform in relevant sections, especially where OS version is discussed.
- If there are platform-specific instructions or troubleshooting steps, provide parity for Linux users (e.g., how to collect logs or diagnose issues on Linux endpoints).
- Ensure that examples and sample data rotate or balance between Windows, Linux, and macOS endpoints to avoid implicit prioritization.
- Add a note clarifying that the service and SDK support multiple operating systems, including Linux, and link to platform compatibility documentation if available.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/email/email-domain-configuration-troubleshooting.md
...ts/email/email-domain-configuration-troubleshooting.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation consistently references the use of the 'nslookup' tool from the Windows CMD terminal for DNS record verification, without mentioning Linux or macOS equivalents (e.g., 'dig', 'host', or 'nslookup' on Unix shells). All command-line instructions and context are Windows-centric, and there are no examples or guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent command-line instructions for Linux and macOS users, such as using 'dig' or 'nslookup' from a Unix shell.
- Explicitly mention that 'nslookup' is available on Linux and macOS, and show example commands for those environments.
- When listing steps, avoid specifying only 'Windows CMD terminal'; instead, use platform-neutral language or provide parallel instructions for each major OS.
- Include screenshots or sample outputs from Linux/macOS terminals where relevant.
- Consider a table or section summarizing DNS query commands across Windows, Linux, and macOS for user convenience.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/best-practices-web.md
...ation-services/concepts/includes/best-practices-web.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed troubleshooting steps and behavioral explanations for Windows (Chrome/Edge) before mentioning macOS, and by referencing Windows-specific UI elements (e.g., desktop taskbar, right-click to quit). There are no examples or guidance for Linux users, and Linux is not mentioned in device or screen sharing sections where OS-specific behavior is discussed.
Recommendations
- Add explicit Linux examples and behavioral notes wherever OS-specific behavior is discussed (e.g., camera sharing, screen sharing).
- When listing OS-specific behaviors, include Linux alongside Windows and macOS, or clarify if behavior is identical.
- Avoid referencing only Windows UI elements (e.g., desktop taskbar, right-click to quit); provide equivalent instructions for Linux desktop environments or note differences.
- If there are no known Linux-specific issues, explicitly state that, to reassure Linux users.
- Ensure parity in troubleshooting steps and recommendations for all major platforms, including Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/enable-interoperability-for-teams-tenant.md
...s/includes/enable-interoperability-for-teams-tenant.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell commands and references the MicrosoftTeams PowerShell module, which is primarily a Windows tool. There are no examples or instructions for performing these tasks on Linux or macOS, nor is there mention of cross-platform alternatives. The instructions assume the reader is using Windows and PowerShell, and do not address Linux users or provide parity.
Recommendations
- Add instructions for installing and using the MicrosoftTeams module on Linux and macOS, including prerequisites such as PowerShell Core (pwsh) and any platform-specific considerations.
- Explicitly state that PowerShell Core is available cross-platform and provide guidance for Linux/macOS users to install and use it.
- Include example commands and installation steps for Linux distributions (e.g., using apt, yum, or snap to install PowerShell, then installing the MicrosoftTeams module).
- Mention any limitations or differences in behavior when using the MicrosoftTeams module on non-Windows platforms.
- Consider providing alternative methods (such as Azure CLI, REST API, or portal-based configuration) if available, to ensure broader accessibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/enable-interoperability-teams.md
...ices/concepts/interop/enable-interoperability-teams.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page provides instructions that exclusively reference the PowerShell Set-CsPhoneNumberAssignment cmdlet for enabling Enterprise Voice, which is a Windows-centric tool. There are no examples or guidance for performing the same operation using Linux or cross-platform tools, nor is there mention of alternative methods for non-Windows environments. The documentation implicitly assumes a Windows environment by referencing PowerShell and Teams PowerShell modules without Linux equivalents.
Recommendations
- Provide equivalent instructions or examples using Azure CLI, REST API, or other cross-platform tools where possible.
- Explicitly state if certain operations can only be performed on Windows, and suggest workarounds for Linux users (e.g., using Azure Cloud Shell).
- Add Linux/macOS-specific guidance or note the availability of Teams PowerShell modules on non-Windows platforms if supported.
- Reorder or supplement documentation to present cross-platform or OS-agnostic methods before Windows-specific tools.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/security.md
...munication-services/concepts/interop/guest/security.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by referencing the Microsoft Teams admin center and PowerShell as the primary (and only) methods for configuring security policies for Teams external users. There are no mentions of Linux-compatible tools, command-line alternatives, or cross-platform administration options. The documentation assumes the use of Windows-centric tools and does not provide parity for Linux administrators.
Recommendations
- Include examples or references for configuring Teams policies using cross-platform tools (e.g., Azure CLI, REST APIs) where possible.
- Explicitly state whether PowerShell modules are available and supported on Linux/macOS, and provide installation instructions if so.
- Mention any web-based or platform-agnostic administration options (such as the Teams admin center via browser) and clarify their OS compatibility.
- Add guidance or links for Linux administrators on how to perform equivalent security configurations.
- Review the documentation for other instances where only Windows tools are mentioned, and ensure Linux parity is addressed.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/teams-administration.md
...ervices/concepts/interop/guest/teams-administration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by exclusively referencing PowerShell modules and cmdlets for configuration and management tasks, and by listing the Teams Admin Center and PowerShell as the only tools for administrators. There are no examples or mentions of Linux-compatible tools, CLI alternatives, or cross-platform scripting. The documentation does not provide parity for Linux administrators or users, nor does it mention how to perform equivalent actions on non-Windows platforms.
Recommendations
- Include Azure CLI or Microsoft Graph API examples for all configuration tasks, especially where PowerShell is referenced.
- Explicitly mention cross-platform tools and workflows, such as the Teams Admin Center (web-based) or Graph API, and clarify their OS compatibility.
- Add Linux/macOS-specific instructions or notes where relevant, including how to install and use cross-platform PowerShell if it is required.
- Where only PowerShell is available, clarify that PowerShell Core is cross-platform and provide installation guidance for Linux/macOS.
- Consider providing bash or shell script equivalents for common administrative tasks, or at least reference their availability.
- Review all tool references to ensure Linux administrators are not excluded from management capabilities.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/teams-user/security.md
...ation-services/concepts/interop/teams-user/security.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft-centric tools and services (Teams, Azure, Entra ID) without mentioning Linux or cross-platform security practices. There are no examples or guidance for Linux users, and all security management is described via Azure Portal or Microsoft tools, which are typically Windows-first in their user experience.
Recommendations
- Include examples or references for managing security using cross-platform tools (e.g., Azure CLI, REST APIs) that are available on Linux.
- Mention how Linux users can interact with Azure Communication Services and Microsoft Entra ID, such as through command-line interfaces or SDKs.
- Provide parity in documentation by explicitly stating that security features and management are accessible from Linux environments, and link to relevant Linux or cross-platform guides.
- Avoid assuming the use of the Azure Portal or other Windows-centric GUIs as the default management method.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/teams-user/teams-shared-line-appearance.md
...pts/interop/teams-user/teams-shared-line-appearance.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Teams PowerShell as a method for assigning delegates, without mentioning or providing equivalent Linux-compatible alternatives. The only command-line tool mentioned is Teams PowerShell, which is primarily a Windows tool. There are no Linux or cross-platform command-line examples or references, and the documentation does not clarify if or how Linux users can perform these tasks.
Recommendations
- Provide Linux-compatible alternatives or clarify if Teams PowerShell can be used on Linux (e.g., via PowerShell Core).
- Include examples using cross-platform tools or REST APIs (such as Microsoft Graph API) for assigning delegates.
- Explicitly state platform requirements and limitations for administrative tasks, and offer guidance for Linux users.
- If no Linux alternative exists, document this limitation and suggest workarounds or feature requests.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-faq.md
.../concepts/interop/tpe/teams-phone-extensibility-faq.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets and the Teams Admin Center (TAC) as the primary or only methods for configuration and management. There are no examples or mentions of Linux or cross-platform CLI tools for administering Teams Phone extensibility, nor are there instructions for performing equivalent tasks on Linux or macOS. The documentation assumes the use of Windows-centric tools and omits Linux alternatives.
Recommendations
- Include examples using cross-platform tools such as the Microsoft Teams CLI (if available) or Azure CLI for configuration tasks, especially for emergency calling policies.
- Explicitly mention whether PowerShell cmdlets can be run on PowerShell Core on Linux/macOS, or provide guidance for non-Windows users.
- Add instructions or references for managing Teams Phone extensibility from Linux or macOS environments, ensuring parity in administrative workflows.
- Where possible, provide REST API or Graph API examples for configuration, which are platform-agnostic.
- Clarify if any features are only available via Windows tools, and suggest workarounds or alternatives for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/plan-user-experience.md
...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Teams Admin Center, PowerShell) as the primary methods for configuration, without mentioning or providing Linux equivalents or cross-platform alternatives. There are no examples or instructions for Linux users, and Windows tools are presented first and exclusively.
Recommendations
- Include cross-platform configuration options, such as Azure CLI or REST API examples, which work on Linux and macOS.
- Explicitly mention whether Teams Admin Center and PowerShell are available or supported on Linux, and provide guidance for Linux users if possible.
- Add examples or instructions using tools that are accessible from Linux environments, such as browser-based portals or platform-agnostic SDKs.
- Ensure that references to configuration tools do not assume a Windows environment; clarify platform requirements where necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/overview.md
...n-services/concepts/interop/virtual-visits/overview.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows and Microsoft-centric tools and workflows. All examples and architecture options are centered around Microsoft 365, Teams, Bookings, and Outlook, which are primarily Windows-oriented or Microsoft-first products. There is no mention of Linux equivalents, cross-platform alternatives, or guidance for non-Windows environments. The documentation assumes familiarity and usage of Microsoft tools, omitting any discussion of how Linux users or organizations might implement or interact with virtual appointments using Azure Communication Services.
Recommendations
- Include examples or guidance for Linux users, such as how to access Teams meetings or Bookings from Linux clients.
- Mention cross-platform alternatives or open standards for scheduling and communication, where applicable.
- Provide sample code or workflows that demonstrate integration with Azure Communication Services from Linux environments (e.g., using curl, bash, or Python instead of PowerShell).
- Clarify which features are available or supported on non-Windows platforms.
- Add a section addressing platform compatibility and considerations for organizations not using Microsoft 365 or Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-troubleshooting.md
...terop/tpe/teams-phone-extensibility-troubleshooting.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias in the troubleshooting steps for resolving Microsoft Entra App permission issues. It exclusively provides PowerShell commands and instructions, assumes the use of PowerShell (a Windows-centric tool), and does not mention or provide equivalent instructions for Linux or macOS environments. There are no CLI or cross-platform alternatives (such as Azure CLI, Microsoft Graph CLI, or REST API) provided. The rest of the document is neutral, but the critical administrative steps are Windows/PowerShell-centric.
Recommendations
- Provide equivalent instructions using Azure CLI, Microsoft Graph CLI, or REST API, which are cross-platform and can be run on Linux, macOS, and Windows.
- Explicitly mention that PowerShell Core is available for Linux/macOS, or provide installation instructions for non-Windows environments.
- Add examples for Linux/macOS environments, including shell commands and package installation steps.
- Reorder or parallelize instructions so that cross-platform methods are presented first or alongside PowerShell examples.
- Add a note clarifying that the administrative steps can be performed from any OS, not just Windows, and link to relevant cross-platform tool documentation.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/pricing/teams-interop-pricing.md
...ion-services/concepts/pricing/teams-interop-pricing.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a Windows bias by referencing Windows-specific tools (e.g., PowerShell cmdlets), mentioning Windows desktop clients and tools before any Linux or cross-platform alternatives, and omitting Linux-specific instructions or examples. There are no examples or instructions for Linux users, and the only command-line tool referenced is a PowerShell cmdlet, which is Windows-centric.
Recommendations
- Provide equivalent instructions for Linux environments, such as using Azure CLI or REST API for license assignments instead of only PowerShell.
- Include explicit mention of Teams clients on Linux (e.g., Teams web client on Linux, or Teams desktop client if available) in all tables and scenarios.
- When referencing desktop clients, clarify cross-platform availability and provide parity in examples (e.g., show a user joining from a Linux desktop).
- If PowerShell is required, note how Linux users can use PowerShell Core or provide alternative commands.
- Add a pricing scenario where a user joins from a Linux device to demonstrate cross-platform support.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/manage-call-quality.md
...es/concepts/voice-video-calling/manage-call-quality.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias primarily in the section about implementing Quality of Service (QoS), where it references Windows Group Policy objects as the method for packet marking and network prioritization. No equivalent Linux tools or methods (such as tc, iptables, or systemd-networkd) are mentioned. The documentation does not provide Linux-specific examples or guidance for QoS, and Windows tooling is mentioned first and exclusively. Other sections are generally cross-platform or platform-agnostic, but the lack of Linux parity in network configuration is a notable gap.
Recommendations
- Add Linux-specific guidance for implementing QoS, such as using tc, iptables, or firewalld to mark packets and prioritize network traffic.
- When discussing network configuration, mention both Windows and Linux approaches side by side, or provide platform-agnostic recommendations with links to OS-specific guides.
- Include examples or references for configuring QoS on common Linux distributions (e.g., Ubuntu, CentOS, Debian).
- Review other sections for potential implicit Windows bias and ensure that any OS-specific instructions are balanced with Linux equivalents.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-python.md
...tomation/includes/audio-streaming-quickstart-python.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits a Windows bias primarily in the prerequisites and reference links. The resource creation link uses a Windows-specific tab and URL parameter ('?tabs=windows'), and the WebSocket documentation link points to a Windows Azure Web Sites blog post. There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux tools or environments. All code samples are Python and OS-agnostic, but supporting documentation and navigation favor Windows.
Recommendations
- Update prerequisite links to use neutral or platform-agnostic tabs/parameters (e.g., '?tabs=none' or provide both Windows and Linux options).
- Provide or link to equivalent Linux documentation for setting up WebSocket servers (e.g., using Nginx, Gunicorn, or other common Linux tools).
- Explicitly mention that the Python code samples are cross-platform and can be run on Linux, macOS, or Windows.
- Add a section or note describing how to set up the environment and run the examples on Linux (e.g., using systemd for service management, or common Linux Python environments).
- Where Windows-specific resources are referenced, provide Linux equivalents or alternatives.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md
...w-tos/call-automation/teams-interop-call-automation.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation demonstrates a Windows bias primarily through its reliance on PowerShell cmdlets (e.g., Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) for administrative setup, which are Windows-centric tools. These are presented as the only method for tenant-level and user-level configuration, with no mention of Linux/macOS alternatives or cross-platform CLI options. The administrative steps and examples assume access to Windows tooling, and the order of presentation puts Windows/PowerShell methods first and exclusively.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure CLI, Microsoft Graph API, or REST endpoints for tenant and user configuration, where possible.
- Explicitly mention whether PowerShell cmdlets can be run on PowerShell Core on Linux/macOS, or provide links to installation guides for non-Windows environments.
- Add examples or guidance for performing administrative setup from Linux/macOS, including any prerequisites or limitations.
- Clarify which steps require Windows-only tools and suggest alternatives or workarounds for Linux users.
- Review all administrative and setup instructions to ensure parity and accessibility for users on all major operating systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/cte-calling-sdk/shared-line-appearance.md
...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Teams PowerShell and Microsoft Teams Client (both Windows-centric tools) as the primary methods for assigning delegates. No Linux or cross-platform alternatives are mentioned, and the examples/tools listed are Windows-specific. The SDK support table lists 'Windows' as a platform but does not mention Linux or macOS, and there are no Linux-specific instructions or parity.
Recommendations
- Include Linux and macOS alternatives for assigning delegates, such as web-based or REST API methods if available.
- Explicitly mention cross-platform compatibility for SDKs and tools, and add Linux/macOS columns to the support table.
- Provide command-line examples using bash or other Linux-native tools where possible.
- Clarify whether Teams PowerShell or Teams Client functionality is available via browser or on non-Windows platforms, and link to relevant documentation.
- Add a section addressing platform support and limitations, including any Linux-specific guidance or caveats.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/managed-identity.md
...les/communication-services/how-tos/managed-identity.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias by prioritizing the Azure Portal (a GUI tool most commonly used on Windows) and Azure CLI examples, with CLI code blocks labeled as 'azurepowershell-interactive' and 'azurecli-interactive'. There is no mention of Linux-specific shell environments, nor are there explicit Bash or cross-platform shell examples. The documentation does not provide any Linux-specific instructions or screenshots, and the use of the Azure Portal is presented first in all cases.
Recommendations
- Add explicit Bash/Linux shell examples for all CLI commands, using the 'bash' code block label where appropriate.
- Clarify that the Azure CLI commands work cross-platform (Windows, macOS, Linux) and provide any necessary notes about differences in shell syntax.
- Include screenshots or instructions for the Azure Portal on Linux/macOS (if available), or clarify platform requirements.
- Avoid labeling CLI code blocks as 'azurepowershell-interactive' unless they are specifically for PowerShell; use 'azurecli' or 'bash' as appropriate.
- Consider providing a 'Linux/macOS' tab for steps that might differ from Windows, especially for command-line usage.
- Explicitly mention that all SDKs and CLI commands are supported on Linux, and provide links to Linux installation guides for Azure CLI if not already present.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/telephony/domain-validation.md
...cation-services/how-tos/telephony/domain-validation.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates Windows bias by exclusively referencing the Windows 'nslookup' command for DNS verification, linking to Windows Server documentation, and not mentioning or providing equivalent Linux/macOS commands (such as 'dig' or 'nslookup' on Linux). No Linux or cross-platform examples are given, and the Windows tool is presented as the default/only method.
Recommendations
- Include Linux/macOS equivalents for DNS verification, such as 'dig -t txt subdomain.contoso.com' or 'nslookup -type=txt subdomain.contoso.com' (noting that 'nslookup' is also available on Linux).
- Provide links to cross-platform or Linux/macOS documentation for DNS tools, not just Windows Server documentation.
- Use neutral language such as 'You can use DNS query tools (e.g., nslookup or dig) on your platform to verify...' rather than only referencing Windows tools.
- Consider providing example commands for both Windows and Linux/macOS environments side by side.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/authenticate-notification-messages-client-net.md
...ludes/authenticate-notification-messages-client-net.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation consistently uses the Windows-specific 'setx' command for setting environment variables, without providing equivalent commands for Linux or macOS (e.g., 'export' for bash/zsh). All environment variable instructions and examples are Windows-centric, and there is no mention of Linux or cross-platform alternatives. Additionally, references to restarting Visual Studio reinforce a Windows development environment bias.
Recommendations
- For every environment variable example using 'setx', provide equivalent Linux/macOS commands (e.g., 'export VAR=value' for bash/zsh, or instructions for adding to ~/.bashrc or ~/.zshrc).
- Explicitly mention that the instructions apply to Windows, and provide parallel instructions for Linux/macOS users.
- Include notes or tabs for different operating systems, so users can select their platform and see relevant commands.
- When referencing tools like Visual Studio, also mention cross-platform editors (e.g., VS Code) and clarify any platform-specific steps.
- Link to official Microsoft documentation on setting environment variables for all supported operating systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-java.md
...ced-messaging/whatsapp/includes/common-setting-java.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation demonstrates a Windows bias by providing only Windows-specific commands (setx) for setting environment variables, and referencing Windows tools (Visual Studio) without mentioning Linux or macOS equivalents. There are no examples or instructions for Linux or macOS users, such as using export or setting environment variables in bash/zsh shells.
Recommendations
- Add Linux/macOS equivalents for setting environment variables (e.g., export VAR=value for bash/zsh).
- Include instructions or notes for users of common Linux/macOS shells (bash, zsh, etc.).
- When referencing Windows tools (e.g., Visual Studio), also mention popular Linux/macOS editors (e.g., VS Code, JetBrains IDEs) and note any platform-specific steps.
- Present cross-platform instructions together, or use tabs to separate Windows, Linux, and macOS steps.
- Review all command-line examples to ensure parity across platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/get-started/messages-get-started-net.md
...tsapp/includes/get-started/messages-get-started-net.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows development tools (Visual Studio, Visual Studio Code) and .NET CLI, with all code examples in C#. There are no explicit Linux or cross-platform instructions, and no mention of Linux-specific development environments or commands. The guidance for building and running the code is focused on Windows-centric tools and workflows, with no Linux or macOS parity.
Recommendations
- Add explicit instructions for building and running the code on Linux and macOS, including terminal commands and any required dependencies.
- Mention and provide examples for using cross-platform editors (e.g., VS Code on Linux/macOS) and the .NET CLI on non-Windows systems.
- Include a section on installing .NET SDK on Linux and macOS, with links to official documentation.
- Clarify that the .NET CLI and Visual Studio Code are cross-platform, and provide parity in instructions for all supported operating systems.
- Consider providing code examples in additional languages (such as Python or JavaScript) if the SDK supports them, or clarify that only .NET is supported.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/python-application-setup.md
...essaging/whatsapp/includes/python-application-setup.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides a Windows-specific command ('type nul > messages-quickstart.py') to create a new file, without offering the equivalent Linux/macOS command (e.g., 'touch messages-quickstart.py'). All other instructions are platform-neutral, but the file creation step demonstrates a Windows bias by only mentioning a Windows tool and not providing parity for Linux users.
Recommendations
- Provide both Windows and Linux/macOS commands for creating new files. For example, show 'type nul > messages-quickstart.py' for Windows and 'touch messages-quickstart.py' for Linux/macOS.
- Consider using platform-neutral language or call out platform-specific steps explicitly.
- Review the documentation for other steps that may assume a particular OS and ensure parity for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/stickers/messages-quickstart-sticker-messages-net.md
...s/stickers/messages-quickstart-sticker-messages-net.md
High Priority
View Details â
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. Visual Studio (a Windows-first IDE) is mentioned before Visual Studio Code and .NET CLI, and keyboard shortcuts are given for Visual Studio only (which are Windows-specific). There are no explicit Linux or macOS instructions, nor are there any terminal or shell examples for Linux users. The documentation assumes familiarity with Windows development environments and omits guidance for Linux users.
Recommendations
- Add explicit instructions and examples for Linux users, such as using the .NET CLI in Bash or other Linux shells.
- Mention cross-platform editors (e.g., Visual Studio Code) and the .NET CLI before or alongside Visual Studio.
- Include Linux/macOS-specific build and run instructions, including relevant keyboard shortcuts or terminal commands.
- Clarify that the .NET SDK and CLI are cross-platform and provide links to installation guides for Linux/macOS.
- Avoid assuming the use of Windows-only tools or workflows; ensure parity in documentation for all supported platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-node.md
...kstart-make-an-outbound-call-using-callautomation-node.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation exhibits a Windows bias by recommending Visual Studio Code (which, while cross-platform, is often associated with Windows) and Azure DevTunnels (whose CLI and setup instructions are more familiar to Windows users). There are no explicit Linux-specific instructions, troubleshooting tips, or alternative tools mentioned. All command-line examples are generic, but there is an implicit assumption of a Windows-like environment (e.g., use of .env files, Visual Studio Code, and lack of mention of Linux shells or editors).
Recommendations
- Explicitly state that all commands work on Linux, macOS, and Windows, or provide OS-specific notes where differences exist.
- Include Linux-specific setup instructions or troubleshooting tips, such as using alternative editors (e.g., Vim, Nano) or confirming that Azure DevTunnels CLI is available and works on Linux.
- Mention that Visual Studio Code is cross-platform, and suggest alternatives for users who prefer other editors.
- Add a note about how to set environment variables in Linux/macOS shells if manual export is needed.
- If there are any Windows-specific behaviors (such as path formats or CLI differences), document the Linux equivalents.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/create-communication-resource.md
...-services/quickstarts/create-communication-resource.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and instructions (such as PowerShell and setx) are presented first or exclusively in several sections. The Azure CLI installation link defaults to Windows, and PowerShell is given its own pivot, while Linux and macOS are grouped under 'unix' or 'linux' tabs. Windows environment variable instructions are presented before Linux/macOS. There is a lack of parity in the prominence and detail of Linux examples and tools.
Recommendations
- Present Linux/macOS instructions and tools with equal prominence to Windows, including placing them before or alongside Windows examples rather than after.
- Provide direct links to Azure CLI installation instructions for Linux and macOS, not just Windows.
- Ensure that all PowerShell examples have Bash equivalents, and consider providing Bash as a primary example where possible.
- Use neutral language and ordering in tabbed instructions (e.g., Linux/macOS first or randomized order).
- Add explicit mention and examples for Linux-native tools and patterns where relevant, not just as an afterthought.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/add-custom-verified-domains.md
...vices/quickstarts/email/add-custom-verified-domains.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its DNS record instructions, which link to guides for adding DNS records using Windows-based DNS tools, but do not provide explicit Linux or cross-platform alternatives. The 'Other (General)' CNAME record link specifically points to a Windows-based DNS guide, and there are no references to Linux command-line tools (e.g., dig, nsupdate, bind) or Linux DNS server management. The platform pivots include Azure CLI (cross-platform), .NET, and PowerShell (Windows-centric), but there is no explicit Linux shell or tool example, nor is Linux mentioned in the DNS record management section.
Recommendations
- Add explicit instructions or links for managing DNS records using Linux tools (e.g., bind, nsupdate, editing /etc/bind/named.conf, using dig for verification).
- Provide parity by including Linux shell examples alongside PowerShell, especially for Azure resource management and DNS configuration.
- Replace or supplement the 'Other (General)' CNAME record link with a cross-platform or Linux-specific guide, rather than only referencing Windows-based DNS.
- Clarify in each section which instructions are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
- Consider adding a Linux-focused pivot (e.g., Bash, Linux shell) for resource provisioning and configuration steps.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-az-cli.md
...ncludes/create-azure-managed-domain-resource-az-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a Windows-first bias by linking only to the Windows Azure CLI installation instructions and using the 'azurepowershell-interactive' code block type for all CLI examples. There are no explicit Linux or macOS installation links, nor are there any shell-specific (bash/zsh) examples or notes about cross-platform usage. This may give the impression that the instructions are primarily for Windows users.
Recommendations
- Provide installation links for Azure CLI on Linux and macOS alongside the Windows link.
- Use neutral code block types (e.g., 'bash' or 'sh') for CLI commands instead of 'azurepowershell-interactive', since the Azure CLI is cross-platform.
- Add a note clarifying that all Azure CLI commands work on Windows, Linux, and macOS terminals.
- Include example commands or screenshots from a Linux shell to demonstrate parity.
- Avoid using terminology or code block types that imply a Windows-only environment when the tool is cross-platform.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-powershell.md
...des/create-azure-managed-domain-resource-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell commands and the Azure Az PowerShell module for all examples and instructions. There are no examples or instructions for Linux users (e.g., using Azure CLI or Bash). Windows tools and patterns are mentioned exclusively and are presented as the default/only option, which may alienate or confuse Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all operations (e.g., creating, updating, listing, and deleting Domain resources).
- Mention that PowerShell can be used cross-platform, but clarify installation steps for Linux/macOS if PowerShell is required.
- Add a section or callout for Linux/macOS users, explaining their options and linking to relevant Azure CLI or REST API documentation.
- Avoid presenting Windows/PowerShell tools as the only or default method; strive for parity by listing cross-platform tools first or side-by-side.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-custom-managed-domain-resource-az-cli.md
...cludes/create-custom-managed-domain-resource-az-cli.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently uses 'azurepowershell-interactive' code blocks for all CLI examples, which implies a Windows/PowerShell environment. The Azure CLI installation link points to the Windows-specific instructions by default, and there is no mention of Linux or macOS equivalents. No Bash or cross-platform shell examples are provided, and there is no guidance for Linux users.
Recommendations
- Provide Bash or generic shell examples for all Azure CLI commands, using 'bash' or 'sh' code blocks instead of 'azurepowershell-interactive'.
- Update the Azure CLI installation link to either a cross-platform landing page or include links for Linux and macOS installation instructions.
- Explicitly state that the Azure CLI commands work on all platforms (Windows, Linux, macOS) and clarify any platform-specific steps if needed.
- Avoid using PowerShell-specific syntax or code block types unless there is a platform-specific reason.
- Add a section or callout for Linux/macOS users to ensure parity and inclusivity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-custom-managed-domain-resource-powershell.md
...es/create-custom-managed-domain-resource-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all operations, without providing any examples or guidance for Linux users or cross-platform alternatives such as Azure CLI, Bash, or REST API. This creates a strong Windows/PowerShell bias, making it less accessible for users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the Azure Az PowerShell Module is available on all platforms, or clarify any platform-specific requirements.
- Include Bash or shell script examples where appropriate, especially for common tasks like authentication and resource management.
- Reference REST API documentation or provide REST examples for advanced users who may prefer direct API calls.
- Reorganize the documentation to present cross-platform or CLI options before or alongside PowerShell examples, to avoid the impression of Windows-first bias.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-powershell.md
...rts/email/includes/create-email-resource-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell commands and references Windows-centric tools (Azure Az PowerShell), with no mention of Linux or cross-platform alternatives such as Azure CLI, Bash, or shell scripts. All examples and instructions assume a Windows environment, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Add equivalent Azure CLI examples for all resource management tasks (creating, updating, listing, and deleting Email Communication Service resources).
- Explicitly mention cross-platform compatibility and provide instructions for Linux and macOS users.
- Reference installation guides for Azure CLI and Bash usage alongside PowerShell.
- Reorder sections or provide parallel examples so that Linux/macOS instructions are presented with equal prominence as Windows/PowerShell instructions.
- Clarify which commands are platform-specific and suggest alternatives where appropriate.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-sender-username-resource-powershell.md
...includes/create-sender-username-resource-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell commands (Az PowerShell Module) for all examples and instructions, which are Windows-centric. There are no examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
- Add equivalent Azure CLI examples for all operations (login, module installation, resource creation, update, listing, and deletion).
- Explicitly mention that PowerShell Core is cross-platform if PowerShell must be used, and provide instructions for installing and using it on Linux/macOS.
- Include Bash shell examples where appropriate, especially for common tasks.
- Provide a section or note for Linux/macOS users, outlining supported tools and any differences in usage.
- Ensure that links to documentation for Azure CLI and other cross-platform tools are included alongside PowerShell links.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-async-sync-net.md
...uickstarts/email/includes/send-email-async-sync-net.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns first (e.g., cmd, PowerShell), omitting explicit Linux/macOS shell examples, and not addressing cross-platform differences in environment variable setup or command-line usage. All code and instructions are C#/.NET-centric, which is cross-platform, but the examples and terminal references default to Windows environments.
Recommendations
- Explicitly mention and provide examples for Linux/macOS terminals (e.g., Bash, zsh) alongside Windows (cmd/PowerShell) in all command-line instructions.
- Show how to set environment variables in both Windows (setx/PowerShell) and Linux/macOS (export in Bash/zsh).
- When referencing 'console window', use inclusive language such as 'terminal (cmd, PowerShell, or Bash)' and alternate the order in which platforms are mentioned.
- Add a note clarifying that all .NET commands work on Linux/macOS as well, and provide troubleshooting tips for common cross-platform issues.
- Where file paths or editor usage is mentioned, provide examples for both Windows and Linux/macOS (e.g., using nano/vim vs. notepad).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-powershell.md
...es/quickstarts/email/includes/send-email-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and setup instructions using Azure PowerShell and Windows-specific commands. There are no Linux or cross-platform CLI examples, and the prerequisite steps explicitly mention Windows PowerShell. No mention is made of Bash, Azure CLI, or other Linux-compatible tools, which may exclude or confuse Linux users.
Recommendations
- Add equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include Bash shell examples for Linux users, especially for tasks like reading files and constructing email payloads.
- Update the prerequisites to mention both PowerShell and Azure CLI, and clarify which steps are platform-specific.
- Provide guidance for installing and using Azure Communication Services modules/tools on Linux and macOS.
- Ensure that all code samples are available in both PowerShell and Bash/Azure CLI formats, or clearly indicate platform compatibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-net.md
...-services/quickstarts/email/includes/send-email-net.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
powershell_heavy
Summary
The documentation is heavily focused on .NET and C# with all code examples and instructions tailored to the .NET SDK. Command-line instructions reference 'cmd', 'PowerShell', and 'Bash' equally, but the overall workflow assumes a Windows-centric development environment (e.g., Visual Studio, .NET, C#). There are no Linux-specific examples, troubleshooting steps, or alternative SDKs (such as Python, Java, or Node.js) shown. The use of .NET as the only SDK and C# as the only language, along with references to Windows command prompts first, demonstrates a Windows bias.
Recommendations
- Add equivalent examples using other supported SDKs (e.g., Python, Java, JavaScript) and show how to run them on Linux.
- Include explicit Linux/macOS shell commands (e.g., bash/zsh) and troubleshooting tips for common Linux environments.
- When mentioning command-line interfaces, list 'Bash' or 'Terminal' before 'cmd' and 'PowerShell', or present them in parallel.
- Provide links or references to cross-platform development tools and editors (e.g., VS Code) rather than assuming Visual Studio or Windows.
- Add a section or callout for Linux users, including any OS-specific prerequisites or package installation instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/inline-attachments-powershell.md
...ail-advanced/includes/inline-attachments-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and instructions using Azure PowerShell commands and Windows-specific patterns. There are no Linux or cross-platform CLI examples, and the prerequisite explicitly references Windows PowerShell. Linux users are not provided with equivalent instructions or code samples, which may hinder their ability to follow the guide.
Recommendations
- Add equivalent instructions and code samples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention support for Linux and macOS environments in the prerequisites and setup sections.
- Provide bash or shell script examples for common tasks, such as sending emails and handling attachments.
- Clarify whether the Az.Communication module can be used in PowerShell Core on Linux/macOS, and provide installation guidance if so.
- If PowerShell is required, include instructions for installing and running PowerShell Core on Linux/macOS, and test all examples for compatibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/inline-attachments-azcli.md
...nd-email-advanced/includes/inline-attachments-azcli.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits a Windows-first bias, particularly in the installation instructions for Azure CLI, which link directly to the Windows installer. The environment variable setup section lists Windows instructions first, and the Linux/macOS instructions are less detailed and somewhat generic. There are no Linux-specific troubleshooting tips or examples, and the documentation does not mention Linux-specific shell or editor considerations beyond a brief note about .bash_profile and .zshrc.
Recommendations
- Provide direct links to Azure CLI installation instructions for Linux and macOS alongside the Windows link in the prerequisites.
- Present environment variable setup instructions in a neutral order (e.g., tabs for Windows, macOS, Linux in alphabetical order or with Linux first, or no implied priority).
- Include Linux-specific troubleshooting tips, such as common permission issues or shell differences.
- Mention common Linux editors (e.g., nano, vim) for editing profile files, not just the file names.
- Ensure all examples and instructions are equally detailed for Linux, macOS, and Windows, including any OS-specific caveats.
- Consider adding a note that the Azure CLI commands work identically across platforms, and highlight any differences if they exist.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/send-email-with-inline-attachments.md
...d-email-advanced/send-email-with-inline-attachments.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides language pivots for multiple SDKs, but includes a dedicated PowerShell section without an equivalent for Bash or Linux shell scripting. PowerShell (a Windows-centric tool) is given equal prominence to cross-platform SDKs, and there is no mention or example of using Bash, curl, or other Linux-native tools for scripting email sending. This may make Linux users feel less supported.
Recommendations
- Add a Bash or shell scripting example for sending emails with inline attachments, using tools like curl or the Azure CLI.
- If PowerShell is included, ensure that a comparable Bash/Linux shell example is also present and given equal prominence.
- Clarify in the documentation which examples are cross-platform and which are Windows-specific.
- Consider adding a note about PowerShell Core's cross-platform support if relevant, or otherwise direct Linux users to alternative methods.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/prepend-net.md
...arts/email/send-email-advanced/includes/prepend-net.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Windows command-line tools (cmd, PowerShell) before Bash, and by not providing any Linux-specific examples or guidance. All command-line instructions are given in a generic form but reference Windows environments first. There are no Linux- or macOS-specific installation, environment variable, or troubleshooting instructions.
Recommendations
- Present Bash (Linux/macOS) examples before or alongside Windows (cmd/PowerShell) examples, especially for command-line instructions.
- Explicitly mention Linux/macOS compatibility in the prerequisites and provide platform-specific installation or troubleshooting notes where relevant.
- Include example commands for setting environment variables on Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...) in addition to Windows (set ...).
- Where file paths or editors are referenced, provide cross-platform alternatives (e.g., nano, vim, or Visual Studio Code for Linux/macOS).
- Add a section or callout for common Linux/macOS issues or differences, such as .NET SDK installation steps for those platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-powershell.md
...send-email-smtp/includes/send-email-smtp-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides instructions and code 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 sendmail, mailx, or Python scripts) mentioned. This creates a strong Windows bias and may exclude or confuse users on non-Windows platforms.
Recommendations
- Add equivalent instructions and code examples for Linux and macOS environments, using common tools such as sendmail, mailx, or Python's smtplib.
- Explicitly mention cross-platform alternatives and provide links to relevant documentation.
- Structure the documentation to present cross-platform or Linux/macOS examples alongside or before Windows/PowerShell examples.
- Clarify any platform-specific requirements or limitations for the SMTP process.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-smtpclient.md
...send-email-smtp/includes/send-email-smtp-smtpclient.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (cmd, PowerShell) before cross-platform options (Bash), and does not provide any Linux- or macOS-specific instructions or examples. All code and terminal instructions are generic, but the explicit mention of Windows tools first and lack of Linux-specific troubleshooting or environment notes suggests a bias toward Windows users.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd and PowerShell when mentioning console windows.
- Explicitly state that the .NET Core SDK and all commands work on Linux and macOS, not just Windows.
- Provide Linux/macOS-specific notes, such as how to install .NET Core on those platforms, or how to run the commands in a typical Linux terminal.
- Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, SSL/TLS, firewall).
- Ensure that all instructions and examples are clearly marked as cross-platform, or provide platform-specific sections if behavior differs.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/send-email-smtp.md
...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority
View Details â
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 sendmail, mailx, or Python scripts on Linux). Windows tools and patterns are mentioned exclusively, and Linux alternatives are missing.
Recommendations
- Add Linux-specific examples for sending email via SMTP, such as using sendmail, mailx, or Python scripts with smtplib.
- Include cross-platform .NET Core examples that run on both Windows and Linux.
- Provide clear instructions for Linux users, including installation and usage of relevant tools.
- Ensure that examples are balanced between Windows and Linux, or explicitly note platform limitations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/smtp-authentication.md
...ickstarts/email/send-email-smtp/smtp-authentication.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses the Azure Portal (web UI) for all configuration steps, with screenshots and instructions tailored to the portal interface. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), nor are there any Linux-specific instructions or considerations. The documentation implicitly assumes use of the Azure Portal, which is most commonly accessed from Windows environments, and does not mention or provide parity for Linux users who may prefer CLI tools or automation.
Recommendations
- Add Azure CLI examples for all resource and role assignment steps, including commands for creating service principals, assigning roles, and creating SMTP usernames.
- If PowerShell examples are provided in other documentation, ensure equivalent Bash/Azure CLI examples are present and shown first or side-by-side.
- Mention that all steps can be performed from any OS using the Azure Portal, but highlight CLI alternatives for Linux users.
- Include a section or appendix with Linux/Bash command-line equivalents for common tasks, such as using az commands to manage resources and permissions.
- Review screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., avoid referencing Windows-specific UI elements or terminology).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email.md
...communication-services/quickstarts/email/send-email.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page includes a dedicated section for Azure PowerShell, a Windows-centric tool, and lists it as a top-level platform pivot, potentially before or at parity with Linux-native options. While Azure CLI (cross-platform) is included, there is no explicit mention of Bash or Linux shell scripting, and no Linux-specific troubleshooting or cleanup examples. The presence of PowerShell as a primary method and the lack of Linux-specific examples or tools indicate a mild Windows bias.
Recommendations
- Add explicit Bash or Linux shell examples for sending emails using Azure Communication Services.
- Ensure that Linux-native tools and examples (e.g., Bash scripts, curl, or other CLI utilities) are presented alongside or before PowerShell examples.
- Include troubleshooting and cleanup instructions specific to Linux environments.
- Clearly indicate the cross-platform nature of Azure CLI and provide sample commands in both Windows (PowerShell/CMD) and Linux (Bash) syntax where applicable.
- Review the order of platform pivots to avoid consistently listing Windows tools (like PowerShell) before Linux equivalents.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/create-event-subscription-powershell.md
...vents/includes/create-event-subscription-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively uses Azure PowerShell (Windows-centric) for all examples and instructions. There are no examples using Azure CLI, Bash, or other cross-platform tools. The prerequisites and all command-line instructions assume PowerShell, which is most common on Windows, and there is no mention of Linux or macOS alternatives.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation instructions.
- Include Bash shell examples where appropriate, especially for scripting scenarios.
- In the prerequisites, list both PowerShell and Azure CLI as options, and link to their respective installation guides for different operating systems.
- For each operation (create, list, update, delete), provide both PowerShell and CLI command examples, and clearly label them.
- Avoid assuming the user is on Windows (e.g., do not use 'PS C:\>' prompt exclusively).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-cli.md
...ity/includes/active-directory/service-principal-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation consistently references Windows-specific resources and examples first or exclusively. All quickstart links for enabling managed identities are for Windows VMs, and there are no Linux VM equivalents or explicit Linux instructions. The guidance for setting environment variables does not mention Linux/macOS shell commands or patterns, and references to Visual Studio reinforce a Windows-centric perspective.
Recommendations
- Include links and examples for enabling managed identities on Linux VMs, not just Windows VMs.
- Provide explicit Linux/macOS shell commands for setting environment variables (e.g., export statements for Bash/Zsh).
- Mention cross-platform development environments (such as VS Code) in addition to or instead of Visual Studio.
- Ensure that all instructions and code samples are clearly marked as cross-platform or provide platform-specific alternatives where necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/manage-teams-identity.md
...nication-services/quickstarts/manage-teams-identity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias, particularly in administrative steps. PowerShell is the only command-line tool referenced for resolving service principal issues, with no mention of Linux or cross-platform alternatives (e.g., Azure CLI, Bash). The instructions for installing modules and running commands assume a Windows/PowerShell environment. No Linux-specific or cross-platform command examples are provided, and Windows tools and patterns are mentioned exclusively and before any Linux equivalents.
Recommendations
- Provide equivalent Azure CLI or Bash commands for all PowerShell instructions, especially for service principal creation and module installation.
- Explicitly mention that PowerShell Core is available cross-platform, or clarify if only Windows PowerShell is supported.
- Add Linux/macOS-specific instructions or notes where administrative actions are required.
- Reorder or parallelize instructions so that cross-platform tools (e.g., Azure CLI) are presented before or alongside Windows/PowerShell tools.
- Include troubleshooting steps for Linux/macOS users, such as how to install required tools and run commands in their environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/microsoft-entra-id-authentication-integration.md
...ntity/microsoft-entra-id-authentication-integration.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. While it does mention the Azure CLI (which is cross-platform), most administrative actions are described in the context of the Azure portal (a web UI, but often associated with Windows environments), and there is a lack of explicit Linux-specific guidance or examples. No Linux shell (bash) or automation examples are provided, and PowerShell is not mentioned, but the absence of Linux-specific instructions or parity in command-line examples suggests a Windows-centric approach. The documentation also refers to the Azure portal and Microsoft Entra admin center without clarifying cross-platform accessibility or alternatives for Linux users.
Recommendations
- Add explicit Linux shell (bash) examples for all CLI commands, especially for service principal creation and resource assignment.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide installation instructions for Linux users.
- Include screenshots or instructions for using the Azure portal and Microsoft Entra admin center from non-Windows environments (e.g., Linux browsers).
- Mention and provide links to Linux-native tools or automation options where available.
- Ensure that any references to GUI tools (Azure portal, Entra admin center) note their cross-platform nature and accessibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/router/includes/router-quickstart-net.md
...s/quickstarts/router/includes/router-quickstart-net.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific consoles (cmd, PowerShell) before Bash, focusing exclusively on .NET and C# (which are cross-platform but have a strong Windows association), and omitting explicit Linux/macOS-specific instructions or examples. No Linux-specific tools, shell commands, or troubleshooting steps are provided, and the only terminal commands shown are generic dotnet CLI commands. There are no references to Linux package managers or environment setup, and the documentation does not mention running the sample on Linux or macOS, nor does it address potential platform-specific issues.
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites and setup sections.
- Provide Linux/macOS-specific instructions or notes where relevant (e.g., using Bash, zsh, or different path separators).
- Include example commands for common Linux shells (e.g., Bash, zsh) alongside Windows (cmd, PowerShell) where applicable.
- Reference Linux package managers (such as apt, yum, or snap) for installing .NET, or link to official cross-platform installation guides.
- Add troubleshooting tips for common Linux/macOS issues (such as permissions, environment variables, or path problems).
- Ensure that all screenshots, file paths, and code snippets are platform-agnostic or provide alternatives for different operating systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/router/job-router-azure-openai-integration.md
...ckstarts/router/job-router-azure-openai-integration.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Visual Studio Code and its Azure Functions extension, with no mention of Linux-specific alternatives or instructions. All tooling and setup steps assume a Windows environment, and there are no examples or guidance for Linux users (e.g., using the Azure Functions Core Tools CLI, terminal commands, or deployment via Bash). The console application is .NET-based, which is cross-platform, but the documentation does not clarify Linux compatibility or provide Linux-specific instructions.
Recommendations
- Add explicit instructions for Linux users, including how to install and use Visual Studio Code and the Azure Functions extension on Linux.
- Include alternative setup and deployment steps using Azure Functions Core Tools CLI, which works on Linux and macOS.
- Provide terminal/Bash command examples alongside or instead of GUI-based instructions.
- Clarify that the .NET console application can be run on Linux and provide any necessary steps for .NET SDK installation on Linux.
- Mention cross-platform compatibility wherever applicable, and avoid assuming a Windows-only environment.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/receive-sms-no-code.md
...rvices/quickstarts/sms/includes/receive-sms-no-code.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively describes workflows using Logic Apps and Power Automate, which are primarily Microsoft (Windows-centric) tools. There are no examples or mentions of Linux-native alternatives, command-line tools, or cross-platform automation options. The screenshots and instructions focus solely on the Power Automate UI, with no parity for Linux users or those using open-source automation tools.
Recommendations
- Add examples using Azure CLI, Azure SDKs (e.g., Python, Node.js), or REST API calls to handle Event Grid events and send SMS, which are cross-platform.
- Mention and provide guidance for using open-source or Linux-friendly automation tools (e.g., Apache Airflow, custom scripts) to process events and send SMS.
- Clarify that Logic Apps and Power Automate are not the only options, and link to documentation for alternative approaches suitable for Linux environments.
- Include at least one end-to-end example that can be executed from a Linux shell, such as using bash scripts with curl or az CLI.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/send-sms-java.md
...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides explicit examples for Command Prompt and PowerShell (both Windows environments) when running Maven commands, but does not include any examples for Linux or macOS shells (such as Bash or Zsh). This may make it less accessible for users on non-Windows platforms, as they are left to infer the correct syntax for their environment.
Recommendations
- Add explicit Bash (or generic Unix shell) command examples alongside Command Prompt and PowerShell, especially for Maven commands.
- When listing command-line instructions, present Bash/Linux examples first or at least equally with Windows examples.
- Include a note clarifying that the Maven commands can be run in any terminal, and provide the syntax differences (if any) for Linux/macOS users.
- Review the documentation for any other places where Windows tools or patterns are assumed, and ensure Linux parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/phone-numbers-net.md
...es/quickstarts/telephony/includes/phone-numbers-net.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias by mentioning Windows-specific shells (cmd, PowerShell) before Bash, and by not providing explicit Linux or macOS-specific instructions or examples. All command-line examples use .NET CLI commands, which are cross-platform, but there is no confirmation or illustration of these commands being run in a Linux environment (e.g., screenshots, terminal prompts, or troubleshooting notes). No Linux-specific tools or patterns are mentioned, and there are no notes about potential platform differences.
Recommendations
- When referencing command-line environments, list Bash (Linux/macOS) before or alongside cmd/PowerShell, e.g., 'in a terminal (such as Bash, cmd, or PowerShell)'.
- Add explicit confirmation that all commands work on Linux and macOS, possibly with a note or a screenshot from a Linux terminal.
- Include troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, installing .NET SDK on Linux).
- Where relevant, provide Linux/macOS-specific instructions for environment variable setup or file paths.
- Consider including a sample run or output from a Linux terminal to reinforce cross-platform parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/voice-routing-sdk-portal.md
...kstarts/telephony/includes/voice-routing-sdk-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by referencing .NET regular expressions and linking to .NET documentation for regex, which is a Windows-centric technology. There are no Linux-specific examples or references to cross-platform tools or documentation. The workflow is described entirely through the Azure Portal UI, with no mention of command-line alternatives (such as Azure CLI or Bash scripting) that are common in Linux environments.
Recommendations
- Provide links to general regular expression documentation (such as PCRE or POSIX regex) in addition to or instead of .NET regex documentation.
- Include examples or references for configuring direct routing using cross-platform tools like Azure CLI, Bash, or REST APIs.
- Clarify that the instructions are platform-agnostic if they are, or explicitly mention Linux compatibility where applicable.
- Add notes or sections for Linux users, especially if any steps differ or if there are recommended tools for Linux environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-answer-teams-calls.md
...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell commands for key setup steps (e.g., creating Teams resource accounts, associating resources, and hosting DevTunnels). There are no equivalent Linux/bash examples or references to cross-platform alternatives. Windows tools and patterns (PowerShell, devtunnel CLI) are mentioned exclusively or before any Linux equivalents, and the prerequisites and instructions assume a Windows environment.
Recommendations
- Provide bash or Azure CLI equivalents for all PowerShell commands, especially for creating and associating Teams resource accounts.
- Clarify whether DevTunnels and related CLI commands are available and supported on Linux/macOS, and provide installation/usage instructions for those platforms.
- Add explicit notes or sections for Linux/macOS users, including troubleshooting tips and environment setup guidance.
- Where possible, use cross-platform tools (e.g., Azure CLI, REST API calls) in examples, or show both Windows and Linux command variants side-by-side.
- Review all links to ensure they do not point exclusively to Windows/Powershell documentation, and add references to Linux-compatible documentation where available.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (such as the Microsoft 365 admin center UI and the Get-CsOnlineApplicationInstance PowerShell cmdlet) without providing Linux or cross-platform alternatives. The instructions for enabling Teams for a user are given only via the Microsoft 365 admin center, which is a web UI but is often described in a way that assumes a Windows-centric workflow. The only command-line tool mentioned is a PowerShell cmdlet, with no mention of equivalent Graph API or CLI commands usable from Linux/macOS. There are no explicit Linux or cross-platform command-line examples for user or resource account management.
Recommendations
- Provide equivalent examples using cross-platform tools such as Azure CLI, Microsoft Graph API, or REST API for all operations currently described with PowerShell cmdlets.
- When referencing the Microsoft 365 admin center, clarify that it is a web-based tool accessible from any OS, and consider linking to equivalent command-line or API-based instructions.
- List Linux/cross-platform methods before or alongside Windows/PowerShell methods to avoid 'windows_first' ordering.
- Explicitly mention that all REST API examples are OS-agnostic and can be used from any platform.
- Where possible, add bash/cURL or Azure CLI examples for provisioning and consent operations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-server-outbound-call.md
.../tpe/teams-phone-extensibility-server-outbound-call.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing the Microsoft Admin portal and Marketplace workflows, which are primarily accessed via web interfaces commonly used in Windows-centric enterprise environments. There are no Linux-specific instructions or command-line examples (e.g., Azure CLI, Bash, or PowerShell Core on Linux) for license assignment or resource management. The code example is in C#, a language most often associated with Windows development, and there are no alternative examples for Linux-preferred languages (e.g., Python, Node.js). No mention is made of Linux-compatible tools or patterns for managing Teams resources or licenses.
Recommendations
- Include Azure CLI and/or REST API examples for license assignment and resource management, which are platform-agnostic and work on Linux.
- Provide code samples in additional languages commonly used on Linux (e.g., Python, Node.js) alongside C#.
- Explicitly mention that all steps can be performed from Linux environments and provide guidance for Linux users (e.g., using browser-based portals from Linux, or using CLI tools).
- Reference PowerShell Core (pwsh), which is cross-platform, if scripting is required, and provide equivalent Bash scripts where possible.
- Add a section or note on Linux compatibility and best practices for cross-platform automation.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-video-calling.md
.../voice-video-calling/get-started-with-video-calling.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page shows evidence of Windows bias, particularly in the 'Clean up resources' section, where only Windows is mentioned in the link to cleaning up resources. There are no explicit Linux or cross-platform CLI examples or references, and the tabs and pivots focus on Windows without mentioning Linux. This may make Linux users feel unsupported or overlooked.
Recommendations
- Add explicit Linux (and macOS, if relevant) instructions or tabs for resource cleanup and other platform-agnostic tasks.
- Ensure that all references to command-line tools or scripts include both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI) equivalents.
- Update links and tabbed content to include Linux pivots where applicable, or clarify if certain features are Windows-only.
- Review included content files (e.g., video-calling-javascript.md) to ensure parity in platform coverage and examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/closed-captions/closed-captions-ios.md
...alling/includes/closed-captions/closed-captions-ios.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tabs and pivots in prerequisite and cleanup links (e.g., '?tabs=windows', '?pivots=platform-azp'), and does not mention or provide Linux or cross-platform alternatives for resource creation or management. All code examples are iOS/Swift-focused, but ancillary Azure resource management instructions are Windows-centric.
Recommendations
- Update prerequisite and cleanup links to include or prioritize Linux and macOS instructions/tabs alongside Windows.
- Ensure that quickstart and resource creation guides referenced support Linux (e.g., Azure CLI, Bash) and are clearly linked.
- Avoid using Windows-specific query parameters (e.g., '?tabs=windows') in links unless alternatives are also provided.
- Explicitly state cross-platform options for Azure resource management, such as Azure CLI or the Azure Portal, not just Windows tools.
- Add a note clarifying that all features and setup steps are available on non-Windows platforms where applicable.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-ios.md
...ludes/teams-auto-attendant/teams-auto-attendant-ios.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Teams Admin Center (a web-based tool but often associated with Windows environments), Microsoft Graph Explorer, and Azure CLI. While the quickstart is for iOS development (macOS), all instructions for Teams configuration and resource management are given using Microsoft-centric tools, with no mention of Linux alternatives or command-line approaches (e.g., PowerShell, bash scripts, or cross-platform REST API usage). There are no Linux-specific examples or guidance for users who may not have access to the Teams Admin Center or prefer CLI/REST approaches.
Recommendations
- Provide equivalent instructions for configuring Teams Auto Attendant and retrieving Object IDs using cross-platform tools such as the Microsoft Graph API via curl or other REST clients.
- Explicitly mention that Teams Admin Center is web-based and accessible from any OS, and provide links to REST API documentation for users who prefer or require command-line or programmatic access.
- Add Linux/macOS CLI examples (e.g., using curl or httpie) for interacting with Microsoft Graph to retrieve resource information.
- Clarify any steps that are platform-agnostic and ensure parity in instructions for users on Linux or other non-Windows platforms.
- Where Azure CLI is used, confirm that all commands work identically on Linux/macOS and note any platform-specific caveats.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-android.md
...s/teams-auto-attendant/teams-auto-attendant-android.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the Teams Admin Center (a web-based tool, but often associated with Windows environments) and Microsoft Graph Explorer for administrative tasks, without mentioning or providing alternatives for Linux users. There are no examples or instructions for performing equivalent tasks using Linux-friendly tools (e.g., Azure CLI, Microsoft Graph CLI, or REST API via curl). Additionally, the documentation refers to the Teams Admin Center before any mention of CLI or API-based approaches, reinforcing a 'windows_first' pattern. No PowerShell-specific commands are present, but the overall workflow assumes familiarity with Microsoft-centric, often Windows-preferred, tools.
Recommendations
- Provide alternative instructions for Linux users, such as using Microsoft Graph CLI or REST API (with curl) to retrieve the Auto Attendant Object ID and related information.
- Explicitly mention that the Teams Admin Center is web-based and accessible from any OS, but also offer CLI/API alternatives for users who prefer or require non-GUI workflows.
- When referencing tools or workflows, present cross-platform options (e.g., Azure CLI, Graph CLI) alongside or before Windows-centric tools.
- Add Linux/macOS-specific notes or examples where relevant, especially for administrative and setup steps.
- Ensure parity in all code and command-line examples by including both Windows and Linux-friendly commands where applicable.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-ios.md
...ling/includes/teams-call-queue/teams-call-queue-ios.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing Windows-centric tools and workflows, such as the Teams Admin Center and Microsoft Graph Explorer, without mentioning or providing Linux equivalents or alternatives. Steps for obtaining necessary information (e.g., Call Queue Object ID) rely on Windows-based portals and tools, and there are no examples or instructions for performing these tasks on Linux or cross-platform environments. The Azure CLI is mentioned for token generation, which is cross-platform, but all other administrative steps are Windows-focused.
Recommendations
- Provide instructions for accessing Teams Admin features via cross-platform tools (e.g., Microsoft Graph API via CLI or REST calls) instead of relying solely on Teams Admin Center.
- Include Linux-friendly examples for administrative tasks, such as using curl or PowerShell Core (pwsh) on Linux to interact with Microsoft Graph.
- Mention and demonstrate how to use browser-based portals on Linux, or clarify that Teams Admin Center is accessible from any OS via web browser.
- Add explicit notes or sections for Linux users, highlighting any OS-agnostic steps and providing alternatives where Windows-only tools are referenced.
- Ensure that any screenshots or step-by-step instructions do not assume a Windows environment unless absolutely necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-android.md
.../includes/teams-call-queue/teams-call-queue-android.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows, such as the Teams Admin Center and Microsoft Graph Explorer, without mentioning Linux alternatives or command-line options. All administrative steps (creating call queues, finding object IDs) are described using GUI tools that are only available on Windows, and there are no examples or instructions for performing these tasks on Linux or via cross-platform command-line tools. The Azure CLI example is cross-platform, but it is only used for token generation, not for Teams or Call Queue management.
Recommendations
- Provide equivalent instructions for managing Teams Call Queues and Resource Accounts using PowerShell, Azure CLI, or Microsoft Graph API scripts that can be run on Linux/macOS.
- Include examples of using Microsoft Graph API via curl or other cross-platform tools to retrieve Object IDs, rather than relying solely on the Graph Explorer web tool.
- Mention and link to any available cross-platform admin tools or document how to perform necessary steps without requiring Windows-only GUIs.
- Clearly indicate which steps require Windows and offer alternatives or workarounds for Linux users where possible.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-javascript.md
...cludes/teams-call-queue/teams-call-queue-javascript.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows by referencing Windows-specific tools and patterns, such as the Teams Admin Center and Microsoft Graph Explorer, without mentioning or providing Linux equivalents or alternatives. The instructions for creating resources link to pages with Windows pivots/tabs by default. There are no explicit Linux or cross-platform command-line examples for administrative tasks, and the documentation assumes the use of a GUI (Teams Admin Center), which is more common on Windows. No PowerShell-specific commands are present, but the absence of Linux CLI or automation alternatives is notable.
Recommendations
- Provide Linux-friendly alternatives for administrative steps, such as using Azure CLI, Microsoft Graph API via curl, or cross-platform scripts, instead of relying solely on Teams Admin Center (GUI).
- When linking to resource creation guides, ensure that Linux and macOS options are equally visible and not defaulted to Windows.
- Explicitly state that all Node.js and npm commands are cross-platform, and verify that all instructions work on Linux/macOS shells.
- Add examples or notes for obtaining the Call Queue Object ID and other administrative data using command-line tools or scripts that can be run on Linux.
- Where screenshots or instructions reference GUI tools, provide equivalent CLI/API instructions for users on non-Windows systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-ios.md
...ce-video-calling/includes/teams-user/teams-user-ios.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation page demonstrates Windows bias primarily in the prerequisites section, where enabling Teams Phone features for users is referenced via a PowerShell link, with no mention of Linux or cross-platform alternatives. The Teams deployment link also points to Windows-centric installation instructions. No Linux or macOS equivalents for Teams management or deployment are mentioned, and the only administrative tooling referenced is PowerShell, which is Windows-specific.
Recommendations
- Include instructions or links for managing Teams Phone licenses and enabling Enterprise Voice using cross-platform tools (e.g., Microsoft Graph API, Teams Admin Center web UI).
- Mention that PowerShell is Windows-specific and provide alternatives for Linux/macOS users.
- Add references to Teams deployment guides for macOS and Linux, or clarify platform requirements.
- Where possible, provide parity in administrative examples, ensuring Linux/macOS users are not excluded from setup steps.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/incoming-audio-low-volume.md
...ideo-calling/audio-issues/incoming-audio-low-volume.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by specifically referencing Windows volume mixer and app volume settings, including a screenshot of the Windows volume mixer, without providing equivalent guidance or visuals for Linux or macOS systems. No Linux-specific tools, commands, or troubleshooting steps are mentioned, and the only OS explicitly referenced is Windows.
Recommendations
- Add equivalent instructions and screenshots for checking and adjusting audio settings on popular Linux desktop environments (e.g., GNOME, KDE) and macOS.
- Mention Linux and macOS system volume controls and app-specific volume settings where applicable, not just Windows.
- Use neutral language such as 'on your operating system' or 'on Windows, Linux, or macOS' rather than only referencing Windows.
- Provide links or references to official documentation for audio troubleshooting on Linux and macOS.
- If including screenshots, provide them for all major platforms or use generic diagrams where possible.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/speaker-issue.md
...ting/voice-video-calling/audio-issues/speaker-issue.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by specifically mentioning Windows volume mixer and app volume settings, including a screenshot of the Windows volume mixer, without providing equivalent guidance or screenshots for Linux or macOS systems. There are no Linux-specific troubleshooting steps or references to common Linux audio tools or settings, and Windows is the only OS called out by name in mitigation steps.
Recommendations
- Add equivalent troubleshooting instructions for Linux (e.g., checking PulseAudio or PipeWire volume controls, using pavucontrol, alsamixer, or system sound settings).
- Include screenshots of audio settings on popular Linux desktop environments (e.g., GNOME, KDE) alongside the Windows example.
- Mention macOS system sound settings and provide a screenshot or description for parity.
- Avoid singling out Windows in mitigation steps; instead, provide OS-agnostic instructions or parallel guidance for all major platforms.
- Reference common Linux and macOS audio troubleshooting tools where appropriate.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-browser-verbose-log.md
...lling/references/how-to-collect-browser-verbose-log.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides only Windows-specific instructions and command-line examples for collecting verbose logs from Edge and Chrome browsers. It references Windows file paths, executable locations, and omits any mention of Linux or macOS equivalents. No Linux or cross-platform examples are provided.
Recommendations
- Add Linux and macOS command-line examples for launching Edge and Chrome with the same logging flags.
- Specify typical Linux and macOS paths for browser executables (e.g., /usr/bin/google-chrome, /Applications/Google Chrome.app/Contents/MacOS/Google Chrome).
- Describe where log files are stored on Linux and macOS (e.g., the --user-data-dir path and resulting log file location).
- Mention any platform-specific differences in logging behavior or file permissions.
- Present examples for all major platforms side-by-side or in separate sections to ensure parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-diagnostic-audio-recordings.md
...ferences/how-to-collect-diagnostic-audio-recordings.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates Windows bias by providing build instructions and prerequisites only for Windows (e.g., Visual Studio 2022, Windows-specific Chromium build instructions, and the .exe extension for the unpack_aecdump tool). There are no instructions or examples for building or running the tool on Linux or macOS, nor are any cross-platform alternatives mentioned.
Recommendations
- Add Linux and macOS build instructions for unpack_aecdump, including required dependencies and example commands.
- Mention cross-platform prerequisites (e.g., gcc/clang, Python 3, depot_tools) and link to the relevant Chromium/Linux/macOS build guides.
- Show example commands for running unpack_aecdump on Linux/macOS (e.g., ./unpack_aecdump audio_debug.5.aecdump).
- Clarify that unpack_aecdump can be built and used on platforms other than Windows, if applicable.
- Ensure screenshots and file paths are not Windows-specific, or provide equivalents for other platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/email-resource-management.md
...nication-services/samples/email-resource-management.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Windows-specific tools in both the main content and code examples. PowerShell commands are provided for resource cleanup, while Linux/bash equivalents are missing. The structure and included files also suggest a preference for PowerShell and Windows-centric workflows.
Recommendations
- Provide equivalent bash/Azure CLI examples for all PowerShell commands, especially for resource cleanup and deletion.
- Ensure that Linux/macOS users are explicitly supported by including bash syntax and instructions.
- Reorganize the documentation to present cross-platform (CLI/bash) examples before or alongside PowerShell examples, rather than defaulting to Windows tools.
- Clearly indicate which commands are platform-specific and offer alternatives where possible.
- Review included files to ensure that Linux and macOS scenarios are as thoroughly documented as Windows/PowerShell scenarios.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-azure-openai-csharp.md
...amples/includes/call-automation-azure-openai-csharp.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation shows evidence of Windows bias. The prerequisites link to resource creation instructions with a '?tabs=windows' parameter, suggesting Windows-first guidance. The sample project is .NET-based, which is cross-platform, but there are no explicit Linux or macOS instructions or examples. No Linux-specific tools or shell commands are mentioned, and the only run command shown is 'dotnet run' without clarification for non-Windows users. The documentation does not mention Linux equivalents or potential platform-specific considerations.
Recommendations
- Provide explicit Linux/macOS instructions or confirm cross-platform compatibility for all steps, especially for running the sample and configuring prerequisites.
- Include Linux/macOS tabs or sections in prerequisite links and setup instructions, not just Windows.
- Mention any platform-specific dependencies or troubleshooting tips for Linux users.
- Clarify that 'dotnet run' works on Linux/macOS if .NET SDK is installed, and provide installation links for those platforms.
- If using dev tunnels or other tools, note their cross-platform support and provide alternative commands if necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-azure-openai-js.md
...es/samples/includes/call-automation-azure-openai-js.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell, Windows terminal, and command prompt as the primary environments for running commands, with only a vague mention of 'the equivalent' for other platforms. There are no explicit Linux or macOS terminal examples, nor are platform-specific differences addressed. The instructions and examples assume familiarity with Windows tools and workflows, potentially leaving Linux users with ambiguity.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal.app) alongside Windows environments.
- Provide command examples for Linux/macOS where differences exist (e.g., environment variable setup, file paths).
- Avoid referencing PowerShell or Windows tools first; instead, use neutral language like 'Open a terminal (PowerShell, Command Prompt, Bash, etc.)'.
- Add notes or sections highlighting any platform-specific steps or caveats.
- Ensure all referenced quickstart links and documentation pivots include Linux/macOS tabs/examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/email-resource-management-azurecli-powershell.md
...ludes/email-resource-management-azurecli-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell scripting throughout all examples, including variable initialization, function definitions, and control flow. Prerequisite checks and installation links are Windows-centric, referencing PowerShell and Windows-specific Azure CLI installation instructions. There are no Bash, shell, or Linux-native script examples provided, nor any mention of how to adapt the workflow for Linux or macOS environments.
Recommendations
- Provide equivalent Bash or shell script examples for all PowerShell code blocks, showing how to perform the same automation tasks on Linux/macOS.
- Include installation instructions and prerequisite checks for Azure CLI and PowerShell on Linux and macOS, not just Windows.
- When referencing command-line usage, clarify cross-platform compatibility and note any differences in syntax or environment setup.
- Consider restructuring the documentation to present platform-agnostic Azure CLI commands first, followed by platform-specific scripting options (PowerShell for Windows, Bash for Linux/macOS).
- Explicitly mention that Azure CLI works on all major platforms and provide links to installation guides for each.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/ui-maui.md
...les/communication-services/samples/includes/ui-maui.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation prioritizes Windows and Mac environments, specifically referencing Visual Studio for Mac/Windows and requiring Windows-specific tools (e.g., GitBash, WSL) to run shell scripts on Windows. There is no mention of native Linux support or instructions for running the sample on Linux, despite .NET MAUI's partial Linux compatibility and the use of shell scripts that would naturally run on Linux.
Recommendations
- Add explicit instructions for running the sample on Linux, including prerequisites (e.g., supported distributions, .NET SDK installation, and any required dependencies).
- Provide Linux-specific guidance for running shell scripts, rather than only referencing GitBash or WSL for Windows users.
- Clarify whether Visual Studio Code or other cross-platform IDEs can be used on Linux, and provide relevant instructions if supported.
- Ensure that all examples and steps are presented for Windows, Mac, and Linux equally, or clearly state platform limitations if Linux is not supported.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/integrate-azure-communication-services-with-copilot-studio.md
...grate-azure-communication-services-with-copilot-studio.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits Windows bias by referencing Windows-specific tabs (e.g., '?tabs=windows') in prerequisite links, mentioning Windows tools (such as 'dev tunnels') without Linux alternatives, and omitting any Linux-specific instructions or examples. There are no explicit Linux or cross-platform setup instructions, and all code samples are in C# with no mention of how to run or adapt them on Linux.
Recommendations
- Provide Linux-specific instructions or tabs alongside Windows in prerequisite links and setup steps.
- Mention and link to Linux-compatible alternatives for tools like 'dev tunnels' (e.g., 'ngrok', 'localtunnel', or Azure Dev Tunnels for Linux if supported).
- Clarify that the sample code can be run on Linux (e.g., using .NET Core/SDK on Linux) and provide any necessary instructions for Linux users.
- Ensure that all referenced documentation and quickstarts include Linux tabs or sections.
- Explicitly state cross-platform compatibility where applicable, and test the sample on Linux to confirm parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/building-app-start.md
...communication-services/tutorials/building-app-start.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several areas. The Node.js, nvm, and npm installation instructions and examples are Windows-centric, referencing a Windows-specific tutorial and using PowerShell commands. There are no equivalent Linux or macOS instructions or shell examples. File path examples and screenshots use Windows conventions (e.g., C:\Users\Documents\ACS\CallingApp), and there is no mention of Linux or macOS alternatives for common setup steps.
Recommendations
- Provide installation instructions and examples for Node.js, nvm, and npm for Linux and macOS, including shell/bash commands.
- Include file path examples using Linux/macOS conventions (e.g., ~/ACS/CallingApp) alongside Windows examples.
- Reference cross-platform documentation for nvm and npm, not just Windows-specific guides.
- Add screenshots or notes indicating how steps look on Linux/macOS, especially for Visual Studio Code and terminal usage.
- Explicitly state that the tutorial is cross-platform and highlight any OS-specific differences where relevant.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/chat-app-teams-embed.md
...mmunication-services/tutorials/chat-app-teams-embed.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft-centric tools (Visual Studio Code, Microsoft Teams Toolkit) and workflows, without mentioning or providing parity for Linux development environments or alternatives. All examples and tool recommendations assume a Windows or Microsoft 365 developer account context, with no explicit guidance for Linux users. There are no Linux-specific instructions, nor is there mention of cross-platform considerations or alternatives to the Microsoft Teams Toolkit for Linux.
Recommendations
- Explicitly state that Visual Studio Code and the Teams Toolkit are available on Linux and provide installation instructions for Linux users.
- Include command-line alternatives (e.g., using Yeoman generators, CLI tools, or manual setup) for users who may not use Visual Studio Code or prefer terminal-based workflows.
- Mention and link to any Linux-specific prerequisites or troubleshooting tips (such as package dependencies, Node.js installation on Linux, or permissions issues).
- Ensure that all screenshots and step-by-step instructions are not Windows-specific, or provide Linux equivalents where UI or paths differ.
- Clarify that a Microsoft 365 developer account can be used from any OS, and provide any relevant notes for Linux users (e.g., browser compatibility, Teams web app usage).
- If any features or tools are not supported on Linux, clearly state this and suggest workarounds or alternatives.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/collecting-user-feedback/collecting-user-feedback.md
...s/collecting-user-feedback/collecting-user-feedback.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias by referencing Azure services and tools (which are Microsoft-centric), and by omitting explicit Linux/macOS-specific instructions or examples. All setup and command-line instructions are platform-neutral in syntax (e.g., npm, Node.js), but there is no mention of Linux-specific considerations, nor are there any examples or troubleshooting tips for Linux users. The Azure portal and tooling are referenced without alternatives or parity notes for Linux users. The guide does not provide parity for Linux environments, such as systemd service setup, SELinux/AppArmor notes, or Linux file permissions, nor does it mention cross-platform testing or deployment.
Recommendations
- Add explicit instructions or notes for Linux/macOS users, such as how to install Node.js and npm on Ubuntu, Fedora, or macOS.
- Include Linux-specific examples for environment variable setup (e.g., using export in bash/zsh) and running the server as a background service (e.g., using systemd or pm2).
- Mention and link to Azure CLI and azcopy, which are cross-platform, as alternatives to the Azure portal for resource creation and management.
- Provide troubleshooting tips for common Linux issues (e.g., file permissions, firewall configuration, SELinux/AppArmor).
- Clarify that all code and instructions are cross-platform unless otherwise noted, and explicitly state any Windows-only steps.
- Consider adding a section or appendix with Linux/macOS-specific deployment best practices.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/trusted-service-js.md
...tion-services/tutorials/includes/trusted-service-js.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation consistently references Visual Studio Code and its Azure Functions extension as the primary (and only) development environment, with all instructions and links tailored to this workflow. There are no explicit examples or instructions for Linux-specific tools, terminal commands, or alternative editors. The use of 'F5' for running the function and right-click context menu actions are more familiar to Windows users. There is no mention of running or deploying the function using command-line tools (e.g., Azure CLI, func CLI) that are cross-platform, nor are there Linux/macOS-specific instructions or screenshots.
Recommendations
- Add explicit instructions and examples for setting up and running the function using cross-platform command-line tools such as Azure Functions Core Tools (func CLI) and Azure CLI.
- Include Linux/macOS-specific instructions for running and deploying the function, such as terminal commands for starting the function locally and deploying to Azure.
- Provide alternative instructions for users who prefer editors other than Visual Studio Code, or clarify that all steps are cross-platform if that is the case.
- Avoid referencing only GUI-based actions (e.g., 'right-click' in VS Code, 'F5') and provide equivalent command-line alternatives.
- Add screenshots or terminal output examples from Linux/macOS environments to demonstrate parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-android-tutorial.md
...orials/includes/twilio-to-acs-chat-android-tutorial.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by recommending Visual Studio (Windows-centric IDE) as the only development environment, providing only PowerShell-based package installation instructions, and omitting Linux alternatives (e.g., VS Code, dotnet CLI on Linux, Bash examples). There are no explicit references to Linux tools or workflows, and all command-line examples use Windows-first syntax.
Recommendations
- Include instructions for installing the Azure Communication Services Chat SDK using Bash (e.g., 'dotnet add package Azure.Communication.Chat') and clarify that this works cross-platform.
- Mention and provide guidance for using cross-platform editors such as Visual Studio Code or JetBrains Rider, in addition to Visual Studio.
- Add explicit notes that the SDK and CLI commands work on Linux and macOS, not just Windows.
- Where PowerShell is used, also provide Bash equivalents or clarify that the command is platform-agnostic.
- Add a section or callout for Linux/macOS developers, including any prerequisites or troubleshooting tips specific to those platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-csharp-tutorial.md
...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by recommending Visual Studio as the sole development environment, using PowerShell for package installation, and omitting Linux/macOS equivalents or cross-platform alternatives. All command-line and setup instructions assume a Windows environment, and there are no references to Linux tools (e.g., bash, dotnet CLI on Linux, VS Code) or guidance for non-Windows users.
Recommendations
- Include instructions for installing the SDK using the dotnet CLI on Linux/macOS (e.g., 'dotnet add package Azure.Communication.Chat' in bash/zsh).
- Mention cross-platform editors like Visual Studio Code and JetBrains Rider as alternatives to Visual Studio.
- Clarify that Azure CLI commands work on Linux/macOS and provide example shell commands.
- Add a 'Platform compatibility' note in prerequisites, explicitly stating support for Windows, Linux, and macOS.
- Provide troubleshooting tips or links for common issues on Linux/macOS (e.g., certificate errors, environment setup).
- Ensure all code and command snippets are platform-agnostic or provide platform-specific variants where necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-js-tutorial.md
...s/tutorials/includes/twilio-to-acs-chat-js-tutorial.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits a Windows bias in the prerequisites section. It provides a link and instructions specifically for installing the Azure CLI on Windows, with no mention of Linux or macOS equivalents. The resource creation link also includes a 'tabs=windows' parameter, suggesting a Windows-centric approach. There are no Linux-specific instructions or examples, and no mention of cross-platform compatibility for CLI commands.
Recommendations
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside Windows.
- Remove or generalize the 'tabs=windows' parameter in resource creation links, or add equivalent links for Linux/macOS.
- Explicitly state that the CLI commands are cross-platform, or provide platform-specific notes where differences exist.
- Include a short note in the prerequisites clarifying that all steps and commands work on Linux, macOS, and Windows, or highlight any platform-specific considerations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-video-ios-tutorial.md
...tutorials/includes/twilio-to-acs-video-ios-tutorial.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias in the prerequisites and setup sections. It provides only Windows-specific instructions and links for installing the Azure CLI, and references the Azure Portal with a Windows tab in the resource creation link. There are no Linux or macOS equivalents or instructions for these steps, despite the rest of the guide being platform-agnostic and focused on iOS development.
Recommendations
- Provide installation instructions and links for Azure CLI on Linux and macOS, not just Windows.
- Use neutral or multi-platform links for resource creation and CLI installation (e.g., tabs for Windows, Linux, macOS).
- Explicitly mention that the Azure CLI and other tools are available on multiple platforms, and link to the general installation guide.
- Ensure all command-line examples are platform-agnostic or provide platform-specific alternatives where necessary.
- Review the documentation for any other Windows-centric language or links and update them to be inclusive of Linux and macOS users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/virtual-visits.md
...les/communication-services/tutorials/virtual-visits.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows/Microsoft ecosystem bias by exclusively referencing Microsoft 365, Teams, Bookings, Outlook, and Azure tools, with all examples and workflows centered around these services. There are no mentions of Linux, cross-platform alternatives, or non-Microsoft scheduling, communication, or deployment tools. The documentation assumes usage of Microsoft web applications and Azure portal, which are optimized for Windows environments, and does not provide parity guidance for Linux users.
Recommendations
- Add explicit notes on cross-platform compatibility for all web-based tools (e.g., clarify that Bookings, Teams, and Azure portal are accessible from Linux browsers).
- Include examples or guidance for deploying and managing the sample application using Linux command-line tools (e.g., Azure CLI on Linux, Bash scripts) in addition to or instead of ARM templates via the portal.
- Reference or link to documentation for using Teams and Bookings on Linux (e.g., Teams web client, supported browsers, known limitations).
- Provide alternative approaches for scheduling and notifications that could be integrated with non-Microsoft or open-source tools, or at least acknowledge their existence.
- Ensure that screenshots and walkthroughs do not assume a Windows environment (e.g., avoid showing only Outlook/Bookings in Windows UI, clarify that the experience is browser-based and OS-agnostic where possible).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/virtual-visits/sample-builder.md
...on-services/tutorials/virtual-visits/sample-builder.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily oriented around Microsoft and Azure tools, with all deployment and configuration steps occurring via the Azure Portal, Microsoft 365 Bookings, and Microsoft Teams. There are no explicit references to Linux tools, command-line interfaces, or cross-platform deployment patterns. All screenshots and instructions assume the use of the Azure Portal (a web UI), and all integration examples are with Microsoft products. There are no examples or guidance for deploying or managing the sample using Linux-native tools, CLI, or automation outside the Microsoft ecosystem.
Recommendations
- Add instructions for deploying the sample using Azure CLI and Azure Resource Manager templates from a Linux terminal.
- Provide examples for managing and configuring the application using cross-platform tools (e.g., Azure CLI, azcopy, curl) rather than only through the Azure Portal.
- Include notes or sections on how to automate deployment and integration steps using shell scripts or Linux-native tools.
- Mention and link to any relevant Linux or open-source tools that can be used for monitoring, deployment, or integration.
- Ensure parity in screenshots and instructions by including examples from both the Azure Portal and command-line interfaces accessible from Linux and macOS.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-arm.md
...idential-computing/quick-create-confidential-vm-arm.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell syntax is used for variable assignment and command chaining throughout, with no equivalent Bash/Linux shell examples. Windows tools (PowerShell, Microsoft Graph SDK) are referenced for prerequisite installation and key management steps, and variable assignment is shown in PowerShell style. In the parameter file section, the Windows example is presented before the Linux example. There are missing Linux/Bash equivalents for critical steps such as variable assignment, command output parsing, and Microsoft Graph SDK usage.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell variable assignments and command chaining.
- Include instructions for installing and using Microsoft Graph SDK on Linux, or offer alternative CLI-based approaches.
- Present Windows and Linux parameter file examples side-by-side or alternate their order to avoid Windows-first bias.
- Ensure all command output parsing (e.g., extracting IDs from az CLI output) is shown for both PowerShell and Bash (using jq or grep/awk).
- Review all steps for implicit Windows assumptions and clarify cross-platform compatibility.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-marketplace.md
...les/confidential-computing/quick-create-marketplace.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Linux and Windows options for deploying Intel SGX VMs, but there is a subtle Windows bias. Windows tools and patterns (such as PowerShell, RDP, and references to Windows authentication) are mentioned alongside or before Linux equivalents. The instructions for connecting to a VM mention PowerShell and Windows-specific scenarios before Linux, and there is a separate section for connecting to Windows VMs, but not for Linux. Additionally, Windows terminology (Administrator name, RDP) is used in places where Linux equivalents could be emphasized.
Recommendations
- Ensure Linux examples and terminology are presented first, especially in cross-platform sections.
- Provide explicit, step-by-step Linux connection instructions before Windows instructions.
- Use neutral terms (e.g., 'username' instead of 'Administrator name') where possible.
- Include Linux-specific troubleshooting or tips, such as using native SSH clients or OpenSSH on Linux.
- Balance references to Windows tools (PowerShell, RDP) with Linux tools (Bash, SSH) and avoid assuming Windows as the default environment.
- Add a dedicated section for connecting to Linux VMs, similar to the Windows VM connection section.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-portal.md
...articles/confidential-computing/quick-create-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation generally presents a balanced approach, but there are subtle signs of Windows bias. Windows terminology and tools (e.g., PowerShell, RDP) are mentioned alongside or before Linux equivalents in several places. The instructions for connecting to the VM mention PowerShell on Windows before Bash on Linux, and there are references to Windows-specific connection methods and tools. There is also a direct link to Windows-specific instructions for post-deployment steps, while Linux instructions are embedded in the main flow.
Recommendations
- Ensure Linux tools and workflows are mentioned before or alongside Windows equivalents, especially in connection instructions.
- Provide Linux and Windows examples in parallel where possible, rather than linking out to Windows instructions.
- Avoid referencing Windows-specific tools (e.g., PowerShell, RDP) before Linux tools unless the majority of users are expected to be on Windows.
- Where possible, provide explicit Linux command-line examples for all steps, not just for SSH.
- Add a section or links for post-deployment steps on Linux, similar to the Windows links provided.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/quick-create-confidential-vm-azure-cli.md
...al-computing/quick-create-confidential-vm-azure-cli.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page shows moderate Windows bias in the advanced (customer-managed key) scenario. Several steps use PowerShell syntax and Windows-specific tools (e.g., Microsoft Graph PowerShell SDK) without providing equivalent Bash or cross-platform alternatives. PowerShell commands are interleaved with Azure CLI, and variables are set using PowerShell syntax, which may not work for Linux/macOS users. The initial sections are cross-platform, but the advanced scenario assumes a Windows/PowerShell environment. Linux parity is restored in the attestation section, which is Linux-focused.
Recommendations
- For every PowerShell command, provide a Bash (or cross-platform) equivalent, especially for variable assignment and Azure CLI invocations.
- Clearly separate Windows/PowerShell and Linux/Bash instructions, or provide tabs for both environments.
- For steps requiring Microsoft Graph, provide REST API or Azure CLI alternatives, or link to platform-agnostic instructions.
- Avoid using PowerShell-specific constructs (e.g., Out-String, ConvertFrom-Json, $var assignment) in mainline CLI documentation unless alternatives are shown.
- Review the order of examples to ensure neither Windows nor Linux is prioritized without justification.
- Add a note at the start of advanced sections clarifying which OS/shell the instructions target, and link to equivalents for other platforms.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/virtual-machine-metablob-disk.md
...onfidential-computing/virtual-machine-metablob-disk.md
High Priority
View Details â
Detected Bias Types
windows_first
os_type_windows_default
powershell_heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows is used as the default or sole OS example in disk creation commands (e.g., --os-type Windows), and PowerShell examples and notes are given equal or greater prominence than CLI or REST. There are no explicit Linux-specific examples or references to Linux disk types, and the documentation does not mention Linux-specific considerations or patterns. The ordering and language suggest Windows as the default use case.
Recommendations
- Provide explicit Linux examples in CLI and REST sections, e.g., use --os-type Linux and show a Linux disk creation workflow.
- Add notes or examples for Linux-specific scenarios, such as disk formats, guest state, or metadata differences.
- Balance PowerShell and CLI coverage by including Bash/Linux shell script examples where appropriate.
- Clarify that the feature is supported for both Windows and Linux VMs, and highlight any differences in usage or behavior.
- Avoid using Windows as the default in examples; alternate or show both OS types in sample commands.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/virtual-machine-solutions-sgx.md
...onfidential-computing/virtual-machine-solutions-sgx.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Windows Server images are mentioned before Ubuntu images in several places, and the ARM template example lists Windows first. The only direct command-line example uses Azure CLI, which is cross-platform, but the command is shown with PowerShell-style backticks for line continuation, which is specific to Windows/PowerShell. There are no Linux shell (bash) examples, nor is there mention of Linux-specific deployment patterns or tools.
Recommendations
- Provide both Windows (PowerShell) and Linux (bash) command-line examples, especially for Azure CLI usage. Use bash-style line continuation (\) alongside PowerShell backticks.
- Alternate or randomize the order of OS images in examples and lists, or explicitly state that the order does not imply preference.
- Include references to Linux-specific deployment tools or patterns, such as cloud-init, where relevant.
- Ensure that links and instructions for ARM templates and VM creation reference both Windows and Linux documentation equally.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/virtual-tpms-in-azure-confidential-vm.md
...ial-computing/virtual-tpms-in-azure-confidential-vm.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows TPM documentation and features (e.g., links to Windows TPM overview, recommendations, Secure Boot, PCR banks) exclusively. There are no examples, references, or links to Linux TPM usage, tools, or documentation. The explanations and links assume familiarity with Windows-centric TPM concepts and do not mention Linux equivalents or how vTPMs are used in Linux confidential VMs.
Recommendations
- Add references and links to Linux TPM documentation, such as tpm2-tools and Linux kernel TPM support.
- Include examples or explanations of how vTPMs are used and accessed in Linux confidential VMs, including command-line usage.
- Mention Linux equivalents for features like Measured Boot and Secure Boot (e.g., Linux's IMA/EVM, UEFI Secure Boot).
- Provide parity in describing how PCRs and attestation are handled in Linux environments.
- Ensure that both Windows and Linux users are addressed in introductory and technical sections.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-oracledatabase.md
...les/connectors/connectors-create-api-oracledatabase.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation assumes the use of the on-premises data gateway, which is primarily a Windows-only tool, and all installation and troubleshooting steps reference installing and running the gateway and Oracle client on 'the computer' without clarifying platform support. There are no Linux-specific instructions or examples, and no mention of Linux compatibility or alternatives. This creates a bias toward Windows environments.
Recommendations
- Explicitly state platform support for the on-premises data gateway and Oracle client (e.g., whether Linux is supported or not).
- If Linux is supported, provide Linux-specific installation steps and troubleshooting guidance for both the gateway and Oracle client.
- If Linux is not supported, clearly call this out in the prerequisites or limitations section.
- Include examples or notes for Linux users, such as using Oracle Instant Client on Linux, or alternatives for connecting from Linux hosts.
- When referencing services or commands (e.g., restarting PBIEgwService), provide Linux equivalents if available, or note their absence.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-native-http-swagger.md
.../articles/connectors/connectors-native-http-swagger.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation demonstrates Windows bias by primarily referencing Windows-centric tools and patterns. The only automation example for enabling CORS uses a PowerShell script, and Azure Storage Explorer (a GUI tool popular on Windows) is mentioned before any CLI alternatives. There are no Linux shell (bash/az CLI) examples, and Windows tools are referenced first or exclusively for key steps.
Recommendations
- Provide equivalent bash/az CLI commands for enabling CORS on Azure Storage, alongside the PowerShell example.
- Mention cross-platform tools (such as az CLI and REST API) before or alongside Windows-specific tools like PowerShell and Azure Storage Explorer.
- Clarify that Azure Storage Explorer is available on Linux and macOS, or suggest alternative CLI workflows for Linux users.
- Add explicit Linux/macOS instructions or examples where automation or tooling is discussed, to ensure parity.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-3270-apps-ibm-mainframe.md
...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias primarily through exclusive reliance on Windows-only tools (such as the 3270 Design Tool, which requires Microsoft .NET Framework 4.8), and by not mentioning or providing alternatives for Linux users. All setup and tool prerequisites are Windows-centric, and there are no examples or guidance for Linux environments. Additionally, the App Service Environment v3 support is explicitly limited to 'Windows plans only', and no mention is made of Linux-based App Service plans or cross-platform compatibility.
Recommendations
- Provide information about Linux-compatible alternatives for the 3270 Design Tool, or clarify if none exist.
- If possible, offer a cross-platform or web-based version of the 3270 Design Tool, or document how Linux/Mac users can generate HIDX files (e.g., via a containerized or remote Windows environment).
- Explicitly state the platform limitations (e.g., '3270 Design Tool is only available for Windows') early in the prerequisites section.
- If the connector or workflow is supported on Linux-based App Service plans, document the steps and any differences.
- Include a section or FAQ addressing Linux and Mac users, outlining their options and any workarounds.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-host-files-ibm-mainframe.md
...icles/connectors/integrate-host-files-ibm-mainframe.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing Windows-only tools such as Host Integration Server (HIS) Designer and Visual Studio, and by requiring the Microsoft .NET Framework 4.8 as a prerequisite. There are no examples or guidance for Linux or cross-platform users, and all setup and workflow steps assume a Windows-based development environment. Linux alternatives or instructions are not mentioned.
Recommendations
- Provide guidance or alternatives for Linux users, such as cross-platform tools for generating HIDX files or accessing host file metadata.
- If the HIS Designer is Windows-only, explicitly state this limitation and suggest possible workarounds (e.g., using a Windows VM, Docker container, or cloud-hosted environment).
- Include examples or instructions for Linux-based workflows, such as using Azure CLI, cross-platform editors, or scripting environments.
- Mention any open-source or third-party tools that can be used on Linux to create or manipulate HIDX files, if available.
- Clarify whether the IBM Host File connector and related processes can be managed entirely through the Azure Portal or CLI, which are cross-platform, and provide examples accordingly.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-ims-apps-ibm-mainframe.md
...rticles/connectors/integrate-ims-apps-ibm-mainframe.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) Designer and Transaction Integrator, which are Windows-only tools. All setup instructions and prerequisites assume the use of Windows (e.g., requiring .NET Framework 4.8), and there is no mention of Linux-compatible alternatives or workflows. No examples or guidance are provided for Linux users, nor is there any discussion of cross-platform support or parity.
Recommendations
- Explicitly state platform requirements and limitations (e.g., HIS Designer is Windows-only) early in the documentation.
- Provide guidance or alternatives for Linux users, such as recommending open-source or cross-platform tools if available, or clarifying if none exist.
- Include a section addressing Linux/macOS users, even if only to acknowledge the lack of support and suggest possible workarounds (e.g., using a Windows VM or container).
- If possible, develop and document Linux-compatible tooling for HIDX file generation and integration.
- Ensure future documentation includes parity in examples and instructions for both Windows and Linux environments.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/code-to-cloud-options.md
.../main/articles/container-apps/code-to-cloud-options.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Visual Studio and Visual Studio Code, and referencing PowerShell before Bash in the CLI section. There is a lack of explicit Linux-focused examples, tools, or workflows, and Windows tools are mentioned first or exclusively throughout the page.
Recommendations
- Add explicit Linux examples and workflows, such as using VS Code on Linux, Docker commands in Bash, and Linux-native deployment steps.
- Provide parity in tooling recommendations, e.g., mention JetBrains Rider or other cross-platform editors alongside Visual Studio.
- In CLI sections, alternate or balance references to PowerShell and Bash, and provide example commands for both shells.
- Include links to documentation for deploying from Linux environments and using Linux container registries.
- Highlight cross-platform compatibility and note any differences or considerations for Linux users.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/get-started-existing-container-image.md
...container-apps/get-started-existing-container-image.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Bash and PowerShell examples throughout, but the PowerShell examples rely heavily on the Az PowerShell module, which is primarily a Windows/PowerShell-centric tool. In several cases, the PowerShell examples are more verbose and use Windows-specific patterns (e.g., object pipelines, hash tables), and the documentation includes instructions to install PowerShell modules. The Azure CLI (Bash) examples are more concise and cross-platform, but PowerShell is given equal prominence, which may suggest a Windows-centric approach. There is no mention of native Linux tools or shell scripting beyond Bash, and PowerShell is presented as the only alternative to Bash, with no mention of other Unix shells.
Recommendations
- Clarify that PowerShell Core is cross-platform, or explicitly mention that PowerShell examples work on Linux/macOS if PowerShell Core is used.
- Consider adding examples using other common Linux shells (e.g., zsh, sh) or note that Bash examples are compatible with them.
- Where possible, simplify PowerShell examples to reduce Windows-specific patterns and make them more approachable for non-Windows users.
- Add a brief note at the start explaining that Azure CLI is the recommended cross-platform tool, and PowerShell is provided for users who prefer it.
- Ensure that any instructions for installing tools (like Az PowerShell modules) include cross-platform guidance.
- If possible, provide a table or toggle to let users select their preferred environment (Windows, Linux, macOS) and show only relevant examples.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/deploy-visual-studio.md
...b/main/articles/container-apps/deploy-visual-studio.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows and Visual Studio, providing only instructions and screenshots for the Visual Studio GUI on Windows. There are no examples or guidance for deploying to Azure Container Apps from Linux environments, nor are alternative tools (such as VS Code, Azure CLI, or Docker CLI) mentioned. The workflow assumes the user is on Windows with Visual Studio, and does not address Linux users or provide parity in tooling or instructions.
Recommendations
- Add a section describing how to deploy containerized .NET applications to Azure Container Apps using cross-platform tools such as Azure CLI, Docker CLI, or Visual Studio Code.
- Include Linux-specific instructions and command-line examples for creating, building, and deploying the application, ensuring users on Linux or macOS can follow along.
- Mention and link to alternative tools (e.g., VS Code with Docker and Azure extensions) earlier in the documentation, not just Visual Studio.
- Provide parity in screenshots and workflow descriptions for Linux users, or at least clarify that the current instructions are Windows/Visual Studio-specific and link to Linux-friendly guides.
- Ensure that all steps that rely on Visual Studio GUI have equivalent command-line or cross-platform alternatives documented.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/environment-variables.md
.../main/articles/container-apps/environment-variables.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for managing environment variables in Azure Container Apps. However, the PowerShell section is significantly more detailed, with step-by-step instructions and explanations of object models, while the Azure CLI section is more concise. There is no mention of Linux-specific shells or scripting (e.g., Bash), and PowerShell (a Windows-centric tool) is given equal or greater prominence. No Linux-native tools or patterns (such as Bash scripting or environment variable manipulation in Dockerfiles) are referenced. The tab order also presents PowerShell immediately after Azure CLI, reinforcing parity with Windows tools.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, showing how to set and export environment variables in a Linux context.
- Include notes or examples for common Linux workflows, such as using environment variables in Dockerfiles or with 'env' files.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, possibly with a note or section for Linux users.
- Consider adding a 'Bash' or 'Linux shell' tab alongside the existing 'Azure CLI' and 'PowerShell' tabs to demonstrate parity.
- Reduce the level of detail in PowerShell-specific object manipulation unless similar depth is provided for Linux-native workflows.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/how-to-use-private-endpoint.md
...articles/container-apps/how-to-use-private-endpoint.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias by providing only Windows-based VM creation and validation steps (e.g., using Windows Server images and PowerShell for DNS testing), with no Linux VM or Bash-based examples. The portal and CLI instructions default to Windows Server, and the only shell commands for endpoint validation are in PowerShell. There are no instructions for creating or testing with a Linux VM, nor are there Bash or Linux-native DNS tools (like dig or nslookup in Bash) shown.
Recommendations
- Add parallel instructions for creating a Linux VM (e.g., Ubuntu) in both portal and CLI sections.
- Provide examples for validating DNS and connectivity using Bash (e.g., using nslookup or dig in a Linux shell) inside the Linux VM.
- When listing VM image options, mention Linux images alongside Windows images, or default to a cross-platform-neutral image.
- Where PowerShell is used, also provide equivalent Bash/Linux commands.
- Review the order of presentation to ensure Linux and Windows are given equal prominence, or group instructions by OS.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/manage-secrets.md
...cs/blob/main/articles/container-apps/manage-secrets.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation consistently provides PowerShell examples for all supported scenarios, and in some cases, PowerShell is the only scripting language shown alongside Azure CLI and ARM templates. There are no explicit Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and PowerShell is presented as a primary automation tool. In some cases, features are not supported in PowerShell, but there are no alternative Linux-native instructions or notes for Linux users. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell objects and parameters, without offering parity for Linux shell users.
Recommendations
- Add explicit bash (Linux shell) scripting examples for all scenarios where PowerShell is shown, especially for tasks like setting environment variables, referencing secrets, and mounting volumes.
- Where PowerShell is not supported (e.g., Key Vault references, mounting secrets as a volume), provide alternative instructions or workarounds for Linux users, or clearly state that Azure CLI is the cross-platform alternative.
- Reorder examples to present Azure CLI (which is cross-platform) before PowerShell, or group examples by platform rather than by tool.
- Include notes or callouts for Linux/macOS users, especially where Windows-specific tools or patterns are used.
- Consider adding a section summarizing cross-platform support for each feature, clarifying which tools and platforms are supported.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/metrics.md
...zure-docs/blob/main/articles/container-apps/metrics.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page references both Azure CLI and Azure PowerShell for retrieving metrics, but PowerShell is mentioned explicitly and linked alongside CLI, suggesting parity. However, there are no concrete command examples for either tool, and no Linux-specific tools or patterns (such as Bash scripting, curl, or jq) are mentioned. The documentation does not provide any Linux-oriented guidance or examples, and the mention of PowerShell may imply a Windows-first audience.
Recommendations
- Provide explicit command-line examples for both Azure CLI and Azure PowerShell, showing how to retrieve metrics.
- Include Linux/Bash-specific examples, such as using Azure CLI in Bash, piping output to jq, or integrating with Linux monitoring tools.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Avoid mentioning PowerShell before CLI, or present both equally, noting their platform compatibility.
- Add a section or note for Linux users, highlighting any differences or tips for monitoring from Linux environments.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/troubleshooting.md
...s/blob/main/articles/container-apps/troubleshooting.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation shows a moderate Windows bias. In several places, Windows terminology and tools are mentioned first or exclusively (e.g., 'elevated command prompt', 'Docker on Windows', PowerShell examples), and PowerShell is given parity with Bash in extension installation, but Linux-specific shells or tools are not discussed. There is no explicit Linux example for running Docker, and the only shell-specific tabs are Bash and PowerShell, with no mention of Linux-specific troubleshooting environments or commands.
Recommendations
- Add explicit Linux shell examples and instructions where relevant (e.g., mention 'terminal' instead of 'elevated command prompt', and provide Linux-specific Docker run instructions).
- When referencing Docker, include links or notes for both Windows and Linux installation and usage.
- In sections with command tabs, consider adding a generic 'Linux' or 'macOS' tab if there are differences, or clarify that Bash examples work on Linux/macOS.
- Avoid Windows-first language (e.g., say 'open a terminal' instead of 'elevated command prompt') and ensure parity in tool references.
- Mention Linux troubleshooting tools or patterns where appropriate, such as using 'journalctl' for Docker logs or checking permissions.
- Ensure that all PowerShell examples have equivalent Bash/Linux CLI examples, and vice versa.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/vnet-custom.md
...-docs/blob/main/articles/container-apps/vnet-custom.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for all command-line steps, but PowerShell is given equal prominence throughout, and Windows-specific tools (PowerShell cmdlets) are used extensively. There are no Linux-specific tools or patterns mentioned, and PowerShell examples are present for every operation, reflecting a bias toward Windows environments. Additionally, some resource creation steps (e.g., Log Analytics workspace) are only shown with PowerShell, not Bash, and PowerShell parameter tables are included alongside Bash, reinforcing Windows parity but not Linux-first approaches.
Recommendations
- Ensure all resource creation and configuration steps (e.g., Log Analytics workspace creation) have Bash/Azure CLI equivalents, not just PowerShell.
- Consider providing Linux-specific troubleshooting tips or notes where platform differences may arise.
- If PowerShell is shown, clarify that it is available cross-platform (Windows, macOS, Linux) to reduce the perception of Windows-only bias.
- Add explicit references to Linux environments and tools where relevant, such as mentioning that Bash examples are suitable for Linux and macOS.
- Review the order of examples to ensure Bash/Linux commands are presented first or with equal prominence to PowerShell/Windows commands.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/automate/cost-management-api-permissions.md
...nt-billing/automate/cost-management-api-permissions.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell as the only command-line automation example for assigning roles, without mentioning Azure CLI or providing Linux/macOS-specific instructions. The portal-based instructions also implicitly favor Windows users, as the Azure portal experience is often described from a Windows-centric perspective. No Linux or cross-platform automation examples are provided.
Recommendations
- Add Azure CLI examples for assigning service principal roles, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide parallel instructions for each.
- Include bash/shell script examples where automation is discussed, not just PowerShell.
- Review portal instructions to ensure they are not written with a Windows-centric assumption (e.g., clarify that the Azure portal is web-based and platform-agnostic).
- Where APIs are referenced for automation, provide sample curl or HTTP request examples that can be run from any OS.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/cost-management-billing-overview.md
...management-billing/cost-management-billing-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Microsoft portals and tools (Azure portal, Microsoft 365 admin center, Power BI) exclusively, without mentioning Linux-friendly alternatives or CLI-based workflows. There are no examples or instructions for managing billing via cross-platform tools like Azure CLI, REST API, or automation scripts (e.g., Bash). The documentation assumes usage of graphical interfaces that are most accessible from Windows environments, and does not provide parity for Linux users.
Recommendations
- Add examples and instructions for managing billing and cost analysis using Azure CLI and REST API, which are cross-platform and accessible from Linux.
- Explicitly mention that all features are available via the Azure portal from any OS/browser, and clarify any limitations.
- Provide sample workflows or scripts for common billing tasks using Bash or other Linux-native tools.
- Reference PowerShell and Power BI only alongside equivalent Linux-friendly tools (e.g., Azure CLI, Jupyter Notebooks with REST API calls, or open-source BI tools).
- Ensure that any screenshots or UI walkthroughs clarify that they are accessible from all major OS platforms.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/analyze-cost-data-azure-cost-management-power-bi-template-app.md
...-cost-data-azure-cost-management-power-bi-template-app.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Power BI (a Windows-centric tool) for cost analysis, with no mention of Linux-compatible alternatives or cross-platform usage. All instructions, screenshots, and troubleshooting steps assume use of the Power BI app/service, which is primarily available on Windows. There are no examples or guidance for Linux users, nor are Linux tools or command-line patterns referenced.
Recommendations
- Include guidance for accessing Azure cost data using cross-platform tools such as Azure CLI, REST API, or Python scripts, which can be run on Linux.
- Add examples or links for Linux users to analyze cost data, such as using Jupyter Notebooks, pandas, or other open-source BI tools.
- Clarify platform requirements and limitations for Power BI, and suggest alternatives for users on non-Windows platforms.
- Provide parity in troubleshooting steps for Linux-based workflows, such as issues encountered when using Azure CLI or API.
- Mention and link to documentation for Linux-compatible cost management solutions or community-supported tools.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/cost-allocation-introduction.md
...nagement-billing/costs/cost-allocation-introduction.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows-centric tools (Azure portal, PowerShell) before cross-platform options (CLI, REST API) when describing resource management. There are no explicit Linux or Bash examples, and PowerShell is mentioned as a primary management tool. The absence of Linux-specific instructions or parity in examples suggests a lack of consideration for non-Windows users.
Recommendations
- Explicitly mention Azure CLI and Bash as first-class management options alongside PowerShell and the Azure portal.
- Provide example commands for both PowerShell and Azure CLI/Bash when describing resource management tasks.
- Include references to Linux-native tools and workflows where applicable.
- Ensure that cross-platform options are listed before or alongside Windows-specific tools to avoid implicit prioritization.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/discover-cloud-footprint.md
...-management-billing/manage/discover-cloud-footprint.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through exclusive references to Microsoft portals (Azure portal, Microsoft 365 admin center) and tools, with no mention of Linux-specific tools, interfaces, or command-line environments. All programmatic examples use Azure CLI, which is cross-platform, but there are no explicit Linux shell or scripting examples, nor is there guidance for Linux-native users. The documentation assumes use of Microsoft-managed environments and does not address Linux or open-source alternatives, nor does it mention PowerShell, but the overall framing and toolset are Windows-centric.
Recommendations
- Include explicit instructions or notes for Linux users, such as confirming that Azure CLI commands work identically on Linux and how to install Azure CLI on Linux.
- Provide examples using Bash or other Linux-native shells where appropriate, especially for automation or scripting tasks.
- Mention cross-platform compatibility for all tools and portals, and clarify any differences in experience for Linux users.
- If possible, reference open-source or third-party tools that Linux users may prefer or need to use.
- Add a section or callout addressing Linux/macOS users, ensuring parity in guidance and troubleshooting steps.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/enable-tag-inheritance.md
...ost-management-billing/costs/enable-tag-inheritance.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively describes enabling and using tag inheritance through the Azure portal, a web-based GUI that is consistent across platforms but is most commonly associated with Windows workflows. There are no examples or instructions for enabling tag inheritance via cross-platform command-line tools such as Azure CLI or REST API, which are widely used on Linux and macOS. No PowerShell-specific commands are present, but the absence of CLI or API instructions creates a Windows-centric bias by default.
Recommendations
- Add instructions and examples for enabling and managing tag inheritance using Azure CLI (az costmanagement or relevant commands), which is cross-platform and widely used on Linux.
- Include REST API examples for automation and integration scenarios, which are platform-agnostic.
- Explicitly mention that the Azure portal is accessible from any OS, but provide parity for users who prefer or require command-line or automated workflows.
- Where screenshots are used, clarify that the portal UI is the same across platforms, and consider adding CLI/API output examples for completeness.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/export-cost-data-storage-account-sas-key.md
...ling/costs/export-cost-data-storage-account-sas-key.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal (a web GUI) for all operations, with no mention of cross-platform CLI tools (such as Azure CLI or Azure PowerShell) or Linux-native workflows. There are no command-line examples, and the instructions assume a GUI-based workflow typical of Windows users. Additionally, troubleshooting and configuration steps are described only in the context of the Azure portal, with no Linux or cross-platform alternatives provided.
Recommendations
- Add Azure CLI examples for creating and managing SAS tokens, as Azure CLI is cross-platform and widely used on Linux.
- Include PowerShell examples, but ensure they are clearly marked as optional and provide parity with CLI examples.
- Document how to perform the same tasks (SAS key creation, export configuration) using the Azure CLI and/or REST API, and link to relevant documentation.
- Mention that all steps can be performed on Linux, macOS, or Windows using the CLI or API, and provide explicit instructions for non-GUI workflows.
- Ensure troubleshooting steps include CLI-based diagnostics and error handling, not just portal-based solutions.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/manage-automation.md
...les/cost-management-billing/costs/manage-automation.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively recommending and referencing Windows-centric tools (Power BI, Excel) for cost data analysis, without mentioning or providing examples for Linux-friendly alternatives. No Linux-specific tools, command-line examples, or cross-platform automation patterns (such as Bash scripts, Python, or open-source BI tools) are included. The guidance assumes use of Windows environments and omits parity for Linux users.
Recommendations
- Include examples using Linux command-line tools (e.g., curl, wget) for API interactions and data downloads.
- Mention and provide guidance for open-source or cross-platform BI tools (e.g., Apache Superset, Grafana, Jupyter Notebooks) for cost data analysis.
- Add sample automation scripts in Bash or Python for retrieving and processing cost data, alongside any PowerShell or Windows-centric examples.
- Explicitly state that the APIs and exports can be consumed on any platform, and provide instructions for Linux users to access exported data from Azure Storage (e.g., using azcopy, Azure CLI, or REST API calls).
- Balance references to Excel and Power BI with alternatives available on Linux, such as LibreOffice Calc or other spreadsheet software.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/quick-create-budget-template.md
...nagement-billing/costs/quick-create-budget-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates mild Windows bias. Throughout the page, deployment instructions and validation steps consistently mention Azure PowerShell and reference PowerShell-specific documentation (e.g., 'deploy-powershell.md') before or alongside Azure CLI and REST API. The 'Deploy templates' link points to a PowerShell-focused page, and PowerShell is given equal or greater prominence compared to CLI in validation and cleanup sections. There is no explicit mention of Linux-specific considerations, nor are Linux shell examples (e.g., bash scripts) provided. The use of the Azure portal (a web interface) is platform-neutral, but the command-line tooling leans toward Windows/PowerShell patterns.
Recommendations
- Ensure that CLI (az) examples are given equal or greater prominence than PowerShell, especially in headings and links.
- Reference both 'deploy-powershell.md' and 'deploy-cli.md' (or equivalent) in deployment instructions and 'See also' links.
- Include explicit bash shell examples for Linux users where interactive input is required (e.g., using 'read' in bash).
- Add notes clarifying that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Consider adding a section or callout for Linux/macOS users, highlighting any differences or best practices.
- Review and balance the order of presentation so that Windows/PowerShell is not always mentioned first.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/tutorial-acm-create-budgets.md
...anagement-billing/costs/tutorial-acm-create-budgets.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples first and in greater detail, referencing Windows-specific tools (PowerShell) and patterns, and mentioning Windows-centric approaches before their Linux equivalents. The CLI example is present but follows PowerShell, and there is no mention of Linux-specific shell usage or cross-platform scripting nuances. The tutorial also references the Azure portal and mobile app, which are platform-neutral, but the programmatic sections favor Windows tools and workflows.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide shell-specific notes (e.g., bash, zsh) where relevant.
- Include Linux/macOS-specific instructions for installing and using Azure CLI and Terraform, such as package manager commands (apt, yum, brew).
- Add notes or examples for scripting budget creation using bash or other common Linux shells.
- Clarify that PowerShell Core is available on Linux/macOS, and provide installation instructions for those platforms.
- Ensure that REST API usage is highlighted as platform-agnostic and provide curl or httpie examples for Linux users.
- Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid referencing Windows-only UI elements or terminology).
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/link-partner-id-power-apps-accounts.md
...-billing/manage/link-partner-id-power-apps-accounts.md
High Priority
View Details â
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 featured prominently and described before Azure CLI, with no mention of Bash or Linux-native scripting. The Azure portal (a GUI tool most commonly used on Windows) is the primary method described for PAL association, and all command-line examples use PowerShell or Azure CLI, with no Linux-specific instructions or examples. There is no discussion of Linux environments, nor are there examples using Bash, shell scripts, or Linux package managers. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux parity.
Recommendations
- Add explicit Bash and shell script examples for PAL association and resource attribution.
- Include instructions for installing and using Azure CLI and PowerShell on Linux, including any platform-specific caveats.
- Mention cross-platform compatibility of Azure CLI and PowerShell, and clarify any differences in usage or output on Linux.
- Provide screenshots or walkthroughs using Linux desktop environments (e.g., GNOME, KDE) where GUI steps are shown.
- Reference Linux package managers (e.g., apt, yum) for installing Azure CLI and PowerShell.
- Add a section discussing best practices for Linux users, including automation and scripting approaches common in Linux environments.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/link-partner-id.md
...cles/cost-management-billing/manage/link-partner-id.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias by presenting all command-line examples with Windows-style prompts (e.g., 'C:\>'), listing PowerShell instructions before Azure CLI, and not providing any explicit Linux/macOS-specific guidance or examples. The installation and usage instructions for both PowerShell and Azure CLI assume a Windows environment, with no mention of Bash, Linux/macOS terminal conventions, or cross-platform differences.
Recommendations
- Provide Linux/macOS-specific examples alongside or immediately after Windows examples, using appropriate shell prompts (e.g., '$' for Bash).
- Clarify that both PowerShell and Azure CLI are cross-platform, and provide installation and usage instructions for Linux/macOS environments.
- Avoid using Windows-style paths and prompts exclusively; instead, show both 'C:\>' and '$' where relevant.
- Explicitly mention any platform-specific prerequisites or differences in behavior.
- Consider including screenshots or instructions from the Azure portal as it appears on non-Windows platforms, if applicable.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/mca-role-migration.md
...s/cost-management-billing/manage/mca-role-migration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation demonstrates a strong Windows bias by exclusively providing a PowerShell script for automating billing role migration, instructing users to select PowerShell in Azure Cloud Shell, and omitting any Bash or cross-platform scripting alternatives. The instructions and screenshots prioritize PowerShell usage, and there is no mention of how to accomplish the task using Linux-native tools or shell environments.
Recommendations
- Provide equivalent Bash (or Azure CLI) script examples for Linux and macOS users.
- Update instructions to include both PowerShell and Bash options in Azure Cloud Shell, with guidance for each.
- Clarify that the process can be completed on any platform, and specify any platform-specific prerequisites or differences.
- Include screenshots and step-by-step instructions for both PowerShell and Bash workflows.
- Reference cross-platform tools (e.g., Azure CLI, REST API via curl/jq) where possible, not just Windows-centric tools.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/programmatically-create-subscription-microsoft-customer-agreement-across-tenants.md
...bscription-microsoft-customer-agreement-across-tenants.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for obtaining the service principal ID, but lists the Azure CLI (cross-platform) example first. However, there is a notable presence of PowerShell-specific instructions, and no explicit mention of Linux or bash scripting environments outside of the Azure CLI. There are no Linux-specific shell examples or guidance for users who may not have access to PowerShell, and the documentation does not clarify cross-platform compatibility for all steps. The rest of the process uses REST API calls, which are platform-agnostic, but the lack of explicit Linux/bash examples or notes may hinder Linux users.
Recommendations
- Ensure that for every PowerShell example, an equivalent bash or shell script example is provided, especially for common Linux environments.
- Explicitly state that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Where REST API calls are shown, provide example invocations using curl or similar Linux-native tools.
- Add a note at the beginning of the 'Programmatically create a subscription' section clarifying that all steps can be performed from Linux, macOS, or Windows, and link to Azure CLI installation instructions for Linux.
- Consider including a table summarizing which tools/commands are available on which platforms (e.g., Azure CLI, Azure PowerShell, curl, etc.).
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/programmatically-create-subscription-microsoft-partner-agreement.md
...ically-create-subscription-microsoft-partner-agreement.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation shows a moderate Windows/PowerShell bias. PowerShell is consistently presented as a first-class automation method alongside REST and Azure CLI, even though the Azure CLI is fully cross-platform and REST is OS-agnostic. In several steps, PowerShell tabs are present but simply instruct users to use Azure CLI or REST, indicating lack of parity or support. The documentation also references PowerShell module installation and usage patterns typical of Windows environments, and PowerShell examples are given equal or greater prominence than CLI. There is no mention of Linux-specific considerations, shells, or scripting environments.
Recommendations
- Ensure all PowerShell examples have equivalent, tested Azure CLI examples, and vice versa.
- Clearly state that Azure CLI is fully supported and cross-platform, and recommend it for Linux/macOS users.
- Avoid presenting PowerShell as the default or first automation method unless it is the only supported option.
- When PowerShell is not supported, consider omitting the tab or providing a clear message about cross-platform alternatives.
- Add notes or sections for Linux/macOS users, including shell-specific tips (e.g., Bash scripting, environment variables).
- Review and balance the order of example tabs so that REST and Azure CLI are not consistently placed after PowerShell.
- Where PowerShell module installation is discussed, provide parallel instructions for Azure CLI extension installation.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/protect-tenants-subscriptions.md
...gement-billing/manage/protect-tenants-subscriptions.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on Microsoft-centric tools and platforms (Azure portal, Microsoft 365 Admin Center, Microsoft Entra ID), with no mention of Linux-specific workflows, CLI examples, or cross-platform alternatives. References to deletion and transfer actions are tied to Microsoft portals and admin centers, which are typically accessed via Windows environments. The only command-line reference in related content is to Azure PowerShell, with no Bash or Azure CLI examples provided, indicating a Windows-first and Windows-tools bias.
Recommendations
- Include Azure CLI and Bash examples alongside Azure PowerShell for resource deletion and subscription management.
- Explicitly mention cross-platform access methods (e.g., using Azure CLI on Linux/macOS) for all actions.
- Provide links or references to Linux/macOS documentation where applicable.
- Clarify that actions can be performed from any OS, not just Windows, and highlight any differences or prerequisites for non-Windows users.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/prepare-buy-reservation.md
...gement-billing/reservations/prepare-buy-reservation.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page displays a mild Windows bias. While it mentions multiple automation options (Azure portal, APIs, PowerShell, CLI), PowerShell is listed before CLI, and the only automation example link that is not generic is for PowerShell. There are no explicit Linux or Bash examples, and the CLI is only mentioned after PowerShell. No Linux-specific tools or workflows are referenced.
Recommendations
- Ensure CLI (az CLI) examples and documentation links are presented alongside or before PowerShell, especially since az CLI is cross-platform and popular among Linux users.
- Add explicit Bash/Linux shell examples where automation or scripting is discussed.
- Include references to Linux-native tools or workflows where relevant, such as using Bash scripts with az CLI for automation.
- Balance the order of tool mentions (e.g., 'PowerShell or CLI' vs. 'CLI or PowerShell') to avoid implying a Windows-first approach.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/reservation-utilization.md
...gement-billing/reservations/reservation-utilization.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing PowerShell and Power BI as primary tools for interacting with reservation utilization data, without providing equivalent examples or explicit instructions for Linux users. There are no CLI (e.g., Azure CLI) or API usage examples, and no mention of Linux-native tools or workflows.
Recommendations
- Add explicit Azure CLI examples for viewing reservation utilization, including command-line instructions suitable for Linux/macOS users.
- Include REST API usage examples with curl or similar cross-platform tools.
- Clarify that Power BI is available on Windows only, and suggest alternative reporting tools or methods for Linux users (such as exporting data to CSV and using open-source BI tools).
- Ensure that any PowerShell instructions are accompanied by Azure CLI equivalents.
- Review all tool references to ensure Linux parity and avoid implying that only Windows tools are supported.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/view-purchase-refunds.md
...nagement-billing/reservations/view-purchase-refunds.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by focusing on the Azure portal (a web GUI), Power BI (a Windows-centric tool), and REST APIs, with no mention of Linux-native tools, CLI commands, or cross-platform scripting examples. Power BI is highlighted as the primary reporting tool, which is not natively available on Linux. There are no examples using Azure CLI, Bash, or other Linux-friendly methods, and Windows-oriented tools are mentioned before any platform-neutral alternatives.
Recommendations
- Add Azure CLI and Bash examples for viewing reservation transactions, including sample commands and expected outputs.
- Mention and provide examples for using cross-platform tools (e.g., Azure CLI, Python scripts) to access reservation data.
- Clarify that Power BI is not natively available on Linux and suggest alternatives, such as exporting data via API and analyzing it with open-source tools (e.g., Jupyter Notebook, pandas).
- Ensure that REST API usage is demonstrated with both Windows (e.g., PowerShell, curl for Windows) and Linux (e.g., curl, wget, jq) command-line examples.
- Reorder sections or provide parallel instructions so that Linux-friendly methods are presented alongside or before Windows-specific tools.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/understand-reserved-instance-usage.md
...ing/reservations/understand-reserved-instance-usage.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_heavy
missing_linux_example
Summary
The documentation page consistently uses Windows-based virtual machines (VMs) as the default example and discusses Windows software costs in detail, without providing equivalent Linux-based examples or mentioning Linux-specific considerations. There are no Linux VM scenarios, nor are there references to Linux software costs or Azure Hybrid Benefit for Linux. This creates a Windows-centric perspective and omits guidance for Linux users.
Recommendations
- Add parallel examples using Linux VMs (e.g., Standard_DS1_v2 running Ubuntu or Red Hat) alongside Windows examples.
- Discuss Linux-specific considerations, such as the absence of additional software charges for most Linux distributions.
- Mention Azure Hybrid Benefit as it applies to Linux (if relevant), or clarify that it is Windows-only.
- Ensure that tables and screenshots include both Windows and Linux VM reservation scenarios.
- Include a note or section addressing differences in reservation usage and billing for Linux VMs.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/view-reservations.md
...t-management-billing/reservations/view-reservations.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides detailed instructions for managing Azure reservations primarily through the Azure portal and Azure PowerShell. There are explicit references to PowerShell for access management, but there are no equivalent examples or guidance for Linux users (e.g., using Azure CLI or Bash). The only command-line tool mentioned is PowerShell, which is more closely associated with Windows environments, and there are no cross-platform command-line examples or alternatives.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell instructions, especially for granting and viewing RBAC access to reservations.
- Explicitly mention that Azure CLI is cross-platform and supported on Linux, macOS, and Windows.
- Where PowerShell is referenced, provide Bash/Azure CLI alternatives side-by-side or in tabs.
- Clarify that all portal-based instructions are OS-agnostic, and highlight any differences if they exist.
- Review related content and ensure that Linux users are not required to use PowerShell for any task that can be accomplished with Azure CLI.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/permission-view-manage.md
...agement-billing/savings-plan/permission-view-manage.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only Azure PowerShell script examples for managing savings plan permissions, with no mention of equivalent Azure CLI (cross-platform) or Bash examples. This creates a bias toward Windows/PowerShell users and may hinder Linux or macOS users who prefer or require CLI/Bash tools. The exclusive use of PowerShell and the absence of Azure CLI or REST API (curl) examples indicate a lack of Linux parity.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell scripts, using 'az role assignment' commands.
- Include Bash/curl examples for REST API operations where applicable.
- Explicitly state that the operations can be performed from any platform (Windows, Linux, macOS) and provide guidance for non-Windows users.
- Consider reordering sections or providing tabs to present PowerShell, Azure CLI, and REST API examples side-by-side.
- Mention that Azure PowerShell is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/scope-level/tutorial-azure-hybrid-benefits-sql.md
...ling/scope-level/tutorial-azure-hybrid-benefits-sql.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows-based SQL Server VM registration guides, omitting Linux equivalents. The only script/tool mentioned for usage analysis is a PowerShell script, with no mention of Bash, CLI, or Linux-native alternatives. All example links and instructions for registering SQL Server VMs point to Windows-specific documentation, and there is no guidance for Linux SQL Server VM scenarios.
Recommendations
- Include links and instructions for registering SQL Server VMs running on Linux, such as documentation for the SQL IaaS Agent Extension on Linux.
- Provide Linux/Bash/CLI examples for gathering license usage and availability details, alongside PowerShell examples.
- Mention Linux-compatible tools or scripts for analyzing Azure Hybrid Benefit usage, or clarify cross-platform compatibility of existing tools.
- Ensure that examples and walkthroughs explicitly address both Windows and Linux SQL Server VM scenarios, or note any limitations.
- Add a section or note clarifying Azure Hybrid Benefit support for SQL Server on Linux VMs, including any differences in management or registration.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/scope-level/sql-iaas-extension-registration.md
...billing/scope-level/sql-iaas-extension-registration.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a Windows bias by providing only Windows-centric examples and instructions. All command-line automation references use PowerShell scripts, and the main registration walkthrough links to a Windows-specific documentation page. There are no Linux-specific instructions, examples, or mentions of Linux tools (such as Bash, Azure CLI, or Linux VM management patterns). The documentation assumes users are operating in a Windows environment and does not address Linux VM scenarios or provide parity for Linux administrators.
Recommendations
- Add Linux-specific instructions for SQL IaaS Agent extension registration, including examples using Azure CLI and Bash.
- Include references and links to Linux documentation pages, such as managing SQL Server on Linux VMs.
- Provide sample scripts for Linux environments, and clarify any differences in the registration process for Linux VMs.
- Mention Linux VM management tools and patterns alongside Windows/PowerShell options, ensuring both are covered equally.
- Ensure that all steps and automation options are available for both Windows and Linux users, and highlight any platform-specific considerations.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/scope-level/transition-existing.md
...-management-billing/scope-level/transition-existing.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing PowerShell scripts for usage analysis and not providing equivalent examples for Linux users. All scripting and automation guidance is centered on PowerShell, with no mention of Bash, Azure CLI, or cross-platform tools. There are no Linux-specific instructions or examples, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux and macOS users, especially for tasks like analyzing SQL license usage.
- Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide installation guidance for non-Windows systems.
- Include sample commands and scripts for Linux environments, ensuring parity in automation and scripting guidance.
- Reference cross-platform tools and patterns (such as Azure CLI) alongside or before Windows-specific tools.
- Add notes or sections clarifying that all features and management experiences are available regardless of the user's operating system.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-billing/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables.md
...tomer-agreement-billing-issues-usage-file-pivot-tables.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively uses Microsoft Excel for all examples and screenshots, implicitly prioritizing a Windows-centric workflow. There are no examples or instructions for Linux users or for using open-source spreadsheet tools like LibreOffice Calc. Keyboard shortcuts and menu paths are specific to Excel, and no alternatives are provided for Linux environments.
Recommendations
- Add parallel examples and screenshots using LibreOffice Calc or another cross-platform spreadsheet tool.
- Include instructions for opening and manipulating CSV files on Linux, such as using Calc or command-line tools (e.g., csvkit, pandas).
- Mention that all steps can be performed on Linux or macOS with equivalent tools, and provide relevant shortcuts/menu paths.
- Consider providing a downloadable template or macro that works in both Excel and LibreOffice.
- Explicitly state that Excel is not required and list supported alternatives at the beginning of the article.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/review-enterprise-agreement-bill.md
...billing/understand/review-enterprise-agreement-bill.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias primarily through exclusive references to Microsoft Excel for handling CSV report formatting issues, with no mention of Linux or cross-platform alternatives. All step-by-step instructions for viewing and manipulating billing data are based on the Azure portal, which is web-based and cross-platform, but the only tooling guidance for CSV manipulation assumes use of Excel on Windows. There are no examples or instructions for Linux users (e.g., using LibreOffice, OpenOffice, or command-line tools like awk/csvkit), nor is there guidance for handling CSV files outside of the Microsoft ecosystem.
Recommendations
- Add instructions for opening and formatting CSV files using Linux-compatible tools such as LibreOffice Calc, OpenOffice Calc, or command-line utilities (awk, csvkit, pandas).
- Include examples of how to inspect and manipulate CSV files on Linux/macOS, such as using 'cat', 'head', 'awk', or 'csvtool'.
- Mention that the Azure portal is accessible from any modern browser on Windows, Linux, or macOS to reinforce cross-platform compatibility.
- Provide troubleshooting steps for CSV import issues in non-Windows environments, including how to set delimiters and data formats in LibreOffice or OpenOffice.
- Consider adding a note or section on cross-platform best practices for handling Azure billing data and reports.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/add-disk.md
...-docs/blob/main/articles/cyclecloud/how-to/add-disk.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows documentation links before or instead of Linux equivalents, especially in the section describing disk types for CycleCloud 8 and above. There are no explicit Linux or cross-platform command-line examples (e.g., Linux mount or format commands), and the links for disk types point to Windows-specific Azure docs. No PowerShell examples are present, but the lack of Linux CLI examples and the preference for Windows documentation indicate a bias.
Recommendations
- Replace or supplement Windows-specific documentation links with Linux equivalents, especially in the 'Disk types' section (e.g., link to /azure/virtual-machines/linux/disks-types).
- Provide Linux command-line examples for mounting and formatting disks (e.g., using 'lsblk', 'mkfs', 'mount').
- Ensure parity in documentation references and examples for both Windows and Linux users.
- Clarify any OS-specific behaviors or requirements for managed disks, and link to both Windows and Linux guides where relevant.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/cycleserver-configuration-reference.md
...cles/cyclecloud/cycleserver-configuration-reference.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation references both Linux and Windows in default values, but the overall structure and examples are minimal and do not provide Linux-specific usage patterns or command-line examples. The mention of the configuration file location is Linux-specific, but there are no equivalent details for Windows (e.g., file path, editing instructions). There are no examples of how to edit or manage the configuration file on either platform, but the lack of Linux command-line examples (such as using nano, vi, or systemctl) is notable. The documentation also lists Windows defaults after Linux in the table, but does not provide parity in operational guidance.
Recommendations
- Add explicit instructions and examples for editing the configuration file on both Linux (e.g., using nano or vi) and Windows (e.g., using Notepad or PowerShell).
- Include the default file path for the configuration file on Windows systems.
- Provide examples of how to restart the CycleServer service after configuration changes on both Linux (e.g., systemctl) and Windows (e.g., using the Services MMC or PowerShell).
- Ensure that any references to platform-specific defaults are accompanied by operational guidance for both platforms.
- Consider adding a section that summarizes platform differences and best practices for both Linux and Windows users.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/configure-open-ondemand.md
...cles/cyclecloud/how-to/ccws/configure-open-ondemand.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page focuses on configuring Open OnDemand with Azure CycleCloud, but it demonstrates Windows bias by referencing Microsoft Entra ID (a Microsoft-specific authentication provider), using terminology and patterns familiar to Windows/Azure users, and omitting any Linux-specific configuration steps or examples. There are no references to Linux authentication providers, command-line configuration, or alternative tools. The workflow is described entirely through the CycleCloud web portal, which is a GUI-centric approach typical of Windows environments.
Recommendations
- Include Linux-specific authentication options, such as configuring Open OnDemand with LDAP, Kerberos, or other open-source identity providers.
- Provide command-line examples for updating configuration files directly on the Open OnDemand VM (e.g., editing YAML or shell scripts), not just through the web portal.
- Mention and document equivalent Linux tools or workflows for managing clusters and authentication.
- Clarify whether the instructions apply to both Windows and Linux-based clusters, and provide parity in examples and screenshots.
- Add troubleshooting steps or notes relevant to Linux environments, such as SELinux, systemd, or file permissions.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/use-spot-instances.md
.../main/articles/cyclecloud/how-to/use-spot-instances.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_links
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently linking to Windows-specific Azure Spot VM documentation before Linux equivalents, referencing Windows documentation for core concepts (Spot VMs, pricing, eviction policy), and omitting Linux-specific configuration or usage examples. Linux links are only present in secondary contexts, and there are no Linux/Powershell command examples or explicit Linux tool references.
Recommendations
- Provide equal prominence to Linux documentation links (e.g., link to both /azure/virtual-machines/windows/spot-vms and /azure/virtual-machines/linux/spot-vms where relevant).
- Include Linux-specific examples or configuration snippets, especially if there are differences in how Spot VMs are managed or evicted on Linux VMs.
- Mention Linux tools or patterns for handling scheduled events and eviction notifications (e.g., systemd services, shell scripts) alongside any Windows/Powershell approaches.
- Ensure that references to Azure features (Spot pricing, eviction policy, scheduled events) include both Windows and Linux documentation, or use platform-neutral links when possible.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/connect-to-node.md
...lob/main/articles/cyclecloud/how-to/connect-to-node.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page provides connection instructions for both Linux and Windows nodes, but Windows-specific tools (RDP, Microsoft RDP client) and examples are mentioned explicitly and sometimes before Linux equivalents. There are detailed instructions for setting up RDP tunnels for Windows, but no equivalent examples for connecting to Linux graphical desktops (e.g., via X11 forwarding or VNC). The documentation references Microsoft RDP client for macOS and Windows, but does not mention Linux RDP clients or alternatives. Overall, the page assumes familiarity with Windows tools and workflows, and omits Linux-specific graphical connection patterns.
Recommendations
- Include examples for connecting to Linux graphical desktops, such as X11 forwarding (e.g., 'ssh -X') or VNC tunnels.
- Mention Linux-compatible RDP clients (e.g., 'remmina', 'xfreerdp') when discussing RDP connections.
- Provide parity in graphical connection instructions for both Linux and Windows nodes.
- When describing connection methods, present Linux and Windows options side-by-side, rather than focusing on Windows tools first.
- Clarify that SSH-based connections are standard for Linux nodes, and provide troubleshooting tips for common Linux SSH issues.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/cluster-templates.md
...b/main/articles/cyclecloud/how-to/cluster-templates.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by referencing Windows-specific Azure VM documentation (e.g., linking to /azure/virtual-machines/windows/spot-vms) and using Windows-centric machine types (Standard_D4v3, H16r) in examples. There are no explicit Linux or cross-platform command-line examples, nor are Linux-specific VM documentation or machine types referenced. The documentation does mention Ubuntu images in lookup tables, but the overall pattern is to present Windows-related concepts and tools first or exclusively.
Recommendations
- Include links to both Windows and Linux Azure VM documentation when discussing features like Spot VMs.
- Provide example machine types for Linux workloads (e.g., Standard_D2s_v3, Standard_B2ms) alongside Windows types.
- Add explicit Linux-centric examples or references (such as using Linux images, SSH keys, or Linux-specific configuration patterns) where applicable.
- Ensure that any referenced documentation or tooling is cross-platform or that Linux alternatives are mentioned with equal prominence.
- Clarify that CycleCloud supports both Windows and Linux clusters, and provide guidance for each where differences exist.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/healthcheck.md
...cs/blob/main/articles/cyclecloud/how-to/healthcheck.md
High Priority
View Details â
Detected Bias Types
missing_windows_example
linux_first
linux_tools
Summary
The documentation provides detailed Linux-centric examples and paths (e.g., Bash scripts, Linux file paths), while Windows-specific instructions, examples, or PowerShell equivalents are missing. Linux is consistently mentioned first, and only Linux scripting (Bash) is demonstrated. Windows support is referenced in passing, but without concrete examples or guidance.
Recommendations
- Add equivalent Windows/PowerShell HealthCheck script examples, including file paths and script placement instructions.
- Provide step-by-step instructions for creating and deploying HealthCheck scripts on Windows VMs.
- Clarify any differences in script support or behavior between Linux and Windows, and ensure both platforms are equally represented in examples and guidance.
- Include screenshots or command-line examples for Windows where GUI or CLI actions are shown for Linux.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/install-cyclecloud-cli.md
...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides installation instructions for both Linux and Windows, but there is a noticeable Windows bias. Windows prerequisites and installation steps are described in detail, including references to Windows Explorer, PowerShell scripts, and GUI actions (right-click, Extract All), while Linux instructions use standard shell commands. The Windows section mentions specific tools (PowerShell, Command Prompt) and GUI patterns before their Linux equivalents. The prerequisites section explicitly calls out the need to install Python for Windows, while assuming Linux/Mac users already have Python. The CLI initialization and usage instructions are platform-neutral.
Recommendations
- Provide equivalent Linux instructions for extracting the zip file using GUI tools (e.g., GNOME Files, KDE Dolphin) for parity with Windows Explorer steps.
- Mention Linux shell alternatives to PowerShell for script execution, and clarify how to run install.sh with different shells if needed.
- Include Mac-specific installation steps if supported, or clarify platform support.
- Balance the prerequisites section by linking to Python installation guides for Linux and Mac, not just Windows.
- Ensure that command-line examples are presented for both platforms in parallel, and avoid assuming Windows users prefer GUI actions while Linux users prefer CLI.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/mount-disk.md
...ocs/blob/main/articles/cyclecloud/how-to/mount-disk.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a mild Windows bias. Device assignment is described using Azure Logical Unit Numbers (LUN) and references a PowerShell module link, which is a Windows-centric tool. No Linux-specific device assignment examples (such as using /dev/sdX or udev rules) are provided. The mention of Azure portal navigation and resource blades is also more familiar to Windows users. While the configuration examples use Linux-style mountpoints and filesystems, there is no explicit parity for Linux device management or command-line tooling.
Recommendations
- Add Linux-specific device assignment examples (e.g., referencing /dev/sdX, using udev, or lsblk).
- Include links to Azure CLI documentation alongside PowerShell references.
- Provide explicit Linux command-line examples for mounting, formatting, and managing volumes.
- Clarify that the configuration applies to both Windows and Linux nodes, and highlight any differences.
- Mention Linux tools (e.g., parted, mkfs, cryptsetup) where appropriate.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation shows mild Windows bias by listing Windows paths and behaviors before Linux equivalents, referencing Windows-specific features and limitations, and omitting Linux-specific command examples or details in some sections. While Linux is supported and mentioned, Windows is often presented first or with more detail.
Recommendations
- Alternate the order of Windows and Linux references so that Linux is presented first in some sections.
- Provide Linux-specific command examples where behaviors differ (e.g., for HealthCheck options, run_on_shutdown).
- Include more details about Linux init scripts, service management, and integration points, similar to the detail given for Windows.
- Clarify any Linux-specific behaviors or limitations, not just Windows-specific ones.
- Ensure parity in documentation for both platforms, including troubleshooting steps, environment variables, and file locations.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/user-authentication.md
...main/articles/cyclecloud/how-to/user-authentication.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric authentication methods (Active Directory) and examples (e.g., DOMAIN\user), mentioning Windows tools and patterns (Active Directory, Entra ID) before Linux equivalents, and omitting Linux-specific authentication examples or guidance (such as integration with OpenLDAP, sssd, or PAM). There are no Linux command-line examples or references to Linux-native tools for authentication management.
Recommendations
- Add Linux-focused authentication examples, such as integrating with OpenLDAP or using sssd for LDAP/AD authentication.
- Provide Linux command-line examples for managing authentication settings, such as using curl or CLI tools to configure CycleCloud.
- Include Linux username formats and authentication patterns (e.g., uid/gid, user@domain, or POSIX account examples) alongside or before Windows examples.
- Mention Linux-native tools and workflows for user management and authentication, not just GUI-based or Windows-centric approaches.
- Ensure parity in troubleshooting steps, such as how to reset authentication or recover access from a Linux environment.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily biased toward Windows environments. It exclusively references Windows Server technologies, Active Directory, and Windows-specific tools (such as PowerShell scripts and Windows Scheduled Tasks). There are no Linux examples or equivalents, and Linux compute nodes are explicitly not supported. All configuration and operational guidance assumes a Windows-centric workflow.
Recommendations
- Add explicit statements about Linux support plans and timelines, if any.
- Provide Linux-based examples or clarify that Linux is not currently supported.
- If possible, develop and document Linux-compatible tools or workflows for cluster management.
- Mention Linux alternatives (e.g., cloud-init, Linux-based schedulers) where relevant, even if not supported, to guide cross-platform users.
- Ensure that any future updates include parity for Linux environments, including CLI tools and automation scripts.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/apply-dataops.md
...-docs/blob/main/articles/data-factory/apply-dataops.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Examples and recommendations for CI/CD, automated testing, and deployment frequently reference PowerShell, Visual Studio, and .NET (NUnit), with no mention of Linux alternatives or cross-platform tools. The use of Azure DevOps and GitHub is described, but the examples and external references (e.g., automated testing) focus on Windows environments and tools, omitting Linux command-line equivalents or open-source alternatives. There are no Bash, Linux shell, or cross-platform scripting examples, and PowerShell is mentioned as a primary automation tool.
Recommendations
- Include Linux/Bash shell examples for CI/CD and deployment tasks alongside PowerShell examples.
- Mention and provide examples for running automated tests using cross-platform frameworks (e.g., pytest for Python, or JavaScript test runners) in addition to NUnit/Visual Studio.
- Reference Azure CLI usage from Linux/macOS terminals, not just PowerShell, for pipeline management and deployment.
- Highlight cross-platform editors (e.g., VS Code) and workflows, and clarify that Azure Data Factory and its tools can be used from Linux environments.
- Add explicit notes or sections on how to perform key tasks (deployment, testing, artifact management) from Linux systems, including sample scripts.
- Balance tool recommendations by listing both Windows and Linux-friendly options for automation and scripting.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/author-global-parameters.md
...main/articles/data-factory/author-global-parameters.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation references PowerShell as the deployment method for global parameters in CI/CD, without mentioning or providing equivalent examples for Linux or cross-platform tools (e.g., Azure CLI, Bash). Windows tooling is implicitly favored, and there are no Linux-specific instructions or parity examples.
Recommendations
- Add equivalent deployment instructions using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Provide Bash script examples for deploying global parameters via ARM templates.
- Explicitly mention that PowerShell is one option and link to cross-platform alternatives.
- Clarify that ARM template deployment can be performed from any OS, and provide steps for Linux users.
- Ensure screenshots and UI instructions do not assume a Windows environment.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-package-store.md
...actory/azure-ssis-integration-runtime-package-store.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows environments. All examples and instructions assume the use of Windows-only tools such as SQL Server Management Studio (SSMS), dtutil, and Windows command-line utilities (cmdkey, net use, batch scripts). There are no examples or guidance for performing equivalent tasks on Linux or macOS, nor is there any mention of cross-platform alternatives. The documentation also introduces Windows tools and patterns first and exclusively, with no Linux parity.
Recommendations
- Provide equivalent instructions and examples for Linux environments, including how to interact with Azure-SSIS IR using cross-platform tools or Azure CLI.
- Mention and demonstrate how to use Azure Data Factory portal or REST APIs for package management tasks as an alternative to SSMS.
- If dtutil is required, clarify whether it can be run via Wine or in a container on Linux, or suggest alternative methods for Linux users.
- Include notes or sections explicitly stating the platform limitations and suggest workarounds for non-Windows users.
- Where possible, use cross-platform scripting languages (e.g., Python, PowerShell Core) or Azure CLI for automation examples.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/built-in-preinstalled-components-ssis-integration-runtime.md
...lt-in-preinstalled-components-ssis-integration-runtime.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily Windows-centric: it specifies Windows Server 2019 as the only OS, lists only Windows-based drivers and providers, and all built-in/preinstalled components are for Windows SSIS. There is no mention of Linux support, Linux equivalents, or cross-platform alternatives. No examples, tools, or instructions for Linux environments are provided.
Recommendations
- Explicitly state whether Linux is supported or not for Azure-SSIS IR, and if not, provide guidance or alternatives for Linux users.
- If Linux support is planned or available, add equivalent lists for Linux-based components, drivers, and connection managers.
- Provide examples or documentation for deploying SSIS workloads in Linux containers or using cross-platform ETL tools.
- Reference open-source or cross-platform alternatives where possible, and clarify any Windows-only limitations.
- Consider adding a comparison table showing feature parity (or gaps) between Windows and Linux environments for Azure Data Factory.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-linked-services.md
...main/articles/data-factory/concepts-linked-services.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as the only command-line scripting example and referencing it before other cross-platform or Linux-native tools. There are no explicit Linux shell (Bash/CLI) examples or references, and the quickstart/tutorial links prioritize .NET and PowerShell (both Windows-centric) before REST API or portal options. No Linux-specific tools, patterns, or examples are provided.
Recommendations
- Add examples and quickstart links for Azure CLI (which is cross-platform and commonly used on Linux) alongside or before PowerShell.
- Include Bash shell script examples for creating linked services, especially using the Azure CLI.
- Ensure that REST API and portal-based instructions are presented before or alongside Windows-centric tools like PowerShell.
- Explicitly mention Linux and macOS compatibility in tool/SDK lists and provide parity in walkthroughs.
- Where PowerShell is referenced, also provide equivalent Azure CLI or Bash commands.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-datasets-linked-services.md
...cles/data-factory/concepts-datasets-linked-services.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by listing PowerShell as a primary tool for creating datasets, referencing PowerShell-based quickstarts and guides, and omitting Linux-specific tools or CLI examples. There are no Bash, Azure CLI, or cross-platform scripting examples, and PowerShell is mentioned before REST API or portal options. This may make Linux users feel unsupported or require extra effort to adapt instructions.
Recommendations
- Add Azure CLI examples for creating datasets, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash shell script examples where appropriate, especially for tasks currently shown only with PowerShell.
- Reorder tool and quickstart lists to present cross-platform or OS-neutral options (e.g., REST API, Azure CLI, portal) before Windows-specific tools like PowerShell.
- Explicitly mention that PowerShell examples are Windows-centric and provide equivalent Linux commands or scripts.
- Add a section or links for Linux/macOS users, highlighting supported tools and any differences in workflow.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based configuration examples and scripts, with no equivalent examples for Linux environments (e.g., Bash, Azure CLI). It references Windows-centric tools and patterns, such as PowerShell and Windows authentication methods, without mentioning or prioritizing cross-platform alternatives. There is no guidance for users operating from Linux or macOS environments.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for all PowerShell scripts to support Linux and macOS users.
- Explicitly mention that configuration can be performed from non-Windows platforms and provide links or references to relevant cross-platform tools.
- Add a section or callout discussing cross-platform support and any platform-specific considerations.
- Where authentication is discussed, clarify options for both Windows (SQL authentication) and cross-platform (Azure AD/Entra ID) scenarios.
- Ensure that any references to tools or commands (e.g., PowerShell) are accompanied by their cross-platform equivalents.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-amazon-redshift.md
...ain/articles/data-factory/connector-amazon-redshift.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by referencing only Windows-supported versions for the Self-hosted Integration Runtime, not mentioning Linux support or providing Linux installation/configuration instructions. All examples and prerequisites assume a Windows environment, and there are no Linux-specific examples or parity guidance. The documentation also refers to Windows support before any mention of cross-platform or Linux compatibility.
Recommendations
- Explicitly state whether the Self-hosted Integration Runtime supports Linux, and if so, provide installation and configuration instructions for Linux environments.
- Add Linux-specific examples or notes where relevant, such as how to configure network access, run the integration runtime, or handle permissions on Linux.
- If Linux is not supported, clearly mention this limitation early in the documentation.
- Ensure that any references to supported operating systems (such as in the prerequisites) mention both Windows and Linux (if applicable), or clarify the scope.
- Provide troubleshooting tips or links for Linux users, if supported.
- Review and update language to avoid Windows-first phrasing, and ensure parity in tool and workflow descriptions.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-search.md
...b/main/articles/data-factory/connector-azure-search.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows by exclusively using Azure Portal UI screenshots and workflows, which are primarily Windows-centric. There are no examples or instructions for performing the same tasks using cross-platform tools (such as Azure CLI, REST API, or ARM templates), nor is there mention of Linux-specific workflows or command-line alternatives. The documentation assumes use of the Azure Portal, which is more familiar to Windows users, and does not provide parity for Linux users who may prefer scripting or non-GUI approaches.
Recommendations
- Add examples for creating and configuring linked services, datasets, and copy activities using Azure CLI, PowerShell (with clear cross-platform notes), and REST API.
- Include sample scripts or commands that can be run on Linux/macOS terminals, not just through the Azure Portal UI.
- Mention and link to documentation for ARM/Bicep templates for users who prefer infrastructure-as-code approaches.
- Clearly indicate which steps are platform-agnostic and which are specific to the Azure Portal, and provide alternatives where possible.
- Ensure that any screenshots or UI walkthroughs are supplemented with equivalent command-line or code-based examples.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-table-storage.md
...articles/data-factory/connector-azure-table-storage.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by providing only PowerShell commands for generating a Shared Access Signature (SAS) token, with no equivalent examples for Linux (e.g., Azure CLI, Bash, or cross-platform tools). Windows/PowerShell tooling is mentioned exclusively for a key authentication step, and no Linux or cross-platform alternatives are referenced or prioritized. This may hinder Linux users or those working in cross-platform environments.
Recommendations
- Add equivalent Azure CLI examples for generating SAS tokens, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and provide usage examples.
- When referencing command-line tools, present cross-platform options first or in parallel with Windows-specific tools.
- Review the documentation for other areas where only Windows/PowerShell tools are mentioned and ensure Linux parity.
- Consider including a note or section on how to perform key tasks (like SAS generation) on Linux/macOS environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-microsoft-access.md
...in/articles/data-factory/connector-microsoft-access.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Microsoft Access ODBC driver (which is only available on Windows), providing example connection strings with Windows file paths (e.g., C:\mydatabase.accdb), and omitting any mention of Linux or cross-platform alternatives. There are no instructions or examples for Linux users, nor is there guidance on running the Integration Runtime or accessing Access databases from non-Windows platforms.
Recommendations
- Explicitly state that the Microsoft Access ODBC driver is only available on Windows and clarify platform limitations.
- Provide guidance or alternatives for Linux users, such as using third-party ODBC drivers (if any exist) or containerized Windows environments.
- Include example connection strings and file paths for both Windows and Linux (if supported), or clearly indicate if Linux is not supported.
- Add a section discussing cross-platform considerations and any workarounds for non-Windows environments.
- If Linux is not supported, suggest alternative approaches for Linux users, such as converting Access databases to supported formats.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-hive.md
...docs/blob/main/articles/data-factory/connector-hive.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows support and tools first and exclusively, such as only mentioning Windows versions for the self-hosted integration runtime and not providing Linux equivalents or examples. There are no Linux-specific instructions, examples, or troubleshooting steps, and the documentation does not clarify Linux compatibility for the self-hosted integration runtime or connector usage.
Recommendations
- Explicitly state Linux support and provide a list of supported Linux distributions for the self-hosted integration runtime, if applicable.
- Add Linux-specific installation and configuration instructions for the self-hosted integration runtime, including any prerequisites or differences from Windows.
- Include Linux-based examples or screenshots where relevant, or clarify if the UI/process is identical.
- Mention any limitations or known issues when using Linux as the host OS for integration runtime.
- Ensure that references to Windows tools or patterns are balanced with Linux equivalents, or clarify if features are Windows-only.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-http.md
...docs/blob/main/articles/data-factory/connector-http.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page exhibits Windows bias in several ways. Windows authentication is listed as a built-in option alongside Basic, Digest, and ClientCertificate, with no mention of Linux equivalents (such as Kerberos or NTLM via Linux tools). The only tool explicitly recommended for testing HTTP requests is PowerShell's Invoke-RestMethod, with no mention of Linux-native tools like curl or wget. Instructions for certificate management and permissions are entirely based on Windows tools (MMC, cert store, DIAHostService), with no guidance for Linux certificate stores or service accounts. These patterns prioritize Windows tooling and workflows, and omit Linux alternatives.
Recommendations
- Include Linux-native tools (e.g., curl, wget) alongside PowerShell for HTTP request testing.
- Add guidance for managing certificates and permissions on Linux self-hosted integration runtime hosts, such as using OpenSSL and Linux certificate stores.
- Clarify authentication options for Linux hosts, including how to use Basic, Digest, or client certificates in a Linux environment.
- Where Windows-specific instructions are given (e.g., MMC, DIAHostService), provide Linux equivalents or note platform differences.
- Explicitly state platform support and limitations for authentication types (e.g., Windows authentication only available on Windows hosts).
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-postgresql.md
...lob/main/articles/data-factory/connector-postgresql.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias in several areas. The only explicit instructions for configuring SSL certificates for ODBC connections reference Windows-specific paths (e.g., C:\Windows\ServiceProfiles\DIAHostService\AppData\Roaming\postgresql\root.crt) and tools, with no mention of Linux equivalents. There are no examples or guidance for Linux-based Self-hosted Integration Runtime (SHIR) deployments, and the documentation implicitly assumes a Windows environment for advanced configuration steps. Additionally, Windows is mentioned first and exclusively in relevant sections.
Recommendations
- Provide equivalent instructions and file paths for configuring SSL certificates on Linux-based SHIR hosts (e.g., /var/opt/ or /home/ directories).
- Explicitly state support for Linux-based SHIR and include examples or notes for Linux users wherever Windows-specific instructions are given.
- Avoid referencing only Windows tools or paths; when necessary, present Linux and Windows instructions side by side.
- Audit the documentation for other implicit Windows assumptions and ensure Linux parity in all advanced configuration and troubleshooting sections.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-netezza.md
...s/blob/main/articles/data-factory/connector-netezza.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by referencing Windows versions as supported platforms for the self-hosted integration runtime, omitting explicit mention of Linux support or instructions. There are no Linux-specific examples or guidance for installing the Netezza ODBC driver or running the integration runtime on Linux, and all platform-specific references are to Windows. Additionally, the only linked reference for prerequisites points to a page about Windows requirements, and there are no Linux or cross-platform command-line examples (e.g., Bash, shell scripts) or troubleshooting notes.
Recommendations
- Explicitly state whether the self-hosted integration runtime and Netezza ODBC driver are supported on Linux, and if so, provide installation instructions for Linux (e.g., Ubuntu, CentOS).
- Add Linux-specific examples for installing the IBM Netezza ODBC driver, including package dependencies and environment variable configuration.
- If the integration runtime is Windows-only, clarify this early in the prerequisites section to set expectations for Linux users.
- Wherever platform-specific instructions are given (such as for driver installation), provide both Windows and Linux variants, or link to official cross-platform guides.
- Include troubleshooting tips or common issues for Linux environments if supported.
- Review referenced prerequisite articles to ensure Linux parity or add Linux sections where missing.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-odata.md
...ocs/blob/main/articles/data-factory/connector-odata.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation displays a Windows bias primarily through the exclusive mention and example of Windows authentication (including domain\user syntax) and the lack of Linux-specific authentication examples or discussion. Windows authentication is listed as a main supported authentication type, and an example is provided, but there is no mention of Linux-integrated authentication methods (such as Kerberos on Linux) or how to configure equivalent authentication from non-Windows environments. Additionally, the use of Windows-centric tools and patterns (e.g., domain\user) is present, and Linux alternatives are not discussed.
Recommendations
- Add examples and guidance for configuring OData authentication from Linux environments, including how to use Kerberos or other common Linux authentication mechanisms if supported.
- Clarify whether Windows authentication is supported only from Windows-based integration runtimes, and if so, explicitly state this limitation.
- Provide parity by including Linux/Unix authentication scenarios or explicitly stating their (un)support.
- If only Windows authentication is supported, suggest alternative authentication methods (e.g., Basic, OAuth, API Key) for Linux users, and provide examples.
- Review and update the documentation to avoid Windows-centric language and patterns where possible, or provide equivalent Linux instructions.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-hana.md
.../blob/main/articles/data-factory/connector-sap-hana.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias in several ways: it only references the SAP HANA ODBC driver for Windows in the prerequisites, does not mention or provide instructions for Linux-based Integration Runtime hosts, and all authentication and setup examples are Windows-centric (e.g., Windows authentication, user@domain.com). There are no Linux-specific examples or guidance, and Windows tools and terminology are presented exclusively and/or first.
Recommendations
- Add instructions and download links for SAP HANA ODBC drivers for Linux, and clarify that Self-hosted Integration Runtime can be installed on Linux (if supported).
- Provide Linux-specific examples for setting up the ODBC driver, including environment variables, installation commands, and configuration file locations.
- Include authentication examples relevant to Linux environments (e.g., basic authentication, Kerberos if supported), and clarify any differences.
- Avoid using 'Windows authentication' as the only advanced authentication example; mention alternatives or note platform limitations.
- When referencing the SAP HANA client, specify both Windows and Linux options, and provide parity in setup steps.
- Explicitly state platform support and any limitations for both Windows and Linux in the prerequisites section.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-switch-activity.md
.../articles/data-factory/control-flow-switch-activity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell and reference Windows file paths (e.g., C:\ADF). There are no equivalent instructions or examples for Linux or cross-platform CLI tools (such as Azure CLI or Bash). The tutorial and walkthrough links also focus on Azure PowerShell, reinforcing the Windows-centric approach.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, including pipeline creation, linked service setup, dataset creation, and pipeline execution.
- Include Linux/macOS file path examples (e.g., /home/user/ADF) alongside Windows paths.
- Explicitly mention cross-platform compatibility and provide instructions for running the workflow on Linux/macOS.
- Link to tutorials or quickstarts that use Azure CLI or REST API, not just PowerShell.
- Add a note clarifying that the steps can be performed on non-Windows platforms, and highlight any platform-specific considerations.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-square.md
...cs/blob/main/articles/data-factory/connector-square.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a Windows bias by referencing Windows support and prerequisites for the Square connector, specifically in the context of the self-hosted integration runtime. There is no mention of Linux support, Linux prerequisites, or examples for Linux-based self-hosted integration runtime deployments. All instructions and compatibility statements focus on Windows, and there are no Linux-specific tools, commands, or screenshots provided.
Recommendations
- Explicitly state whether Linux-based self-hosted integration runtime is supported for the Square connector. If supported, provide Linux-specific prerequisites and instructions.
- Include examples or references for deploying and configuring the self-hosted integration runtime on Linux, alongside the existing Windows information.
- If Linux is not supported, clearly mention this limitation to avoid confusion.
- Ensure that any references to operating system requirements are presented in a cross-platform manner, or provide parallel guidance for both Windows and Linux environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sybase.md
...cs/blob/main/articles/data-factory/connector-sybase.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by mentioning Windows authentication as a primary supported method, referencing Windows-specific data providers, and omitting any discussion of Linux equivalents or examples. There are no instructions or examples for installing the Sybase provider on Linux, nor any mention of Linux authentication or integration runtime setup. The documentation implicitly assumes a Windows environment for self-hosted integration runtime and Sybase connectivity.
Recommendations
- Add explicit instructions and examples for installing the Sybase data provider on Linux-based integration runtime hosts.
- Discuss Linux authentication options, such as Kerberos or other supported mechanisms, if available.
- Provide parity in examples by including Linux command-line or configuration steps alongside Windows-focused instructions.
- Clarify whether the self-hosted integration runtime and Sybase connector are supported on Linux, and if so, document any platform-specific requirements or limitations.
- Mention any differences in setup or troubleshooting for Linux environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-teradata.md
.../blob/main/articles/data-factory/connector-teradata.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: it references Windows-specific dependencies (such as .NET Data Provider and Visual C++ Redistributable), authentication types prioritize 'Windows' alongside 'Basic' and 'LDAP', and examples for authentication and driver installation are Windows-centric. There are no explicit Linux equivalents, instructions, or examples for installing dependencies or configuring the integration runtime on Linux systems. The documentation does not mention Linux support or provide parity for Linux-based self-hosted integration runtime scenarios.
Recommendations
- Add explicit instructions and examples for installing required Teradata drivers and dependencies on Linux systems, including supported distributions.
- Clarify whether the self-hosted integration runtime and Teradata connector are supported on Linux, and provide guidance if so.
- Include Linux authentication scenarios (e.g., Kerberos, LDAP on Linux) and configuration examples.
- Avoid using 'Windows authentication' as a default or primary example; instead, present 'Basic' or 'LDAP' first, and clearly indicate platform-specific options.
- Mention Linux equivalents for required system libraries (e.g., .NET Core/Mono, relevant C++ libraries) and provide installation commands.
- Add troubleshooting tips for Linux environments, if supported.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-blob-storage.md
...a-factory/connector-troubleshoot-azure-blob-storage.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation shows Windows bias by referencing Windows-specific tools (e.g., diawp.exe.config) and policies (FIPS mode on Windows VMs) without mentioning Linux equivalents or providing guidance for Linux users. There are no Linux-specific troubleshooting steps or examples, and the only OS-specific advice is for Windows, which is presented first and exclusively.
Recommendations
- Add troubleshooting steps for Linux environments, such as how to handle FIPS-related issues on Linux-based self-hosted integration runtimes.
- Include Linux-specific file paths and configuration examples alongside Windows ones (e.g., where to find and edit configuration files on Linux).
- Explicitly state whether certain errors or solutions are Windows-only, and provide Linux alternatives if available.
- Ensure parity in examples and recommendations by including both Windows and Linux scenarios where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sap.md
...in/articles/data-factory/connector-troubleshoot-sap.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell (Windows-specific) example for network troubleshooting (Test-NetConnection), with no equivalent Linux or cross-platform commands. This suggests a bias toward Windows environments and tools, potentially excluding Linux users.
Recommendations
- Add equivalent Linux troubleshooting commands, such as using 'nc', 'telnet', or 'curl' to test connectivity to the SAP server.
- Present both Windows and Linux examples side by side to ensure parity.
- Explicitly mention that the troubleshooting steps apply to both Windows and Linux integration runtime hosts, if applicable.
- Consider referencing cross-platform tools or commands where possible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-hive.md
...n/articles/data-factory/connector-troubleshoot-hive.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides troubleshooting steps that reference Windows-specific paths (e.g., C:\Program Files\MIT\Kerberos\bin) and environment variable configuration, without mentioning Linux equivalents. There are no Linux-specific instructions or examples, and the guidance implicitly assumes a Windows environment.
Recommendations
- Include Linux-specific paths for the krb5.conf file (e.g., /etc/krb5.conf) and describe where to find or place Kerberos configuration files on Linux systems.
- Provide instructions for setting environment variables (KRB5_CONFIG, KRB5CCNAME) on Linux (e.g., using export in bash) alongside the Windows system variable method.
- Mention how to restart relevant services or processes on Linux, not just 'restart the VM and SHIR from the machine'.
- Wherever file paths or commands are given, present both Windows and Linux versions in parallel for parity.
- Explicitly state that the instructions apply to both Windows and Linux, and clarify any platform-specific differences.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-rest.md
...n/articles/data-factory/connector-troubleshoot-rest.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing 'Command Prompt' as the default terminal for running curl, and by recommending Fiddler (a Windows-centric tool) for SSL troubleshooting. There are no explicit Linux or macOS examples, nor are alternative Linux tools mentioned. The guidance assumes a Windows environment and omits parity for Linux users.
Recommendations
- Provide explicit Linux (and optionally macOS) examples for running curl, e.g., 'open a terminal on Linux/macOS'.
- Mention cross-platform alternatives to Fiddler, such as mitmproxy or Wireshark, for SSL troubleshooting.
- Avoid assuming the use of 'Command Prompt'; instead, use neutral language like 'open a terminal window'.
- Where possible, add notes about any platform-specific differences in curl usage or troubleshooting steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sharepoint-online-list.md
...ctory/connector-troubleshoot-sharepoint-online-list.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively recommending the SharePoint Online Management Shell (a Windows-only tool) and providing only PowerShell command examples for troubleshooting. There are no equivalent instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives. The troubleshooting steps assume the reader is using Windows, omitting guidance for non-Windows environments.
Recommendations
- Provide equivalent troubleshooting steps using cross-platform tools, such as Azure CLI or PowerShell Core, which are available on Linux and macOS.
- Include examples for Linux and macOS users, specifying any prerequisites or differences in authentication and command syntax.
- Mention and link to cross-platform alternatives where Windows-only tools are referenced.
- Clearly state platform requirements and offer guidance for users who do not have access to Windows environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-upgrade-guidance.md
...in/articles/data-factory/connector-upgrade-guidance.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only PowerShell script examples for programmatically finding impacted objects, with no mention of Linux-compatible alternatives such as Azure CLI, Bash, or Python scripts. This creates a bias toward Windows users and tools, potentially excluding Linux or cross-platform users from easily following the guidance.
Recommendations
- Add equivalent examples using Azure CLI and/or Bash scripts for Linux and cross-platform users.
- Mention that PowerShell Core is available on Linux, if the provided scripts are compatible, and provide instructions for installing and running PowerShell on Linux.
- Provide Python script examples, as Python is widely used and cross-platform.
- Explicitly state that the guidance applies to all platforms, and ensure that tool recommendations are inclusive of both Windows and Linux environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-xero.md
...docs/blob/main/articles/data-factory/connector-xero.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing 'Windows versions' as a prerequisite for the self-hosted integration runtime, without mentioning Linux support or alternatives. There are no Linux-specific instructions, examples, or clarifications about cross-platform compatibility for the integration runtime. The only command-line example given (for generating a private key) uses 'openssl', which is cross-platform, but the context does not clarify Linux support. The documentation does not provide parity for Linux users in terms of setup, troubleshooting, or platform-specific considerations.
Recommendations
- Explicitly state whether the self-hosted integration runtime is supported on Linux, and if so, provide installation and configuration instructions for Linux alongside Windows.
- If only Windows is supported, clearly mention this limitation early in the documentation.
- Provide Linux-specific examples or notes where relevant (e.g., for openssl commands, file paths, environment variables).
- Include troubleshooting tips or known issues for Linux environments if supported.
- Ensure that references to 'Windows versions' are balanced with equivalent Linux information or a clear statement of platform support.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-web-table.md
...blob/main/articles/data-factory/connector-web-table.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a bias towards Windows by exclusively recommending Microsoft Excel (and Power Query/Power BI) for extracting the index of a table from an HTML page. No Linux or cross-platform alternatives are mentioned, and all step-by-step instructions and screenshots are for Windows tools. There are no examples or guidance for users on Linux or macOS platforms.
Recommendations
- Add instructions for extracting table indexes using cross-platform or Linux tools, such as Python scripts (e.g., using BeautifulSoup or pandas), command-line utilities (e.g., curl + pup/xq), or browser developer tools.
- Include at least one example using a Linux or macOS environment to demonstrate parity.
- Mention open-source, platform-independent alternatives before or alongside Windows-specific tools.
- Clarify that the current method using Excel is only one option and not a requirement, and encourage community contributions for other platforms.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-vertica.md
...s/blob/main/articles/data-factory/connector-vertica.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias, particularly in the 'Install Vertica ODBC driver' section, where only Windows installation steps and screenshots are provided. There are no instructions or examples for installing the ODBC driver on Linux or macOS, nor are cross-platform considerations mentioned. The use of Windows-specific tools (e.g., ODBC Data Source Administrator) is referenced without Linux equivalents.
Recommendations
- Add installation instructions and screenshots for the Vertica ODBC driver on Linux (and macOS, if supported), including common distributions (e.g., Ubuntu, RHEL).
- Mention and provide examples for Linux tools and commands (e.g., using 'odbcinst' or editing odbc.ini/odbcinst.ini files) alongside Windows tools.
- Clearly indicate platform-specific steps and provide parity in documentation structure and detail.
- Where screenshots are used, provide alternatives or notes for Linux users.
- Explicitly state supported platforms for the self-hosted integration runtime and Vertica ODBC driver, and link to relevant platform-specific resources.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-until-activity.md
...n/articles/data-factory/control-flow-until-activity.md
High Priority
View Details â
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 are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There are no examples or instructions for Linux or cross-platform CLI tools such as Azure CLI, Bash, or Python SDK. The only automation walkthrough is for Azure PowerShell, and the page does not mention or link to Linux/macOS alternatives. The 'devx-track-azurepowershell' custom tag further reinforces the Windows/PowerShell focus.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, including pipeline deployment and monitoring.
- Provide Bash shell script examples for Linux/macOS users, using platform-agnostic file paths and commands.
- Mention and link to cross-platform tools (e.g., Azure CLI, REST API, Python SDK) in the introductory and example sections.
- Use neutral file paths (e.g., ./ADF/) or show both Windows and Linux path formats in examples.
- Include a note clarifying that all features are available on Linux/macOS and how to use them outside of PowerShell.
- Balance PowerShell and CLI examples, or provide tabs/switchers for users to select their preferred platform.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-automate-azure-pipelines.md
...ntinuous-integration-delivery-automate-azure-pipelines.md
High Priority
View Details â
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 instructions, referencing Windows-centric tools and workflows (such as .ps1 scripts and Azure PowerShell modules), and omitting equivalent Linux/bash examples. There is no mention of cross-platform alternatives or guidance for users operating in Linux environments, and Windows/PowerShell approaches are presented as the default or only option.
Recommendations
- Provide equivalent bash or Azure CLI examples for all PowerShell scripts and tasks, especially for stopping and starting triggers.
- Explicitly mention that Azure Pipelines agents can run on Linux and MacOS, and provide instructions for those platforms.
- Reference cross-platform tools (e.g., Azure CLI) alongside PowerShell, and clarify when a task or script is Windows-specific.
- Add notes or sections for Linux users, including how to install necessary modules and run deployment scripts.
- Ensure that all code samples and automation steps have Linux-compatible alternatives, and test them for parity.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-sample-script.md
...ctory/continuous-integration-delivery-sample-script.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses Azure PowerShell for all examples and instructions, with no mention of Bash, Azure CLI, or Linux shell scripting alternatives. All code samples, parameters, and YAML pipeline tasks are PowerShell-centric, and there is no guidance for users on Linux or macOS environments. The documentation assumes familiarity with Windows/PowerShell tools and patterns, which may hinder Linux users.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for pre- and post-deployment tasks.
- Include instructions for installing and configuring Azure CLI on Linux/macOS.
- Show YAML pipeline tasks using the AzureCLI@2 task and Bash scripts, in addition to AzurePowerShell.
- Explicitly mention cross-platform compatibility and note any differences or limitations.
- Add a section or notes for users running pipelines on Linux agents, including script compatibility considerations.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-linked-templates.md
...ry/continuous-integration-delivery-linked-templates.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools (such as VSTS, now Azure DevOps, which is historically Windows-focused), and omitting explicit Linux or cross-platform alternatives. There are no examples or instructions for Linux users, such as using Azure CLI, Bash, or cross-platform deployment scripts. The guidance assumes familiarity with Windows workflows and does not mention Linux-specific considerations or tooling.
Recommendations
- Add explicit examples for Linux environments, such as using Azure CLI or Bash scripts for uploading templates and managing SAS tokens.
- Mention cross-platform tools (e.g., Azure DevOps Pipelines, GitHub Actions) and provide parity in instructions for both Windows and Linux users.
- Include references to Linux-compatible storage upload methods (e.g., az storage blob upload) and how to generate SAS tokens using CLI.
- Clarify that the process is platform-agnostic where possible, and highlight any platform-specific steps or caveats.
- Provide sample scripts for both PowerShell and Bash to cover pre- and post-deployment tasks.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery.md
...ticles/data-factory/continuous-integration-delivery.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively recommending PowerShell scripts for pre- and post-deployment tasks, referencing only PowerShell Core and not mentioning Bash or other Linux-compatible scripting alternatives. There are no Linux shell or cross-platform script examples, and the guidance assumes the use of Windows-centric tools and patterns, such as PowerShell modules, without providing Linux equivalents or parity.
Recommendations
- Provide equivalent Bash or shell script examples for pre- and post-deployment tasks, or explicitly mention how to adapt the PowerShell scripts for Linux environments.
- Clarify that PowerShell Core is cross-platform, but also offer native Linux shell alternatives for users who prefer Bash or other scripting languages.
- Mention and document how to run deployment automation from Linux-based agents in Azure Pipelines, including any prerequisites or differences.
- List both Windows and Linux approaches side-by-side where scripts or automation are required, ensuring Linux users are not left out.
- Review all referenced scripts and tools for Windows-specific dependencies and provide guidance or alternatives for Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-if-condition-activity.md
...les/data-factory/control-flow-if-condition-activity.md
High Priority
View Details â
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 commands and referencing Windows file paths (e.g., C:\ADF). There are no examples or instructions for Linux or cross-platform CLI tools such as Azure CLI, Bash, or Cloud Shell. The only automation walkthrough is for Azure PowerShell, and no Linux or macOS equivalents are mentioned or linked.
Recommendations
- Add equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
- Provide Bash shell command examples for running pipelines, uploading JSON files, and monitoring pipeline runs.
- Use platform-neutral file paths in examples (e.g., ./ADF or ~/ADF) or show both Windows and Linux/macOS path formats.
- Explicitly mention that the PowerShell example is for Windows users and provide links or sections for Linux/macOS users.
- Include a note or section on how to perform the same operations in the Azure Portal or with REST API calls, which are platform-independent.
- Ensure that all step-by-step walkthroughs have parity for both PowerShell and Azure CLI users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-wait-activity.md
...in/articles/data-factory/control-flow-wait-activity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides only PowerShell-based examples and walkthroughs for running pipelines, with no mention of Linux or cross-platform alternatives (such as Azure CLI, Bash, or REST API). The only step-by-step tutorial referenced is for Azure PowerShell, which is primarily associated with Windows environments. There are no Linux-specific or cross-platform command-line examples, nor is there guidance for users on non-Windows systems.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Include Bash shell command examples for pipeline execution, or reference REST API usage for platform-agnostic automation.
- When referencing tutorials, provide links to both PowerShell and Azure CLI (or REST API) guides, and mention their cross-platform compatibility.
- Explicitly state that the Wait activity and pipeline execution can be managed from any OS, and provide parity in documentation for Linux/macOS users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-web-activity.md
...ain/articles/data-factory/control-flow-web-activity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides a PowerShell snippet for base64-encoding a PFX certificate but does not offer equivalent Linux/macOS commands (e.g., using OpenSSL or base64). No Linux tools or shell examples are mentioned, and the only code for certificate conversion/encoding is Windows-specific. This may hinder users on non-Windows platforms.
Recommendations
- Add equivalent Linux/macOS shell commands for base64-encoding a PFX file (e.g., using 'base64' or 'openssl').
- Explicitly mention that certificate conversion and encoding can be performed on any OS, and provide cross-platform guidance.
- Wherever PowerShell is used, provide a Bash or POSIX shell alternative.
- Review other sections for implicit Windows-first assumptions and ensure parity in tool and example coverage.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-activity-overview.md
...b/main/articles/data-factory/copy-activity-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its choice of examples and tutorials. The only explicit platform-specific example is 'Copy data from a SQL Server database to Azure (tutorial-hybrid-copy-powershell.md)', which uses PowerShell, a Windows-centric tool. There are no Linux or cross-platform command-line examples, and no mention of Linux-specific tools or workflows. The documentation does not provide parity in Linux or bash scripting examples, nor does it reference Linux file systems or tools in its scenarios.
Recommendations
- Add Linux/bash-based examples for hybrid and on-premises scenarios, such as using bash scripts or Azure CLI on Linux.
- Include references to Linux file systems and workflows in the scenarios and examples, especially when discussing on-premises data movement.
- Provide parity in tutorials and quickstarts by including at least one that uses Linux-native tools or environments.
- When mentioning PowerShell or Windows tools, also mention their Linux equivalents (e.g., Azure CLI, bash) and provide links or code samples.
- Review connector documentation to ensure Linux and cross-platform usage is equally represented and accessible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-activity-performance-features.md
...les/data-factory/copy-activity-performance-features.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias, particularly in the 'Staged copy' section, where firewall configuration examples reference only the Windows firewall and do not mention Linux or cross-platform equivalents. No Linux-specific examples or tools are provided, and the only OS-specific mention is Windows. There are no PowerShell or CLI examples, but the absence of Linux references and the exclusive mention of Windows tools/patterns indicates a Windows-first perspective.
Recommendations
- When discussing firewall configuration, include Linux firewall equivalents (e.g., iptables, firewalld, ufw) alongside Windows firewall instructions.
- Explicitly state that the guidance applies to both Windows and Linux self-hosted integration runtime nodes, and provide links to relevant Linux documentation where appropriate.
- If referencing OS-specific requirements (such as opening ports), provide instructions or references for both Windows and Linux environments.
- Consider adding a note or section on deploying and optimizing the self-hosted integration runtime on Linux, since it is supported.
- Review the documentation for other implicit Windows assumptions and ensure parity in examples, terminology, and guidance for Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-integration-runtime.md
...icles/data-factory/create-azure-integration-runtime.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides a PowerShell-only example for creating an Azure Integration Runtime, which is a Windows-centric tool. There are no examples using cross-platform tools like Azure CLI, Bash, or REST API, nor is there mention of Linux/macOS workflows. This creates a bias towards Windows users and may hinder Linux or macOS users from following the instructions easily.
Recommendations
- Add equivalent Azure CLI examples for creating and managing Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include REST API or ARM template examples for users who prefer declarative or programmatic approaches, which are OS-agnostic.
- Explicitly mention that PowerShell examples are primarily for Windows, and provide guidance or links for Linux/macOS users.
- Consider reordering or balancing the documentation so that cross-platform methods (CLI/REST) are presented before or alongside PowerShell.
- Add a table or section summarizing all available methods (PowerShell, CLI, REST, Portal) with links to detailed instructions for each.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation primarily references Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, with no mention of Linux-compatible alternatives or cross-platform methods. There are no Linux-specific instructions or examples, and the tools mentioned are traditionally Windows-only. Additionally, the related content highlights Azure PowerShell before other provisioning methods, reinforcing a Windows-first perspective.
Recommendations
- Include information about cross-platform or Linux-compatible tools (if available) for deploying and running SSIS packages.
- Explicitly state the platform requirements and limitations for the mentioned tools (e.g., SSDT, SSMS, dtutil, AzureDTExec), and suggest alternatives or workarounds for Linux users.
- Provide Linux command-line examples or guidance for users who may be working in non-Windows environments.
- Balance the order of related content to avoid prioritizing Windows-specific tools (e.g., list ARM template or CLI methods before or alongside PowerShell).
- If no Linux support exists, clearly document this limitation and link to feature requests or roadmap items for Linux parity.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-resource-manager-template.md
...ure-ssis-integration-runtime-resource-manager-template.md
High Priority
View Details â
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 commands for deploying and managing Azure-SSIS integration runtimes. No examples are given for Linux or cross-platform tools such as Azure CLI, and Windows-specific tools and patterns (PowerShell cmdlets) are mentioned first and exclusively. There is no mention of how to perform these tasks on Linux or macOS, nor are alternative command-line interfaces or automation approaches suggested.
Recommendations
- Add equivalent Azure CLI examples for deploying and managing Azure-SSIS IR, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention that PowerShell examples are Windows-centric and provide guidance for users on other platforms.
- Include links or references to documentation for using REST API or ARM templates via Azure CLI or other cross-platform tools.
- Where possible, provide bash script examples or instructions for Linux users.
- Review related content and ensure Linux/cross-platform parity in referenced articles.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime.md
.../data-factory/create-azure-ssis-integration-runtime.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) for deploying and managing Azure-SSIS IR, without mentioning Linux or cross-platform alternatives. PowerShell is the only command-line example referenced, and there are no Linux-native instructions or examples. The order of presentation also places Windows tools and patterns before any mention of platform-agnostic or Linux-compatible options.
Recommendations
- Include examples using Azure CLI, which is cross-platform, for provisioning and managing Azure-SSIS IR.
- Mention and provide guidance for using Data Factory REST APIs, which are platform-agnostic.
- Clarify whether any of the deployment tools (e.g., dtutil, AzureDTExec) are available or supported on Linux, and if not, suggest alternatives or workarounds.
- Add explicit Linux/macOS instructions or notes where only Windows tools are referenced (e.g., for firewall rule configuration, database connection, or package deployment).
- Reorder tool mentions to highlight cross-platform or web-based options (e.g., Azure portal, Azure CLI, REST API) before Windows-specific tools.
- Where PowerShell is referenced, also provide equivalent Azure CLI commands.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-shared-self-hosted-integration-runtime-powershell.md
...eate-shared-self-hosted-integration-runtime-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell-based examples and instructions, explicitly referencing Windows tools (such as Windows PowerShell ISE), and linking to PowerShell installation instructions for Windows. There are no equivalent examples or instructions for Linux or macOS users (e.g., Bash, Azure CLI, or cross-platform PowerShell Core). The UI instructions are platform-agnostic, but all command-line automation is Windows-centric.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Clarify that PowerShell Core (pwsh) can be used on Linux/macOS, and provide installation instructions for non-Windows platforms.
- Replace references to 'Windows PowerShell ISE' with more general or cross-platform editors, or note that scripts can be run in any terminal.
- Explicitly mention and provide guidance for Linux/macOS users, including any platform-specific prerequisites or differences.
- Include sample scripts or commands for Bash or other common Linux shells where appropriate.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-service-identity.md
...articles/data-factory/data-factory-service-identity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits a Windows bias by providing PowerShell-based examples for generating and retrieving managed identities, with no equivalent examples for Linux-native tools (e.g., Azure CLI, Bash). PowerShell is mentioned first and most frequently for command-line operations, and there are no references to Linux or cross-platform command-line usage. The documentation assumes the use of Windows tools and patterns, potentially excluding Linux users or those who prefer Azure CLI.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations (e.g., generating and retrieving managed identities).
- When listing ways to perform tasks (e.g., 'using PowerShell, REST API, ARM template, SDK'), mention Azure CLI and Bash scripts, and do not always list PowerShell first.
- Include explicit notes or sections for Linux/macOS users, clarifying that Azure CLI is cross-platform and providing relevant commands.
- Where possible, provide Bash script snippets or generic REST API curl examples to ensure parity for non-Windows environments.
- Review the documentation for other places where only Windows-centric tools are referenced and add Linux-friendly alternatives.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-ux-troubleshoot-guide.md
...les/data-factory/data-factory-ux-troubleshoot-guide.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (e.g., Command Prompt and nslookup) for troubleshooting network issues, without providing equivalent instructions for Linux or macOS users. All command-line examples assume a Windows environment, and there are no examples or guidance for users on other operating systems. Browser instructions are cross-platform (Edge and Chrome), but the troubleshooting steps for network issues are Windows-centric.
Recommendations
- Add Linux and macOS equivalents for command-line troubleshooting steps, such as using the Terminal and the 'dig' or 'nslookup' commands.
- When referencing 'Command Prompt', clarify that Linux/macOS users should use their respective terminal applications.
- Provide example outputs for Linux/macOS commands alongside Windows examples.
- Explicitly state that the troubleshooting steps apply to all platforms, and note any platform-specific differences.
- Consider including a table or tabbed sections for Windows, Linux, and macOS users when describing command-line troubleshooting.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-flow-script.md
...cs/blob/main/articles/data-factory/data-flow-script.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets as the primary or sole method for programmatically interacting with Data Flow Script outside the UI. There are no examples or mentions of Linux/Unix command-line tools, shell scripting, or cross-platform alternatives. The instructions and workflow descriptions assume a Windows-centric environment, omitting Linux equivalents or guidance.
Recommendations
- Add examples and instructions for using Data Flow Script with Linux/macOS environments, such as using Azure CLI, Bash scripts, or REST API via curl.
- When referencing PowerShell, also mention cross-platform PowerShell Core (pwsh) and/or provide Bash equivalents.
- Avoid assuming the use of Windows tools as the default; present cross-platform or OS-neutral approaches first, or at least in parallel.
- Explicitly state that Data Flow Script can be used from any platform via REST API, and provide code snippets for both Windows (PowerShell) and Linux/macOS (Bash/curl).
- Review all tool and workflow mentions to ensure Linux users are not excluded and have clear, actionable guidance.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-hdfs-azure-storage.md
...-factory/data-migration-guidance-hdfs-azure-storage.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively recommending installation of the Data Factory self-hosted integration runtime on Windows machines or Windows VMs, with no mention of Linux support or examples. Windows is presented as the default or only platform for hosting the integration runtime, and pricing estimates are based on Azure Windows VMs. There are no Linux-specific instructions, examples, or parity in tooling recommendations.
Recommendations
- Explicitly mention and document support for installing the self-hosted integration runtime on Linux machines, if supported.
- Provide Linux-based examples and instructions alongside Windows instructions, including VM sizing and scaling recommendations for common Linux distributions.
- Include pricing estimates for both Windows and Linux VM scenarios.
- Clarify any platform-specific limitations or differences in performance, monitoring, or management between Windows and Linux hosts.
- Ensure that all references to 'Windows machine' or 'Windows VM' are accompanied by Linux alternatives where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-s3-azure-storage.md
...ta-factory/data-migration-guidance-s3-azure-storage.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias in its guidance for deploying self-hosted Integration Runtime (IR) on Azure VMs. It exclusively references Windows VMs for self-hosted IR installation, does not mention Linux support, and provides configuration recommendations only for Windows-based environments. No Linux equivalents or examples are given.
Recommendations
- Explicitly state whether self-hosted Integration Runtime can be installed on Linux VMs. If supported, provide parallel instructions and recommendations for Linux deployments.
- Include Linux-based VM sizing and configuration guidance alongside Windows examples.
- If self-hosted IR is Windows-only, clarify this limitation early in the documentation and suggest alternative approaches for Linux-preferred environments.
- Add Linux command-line or automation examples where relevant, ensuring parity with any Windows/PowerShell instructions.
- Review and update diagrams and architecture sections to reflect both Windows and Linux deployment options where possible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/deploy-linked-arm-templates-with-vsts.md
.../data-factory/deploy-linked-arm-templates-with-vsts.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by primarily referencing the Azure portal (a GUI tool often associated with Windows users) for all steps, without mentioning or providing examples for command-line alternatives like Azure CLI or PowerShell scripts. While Azure CLI is briefly mentioned in the overview, no actual CLI or cross-platform command examples are given. There are no Linux-specific instructions or screenshots, and all workflows assume use of the Azure portal and Azure DevOps GUI, which are more familiar to Windows users.
Recommendations
- Provide equivalent step-by-step instructions using Azure CLI commands for all major tasks (e.g., creating a storage account, generating SAS tokens, creating containers, managing Key Vault secrets).
- Include PowerShell and Azure CLI script examples alongside or in place of GUI instructions, making it clear these can be run on Linux, macOS, or Windows.
- Add screenshots or terminal output from Linux environments where appropriate.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and link to relevant cross-platform tool documentation.
- Consider reordering sections so that cross-platform (CLI/scripted) approaches are presented before or alongside portal-based (GUI) instructions.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-aad-authentication-azure-ssis-ir.md
...ata-factory/enable-aad-authentication-azure-ssis-ir.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a strong Windows bias by exclusively providing PowerShell commands for scripting, referencing only Windows-based tools like SQL Server Management Studio (SSMS), and omitting any Linux or cross-platform alternatives. All automation and CLI examples use PowerShell, and there are no Bash, Azure CLI, or cross-platform instructions. The workflow assumes the use of Windows tools and patterns throughout.
Recommendations
- Provide equivalent Azure CLI (az) or Bash examples for all PowerShell commands, especially for group and managed identity management.
- Mention and demonstrate cross-platform tools such as Azure Data Studio for database access and T-SQL execution, in addition to SSMS.
- Clearly indicate which steps require Windows-only tools and offer alternatives for Linux/macOS users where possible.
- Reorder sections or provide parallel instructions so that Linux/cross-platform options are presented alongside or before Windows-specific ones.
- Add a note about platform compatibility for all tools and scripts referenced.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/format-orc.md
...ure-docs/blob/main/articles/data-factory/format-orc.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias in the 'Self-hosted Integration Runtime' section. It describes Java runtime detection by first checking the Windows registry, references the installation of Microsoft Visual C++ Redistributable (a Windows-only dependency), and provides no explicit Linux installation or configuration examples. There are no Linux-specific instructions or troubleshooting steps, and the only environment variable example (_JAVA_OPTIONS) is shown in a Windows context.
Recommendations
- Add explicit instructions for installing and configuring the required Java runtime and dependencies on Linux-based Self-hosted IR machines, including package manager commands (e.g., apt, yum) and file paths.
- Document how the Self-hosted IR locates the Java runtime on Linux (e.g., reliance on JAVA_HOME or standard Linux paths) and clarify any differences from Windows.
- If Visual C++ Redistributable is not required on Linux, state this clearly; if an equivalent dependency is needed, provide Linux installation instructions.
- Provide Linux shell command examples for setting environment variables (e.g., export _JAVA_OPTIONS='-Xms256m -Xmx16g') alongside the Windows examples.
- Include troubleshooting steps and screenshots relevant to Linux environments where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/format-parquet.md
...docs/blob/main/articles/data-factory/format-parquet.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways. When describing how the Self-hosted Integration Runtime locates the Java runtime, it first references the Windows registry and provides explicit examples and download links for Windows JDK installations. The environment variable examples use Windows-style paths (e.g., C:\Program Files\Java\jdk-23), and there are no Linux-specific instructions, examples, or download links. There is no mention of Linux equivalents for registry lookup, environment variable configuration, or file paths, and no Linux screenshots or shell commands are provided.
Recommendations
- Add explicit instructions and examples for Linux environments, including setting JAVA_HOME and PATH variables using Linux shell syntax (e.g., export JAVA_HOME=/usr/lib/jvm/java-23-openjdk).
- Include download links and installation steps for JDK/OpenJDK on Linux, referencing popular distributions (e.g., Ubuntu, CentOS).
- Clarify how the Self-hosted Integration Runtime locates the Java runtime on Linux (e.g., only via JAVA_HOME, as registry does not exist).
- Provide Linux-specific troubleshooting steps for JVM heap size configuration (e.g., editing /etc/environment or using export in shell).
- Use cross-platform file path examples, or provide both Windows and Linux variants side-by-side.
- Add screenshots or command-line examples from Linux environments where relevant.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-create-tumbling-window-trigger.md
.../data-factory/how-to-create-tumbling-window-trigger.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways. The PowerShell example is presented first and in detail, with explicit references to Windows paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json) and instructions to install Azure PowerShell 'on Windows.' There are no explicit Linux/macOS shell examples (such as Bash), and the CLI section does not clarify cross-platform usage or address Linux-specific considerations. The documentation assumes a Windows environment for file paths and tool installation, and does not mention or show parity for Linux users.
Recommendations
- Add explicit Bash/Linux shell examples for creating and managing triggers using the Azure CLI, including sample commands for common Linux distributions.
- When referencing file paths, provide both Windows (e.g., C:\path) and Linux/macOS (e.g., ~/path or /home/user/path) equivalents.
- Clarify in prerequisites that Azure PowerShell and Azure CLI are cross-platform, and provide installation links and instructions for Linux/macOS users.
- Present CLI (which is cross-platform) examples before or alongside PowerShell examples to avoid the impression of Windows-first bias.
- Where screenshots or UI instructions are given, note any platform-specific differences or confirm that the experience is the same across OSes.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-azure-ssis-ir-enterprise-edition.md
...y/how-to-configure-azure-ssis-ir-enterprise-edition.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based instructions for provisioning, referencing Windows authentication for SSAS connectivity, and omitting any Linux or cross-platform alternatives. All setup and configuration steps assume the use of Windows tools and patterns, with no mention of Bash, Azure CLI, or Linux environments.
Recommendations
- Add equivalent Azure CLI (cross-platform) instructions and examples for provisioning the Azure-SSIS IR Enterprise Edition.
- Explicitly state platform requirements and clarify if any features are Windows-only, or provide Linux/macOS alternatives where possible.
- Include Bash or shell script examples alongside PowerShell to support Linux users.
- Reference cross-platform authentication options (such as service principals or managed identities) in addition to Windows Authentication.
- Review and update related content to ensure Linux parity and avoid exclusive reliance on Windows tools.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-develop-azure-ssis-ir-licensed-components.md
...ry/how-to-develop-azure-ssis-ir-licensed-components.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows-specific tools (Registry, environment variables, GAC), file paths, and setup executables. There are no Linux examples or instructions, and all technical steps assume a Windows OS. The use of Windows Registry keys, Windows environment variables, and Windows file paths is pervasive, and there is no mention of Linux equivalents or cross-platform considerations.
Recommendations
- Add explicit statements clarifying OS support and limitations (e.g., if Azure-SSIS IR only runs on Windows, state this up front).
- If Linux support is possible or planned, provide parallel instructions for Linux environments, including environment variable access, file system paths, and component installation.
- Where possible, use OS-agnostic terminology or provide both Windows and Linux examples for environment variable access, file storage, and registry/configuration management.
- Clarify whether custom components or ISV setups can be developed or installed on Linux, and provide guidance for cross-platform development.
- If the use of Windows-specific features (Registry, GAC, etc.) is required, explain why and suggest alternatives or workarounds for non-Windows environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-managed-instance-agent.md
...y/how-to-invoke-ssis-package-managed-instance-agent.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively references Windows-based tools and workflows, specifically SQL Server Management Studio (SSMS) and Windows authentication, without mentioning or providing alternatives for Linux users. All examples and UI walkthroughs assume the use of SSMS, which is only available on Windows. There are no command-line or cross-platform alternatives provided, and Windows-centric patterns (e.g., UNC paths, Windows authentication) are used throughout.
Recommendations
- Provide guidance for Linux and macOS users, such as using Azure Data Studio (if supported) or relevant cross-platform tools.
- Include command-line examples (e.g., using sqlcmd, Azure CLI, or PowerShell Core on Linux) for creating and managing agent jobs.
- Clarify whether any of the described workflows can be performed via the Azure Portal or REST APIs, and provide examples.
- Explicitly state the platform requirements and limitations at the beginning of the article.
- If SSMS is required and only available on Windows, suggest alternatives or workarounds for non-Windows users, or link to relevant resources.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-migrate-ssis-job-ssms.md
.../articles/data-factory/how-to-migrate-ssis-job-ssms.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, and the SQL Server Agent, which is also Windows-centric. All migration steps and screenshots are based on SSMS, with no mention of Linux-compatible tools, command-line alternatives, or cross-platform approaches. There are no examples or guidance for users on Linux or macOS platforms, nor is Azure Data Studio (which is cross-platform) discussed as an alternative.
Recommendations
- Provide guidance or alternatives for Linux and macOS users, such as using Azure Data Studio (if supported) or relevant command-line tools (e.g., sqlcmd, Azure CLI, PowerShell Core).
- Explicitly state the Windows-only nature of the SSMS-based migration wizard and suggest any cross-platform migration strategies if available.
- Include examples or references for performing similar migrations using cross-platform tools or APIs, if possible.
- If no Linux alternative exists, add a note to clarify this and point users to feature requests or roadmap items for Linux support.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell, with explicit references to Windows file paths (e.g., C:\ADF\RunSSISPackage) and no mention of Linux or cross-platform alternatives such as Azure CLI, Bash, or automation via REST API. The use of PowerShell is assumed throughout, and there are no examples or instructions for running these steps on Linux or macOS. Windows-centric tooling and patterns are presented exclusively and before any alternatives.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, demonstrating cross-platform usage.
- Replace or supplement Windows file paths (e.g., C:\ADF\RunSSISPackage) with Linux/macOS-friendly paths (e.g., ~/ADF/RunSSISPackage) and note cross-platform differences.
- Explicitly mention that Azure Data Factory and SSIS can be managed from Linux/macOS environments and provide instructions for doing so.
- Include Bash or shell script examples for file creation and command execution.
- Reference REST API options for automation, which are platform-agnostic.
- Add a section or callout highlighting cross-platform support and any limitations.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-sqldb-to-cosmosdb.md
...main/articles/data-factory/how-to-sqldb-to-cosmosdb.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows by referencing the Adventure Works sample database with a link to SQL Server Management Studio (SSMS), a Windows-only tool, and by not providing any Linux-specific instructions or examples. There are no mentions of Linux-compatible tools (such as Azure Data Studio or sqlcmd), nor are there any command-line examples or guidance for users on Linux or macOS. The documentation assumes the use of Windows-based tools and patterns throughout.
Recommendations
- Include instructions or links for installing and accessing the Adventure Works sample database using cross-platform tools such as Azure Data Studio or sqlcmd.
- Provide examples or notes for users on Linux and macOS, especially for any steps that reference SSMS or other Windows-only tools.
- Explicitly mention that Azure Data Factory and Azure Cosmos DB are accessible from any OS via the Azure Portal, and clarify that no step requires a Windows-only environment.
- Wherever possible, use tool-agnostic language and provide parity in screenshots or command-line examples for Linux/macOS users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-create-install-integration-runtime.md
...des/data-factory-create-install-integration-runtime.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides PowerShell commands and instructions for Windows environments. All installation and configuration steps reference Windows tools (e.g., 'Add or Remove Programs', Windows installer, GUI setup wizards), and there is no mention of Linux or cross-platform alternatives. No Linux shell or CLI examples are provided, and the download link is for a Windows-only installer.
Recommendations
- Provide equivalent instructions and examples for Linux environments, including bash/CLI commands where possible.
- Clarify up front if the self-hosted integration runtime is only supported on Windows, or provide links to Linux support if available.
- If Linux is supported, include installation steps for Linux (e.g., using .tar.gz packages, systemd services, etc.).
- Mention Linux tools and patterns (such as package managers or command-line uninstall methods) alongside Windows tools.
- Ensure that all code examples are available in both PowerShell and bash (or other relevant shells) where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-prerequisites.md
...tory/includes/data-factory-quickstart-prerequisites.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits Windows bias by referencing Windows-specific tools and patterns (e.g., Notepad, C:\ paths), omitting Linux/macOS equivalents for file creation and storage paths, and not providing cross-platform instructions for tasks such as editing files or navigating the filesystem. All examples and instructions assume a Windows environment, with no mention of Linux or macOS alternatives.
Recommendations
- Provide Linux/macOS equivalents for file creation (e.g., using nano, vim, or TextEdit instead of Notepad).
- Use platform-agnostic or parallel file path examples (e.g., C:\ADFv2QuickStartPSH for Windows, ~/ADFv2QuickStart for Linux/macOS).
- Explicitly mention that the Azure portal steps are cross-platform, but clarify any OS-specific steps.
- Include notes or callouts for Linux/macOS users where instructions differ (e.g., uploading files from different local paths).
- Avoid assuming the use of Windows-only tools or patterns unless necessary, and always provide alternatives.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-verify-output-cleanup.md
...ludes/data-factory-quickstart-verify-output-cleanup.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only PowerShell commands for resource cleanup, which are primarily used on Windows. There are no examples for Linux users, such as Azure CLI or Bash equivalents. This creates a bias towards Windows users and tools.
Recommendations
- Add equivalent Azure CLI commands for deleting resource groups and data factories, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Explicitly mention that PowerShell commands can be run on any platform with PowerShell Core, or provide guidance for installing PowerShell on Linux/macOS.
- Reorder or parallelize examples so that both PowerShell and Azure CLI/Bash commands are shown together, ensuring parity for Linux users.
- Include a note or section addressing cross-platform usage, clarifying that the steps can be performed on any OS with the appropriate tools.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-v2-connector-get-started.md
...tory/includes/data-factory-v2-connector-get-started.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page lists Azure PowerShell as a primary tool for performing copy activities, which is a Windows-centric technology. There is no mention of Linux-specific command-line tools (such as Azure CLI), and the order of tools places PowerShell before more cross-platform options. The examples and tool references lean towards Windows environments, with no explicit Linux examples or parity.
Recommendations
- Include Azure CLI as a recommended tool, as it is cross-platform and widely used on Linux.
- Provide explicit examples or links for Linux users, such as bash scripts or CLI commands.
- Reorder the list to avoid implicit prioritization of Windows tools; group cross-platform tools together.
- Add notes or sections clarifying tool availability and usage on Linux/macOS platforms.
- Ensure parity in documentation by providing both PowerShell and CLI examples where applicable.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tenant-management-emergency-access-account.md
...tory-b2c/tenant-management-emergency-access-account.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides only Azure Portal (web UI) instructions and does not reference any command-line tools or scripts. However, where command-line or automation might be expected (e.g., PowerShell, CLI), there are no examples for either Windows or Linux. The only implicit bias is that, in Azure documentation, PowerShell or Windows tools are often mentioned first or exclusively, but here, no CLI tools are mentioned at all. There is a slight 'windows_first' bias in the language (e.g., 'Sign in to the Azure portal' is a common pattern in Microsoft docs, and there is no mention of Azure CLI or cross-platform automation). There are no Linux-specific instructions or parity suggestions.
Recommendations
- Add Azure CLI examples for creating emergency access accounts, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- If PowerShell automation is relevant, provide equivalent Bash or Azure CLI scripts.
- Explicitly mention that the Azure Portal is web-based and accessible from any OS, to clarify cross-platform compatibility.
- Include a section or note on how to perform these tasks using automation tools suitable for Linux environments.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/enable-api-analysis-linting.md
...ain/articles/api-center/enable-api-analysis-linting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but consistently presents Bash (Linux/macOS) examples first, followed by PowerShell (Windows) syntax. However, there is a notable emphasis on Visual Studio Code (VS Code) with Azure Functions extension for deployment, which is cross-platform but more commonly associated with Windows workflows. The documentation does not provide any Linux-specific tools or workflows outside of Bash CLI usage, and all portal-based instructions are platform-agnostic. There are no exclusive Windows-only tools or patterns, but PowerShell syntax is always included, indicating a slight bias toward Windows users.
Recommendations
- Ensure that all command-line examples are tested and work in both Bash (Linux/macOS) and PowerShell (Windows) environments.
- Explicitly mention that Visual Studio Code and the Azure Functions extension are available and supported on Linux and macOS, not just Windows.
- Where possible, include references to alternative Linux-native editors (such as Vim or Emacs) for users who may not use VS Code.
- Clarify that all Azure CLI commands can be run in native Linux terminals without requiring PowerShell.
- Consider adding a short section or note highlighting any Linux-specific considerations or troubleshooting tips.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/enable-api-center-portal-vs-code-extension.md
...i-center/enable-api-center-portal-vs-code-extension.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently references Visual Studio Code and its extension ecosystem, which is cross-platform, but all keyboard shortcuts and UI instructions use Windows conventions (e.g., Ctrl+Shift+P) without mentioning Linux or macOS equivalents. There are no explicit Linux/macOS-specific instructions, troubleshooting steps, or examples, and no mention of platform-specific differences. This subtly prioritizes Windows users and may confuse or inconvenience Linux/macOS users.
Recommendations
- Include keyboard shortcut equivalents for Linux (e.g., Ctrl+Shift+P is the same, but Cmd+Shift+P for macOS) and mention them explicitly.
- Add notes or sections clarifying that all instructions apply equally to Linux and macOS, or call out any platform-specific differences if they exist.
- If screenshots are provided, consider including at least one from a Linux or macOS environment, or note that the UI may look slightly different.
- Explicitly state that the Visual Studio Code extension and all features described are supported on Linux, macOS, and Windows.
- In troubleshooting, mention any platform-specific issues or links to platform-specific VS Code documentation.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/import-api-management-apis.md
...main/articles/api-center/import-api-management-apis.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both bash and PowerShell examples for Azure CLI commands, but PowerShell examples are consistently presented immediately after bash, with explicit formatting for PowerShell. There is a note clarifying differences in variable syntax between bash and PowerShell, but no mention of other Linux shells or environments. The documentation does not show exclusive use of Windows tools, but the prominence and parity given to PowerShell may suggest a slight Windows-first bias.
Recommendations
- Explicitly mention that bash examples work on Linux, macOS, and Windows (via WSL or native bash).
- Include a brief note about running Azure CLI in native Linux/macOS terminals, not just bash or PowerShell.
- Consider providing examples for other common shells (e.g., zsh, fish) or clarify that bash syntax is broadly applicable.
- Ensure that Linux/macOS users are addressed in prerequisites and environment setup sections.
- Review and balance the order of examples so that Linux-first or cross-platform parity is maintained, rather than consistently listing PowerShell second.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/configure-managed-identity-apim-reader.md
...ter/includes/configure-managed-identity-apim-reader.md
Medium Priority
View Details â
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 labeled as 'Formatted for PowerShell' and always appear immediately after the Bash examples. There is no explicit mention of Linux or macOS, and the PowerShell examples may suggest a Windows-first approach. However, both platforms are technically covered. No Linux-specific tools or shell patterns are discussed, and the portal instructions are platform-agnostic.
Recommendations
- Explicitly mention that the Bash examples are suitable for Linux and macOS users, and the PowerShell examples are for Windows users.
- Consider using tabbed code blocks labeled 'Bash (Linux/macOS)' and 'PowerShell (Windows)' for greater clarity.
- Ensure that any platform-specific prerequisites (e.g., installing Azure CLI on Linux) are referenced or linked.
- If possible, provide a short note at the start of the CLI section explaining which example to use based on the user's operating system.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/configure-managed-identity-kv-secret-user.md
.../includes/configure-managed-identity-kv-secret-user.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell versions are labeled as 'Formatted for PowerShell' and appear immediately after the Bash examples. There is a slight Windows bias in that PowerShell (a Windows-centric shell) is given parity with Bash, and the variable assignment syntax in PowerShell is shown for every step. However, Linux-specific considerations (such as shell differences or troubleshooting) are not discussed, and the examples do not mention alternative Linux tools or workflows beyond Bash.
Recommendations
- Clarify which examples are for Bash (Linux/macOS) and which are for PowerShell (Windows), possibly using tabs or clearer headings.
- Ensure that Linux/Bash examples are presented first, or at least equally, to avoid implicit prioritization of Windows/PowerShell.
- Add troubleshooting notes or tips for common issues on Linux (e.g., permissions, environment differences).
- Mention that Bash examples work on macOS as well as Linux, and clarify any platform-specific caveats.
- Consider including a note about using WSL (Windows Subsystem for Linux) for users on Windows who prefer Bash.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/vscode-extension-basic-prerequisites.md
...enter/includes/vscode-extension-basic-prerequisites.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page exclusively references Visual Studio Code and its Azure API Center extension, both of which are cross-platform, but does not mention or provide examples for Linux-specific tools, editors, or workflows. There is an implicit bias toward Windows environments by focusing on Visual Studio Code (which, while cross-platform, is often associated with Windows) and not acknowledging alternative editors or command-line workflows common on Linux.
Recommendations
- Explicitly state that Visual Studio Code and the Azure API Center extension are available on Linux and macOS, not just Windows.
- Mention or provide examples for alternative editors or command-line tools that Linux users might prefer (e.g., Vim, Emacs, or using Azure CLI directly).
- Include instructions or links for installing Visual Studio Code and the extension on Linux.
- If possible, add a section or note about using the Azure API Center with Linux-native tools or workflows.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-portal.md
...b/main/articles/api-center/set-up-api-center-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias by referencing only the Azure portal (a web-based tool, but often associated with Windows-centric workflows) and Visual Studio Code (commonly used on Windows, though cross-platform). There are no explicit Linux-specific instructions, command-line examples, or mentions of Linux tools. No PowerShell or CLI examples are provided, but the absence of Linux terminal or shell instructions means Linux users may feel underrepresented.
Recommendations
- Add Azure CLI and/or Azure PowerShell command examples for key setup steps, and ensure both Windows and Linux shells are covered.
- Explicitly mention that the Azure portal and Visual Studio Code are cross-platform, and provide links or notes for Linux users where relevant.
- Include troubleshooting or setup notes for common Linux environments (e.g., Ubuntu, Fedora) where applicable.
- If any downloadable scripts or code snippets are provided, ensure they are compatible with Bash/zsh as well as PowerShell.
- Consider adding a section or callout for Linux users to clarify any OS-specific considerations.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/tutorials/configure-environments-deployments.md
...center/tutorials/configure-environments-deployments.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively uses the Azure portal (a web-based GUI) for all instructions, with no mention of command-line tools or automation options. There are no examples using cross-platform tools such as Azure CLI, nor are there any references to Linux-specific workflows. The only tool referenced is the Azure portal, which is platform-agnostic but often associated with Windows-centric workflows in Azure documentation. No PowerShell or Windows-only commands are present, but the lack of CLI or Linux examples creates an implicit bias.
Recommendations
- Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux.
- If automation is possible, provide examples using both Azure CLI and PowerShell, and present CLI examples first or side-by-side.
- Explicitly mention that the Azure portal is accessible from any OS/browser to avoid the impression of a Windows-only workflow.
- Include screenshots or terminal examples from Linux environments where relevant.
- Reference documentation or tutorials for Linux users, such as installing and using Azure CLI on Linux.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-app-with-api-options.md
...-b2c/enable-authentication-web-app-with-api-options.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on ASP.NET Core and C# code samples, which are most commonly associated with Windows development environments. There are no references to Linux-specific tools, patterns, or deployment instructions, nor are there examples or guidance for developers working on Linux or cross-platform environments. No PowerShell or Windows-only tools are mentioned, but the overall approach and examples implicitly favor Windows by omitting Linux or cross-platform considerations.
Recommendations
- Add explicit notes or sections on how to configure and run ASP.NET Core applications on Linux (e.g., using dotnet CLI, configuring appsettings.json, and Startup.cs on Linux).
- Include examples or links for deploying and managing Azure AD B2C-enabled web apps on Linux environments (such as Ubuntu or CentOS), including common Linux workflows.
- Mention cross-platform development tools (e.g., Visual Studio Code, JetBrains Rider) and provide instructions for both Windows and Linux users.
- If any command-line instructions are needed, provide both Windows (PowerShell/CMD) and Linux (bash) equivalents.
- Clarify that ASP.NET Core is cross-platform and can be developed and deployed on Linux, macOS, and Windows.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-app-with-api.md
...irectory-b2c/enable-authentication-web-app-with-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is heavily focused on ASP.NET and Visual Studio tooling, which are primarily used on Windows. The only explicit environment-specific instructions are for Visual Studio and Visual Studio Code, with no mention of Linux or macOS equivalents. There are no examples or guidance for running, building, or troubleshooting the application on Linux (e.g., using bash shell, Linux package managers, or Linux-specific .NET development patterns). The command-line instructions and project structure assume a Windows-centric workflow.
Recommendations
- Add explicit instructions and examples for Linux users, such as using bash/zsh shells and common Linux distributions.
- Include guidance for installing .NET SDK and running the application on Linux (e.g., using apt, yum, or snap).
- Provide parity in tooling instructions, such as using VS Code on Linux, JetBrains Rider, or the dotnet CLI exclusively.
- Clarify that the dotnet CLI commands are cross-platform, and provide any Linux/macOS-specific notes where necessary (e.g., file paths, environment variables).
- Mention how to run and debug the ASP.NET application on Linux (e.g., using 'dotnet run' in a terminal, opening localhost URLs, handling HTTPS certificates on Linux).
- If referencing Visual Studio, always include equivalent instructions for Linux-friendly tools and make it clear that the workflow is cross-platform.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-application-options.md
...y-b2c/enable-authentication-web-application-options.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric development tools and workflows, such as Visual Studio and C#/.NET, without mentioning or providing examples for Linux or cross-platform development environments. There are no instructions or examples for Linux users, such as using VS Code, command-line tools, or alternative project setup methods. All code snippets and project guidance assume a Windows/Visual Studio context.
Recommendations
- Include instructions for setting up and configuring Azure AD B2C authentication in cross-platform environments, such as using VS Code or JetBrains Rider on Linux.
- Provide equivalent command-line instructions (e.g., dotnet CLI) for creating controllers and modifying project files, rather than relying solely on Visual Studio's GUI.
- Clarify that the .NET Core/ASP.NET Core stack is cross-platform and can be used on Linux and macOS, and provide links or notes for Linux/macOS-specific setup.
- Add examples or notes for editing configuration files and running the application on Linux (e.g., using nano/vim for appsettings.json, running dotnet run, etc.).
- Avoid language that assumes Visual Studio or Windows as the default environment; mention alternatives and ensure parity in guidance.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-generic-saml-options.md
...irectory-b2c/identity-provider-generic-saml-options.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely platform-neutral, focusing on XML configuration and SAML protocol details. However, in the 'Debug SAML protocol' section, it lists browser extensions for Chrome and Firefox, but when mentioning built-in developer tools, it only references Microsoft Edge and Internet Explorer (both Windows browsers), with no mention of Linux or macOS equivalents (e.g., Chrome DevTools, Firefox Developer Tools). This subtly prioritizes Windows tools and omits Linux-native options.
Recommendations
- When referencing browser developer tools, mention Chrome DevTools and Firefox Developer Tools explicitly, as these are cross-platform and available on Linux.
- If providing links or instructions for built-in browser tools, include those for Chrome and Firefox, not just Edge/IE.
- Where possible, avoid referencing only Windows-specific browsers or tools. If a tool is Windows-only, clarify that and suggest Linux alternatives.
- Consider adding a note that all XML and SAML configuration steps are platform-agnostic and can be performed on any OS.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/microsoft-graph-get-started.md
...es/active-directory-b2c/microsoft-graph-get-started.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively references the Azure portal (a web-based GUI) for all steps and does not provide any command-line examples. There is no mention of cross-platform CLI tools (such as Azure CLI or Microsoft Graph CLI), nor are there any PowerShell or Windows-specific commands. However, by omitting CLI-based instructions, the documentation implicitly favors Windows/GUI workflows, which are more common in Windows environments, and does not address Linux or automation-focused users who may prefer or require CLI/scripted approaches.
Recommendations
- Add Azure CLI examples for application registration, permission assignment, and role assignment, as Azure CLI is cross-platform and widely used on Linux.
- Include Microsoft Graph CLI or REST API examples for relevant operations, enabling automation and parity for Linux and macOS users.
- Explicitly mention that all steps can be performed via CLI and provide links or code snippets for these alternatives.
- Ensure that any references to tools or workflows are balanced between GUI and CLI, and clarify platform compatibility where relevant.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-protect-backend-with-aad.md
...ement/api-management-howto-protect-backend-with-aad.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Azure portal (a web-based, Microsoft-centric tool) for all configuration steps, without mentioning or providing alternatives using cross-platform or Linux-friendly tools such as Azure CLI, Azure PowerShell (on Linux), or REST APIs. No command-line or automation examples are provided, which are often preferred in Linux environments.
Recommendations
- Add equivalent instructions using Azure CLI commands for all major steps, such as app registration and scope creation.
- Provide REST API examples for automation and cross-platform compatibility.
- Mention and link to Azure PowerShell (which is cross-platform) as an alternative to the Azure portal.
- Explicitly state that all steps can be performed from Linux, macOS, or Windows using CLI or REST, and provide sample commands.
- Consider including a table or section comparing different methods (Portal, CLI, REST) for each configuration step.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/page-layout.md
...blob/main/articles/active-directory-b2c/page-layout.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page exhibits mild Windows bias, primarily through references to Microsoft Edge and Internet Explorer compatibility, and mentions of features (such as saving passwords to iCloud Keychain) that are platform-specific. There are no explicit Linux or cross-platform examples, and browser compatibility fixes are described in terms of Windows browsers first (Edge, IE11), with no mention of Linux browsers or environments. No PowerShell or Windows command-line examples are present, but the focus on Windows browser compatibility and terminology suggests a Windows-centric perspective.
Recommendations
- Include explicit references to Linux and macOS browser compatibility (e.g., Firefox, Chrome on Linux/macOS) when discussing browser-specific features or fixes.
- Add examples or notes for developers working on Linux environments, such as testing with Linux browsers or using Linux-based development tools.
- Where browser compatibility is discussed, list non-Windows browsers/environments alongside Windows ones, or provide a compatibility matrix.
- Avoid assuming Windows as the default platform; use neutral language (e.g., 'major browsers' instead of 'Microsoft Edge and Internet Explorer').
- If platform-specific features are mentioned (e.g., iCloud Keychain), clarify their applicability and suggest alternatives for other platforms.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-twilio.md
...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing .NET and web.config (Windows-centric technologies) and providing configuration and deployment guidance only for Azure App Service, with no mention of Linux hosting, Linux deployment steps, or cross-platform alternatives. There are no examples or instructions for Linux environments, such as using environment variables, Linux-compatible certificate management, or deployment to Linux-based hosts.
Recommendations
- Add instructions for deploying the demo app on Linux-based hosts (e.g., Azure App Service for Linux, Docker, or other Linux web servers).
- Provide configuration examples using environment variables or appsettings.json, which are cross-platform, instead of only web.config.
- Include certificate creation and management steps for Linux (e.g., using OpenSSL) alongside Windows instructions.
- Mention Linux-compatible .NET hosting and provide parity in deployment guidance.
- Clarify that the solution can be hosted on both Windows and Linux platforms, and provide links or steps for both.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-whoiam.md
...b/main/articles/active-directory-b2c/partner-whoiam.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows/Azure-centric bias by exclusively referencing Azure services, portals, and workflows, with no mention of Linux tools, command-line interfaces, or cross-platform deployment options. All configuration and testing steps assume use of the Azure Portal UI, which is most commonly accessed from Windows environments, and there are no CLI or automation examples (e.g., Azure CLI, Bash scripts) that would help Linux users. There are no references to Linux-specific tools or deployment scenarios.
Recommendations
- Add examples using Azure CLI commands, which are cross-platform and can be run on Linux, macOS, and Windows.
- Include instructions for deploying BRIMS API and admin portal using command-line tools (e.g., Bash scripts, ARM templates, or Terraform) in addition to the Azure Portal.
- Mention that the Azure Portal and all Azure services can be accessed from any OS, and clarify that the tutorial is platform-agnostic.
- Provide troubleshooting steps or notes for Linux users, such as managing environment variables, file permissions, or using open-source tools.
- If any local development or testing is required, include instructions for both Windows and Linux environments.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/azure-ai-foundry-api.md
...b/main/articles/api-management/azure-ai-foundry-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web-based GUI commonly accessed from Windows environments) for all instructions, with no mention of command-line alternatives such as Azure CLI, Bash, or PowerShell. There are no Linux-specific examples or guidance for users who may prefer or require non-GUI, cross-platform workflows. The absence of CLI or automation options limits parity for Linux users and those working in headless or automated environments.
Recommendations
- Add equivalent instructions for importing Microsoft Foundry APIs using Azure CLI, Bash, or PowerShell, ensuring examples are cross-platform.
- Include sample commands and scripts for Linux environments, such as using az apim commands to create and configure APIs.
- Reference automation and infrastructure-as-code options (e.g., ARM templates, Bicep, Terraform) for users who do not use the portal.
- Explicitly state that the portal is accessible from any OS, but provide parity for users who prefer or require CLI-based workflows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-versions.md
...ain/articles/api-management/api-management-versions.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page references Azure PowerShell as a management tool alongside Azure CLI, Resource Manager templates, and REST API, but does not mention Linux-specific equivalents or clarify cross-platform compatibility. Azure PowerShell is a Windows-centric tool, and its mention before clarifying CLI parity may suggest a Windows-first approach. No explicit Linux command-line examples or Linux-specific instructions are provided.
Recommendations
- Clarify that Azure CLI and Azure PowerShell are both cross-platform, and provide explicit instructions or examples for Linux users where relevant.
- Include Linux shell (bash) examples for API management tasks, especially where PowerShell is referenced.
- Mention that Azure CLI is available on Linux and macOS, and highlight any differences in usage or installation between platforms.
- If screenshots or UI instructions are provided, note any platform-specific differences in appearance or behavior.
- Consider listing Azure CLI before Azure PowerShell to avoid implicit Windows-first ordering.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/credentials-how-to-azure-ad.md
...articles/api-management/credentials-how-to-azure-ad.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all configuration steps, which is a cross-platform tool, but it does not provide any command-line examples. There are no references to Linux-native tools (such as Azure CLI or Bash scripting), nor are there any PowerShell or Windows-specific commands. However, the absence of CLI examples (like Azure CLI or Bash) means Linux users do not have parity with those who might prefer or require command-line automation.
Recommendations
- Add equivalent Azure CLI commands for each portal-based step, especially for app registration, permission granting, and credential provider setup.
- Include Bash script examples for automating the process on Linux systems.
- Explicitly mention that all steps can be performed using Azure CLI or REST API, and link to relevant documentation.
- Provide a section or appendix with end-to-end CLI-based workflow for Linux users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/expose-existing-mcp-server.md
.../articles/api-management/expose-existing-mcp-server.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation page demonstrates mild Windows bias by recommending Visual Studio Code (VS Code) for testing the MCP server and referencing GitHub Copilot integration, both of which are commonly associated with Windows environments. There are no explicit examples or instructions for Linux users, nor are alternative Linux-native tools suggested. The documentation does not provide command-line or shell examples, nor does it mention Powershell, but it does omit Linux-specific testing workflows and tools.
Recommendations
- Include Linux-native alternatives for testing MCP servers, such as curl, httpie, or Postman (which is cross-platform).
- Explicitly mention that VS Code and GitHub Copilot are available on Linux and macOS, or suggest equivalent editors and tools for those platforms.
- Provide example commands for both Windows (Powershell, CMD) and Linux (bash, zsh) when relevant.
- Add a section or note on how to test MCP servers from a Linux shell environment.
- Ensure screenshots and instructions are not exclusively tailored to Windows UI conventions.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-app-service-as-api.md
...n/articles/api-management/import-app-service-as-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric development tools (such as Visual Studio Code and ASP.NET Core tutorials) and omitting Linux-specific instructions or examples. There are no examples of using Linux command-line tools, deployment patterns, or alternative Linux-based workflows. The documentation assumes usage of the Azure portal and Visual Studio Code, which, while cross-platform, are more commonly associated with Windows environments. No Linux shell commands, package managers, or deployment instructions are provided.
Recommendations
- Add explicit instructions and examples for deploying web APIs from Linux environments, such as using the Azure CLI, Bash scripts, or Linux-based CI/CD pipelines.
- Include references to Linux development tools (e.g., VS Code on Linux, JetBrains Rider, or command-line editors) and how to publish to Azure App Service from those environments.
- Provide sample commands for creating and deploying web apps using Linux shell (e.g., Bash) and the Azure CLI.
- Mention cross-platform compatibility for all tools and clarify when steps are identical or different on Linux vs. Windows.
- Add links to documentation or tutorials specifically targeting Linux users, such as 'Deploy a Python/Node.js web app to Azure App Service from Ubuntu'.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/protect-with-defender-for-apis.md
...icles/api-management/protect-with-defender-for-apis.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes using the Azure portal (a web-based GUI) for all operations, with no mention of command-line alternatives such as Azure CLI, PowerShell, or REST API. While this avoids explicit Windows tool bias, it implicitly favors Windows/GUI workflows, which are more familiar to Windows users. There are no examples or guidance for Linux users or those who prefer automation via CLI or scripts.
Recommendations
- Add Azure CLI examples for enabling Defender for APIs, onboarding/offboarding APIs, and viewing security insights, as Azure CLI is cross-platform and widely used on Linux.
- If relevant, provide REST API examples for all major operations, allowing users on any platform to automate tasks.
- If PowerShell examples are included in the future, ensure Azure CLI or Bash equivalents are always provided alongside.
- Explicitly mention that all operations can be performed via the portal, CLI, or REST API, and link to relevant automation documentation.
- Consider a section summarizing cross-platform options for managing Defender for APIs, highlighting parity between Windows and Linux workflows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/self-hosted-gateway-enable-azure-ad.md
.../api-management/self-hosted-gateway-enable-azure-ad.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure portal and PowerShell/CLI tools before or alongside Linux-friendly options, and by linking to portal-based (GUI) instructions, which are more familiar to Windows users. However, the actual deployment and configuration steps are Kubernetes/YAML-centric, which are cross-platform and Linux-native. There are no explicit PowerShell-only examples, but the instructions for creating roles and app registrations reference the Azure portal and PowerShell/CLI documentation before mentioning Linux-specific alternatives.
Recommendations
- Provide explicit Azure CLI examples for all steps (role creation, assignment, app registration) directly in the documentation, not just as links.
- When referencing Azure portal or PowerShell, always mention Azure CLI and/or ARM templates as first-class alternatives, and consider listing CLI examples before portal/PowerShell.
- Add a section or callout clarifying that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Where possible, include bash scripts or command-line snippets for Linux users, especially for role assignments and app registration.
- Review all links to ensure parity between Windows (PowerShell/portal) and Linux (CLI/script) guidance.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/integrate-with-application-gateway.md
...vice/environment/integrate-with-application-gateway.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by referencing validation steps such as 'validate the name resolution from a command prompt' and showing screenshots that imply Windows usage (e.g., Windows command prompt and browser). There are no explicit Linux or cross-platform CLI examples for DNS validation, nor are Linux tools (like dig, nslookup on Linux, or curl) mentioned. The instructions and screenshots focus on Azure Portal UI, which is cross-platform, but when command-line validation is referenced, it defaults to Windows terminology and visuals.
Recommendations
- Include Linux-specific examples for DNS validation, such as using 'dig', 'nslookup', or 'host' commands.
- Add screenshots or command snippets from a Linux terminal alongside Windows command prompt examples.
- Use neutral language when referring to command-line validation (e.g., 'from a terminal' instead of 'from a command prompt').
- Explicitly mention that steps can be performed from any OS and provide parity in instructions for both Windows and Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-apple.md
...app-service/configure-authentication-provider-apple.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a C# example for generating the client secret JWT using the Microsoft.IdentityModel.Tokens NuGet package, which is Windows/.NET-centric. There are no examples or guidance for Linux-native tools or languages (such as Python, Node.js, or OpenSSL) that are commonly used on Linux platforms. The documentation does not mention or demonstrate how to perform these steps on Linux, nor does it reference Linux-specific tools or workflows.
Recommendations
- Add examples for generating the client secret JWT using cross-platform or Linux-native tools, such as Python (PyJWT), Node.js (jsonwebtoken), or OpenSSL.
- Include command-line instructions for Linux environments, such as using OpenSSL to handle the .p8 key and sign JWTs.
- Reference Linux package managers (apt, yum) for installing necessary libraries, and provide sample scripts for Bash.
- Clarify that the process is not limited to Windows/.NET and explicitly mention Linux compatibility.
- Provide parity in code samples by showing both Windows/.NET and Linux/open-source approaches side-by-side.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-continuous-deployment.md
...n/articles/app-service/deploy-continuous-deployment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a subtle Windows bias. The 'External Git' section explicitly states it is for 'Windows apps', with no mention of Linux or cross-platform scenarios. There are no Linux-specific deployment examples, nor references to Linux tools or workflows. The documentation does not clarify whether the instructions or features apply equally to Linux-based App Service apps, and omits any Linux shell or CLI examples.
Recommendations
- Clarify whether 'External Git' is supported for Linux App Service apps, and provide equivalent instructions/examples for Linux.
- Add explicit Linux deployment examples, such as using Bash, Azure CLI, or Linux-native tools.
- Ensure all features and instructions are described as cross-platform where applicable, or note any platform-specific limitations.
- Avoid language that implies Windows is the default or only supported platform unless that is technically accurate.
- Include screenshots and workflow examples for Linux-based App Service apps if the experience differs.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation-terraform.md
...articles/app-service/environment/creation-terraform.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is presented as a primary tab alongside CLI, which can indicate a Windows-first approach. There are no Linux-specific shell examples (e.g., Bash) or explicit mention of Linux environments, and PowerShell is highlighted as an equal alternative to CLI, despite being Windows-centric.
Recommendations
- Add explicit Bash shell examples for Linux users, especially for variable assignment and command usage.
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend CLI as the default for parity.
- If PowerShell is included, note its availability on Linux/macOS, or clarify its Windows-centric nature.
- Ensure that instructions for creating files and directories use cross-platform commands (e.g., 'mkdir' and 'cd') or provide alternatives for both Windows and Linux.
- Review all referenced scripts and code snippets to ensure they do not assume a Windows environment (e.g., file paths, environment variable syntax).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/managed-instance/preview-note.md
.../app-service/includes/managed-instance/preview-note.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation explicitly states that the Managed Instance feature is available only for Windows web apps, with Linux and containers not supported. There are no Linux-related examples, instructions, or parity in feature availability.
Recommendations
- Clearly indicate the roadmap or timeline for Linux and container support if available.
- Provide alternative solutions or workarounds for Linux users.
- Include a comparison table showing feature availability across Windows and Linux platforms.
- Add links to Linux-specific documentation or guidance for similar scenarios.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-1.md
...tart-python/create-app-service-visual-studio-code-1.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references the Azure Tools for VS Code extension, which is commonly associated with Windows environments. There are no examples or instructions for Linux users, such as alternative methods for accessing Azure resources or using VS Code on Linux.
Recommendations
- Include instructions for installing and using the Azure Tools extension on Linux.
- Mention any platform-specific differences in accessing the Azure icon or using VS Code extensions.
- Provide screenshots or examples from both Windows and Linux environments to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-2.md
...tart-python/create-app-service-visual-studio-code-2.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides steps for using the Azure Tools extension in VS Code without specifying platform-specific instructions. However, it implicitly assumes a Windows environment by not mentioning Linux or macOS, nor does it provide any examples or notes for users on those platforms.
Recommendations
- Explicitly state that the instructions apply to all supported platforms (Windows, Linux, macOS) if true.
- Add notes or examples for Linux users, such as differences in UI, installation, or permissions.
- Include troubleshooting tips for common Linux-specific issues (e.g., file permissions, dependency installation).
- Ensure parity in screenshots and terminology for all platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-visual-studio-code-1.md
.../quickstart-python/stream-logs-visual-studio-code-1.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively references the Azure Tools for VS Code extension, which is commonly used on Windows, and does not provide alternative instructions or examples for Linux users (such as using Azure CLI or other cross-platform tools). No Linux-specific guidance or parity is offered.
Recommendations
- Add instructions for enabling streaming logs using Azure CLI, which is available on both Windows and Linux.
- Include examples for common Linux workflows, such as using terminal commands.
- Clarify that the VS Code extension is cross-platform, if applicable, or provide alternatives for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/remove-resource-group-azure-portal-2.md
...ckstart-python/remove-resource-group-azure-portal-2.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides instructions that assume a graphical interface typical of Windows environments, without mentioning equivalent command-line or Linux-native methods for deleting a resource group. There are no examples or guidance for Linux users (e.g., using Azure CLI or shell commands).
Recommendations
- Add instructions for deleting a resource group using the Azure CLI, which works across Windows, Linux, and macOS.
- Include examples of using shell commands (bash) for Linux users.
- Clarify that the graphical interface is available on all platforms, if applicable, or specify platform differences.
- Present both GUI and CLI methods side-by-side to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-ai-agent-web-app-semantic-kernel-foundry-dotnet/configure-model-permissions.md
...c-kernel-foundry-dotnet/configure-model-permissions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses on Azure portal UI steps, which are generally platform-agnostic, but it lacks any mention of command-line alternatives. The only linked instructions are for the Azure portal, which is most commonly used on Windows. There are no examples or references to Linux tools (such as Azure CLI or Bash), nor is PowerShell mentioned, but the absence of Linux command-line instructions creates a subtle Windows-first bias.
Recommendations
- Add instructions for assigning Azure roles using Azure CLI, which is cross-platform and commonly used on Linux.
- Include Bash or shell script examples for Linux users.
- Explicitly mention that the Azure portal is accessible from any OS, and provide parity for command-line steps.
- If PowerShell is referenced elsewhere, ensure equivalent Bash/CLI examples are provided.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation only describes resource cleanup using the Azure portal, which is a graphical interface commonly associated with Windows environments. There are no command-line examples (such as Azure CLI or PowerShell), and no mention of Linux-specific tools or workflows. This can be interpreted as a subtle Windows bias, as Linux users often prefer or require CLI instructions.
Recommendations
- Add Azure CLI examples for deleting the resource group, as the CLI is cross-platform and widely used on Linux.
- Include PowerShell examples if relevant, but ensure CLI instructions are presented first or alongside them.
- Explicitly mention that the Azure portal is accessible from any OS, but provide parity for users who prefer command-line operations.
- Consider adding a note or section about automating resource cleanup from Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnetcore-sqldb-app/deploy-from-local-git-azure-portal-2.md
...core-sqldb-app/deploy-from-local-git-azure-portal-2.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides instructions that are generic but implicitly assume a Windows-style UI (e.g., 'menu on the left side', 'top menu bar'), which may differ on Linux or cross-platform environments. There are no examples or notes about Linux-specific interfaces, nor any mention of command-line alternatives that are common on Linux systems.
Recommendations
- Add explicit notes or screenshots for Linux users, highlighting any UI differences.
- Include command-line instructions (e.g., using Azure CLI) as an alternative to GUI steps.
- Clarify whether the instructions apply identically on Linux, macOS, and Windows, or specify platform differences.
- Ensure parity by referencing both Windows and Linux environments where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnet-storage-managed-identity/introduction.md
...torial-dotnet-storage-managed-identity/introduction.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents both Azure Portal (GUI), PowerShell, and Azure CLI instructions for key steps. However, PowerShell examples are given before Azure CLI, and there is no mention of Linux-specific tools or shell environments. PowerShell is a Windows-centric tool, and its precedence in the documentation may signal a Windows bias. There are no Bash or Linux shell script examples, nor any explicit references to Linux environments or considerations.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform and widely used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash script examples where appropriate.
- Add notes or sections for Linux users, such as how to install and use Azure CLI on Linux, and clarify that PowerShell Core is available cross-platform if PowerShell examples are retained.
- Consider including troubleshooting tips or environment-specific notes for Linux users, especially regarding authentication and permissions.
- Avoid assuming Visual Studio usage, as it is primarily a Windows tool; mention alternatives like VS Code or command-line deployment for Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions, but PowerShell is presented first and in greater detail. PowerShell is traditionally associated with Windows environments, and the initial emphasis may suggest a Windows-centric workflow. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or patterns. The instructions reference Visual Studio (a Windows-first IDE) for enabling managed identity, with no mention of alternatives for Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) first.
- Add explicit bash shell examples where possible, especially for steps that can be performed outside PowerShell.
- Mention cross-platform IDEs (such as VS Code) and deployment methods for enabling managed identity, not just Visual Studio.
- Clarify that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide installation instructions for each platform.
- Ensure screenshots and UI instructions do not assume a Windows environment.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
...-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation describes steps for accessing deployment credentials but does not provide platform-specific instructions or examples. There is no mention of Linux or cross-platform tooling, and the instructions implicitly assume a generic workflow that may default to Windows users. No Linux-specific commands, tools, or considerations are provided.
Recommendations
- Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash) environments for using the credentials.
- Mention cross-platform Git usage, including command-line examples for both Windows and Linux.
- Clarify any differences in credential storage or usage between Windows and Linux systems.
- Include screenshots or references for both Windows and Linux UI where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-stream-diagnostic-logs-1.md
...php-mysql-app/azure-portal-stream-diagnostic-logs-1.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides instructions that implicitly assume a Windows environment (e.g., 'File System' logging) and does not mention Linux-specific logging options or differences. There are no examples or notes for Linux users, nor is there guidance on how these steps may differ on Linux-based App Service plans.
Recommendations
- Add explicit notes or sections describing how logging works on Linux-based App Service plans.
- Provide Linux-specific examples or clarify if the 'File System' option is available and behaves the same on Linux.
- Mention any differences in log file locations, access methods, or configuration steps for Linux.
- Ensure parity by listing both Windows and Linux options where applicable, and avoid assuming the user is on Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/ip-address-change-outbound.md
...ain/articles/app-service/ip-address-change-outbound.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation page does not provide any platform-specific examples or instructions, but it implicitly assumes a Windows-centric context by referencing the Azure portal and common enterprise patterns (such as firewalls and inclusion lists) without mentioning Linux-specific tools or command-line alternatives. There are no examples for Linux environments (e.g., using CLI, iptables, or configuration files), nor is there guidance for users who may manage outbound IPs outside of GUI tools.
Recommendations
- Add examples for managing outbound IP addresses using Azure CLI and PowerShell, and ensure both are presented equally.
- Include instructions for updating outbound IP addresses in common Linux firewall tools (e.g., iptables, ufw) and configuration files.
- Mention how to automate IP address updates using shell scripts or configuration management tools (e.g., Ansible, Bash).
- Present platform-agnostic guidance first, then provide platform-specific examples for both Windows and Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-sidecar/common-faqs.md
...s/app-service/includes/tutorial-sidecar/common-faqs.md
Medium Priority
View Details â
Detected Bias Types
missing_windows_example
linux_first
Summary
The documentation page focuses on Linux scenarios, specifically mentioning 'code-based Linux apps' and the built-in Linux container as the main container. There are no Windows or PowerShell examples, nor are Windows tools or patterns referenced. The only platform-specific note is about Linux, and Windows scenarios are not discussed or illustrated.
Recommendations
- Add equivalent examples and notes for Windows-based containers, including how sidecars and volume mounts behave in Windows environments.
- Clarify whether the volume mounts feature and sidecar networking work similarly for Windows containers, or note any differences.
- Include explicit Windows container configuration steps or references if supported, or state limitations if not.
- Provide PowerShell or Windows command-line examples where relevant, alongside Linux shell examples.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/ip-address-change-ssl.md
...lob/main/articles/app-service/ip-address-change-ssl.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes steps using the Azure portal GUI, which is platform-agnostic but omits any command-line examples. There are no references to Linux-specific tools, shell commands, or CLI workflows, nor are there any Powershell or Windows tool references. However, the absence of Linux CLI (e.g., Azure CLI, bash) examples means Linux users do not see parity in automation or scripting options.
Recommendations
- Add Azure CLI command examples for releasing and assigning TLS/SSL IP addresses.
- Include bash shell snippets for DNS record updates using common Linux tools (e.g., dig, nsupdate).
- Explicitly mention that the steps are applicable regardless of OS, and provide links to both Powershell and bash/CLI documentation for advanced users.
- Ensure that automation options (CLI, scripting) are presented alongside GUI instructions for cross-platform parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-app-service-arc.md
...b/main/articles/app-service/migrate-app-service-arc.md
Medium Priority
View Details â
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 example. There are no Linux-specific shell examples (e.g., bash scripts), nor is there mention of Linux-native tools. The documentation does not reference Windows-only tools, but the inclusion of PowerShell examples alongside CLI may signal a Windows-centric approach, especially since PowerShell is primarily associated with Windows environments, despite its cross-platform availability.
Recommendations
- Add bash shell script examples for all resource queries to demonstrate Linux parity.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, while PowerShell is also cross-platform but more familiar to Windows users.
- Consider listing CLI (bash) examples first, as CLI is the most platform-neutral and widely used on Linux.
- Clarify in the documentation that no Windows-only tools are required and that all steps can be performed on Linux systems.
- If PowerShell is included, note its cross-platform support and provide links to installation instructions for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-gateway-based-vnet-integration.md
.../app-service/migrate-gateway-based-vnet-integration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page provides step-by-step instructions for migrating App Service virtual network integration, and consistently presents Azure PowerShell examples alongside Azure CLI and portal instructions. PowerShell examples are given equal prominence to CLI and portal, but PowerShell is a Windows-centric tool, and there is no mention of Linux-specific tools or shell patterns (e.g., Bash, scripting nuances). The documentation does not reference Linux-specific commands, nor does it acknowledge differences in experience for Linux users. While Azure CLI is cross-platform, the inclusion and equal emphasis on PowerShell throughout the page reflects a subtle Windows bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
- Add notes or sections highlighting any differences or considerations for Linux users, such as shell syntax, environment setup, or troubleshooting.
- Consider providing Bash script examples for common operations, or at least mention how Linux users can automate these steps.
- Review the order of examples: present Azure CLI before PowerShell to subtly prioritize cross-platform tooling.
- Where PowerShell is shown, clarify its platform requirements and suggest alternatives for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/monitor-app-service.md
.../blob/main/articles/app-service/monitor-app-service.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias by mentioning Visual Studio integration for Application Insights and listing PowerShell as a primary method for querying Azure activity logs, with no explicit mention of Linux tools or examples. There are no Linux-specific CLI or shell examples, and Windows tools are referenced before cross-platform alternatives.
Recommendations
- Include examples using Azure CLI and Bash for querying activity logs and managing monitoring features, alongside PowerShell.
- Mention cross-platform editors and IDEs (such as VS Code) in addition to Visual Studio when discussing Application Insights integration.
- Add explicit references to Linux-compatible monitoring workflows and tools where relevant.
- Ensure that any tool or method listed (e.g., PowerShell) is accompanied by its cross-platform equivalent, and present them together or with Linux-first parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-authentication-authorization.md
...s/app-service/overview-authentication-authorization.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page presents the Windows (IIS module) architecture before the Linux/container equivalent, and references IIS modules as the native implementation. The Linux/container architecture is described as an alternative, with less direct integration. There are no explicit PowerShell-heavy examples or Windows-only CLI instructions, but the architectural explanation is Windows-first and Windows-centric. No Linux-specific tools or patterns are mentioned, and CLI examples use Azure CLI (cross-platform).
Recommendations
- Present Linux/container architecture before or alongside Windows architecture to avoid Windows-first bias.
- Provide more details about Linux/container implementation, including any relevant troubleshooting, configuration, or integration differences.
- Reference Linux-native concepts (such as NGINX/Apache modules or reverse proxy patterns) where appropriate, not just IIS.
- Include links or examples for Linux-specific scenarios, such as troubleshooting authentication in Linux containers.
- Ensure parity in architectural diagrams and explanations for both Windows and Linux/container deployments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-agent-identity.md
...b/main/articles/app-service/overview-agent-identity.md
Medium Priority
View Details â
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 C# code samples. There are no examples or guidance for deploying or configuring agent identity on Linux-based hosting options, nor are there any Linux-specific tools, shell commands, or deployment patterns mentioned. The documentation does not address cross-platform concerns or provide parity for Linux users.
Recommendations
- Include explicit instructions and examples for deploying .NET agent identity apps on Linux-based App Service plans and Azure Functions (e.g., using containers or Linux runtime).
- Provide Linux shell (bash) equivalents for environment variable configuration and deployment steps, alongside any PowerShell or Windows-specific instructions.
- Mention and link to documentation for Linux-based development and deployment workflows, such as using Azure CLI in bash, Docker containers, or GitHub Actions for Linux runners.
- Add notes clarifying platform compatibility, and highlight any differences or additional steps required for Linux environments.
- Offer sample code and configuration for other languages and frameworks commonly used on Linux, such as Python or Node.js, to demonstrate agent identity usage outside of C#/.NET.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-java.md
...docs/blob/main/articles/app-service/quickstart-java.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page provides separate pivots for Java Tomcat (Linux), Java SE (Windows), and Java JBoss (Windows), but both Java SE and JBoss examples are Windows-only. There are no Linux equivalents for Java SE or JBoss, and the Windows pivots are listed before Linux in those cases. This creates a bias toward Windows by omitting Linux instructions for those runtimes and prioritizing Windows examples.
Recommendations
- Provide Linux-based quickstart pivots/examples for Java SE and JBoss, if supported by Azure App Service.
- Ensure that Linux and Windows pivots are presented with equal prominence and ordering.
- Explicitly mention platform support limitations if certain runtimes are not available on Linux, to clarify the absence of Linux examples.
- Add cross-platform notes or tables summarizing which runtimes are supported on which OS, to help users quickly understand parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/samples-bicep.md
...e-docs/blob/main/articles/app-service/samples-bicep.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides both Linux and Windows examples for basic app deployment, but Windows-specific scenarios (such as Windows container apps and MySQL on Windows) are more prevalent and appear before or in greater detail than their Linux equivalents. There are examples for Windows containers and Windows+MySQL, but no corresponding Linux container or Linux+MySQL samples. The ordering and coverage suggest a slight Windows bias.
Recommendations
- Add examples for Linux container app deployments to match the Windows container sample.
- Include a sample for App Service app on Linux with Azure Database for MySQL to parallel the Windows+MySQL example.
- Ensure parity in the number and detail of Linux and Windows scenarios, especially for common configurations.
- Consider alternating the order of Windows and Linux examples or grouping them together for direct comparison.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-optimize-azure-functions.md
...esting/load-testing/how-to-optimize-azure-functions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes usage of the Azure portal UI for optimizing Azure Functions, without mentioning command-line alternatives or platform-specific tooling. There are no examples using PowerShell, but the workflow assumes use of the Azure portal, which is most commonly accessed from Windows environments. No Linux-specific tools, CLI commands, or parity examples (such as Azure CLI or Bash scripting) are provided, and there is no mention of how to perform these tasks from Linux or cross-platform environments.
Recommendations
- Add Azure CLI examples for creating and managing test profiles, running load tests, and viewing results, ensuring parity with portal-based instructions.
- Include explicit instructions or links for performing these tasks from Linux/macOS environments.
- Mention cross-platform access to the Azure portal, and clarify that all steps can be performed from any OS with a supported browser.
- Where screenshots are provided, consider including CLI output or terminal screenshots alongside portal UI images.
- Highlight any differences or considerations for Linux users, such as authentication methods or required tools.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-execution.md
...cs/blob/main/articles/app-service/webjobs-execution.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation generally describes WebJobs in a cross-platform manner, but there is subtle Windows bias: the folder structure uses Windows-style paths (e.g., 'site/wwwroot/App_Data/jobs/'), and there are no explicit Linux or cross-platform examples for job creation, folder navigation, or log access. Linux-specific troubleshooting is limited to a single bullet point about permissions, and there are no PowerShell or Windows tool examples, but the documentation does not provide parity for Linux command-line workflows or highlight Linux-first patterns.
Recommendations
- Add explicit Linux examples for folder navigation (e.g., using bash commands to access job folders and logs).
- Include sample commands for setting permissions on Linux (e.g., 'chmod +x run.sh') in the main workflow, not just troubleshooting.
- Show both Windows and Linux path formats when referencing folders.
- Provide examples of how to access logs or trigger jobs using Linux tools (curl, bash) alongside portal/Kudu instructions.
- Clarify any differences in behavior or requirements between Windows and Linux environments in relevant sections.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-create-and-run-load-test-with-jmeter-script.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-create-and-run-load-test-with-jmeter-script.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure CLI examples using Windows-style variable assignment and shell syntax, without any Linux-specific instructions or examples. There is no mention of Linux shell equivalents, nor are there references to Linux tools or usage patterns. The CLI examples use syntax (e.g., variable assignment with quotes and backticks) that is specific to Windows CMD or PowerShell, which may not work as-is on Linux or macOS terminals.
Recommendations
- Add Linux/bash-specific examples for Azure CLI usage, including correct variable assignment and command syntax.
- Explicitly mention cross-platform compatibility for the Azure CLI, and provide instructions for both Windows (CMD/PowerShell) and Linux/macOS (bash/zsh).
- Include notes or tabs that show how to run the CLI commands on Linux/macOS, highlighting any differences in syntax or environment setup.
- Ensure screenshots and instructions do not assume a Windows environment unless explicitly stated, and provide parity for Linux users.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-create-manage-test-runs.md
...testing/load-testing/how-to-create-manage-test-runs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes managing Azure Load Testing test runs via the Azure portal, which is a web-based GUI and does not reference any command-line tools or platform-specific instructions. However, all screenshots and navigation instructions implicitly assume a Windows environment (e.g., terminology like 'ellipsis (...)', left pane navigation, and context menus), and there is no mention of Linux-specific workflows, CLI, or automation options. No PowerShell or Windows-only tools are mentioned, but there is a lack of parity for Linux users who may prefer CLI or non-GUI workflows.
Recommendations
- Add instructions for managing test runs using Azure CLI or REST API, including examples for both Windows (PowerShell, Command Prompt) and Linux (Bash).
- Include screenshots or descriptions that are platform-neutral, or explicitly mention that the Azure portal is accessible from any OS.
- Provide links or sections for automation and scripting options, highlighting cross-platform compatibility.
- Clarify that the Azure portal is web-based and does not require a Windows environment, to avoid implicit Windows bias.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-move-between-regions.md
...pp-testing/load-testing/how-to-move-between-regions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure Portal (GUI) for all steps and does not mention or provide examples for command-line tools such as Azure CLI, PowerShell, or Bash. While this avoids explicit Windows tool bias, the lack of Linux-friendly CLI instructions means users on Linux or those preferring automation are underserved. The workflow assumes a graphical interface, which is more common on Windows, and does not address parity for Linux users.
Recommendations
- Add equivalent instructions using Azure CLI commands for exporting, modifying, and deploying ARM templates.
- Include examples for downloading test artifacts using CLI or automation scripts.
- Provide guidance for recreating resources and tests via command-line tools (Azure CLI, Bash, PowerShell), and mention cross-platform compatibility.
- Explicitly state that all steps can be performed on Linux, Mac, and Windows, and link to CLI documentation where appropriate.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/quickstart-add-load-test-cicd.md
...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively describes automating load tests using Azure Pipelines, which is tightly integrated with Azure DevOpsâa platform historically associated with Windows environments. All examples, screenshots, and step-by-step instructions focus on Azure Pipelines and the Azure portal, with no mention of Linux-native CI/CD tools (such as Jenkins, GitLab CI, or Travis CI), nor any command-line or scripting examples for Linux shells. The only alternative (GitHub Actions) is relegated to a single sentence and links to a separate manual configuration guide, rather than being presented alongside Azure Pipelines. There is no discussion of Linux-specific workflows, tools, or patterns.
Recommendations
- Provide parallel examples for Linux-native CI/CD tools (e.g., Jenkins, GitLab CI, Travis CI) and show how to automate Azure Load Testing from those environments.
- Include command-line examples using Bash or other Linux shells for configuring and triggering load tests, in addition to portal-based workflows.
- Present GitHub Actions automation steps in the main quickstart, not only as a separate manual configuration link.
- Add notes or sections on how the process differs (if at all) for users working on Linux or macOS environments.
- Ensure screenshots and instructions do not assume Windows-only tools or interfaces, and clarify cross-platform compatibility where relevant.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-manage-access-tokens.md
...g/playwright-workspaces/how-to-manage-access-tokens.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively describes managing workspace access tokens via the Azure portal UI, which is a web-based interface and not inherently OS-specific. However, there are no command-line examples or references to CLI tools (such as Azure CLI, PowerShell, Bash, etc.), nor any mention of Linux-specific workflows. The absence of CLI examples means that users on Linux (or those preferring automation/scripting) are not provided with parity or guidance, while Windows users may implicitly benefit from the default association with Azure portal and PowerShell in Microsoft documentation. There is a subtle 'Windows-first' bias due to the lack of cross-platform command-line instructions.
Recommendations
- Add Azure CLI examples for creating, viewing, and deleting access tokens, ensuring commands work on both Windows and Linux.
- Explicitly mention that all portal-based instructions apply equally to users on any OS, and provide links to CLI documentation.
- Include Bash script examples for Linux users to automate token management.
- If PowerShell is referenced in other related documentation, ensure Bash/Azure CLI equivalents are provided and linked.
- Clarify any OS-specific limitations or considerations for managing access tokens.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-listeners.md
...rticles/application-gateway/configuration-listeners.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a PowerShell-only example for enabling HTTP/2 support, with no equivalent CLI or Bash example for Linux users. There is no mention of Linux tools or cross-platform command-line alternatives, and the only automation example is Windows-centric.
Recommendations
- Add Azure CLI and Bash examples alongside PowerShell snippets for all configuration steps, especially for enabling HTTP/2 support.
- Explicitly mention that configuration can be performed from Linux, macOS, and Windows platforms using Azure CLI or REST API.
- Where automation is discussed, provide parity between PowerShell and CLI/Bash to ensure Linux users are equally supported.
- Consider including a table or section comparing available tools (PowerShell, CLI, REST API) for common tasks.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-configure-visual-comparisons.md
...ight-workspaces/how-to-configure-visual-comparisons.md
Medium Priority
View Details â
Detected Bias Types
linux_first
missing_windows_example
Summary
The documentation page consistently uses Linux as the reference OS for configuring visual comparisons and snapshot paths in Playwright Workspaces. All code examples hardcode 'linux' as the OS, and the service configuration explicitly sets the OS to Linux. There are no examples or guidance for Windows users, nor is there mention of how to adapt the configuration for Windows environments.
Recommendations
- Provide equivalent configuration examples for Windows, such as using 'windows' in snapshotPathTemplate and ServiceOS.
- Add guidance for users running Playwright Workspaces on Windows, including any differences in path formats or expected behavior.
- Explicitly mention how to switch between Linux and Windows in the configuration, and discuss cross-platform considerations.
- Ensure that both Linux and Windows users are addressed in documentation, with examples and troubleshooting tips for each.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-manage-workspace-access.md
...laywright-workspaces/how-to-manage-workspace-access.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes managing Playwright Workspace access using the Azure portal GUI, which is primarily accessed via a web browser on Windows. There are no examples or instructions for managing access using cross-platform command-line tools such as Azure CLI, nor are there any Linux-specific patterns or alternatives mentioned. This results in a Windows-first and GUI-centric bias, with missing parity for Linux users who may prefer or require CLI-based workflows.
Recommendations
- Add examples for managing workspace access using Azure CLI commands, which are available on both Windows and Linux.
- Include instructions for using Azure PowerShell and explicitly note its cross-platform support, or provide Bash shell equivalents.
- Mention that all Azure portal operations can be performed from any OS with a supported browser, but highlight CLI alternatives for automation and Linux environments.
- Provide sample scripts for role assignment and revocation using Azure CLI (az role assignment), and link to relevant CLI documentation.
- Ensure screenshots and step-by-step instructions are supplemented with text-based commands for parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health.md
...lication-gateway/application-gateway-backend-health.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents PowerShell as the first and only explicit scripting example for backend health retrieval, with no mention of Linux shell alternatives (e.g., Bash). While Azure CLI is included, it is listed after PowerShell and lacks contextual parity (no Linux-specific notes or troubleshooting tools). There are no references to Linux-native tools or troubleshooting patterns, and the troubleshooting section focuses on Azure portal and Windows-centric tools.
Recommendations
- Provide Bash/Linux shell examples alongside PowerShell, especially for backend health retrieval.
- Explicitly mention that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
- Include troubleshooting steps or tools that are relevant for Linux environments (e.g., curl, openssl for certificate checks).
- Avoid listing PowerShell before CLI or Bash unless there is a clear reason; consider presenting CLI first for cross-platform parity.
- Add notes or links for Linux users regarding certificate management and backend server diagnostics.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-overview.md
...articles/application-gateway/configuration-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page lists Windows-centric tools and workflows (PowerShell) before Linux-friendly alternatives (Azure CLI) in the 'Next steps' section, suggesting a Windows-first approach. There is an explicit mention of PowerShell, which is primarily associated with Windows, and it appears before the Azure CLI, which is more commonly used on Linux and cross-platform environments. No Linux-specific examples or tools are provided, and no parity is shown for Linux users in terms of command-line instructions or workflows.
Recommendations
- List Azure CLI instructions before PowerShell to avoid implicit Windows-first bias.
- Include explicit Linux examples or workflows where relevant, such as using Bash or shell scripts.
- Clarify that Azure CLI is cross-platform and provide links to installation guides for Linux and macOS.
- Consider adding a table or section comparing PowerShell and CLI usage for common tasks, highlighting Linux compatibility.
- Ensure that screenshots and step-by-step guides do not assume a Windows environment unless necessary.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-create-application-gateway-for-containers-managed-by-alb-controller.md
...ation-gateway-for-containers-managed-by-alb-controller.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation relies exclusively on Azure CLI commands and Bash scripting, which are cross-platform but are most commonly used in Windows environments via Azure Cloud Shell or Windows Subsystem for Linux (WSL). There is no explicit mention of Linux-specific tools, nor are there examples tailored for Linux-native environments. The instructions for subnet and resource management use Azure CLI, which is available on Linux, but the documentation does not clarify Linux compatibility or provide Linux-specific notes. There is no evidence of PowerShell usage, but the focus on Azure CLI without explicit Linux context may suggest a subtle Windows-first bias.
Recommendations
- Explicitly state that all Azure CLI and kubectl commands work natively on Linux, macOS, and Windows.
- Add notes or examples showing command execution in a Linux shell (e.g., Ubuntu terminal), especially for users running AKS on Linux hosts.
- Mention installation instructions for Azure CLI and kubectl on Linux systems.
- If any commands have different syntax or requirements on Linux (e.g., environment variable handling), provide those details.
- Consider adding a 'Platform compatibility' section to clarify that the steps are OS-agnostic and highlight any platform-specific caveats.
Avere Vfxt
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/avere-vfxt/avere-vfxt-demo-links.md
...blob/main/articles/avere-vfxt/avere-vfxt-demo-links.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page lists a specific tutorial for setting up a Windows 10 workstation with Avere vFXT, but does not mention or provide equivalent instructions for Linux or macOS clients. This suggests a bias towards Windows environments, both in terms of example prioritization and omission of Linux setup guidance.
Recommendations
- Add a tutorial or documentation link for setting up a Linux workstation with Avere vFXT, including mounting procedures and client configuration.
- Ensure that client setup instructions are provided for multiple platforms (Linux, macOS) alongside Windows to improve parity.
- Review referenced GitHub documentation to confirm that Linux examples are present and clearly linked from this page.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-certificate-management.md
...cles/application-gateway/ssl-certificate-management.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias by mentioning PowerShell commands before Azure CLI commands when describing how to list SSL certificate objects. No Linux-specific tools or examples are provided, and the only command-line references are to PowerShell and Azure CLI, with PowerShell listed first. There are no explicit Linux examples or references to Linux certificate management tools or workflows.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation or usage links for Linux users.
- Include references or examples for managing certificates using Linux-native tools (e.g., OpenSSL for certificate creation or inspection).
- Avoid listing Windows-specific tools or commands first unless there is a technical reason; strive for parity in example ordering.
- Add a section or note for Linux administrators, highlighting any platform-specific considerations or best practices.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/overview-about.md
...e-docs/blob/main/articles/automanage/overview-about.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page mentions both Windows and Linux support but consistently lists Windows before Linux (e.g., 'Supported Windows Server versions and Linux distros'), and does not provide any concrete examples, walkthroughs, or tool references for either platform. However, the structure and phrasing (such as 'Automanage for Windows Server' and 'Automanage for Linux') suggest a Windows-first approach, and there are no Linux-specific examples or tools mentioned, which may leave Linux users with less clarity.
Recommendations
- Provide explicit Linux examples and walkthroughs alongside Windows ones, ensuring parity in detail and clarity.
- When listing supported platforms, alternate the order or use neutral phrasing (e.g., 'Supported operating systems: Windows Server and Linux distributions').
- Include references to Linux-specific tools, commands, or configuration steps where relevant.
- Ensure that any linked pages (such as 'Automanage for Linux') are equally comprehensive as their Windows counterparts.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-go-sdk.md
...ure-docs/blob/main/articles/automanage/quick-go-sdk.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates bias towards Windows by linking only to the Windows VM quick-create portal in the prerequisites, without mentioning or providing equivalent instructions for Linux VMs. There are no Linux-specific examples or references, and the documentation implicitly assumes the user is working with Windows virtual machines.
Recommendations
- Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
- Explicitly state that Automanage supports both Windows and Linux VMs, if applicable.
- Provide example resource IDs or configuration profile assignments for Linux VMs, if they differ.
- Add notes or examples relevant to Linux VM onboarding and management where appropriate.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-python-sdk.md
...docs/blob/main/articles/automanage/quick-python-sdk.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing only Windows virtual machines in the prerequisites section and linking exclusively to the Windows VM quick-create guide. There are no Linux VM examples, nor is there mention of Linux-specific considerations or links to Linux VM documentation. All instructions and code samples are generic, but the context and references favor Windows.
Recommendations
- Include links to both Windows and Linux VM quick-create guides in the prerequisites.
- Explicitly state that the instructions apply to both Windows and Linux VMs, or provide notes on any OS-specific differences.
- Add examples or notes for onboarding Linux VMs, if there are any differences in the process.
- Ensure parity in documentation references and resources for both Windows and Linux users.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-javascript-sdk.md
.../blob/main/articles/automanage/quick-javascript-sdk.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by linking exclusively to the Windows VM quick-create guide in the prerequisites, without mentioning or providing equivalent instructions for Linux virtual machines. There are no Linux-specific examples, notes, or links, and the documentation implicitly assumes the user is working with Windows VMs.
Recommendations
- Add links to both Windows and Linux VM quick-create guides in the prerequisites section.
- Clarify that Automanage supports both Windows and Linux VMs, if applicable.
- Include examples or notes for Linux VM scenarios, such as differences in configuration profile application or prerequisites.
- Ensure terminology and instructions are platform-neutral unless a feature is Windows-only, in which case explicitly state the limitation.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-best-practices.md
...articles/automanage/virtual-machines-best-practices.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific features (such as Windows security baselines) without mentioning Linux equivalents. There are no explicit examples or guidance for Linux VMs, and the guest configuration section only refers to Windows security baselines, omitting information about Linux compliance or configuration options.
Recommendations
- Include information about Linux security baselines or compliance options in the guest configuration section.
- Provide examples or references for both Windows and Linux VM onboarding and configuration.
- Clarify which services and features apply to Linux VMs and highlight any differences in implementation.
- Add links to documentation about configuring best practices for Linux VMs, such as CIS benchmarks or other relevant standards.
- Ensure that any mention of Windows-specific tools or settings is paired with Linux equivalents where available.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-run-as-account.md
...blob/main/articles/automation/delete-run-as-account.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses on deleting Azure Automation Run As accounts, mentioning PowerShell and the Azure portal as the primary methods. There is a notable absence of Linux-specific examples, such as using Azure CLI or Bash scripts, and the mention of PowerShell comes before any cross-platform alternatives. This indicates a Windows-first bias and a lack of Linux parity in the instructions.
Recommendations
- Add examples using Azure CLI commands for deleting Run As accounts, which are cross-platform and commonly used on Linux.
- Include Bash script snippets for automation tasks, where applicable.
- Explicitly mention that PowerShell Core is available on Linux and macOS, or clarify when instructions are Windows-specific.
- Provide parity in tool recommendations, listing Azure CLI and Bash alternatives alongside PowerShell and Azure portal steps.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/runbook-authoring-extension-for-vscode.md
...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing PowerShell modules as a prerequisite and omitting explicit Linux or cross-platform instructions. There are no examples or guidance for Linux users regarding Python package management, shell usage, or troubleshooting. The documentation assumes familiarity with Windows-centric tools and does not mention Linux-specific considerations, such as using Bash, installing Python packages via pip, or handling permissions.
Recommendations
- Add explicit instructions and examples for Linux users, such as how to install Python packages using pip and manage dependencies.
- Clarify that both PowerShell and Python are supported, and provide guidance for using Bash or other shells on Linux.
- Include troubleshooting steps or notes for common Linux issues, such as file permissions or environment setup.
- Mention cross-platform compatibility of the Azure Automation extension and highlight any differences in behavior or requirements between Windows and Linux.
- Provide screenshots or terminal commands from Linux environments to ensure parity and inclusivity.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/enforce-job-execution-hybrid-worker.md
...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell examples are consistently presented after CLI, and PowerShell is highlighted as a primary method for obtaining policy definition IDs. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users (such as shell scripting or references to Linux package managers). The CLI examples are platform-neutral, but the prominence and detail of PowerShell usage may imply a Windows-centric approach.
Recommendations
- Explicitly state that Azure CLI commands work on both Windows and Linux/macOS platforms.
- Add Bash shell script examples for Linux users, especially for file creation and command chaining.
- Include notes or links about running Azure CLI in native Linux environments, such as Ubuntu or CentOS.
- Mention installation instructions for Azure CLI and PowerShell on Linux, or link to cross-platform setup guides.
- Balance the order of examples by sometimes presenting CLI/Bash first, or grouping examples by platform.
- Clarify that PowerShell Core is cross-platform, and provide examples using pwsh on Linux/macOS if relevant.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-packages.md
...-docs/blob/main/articles/automation/python-packages.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias by exclusively providing instructions and examples for downloading Python packages and dependencies using Windows tools and paths (e.g., 'C:\Python27\Scripts\pip2.7.exe') and explicitly stating to use a Windows 64-bit machine. There are no equivalent instructions or examples for Linux or macOS users, nor is there mention of cross-platform alternatives.
Recommendations
- Add equivalent instructions for Linux and macOS, such as using 'pip2.7 download -d <output dir> <package name>' in a bash shell.
- Include examples with Linux file paths and commands (e.g., '/usr/bin/pip2.7').
- Clarify that the process is not limited to Windows and provide guidance for users on other platforms.
- Mention any platform-specific considerations (e.g., wheel compatibility, Python installation locations) for Linux/macOS.
- Ensure screenshots and references do not imply Windows exclusivity unless truly required.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstart-create-automation-account-template.md
...ation/quickstart-create-automation-account-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page exhibits mild Windows bias. PowerShell is mentioned before Azure CLI when describing how to run the ARM template, and the error handling example is given first for PowerShell. The sample runbooks include a PowerShell runbook and a Python runbook, but no explicit Bash or Linux shell example. References to running the template from PowerShell are given before Azure CLI, and the instructions for specifying parameters use PowerShell syntax first.
Recommendations
- Present Azure CLI and PowerShell instructions in parallel, or list Azure CLI first to avoid Windows-first ordering.
- Add explicit Bash or Linux shell runbook examples alongside PowerShell and Python.
- Ensure error messages and troubleshooting steps include both PowerShell and Azure CLI examples, with equal prominence.
- Reference Linux tools and workflows where appropriate, such as running ARM templates from Bash or other Linux shells.
- Clarify that both Windows and Linux users can follow the steps, and provide links to platform-specific guidance if needed.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/create-azure-automation-account-terraform.md
...ickstarts/create-azure-automation-account-terraform.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence despite being Windows-centric. The 'Next steps' section specifically links to a PowerShell runbook tutorial, reinforcing a Windows/PowerShell bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux tools or patterns. The initial instructions and Terraform usage are platform-neutral, but verification and follow-up content lean toward Windows/PowerShell.
Recommendations
- Add explicit Bash/Linux shell examples for verification steps alongside Azure CLI and PowerShell.
- Include links to tutorials for creating Automation runbooks using Python or Bash, not just PowerShell.
- Clarify that Azure CLI commands work cross-platform and highlight usage on Linux/macOS.
- Balance 'Next steps' by featuring non-PowerShell runbook options.
- Mention Linux compatibility in the prerequisites and throughout the guide.
Avere Vfxt
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/avere-vfxt/avere-vfxt-prereqs.md
...cs/blob/main/articles/avere-vfxt/avere-vfxt-prereqs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently provides instructions using the Azure portal (GUI) and Azure CLI, but does not offer any Linux-specific examples or mention Linux tools or shell commands. There is no explicit Windows-only tooling, but the lack of Linux-specific guidance (such as bash shell commands, Linux package requirements, or Linux environment considerations) and the use of GUI instructions (which are more common in Windows workflows) indicate a subtle Windows-first bias. No PowerShell-specific examples are present, but Linux parity is missing.
Recommendations
- Add explicit Linux shell (bash) command examples for steps such as accepting software terms and creating service endpoints.
- Mention any Linux-specific prerequisites or considerations (e.g., required packages, environment variables, or permissions).
- Provide instructions for performing tasks via the Linux terminal, not just the Azure portal or Azure CLI.
- Clarify that Azure CLI commands work on both Windows and Linux, and provide any necessary setup instructions for Linux users.
- Include screenshots or terminal output examples from Linux environments where relevant.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/azure-pipeline-export-task.md
.../azure-app-configuration/azure-pipeline-export-task.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides an explicit example of consuming exported key-values using PowerShell syntax only (echo "$env:myBuildSetting"). There are no equivalent examples for Linux shells (e.g., Bash), nor is there mention of cross-platform usage patterns. This may lead Linux users to feel unsupported or unsure how to access pipeline variables in their environment.
Recommendations
- Add equivalent examples for Bash (e.g., echo "$myBuildSetting" or echo "$MYBUILDSETTING") when showing how to consume pipeline variables.
- Explicitly state that pipeline variables are available as environment variables in all supported agent operating systems, including Linux and macOS.
- Where PowerShell is mentioned, also mention Bash or other common Linux shells to ensure parity.
- Consider adding a table or section with cross-platform usage patterns for accessing pipeline variables.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/concept-preview-api-life-cycle.md
...re-app-configuration/concept-preview-api-life-cycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for checking API versions, but PowerShell is given equal prominence, which may indicate a slight Windows bias. There are no Linux-specific tools or patterns mentioned, and Windows/PowerShell is presented as a primary alternative to Bash. No Linux examples are missing, but the inclusion of PowerShell may prioritize Windows users.
Recommendations
- Ensure that Bash examples are presented first, as Bash is the default shell on most Linux systems.
- Consider adding examples for other common Linux shells (e.g., zsh) or scripting languages (e.g., Python) where relevant.
- Clarify in the documentation which examples are intended for Linux/macOS and which for Windows, to help users choose the appropriate commands.
- If PowerShell is included, note that PowerShell Core is cross-platform, but specify if the example is Windows-specific.
- Include troubleshooting tips or notes for Linux users, such as package installation or environment setup, to improve parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page presents environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and provides detailed steps for Visual Studio (a Windows-centric tool) including F5 debugging and firewall exception notes. PowerShell and Windows command prompt examples are given equal or greater prominence than bash, and Visual Studio is assumed as the primary local development environment.
Recommendations
- Present Linux/macOS (bash) instructions before or alongside Windows instructions, rather than after.
- Include instructions for cross-platform editors and tools, such as VS Code or Azure Functions Core Tools CLI, not just Visual Studio.
- Add notes for Linux/macOS users regarding local testing, such as using 'func start' from Azure Functions Core Tools.
- Avoid assuming Visual Studio as the default; mention alternatives for Linux/macOS users.
- Ensure that all command examples (environment variable setup, local testing) are given equal prominence for Linux/macOS and Windows.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-app.md
...ration/enable-dynamic-configuration-java-spring-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits mild Windows bias by providing command-line examples using the Windows-style 'cmd' prompt and syntax (e.g., 'curl -X GET http://localhost:8080/' under a 'cmd' code block), without offering equivalent Linux or macOS shell examples. There is no mention of Linux-specific tools, nor are Linux shell commands (such as Bash) shown. The Azure Portal instructions are platform-neutral, but the command-line testing section implicitly prioritizes Windows.
Recommendations
- Provide both Windows (cmd/PowerShell) and Linux/macOS (Bash/sh) command-line examples for testing the application, e.g., show 'curl' usage in a Bash shell.
- Use generic shell code blocks (e.g., 'shell' or 'bash') for commands that work cross-platform, or explicitly show both variants if there are differences.
- Include a note clarifying that the commands work on Linux/macOS as well, and mention any platform-specific considerations if relevant.
- Ensure that documentation does not assume a Windows environment by default, especially for Java/Spring Boot applications which are commonly deployed on Linux.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-python.md
...p-configuration/enable-dynamic-configuration-python.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific Python setup documentation in the prerequisites and omitting explicit Linux or macOS setup guidance. No Linux/macOS command-line examples or platform-specific notes are provided, and the only external setup link is for Windows.
Recommendations
- Add links or instructions for setting up Python on Linux and macOS alongside the Windows documentation link.
- Include platform-agnostic or platform-specific notes for environment variable setup and running Python scripts (e.g., differences in shell syntax).
- Explicitly mention that the examples work on Linux/macOS and provide troubleshooting tips for those platforms if needed.
- Ensure parity in CLI instructions, such as referencing both Bash and PowerShell where relevant.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-background-service.md
...enable-dynamic-configuration-dotnet-background-service.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows command prompt and PowerShell before mentioning Linux/macOS equivalents. Windows-specific tools (cmd, PowerShell) are listed first, and PowerShell commands are included, which can reinforce a Windows-centric approach. However, Linux/macOS instructions are present and the .NET CLI is emphasized as cross-platform.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
- Group environment variable setup commands by platform, or use tabs to allow users to select their OS.
- Explicitly state cross-platform compatibility at the start of relevant sections.
- Include screenshots or examples from Linux/macOS terminals as well as Windows.
- Avoid giving Windows instructions (cmd, PowerShell) priority in ordering unless there is a user base justification.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-app-configuration-event.md
...ure-app-configuration/howto-app-configuration-event.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation uses Azure CLI for all examples, which is cross-platform, but it subtly assumes a Windows-first perspective by referencing the Azure Cloud Shell and local CLI installation without mentioning Linux-specific considerations or shell differences. There are no explicit Linux shell examples (e.g., bash vs. PowerShell), and no mention of Linux-specific tools or troubleshooting steps. All command-line examples use a syntax compatible with bash but do not clarify shell compatibility, which may confuse users on Windows using PowerShell or CMD.
Recommendations
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, and clarify any shell-specific syntax (e.g., variable assignment differences between bash and PowerShell).
- Provide parallel examples or notes for PowerShell and bash where syntax differs, or link to documentation explaining these differences.
- Mention Linux and macOS as supported platforms for the Azure CLI, and provide installation links for all platforms.
- Add troubleshooting tips or notes for common issues on Linux (e.g., permissions, path issues) and clarify that the Cloud Shell is available in both bash and PowerShell flavors.
- Where environment variables are used (e.g., $sitename), clarify that this syntax is for bash and provide the equivalent for PowerShell if needed.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-chat-completion-config.md
...zure-app-configuration/howto-chat-completion-config.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides instructions primarily through the Azure Portal UI and does not include any explicit command-line examples. Where command-line options are referenced, it generically mentions 'the CLI' without specifying or providing examples for either Windows (PowerShell/Command Prompt) or Linux (Bash). There are no Linux-specific instructions, nor is there parity in showing how to perform tasks using Bash or cross-platform CLI tools. The ordering and language imply a Windows-first approach, as is common in Azure documentation, and there is a lack of Linux or cross-platform command-line examples.
Recommendations
- Add explicit CLI examples for both Windows (PowerShell) and Linux (Bash) where relevant, such as using Azure CLI commands to create and manage chat completion configurations.
- When referencing the CLI, specify the commands for both Windows and Linux environments, or clarify that the Azure CLI is cross-platform and provide examples in Bash.
- Include screenshots or terminal outputs from Linux environments where applicable.
- Ensure that any references to tools or workflows (such as Key Vault references or adding key-values) are demonstrated with cross-platform parity, not just through the Azure Portal UI.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-feature-filters-aspnet-core.md
...app-configuration/howto-feature-filters-aspnet-core.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides instructions and examples that are platform-neutral in terms of .NET Core usage, but it implicitly assumes a Windows or Windows-first development environment by not mentioning Linux or macOS explicitly. All command-line instructions use dotnet CLI, which is cross-platform, but there are no notes or examples for Linux users (e.g., shell commands, environment differences, or screenshots from non-Windows systems). The browser screenshots and folder navigation instructions also implicitly reflect a Windows-centric workflow.
Recommendations
- Explicitly state that the instructions work on Windows, Linux, and macOS, and mention any platform-specific prerequisites if applicable.
- Include example shell commands (e.g., using bash) or clarify that the dotnet CLI commands are cross-platform.
- Add screenshots or notes that reflect running the application on Linux (e.g., terminal output, browser screenshots showing localhost on Linux).
- Mention common Linux development patterns, such as using VS Code on Linux, or navigating directories with Linux commands.
- If any step is platform-specific (such as file paths or environment variable configuration), provide Linux/macOS equivalents.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-labels-aspnet-core.md
...es/azure-app-configuration/howto-labels-aspnet-core.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates per-environment configuration using Azure App Configuration in the context of an ASP.NET Core app. It references modifying 'launchSettings.json' and uses .NET CLI commands, but does not provide Linux-specific instructions or examples (e.g., setting environment variables via bash or running the app outside Visual Studio/Windows-centric workflows). The workflow assumes a Windows/Visual Studio development environment, with no mention of Linux or cross-platform alternatives.
Recommendations
- Add instructions for setting environment variables on Linux/macOS (e.g., using 'export ASPNETCORE_ENVIRONMENT=Production' in bash).
- Mention how to run the app and set environment variables outside of 'launchSettings.json', which is specific to Visual Studio/Windows workflows.
- Include a note or section for developers using Linux or macOS, highlighting any differences or additional steps.
- Provide equivalent bash/zsh shell commands alongside .NET CLI examples where applicable.
- Clarify that the instructions apply to all platforms supported by .NET, and explicitly mention cross-platform compatibility.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. Windows and PowerShell commands are listed first, which may suggest a prioritization of Windows users. However, Linux/macOS instructions are present and correct, and the rest of the tutorial is platform-neutral.
Recommendations
- Present environment variable setup instructions for all platforms together, or list Linux/macOS first to balance historical bias.
- Consider grouping platform-specific commands in a table or side-by-side format for parity.
- Explicitly state that the tutorial is cross-platform and works equally well on Linux/macOS and Windows.
- Add a note that the Python code and Azure services are platform-independent.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-targetingfilter-javascript.md
...-app-configuration/howto-targetingfilter-javascript.md
Medium Priority
View Details â
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 method. Windows-specific commands (setx, PowerShell syntax) are described in detail, with Linux/macOS covered last and more briefly. No Linux-specific tools or patterns are discussed elsewhere, but the environment variable section demonstrates a 'windows_first' and 'powershell_heavy' bias.
Recommendations
- Present environment variable instructions for Linux/macOS first or in parallel with Windows, to avoid implying Windows is the primary platform.
- Include more detailed Linux/macOS instructions, such as how to persist environment variables across sessions (e.g., editing .bashrc/.zshrc), not just the export command.
- Consider grouping all platform-specific instructions together and using clear headings for each OS, so users can quickly find relevant information.
- If possible, provide parity in troubleshooting steps and screenshots for Linux/macOS users, not just Windows.
- Review other sections for subtle Windows-centric language or assumptions, and ensure examples and terminology are inclusive of all major platforms.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry.md
...in/articles/azure-app-configuration/howto-telemetry.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal UI and Application Insights, which are typically accessed via a web browser on any OS, but does not provide any command-line or automation examples. There are no references to Linux-specific tools, CLI commands, or automation via Bash or cross-platform scripting. No PowerShell or Windows-specific tools are directly mentioned, but the lack of parity for Linux/CLI users is evident.
Recommendations
- Add Azure CLI and/or Azure PowerShell command examples for enabling telemetry and managing feature flags, ensuring both Windows and Linux users can automate these tasks.
- Include examples or references for interacting with Azure App Configuration and Application Insights via REST API or SDKs, which are cross-platform.
- Provide guidance for headless or automated environments (e.g., CI/CD pipelines) where portal access is not practical.
- Explicitly mention that all portal steps are OS-agnostic, and offer alternative instructions for users who prefer or require command-line or script-based workflows.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-variant-feature-flags-javascript.md
...onfiguration/howto-variant-feature-flags-javascript.md
Medium Priority
View Details â
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 command prompt and PowerShell commands are listed first, with Linux/macOS only mentioned afterwards. This ordering and explicit inclusion of PowerShell and setx (Windows-specific tools) demonstrate a subtle Windows-first and PowerShell-heavy bias.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel, rather than listing Windows first.
- Use tabbed or collapsible sections for platform-specific instructions to avoid implicit prioritization.
- Explicitly mention that all platforms are supported and provide equal detail for each.
- Consider using cross-platform tools (e.g., cross-env for npm scripts) in examples where possible.
- Add troubleshooting notes for platform-specific issues, if any, for parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-bicep.md
...n/articles/azure-app-configuration/quickstart-bicep.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented in parallel tabs throughout. There are no Linux-specific instructions, nor is there mention of Linux shell patterns or tools. The use of PowerShell may implicitly favor Windows users, as it is less commonly used on Linux. The documentation does not explicitly state platform requirements or differences, and does not mention Linux or macOS environments.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS), while PowerShell is most common on Windows.
- Add a note clarifying that PowerShell examples are primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Consider listing Azure CLI examples first, as it is the most cross-platform tool.
- Include brief instructions or links for installing Azure CLI on Linux/macOS.
- Mention that PowerShell Core is available on Linux/macOS, but is less commonly used for Azure tasks on those platforms.
- Add troubleshooting tips for Linux/macOS users if any steps differ.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-aspnet-core.md
...p-configuration/quickstart-feature-flag-aspnet-core.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation implicitly assumes a Windows-centric development environment by referencing only the .NET CLI and Azure Portal, without addressing cross-platform shell differences or providing explicit Linux/macOS instructions. There are no examples or notes for Linux users regarding environment setup, shell commands, or alternative tools.
Recommendations
- Explicitly state that the .NET CLI commands work on Windows, Linux, and macOS, and provide any necessary prerequisites for Linux/macOS (e.g., installing .NET SDK).
- Include notes or callouts for Linux/macOS users, such as common shell differences, file path conventions, or troubleshooting tips.
- If any steps differ on Linux (e.g., file permissions, case sensitivity), document them.
- Mention that the Azure Portal is web-based and platform-agnostic, but also provide Azure CLI or Azure PowerShell alternatives for managing feature flags, with example commands for both Windows and Linux shells.
- Add a section or note confirming that the instructions are cross-platform, or link to platform-specific guides as appropriate.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-chat-completion-dotnet.md
...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Build and run the app' section, where instructions for setting environment variables are presented with Windows Command Prompt and PowerShell examples before the macOS/Linux equivalent. However, Linux/macOS instructions are present and accurate. There is no exclusive use of Windows tools or patterns, and no missing Linux examples.
Recommendations
- Present cross-platform instructions in parallel tables or grouped lists, rather than listing Windows first.
- For setting environment variables, consider using a tabbed interface (Windows CMD, PowerShell, Linux/macOS Bash) to give equal prominence.
- Explicitly confirm that all steps and code samples are cross-platform and tested on Linux/macOS.
- Add a note at the start of the 'Build and run the app' section stating that the guide works on Windows, Linux, and macOS.
- Where possible, provide troubleshooting tips for common Linux/macOS issues (e.g., environment variable persistence).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-deployment-overview.md
...re-app-configuration/quickstart-deployment-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently references the Azure portal UI for configuration steps and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash scripts) for managing App Configuration resources. While the portal is cross-platform, the absence of CLI examples (which are especially important for Linux and automated deployments) and the lack of explicit Linux-oriented instructions or screenshots indicate a subtle Windows-first and GUI-first bias. There are no Linux-specific tools, shell commands, or automation examples provided.
Recommendations
- Add Azure CLI examples for all configuration steps (e.g., setting authentication mode, enabling private network access), as Azure CLI is cross-platform and widely used in Linux environments.
- Include Bash script snippets for common deployment tasks to demonstrate parity with PowerShell/Windows approaches.
- Where screenshots of the Azure portal are used, supplement them with equivalent CLI commands and outputs.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to CLI documentation.
- If PowerShell is referenced in related articles, ensure Bash/Azure CLI equivalents are also present.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-event-grid.md
...ain/articles/azure-cache-for-redis/cache-event-grid.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page lists PowerShell as a primary tool for interacting with Azure Cache for Redis events, alongside Azure CLI and the Azure portal. PowerShell is a Windows-centric tool, and its inclusion as a top-level quickstart (both in the table and in the 'Next steps' section) suggests a slight Windows-first bias. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users. However, the presence of Azure CLI (which is cross-platform) mitigates the bias somewhat.
Recommendations
- Add explicit Linux/Bash examples or quickstarts to ensure parity for Linux users.
- Clarify that Azure CLI is cross-platform and provide instructions for installing and using it on Linux.
- Consider including references to Linux-native tools or environments where appropriate.
- Reorder examples so that cross-platform tools (Azure CLI) are listed before Windows-specific tools (PowerShell) to avoid implicit prioritization.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-spring-boot.md
...p-configuration/quickstart-feature-flag-spring-boot.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). Windows-specific commands (setx, PowerShell syntax) are described in detail, while Linux/macOS instructions are present but appear after Windows examples. No Linux-specific tools or patterns are mentioned elsewhere, but parity is generally maintained in other sections.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in tabs, rather than listing Windows first.
- Include notes about differences in environment variable persistence between setx (Windows) and export (Linux/macOS).
- Explicitly mention that Linux/macOS users do not need to restart their terminal for environment variable changes to take effect.
- Where possible, use cross-platform commands (e.g., Maven, Java) before platform-specific instructions.
- Consider adding troubleshooting notes for Linux/macOS users, such as shell-specific environment variable behavior.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-javascript.md
...pp-configuration/quickstart-feature-flag-javascript.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
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. Additionally, the prerequisites link for installing Node.js prioritizes Windows and WSL, with no direct mention of Linux-native installation methods. PowerShell and Windows command prompt commands are given more detailed instructions (e.g., restart requirement), while Linux/macOS instructions are more succinct.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
- Include links or guidance for installing Node.js natively on Linux distributions (e.g., apt, yum, snap) in the prerequisites.
- Provide equal detail for Linux/macOS commands (e.g., mention shell profile persistence for environment variables).
- Consider using tabs or side-by-side formatting for OS-specific instructions to avoid implicit prioritization.
- Review all examples and ensure parity in explanation and troubleshooting steps for Linux/macOS users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-python-provider.md
.../azure-app-configuration/quickstart-python-provider.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias. In the prerequisites, it links only to Windows-specific Python installation instructions. When setting environment variables, Windows command prompt and PowerShell instructions are consistently presented before Linux/macOS equivalents. Both Windows and Linux/macOS commands are provided, but Windows is prioritized in order and detail.
Recommendations
- Provide links to Python installation instructions for Linux and macOS alongside the Windows link in the prerequisites.
- Alternate the order of environment variable instructions, or present all platforms in parallel (e.g., in a table or tabbed format) to avoid prioritizing Windows.
- Ensure that Linux/macOS instructions are as detailed as Windows instructions (e.g., mention shell session persistence if relevant).
- Consider adding a short note affirming cross-platform support and parity to reassure non-Windows users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md
...e-app-configuration/reload-key-vault-secrets-dotnet.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation is focused exclusively on ASP.NET Core applications, which are commonly developed on Windows, and does not provide any Linux-specific instructions, examples, or considerations. All code examples and prerequisites assume a Windows-centric development environment (e.g., Visual Studio, C#), and there are no mentions of Linux tools, shell commands, or cross-platform development patterns. The Azure Portal UI instructions are platform-agnostic, but the lack of Linux parity in code and tooling is evident.
Recommendations
- Add explicit instructions or notes for developers working on Linux, such as using VS Code, JetBrains Rider, or command-line .NET SDK tools.
- Provide shell (bash) commands for common tasks (e.g., using the Azure CLI to manage Key Vault and App Configuration) alongside or in place of portal instructions.
- Clarify that the .NET Core SDK and Azure App Configuration libraries are cross-platform, and provide guidance for running and testing the sample code on Linux.
- Include troubleshooting tips or links for Linux users, especially around authentication (e.g., DefaultAzureCredential behavior on Linux).
- Ensure that future examples and tutorials include parity for both Windows and Linux development environments.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/secure-azure-app-configuration.md
...re-app-configuration/secure-azure-app-configuration.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation does not provide any OS-specific examples, commands, or scripts. However, where code or integration examples are referenced, they are exclusively for ASP.NET Core (a .NET/Windows-centric framework), and there are no equivalent examples or references for Linux-first or cross-platform frameworks (e.g., Java, Python, Node.js). There are no mentions of Linux command-line tools, shell scripts, or deployment patterns, and the only explicit code integration references are for .NET/ASP.NET, which is most commonly associated with Windows environments.
Recommendations
- Add code and integration examples for popular Linux-first or cross-platform frameworks (e.g., Python, Java, Node.js) alongside or in place of ASP.NET Core examples.
- Include references to Linux command-line tools and shell scripting for tasks such as key rotation, monitoring, or deployment, where appropriate.
- When referencing tutorials (such as Key Vault integration), provide links or guidance for non-.NET platforms and frameworks.
- Explicitly mention that all features and guidance apply equally to Linux-based deployments, and provide examples or notes for Linux users where there may be differences.
- Consider adding a section or callout for cross-platform best practices, ensuring parity for both Windows and Linux environments.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-best-practices-scale.md
...es/azure-cache-for-redis/cache-best-practices-scale.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation mentions PowerShell before Azure CLI and REST API when describing programmatic scaling, which can be interpreted as a Windows-first and PowerShell-heavy bias. There are no explicit Linux examples or tools highlighted, and the ordering suggests a preference for Windows tooling.
Recommendations
- List Azure CLI before PowerShell when mentioning programmatic scaling, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI and REST API are fully supported on Linux and macOS.
- Provide example commands for both PowerShell and Azure CLI (and/or Bash) to ensure parity.
- Avoid language that implies PowerShell is the primary or default method for automation.
- Consider adding a table or section summarizing cross-platform options for scaling (Portal, PowerShell, Azure CLI, REST API) and their OS compatibility.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md
...s/azure-cache-for-redis/cache-troubleshoot-timeouts.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page primarily presents troubleshooting steps and examples in a platform-neutral way, but there are subtle signs of Windows bias. Windows-specific tools and patterns (such as performance counters and VM upgrades) are mentioned without Linux equivalents, and guidance for monitoring CPU and memory is described in terms of Windows conventions first. The only explicit Linux mention is a brief reference to TCP settings for Linux-based clients, which lacks detail or examples. There are no Linux-specific troubleshooting commands, monitoring instructions, or examples for common Linux tools (e.g., top, htop, vmstat, sar).
Recommendations
- Add Linux-specific examples for monitoring CPU and memory usage, such as using top, htop, free, vmstat, or sar.
- Provide equivalent instructions for monitoring page faults and network bandwidth on Linux (e.g., /proc/meminfo, netstat, iftop, nload).
- Include Linux command-line examples for troubleshooting, not just references to Windows performance counters.
- Expand the 'TCP settings for Linux based client applications' section with concrete configuration examples and troubleshooting steps.
- Ensure parity in troubleshooting steps and examples for both Windows and Linux environments throughout the documentation.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/includes/cache-delete-resource-group.md
...ache-for-redis/includes/cache-delete-resource-group.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation only provides instructions for deleting Azure resource groups via the Azure portal, which is a graphical interface commonly used on Windows. There are no examples or references to command-line methods such as Azure CLI or PowerShell, which are cross-platform and especially relevant for Linux users. The absence of Linux-specific or CLI-based instructions may make it less accessible for users who prefer or require non-Windows environments.
Recommendations
- Add instructions for deleting resource groups using Azure CLI (az group delete), which works on Linux, macOS, and Windows.
- Include PowerShell examples, but ensure Azure CLI examples are presented first or alongside them to avoid Windows-first bias.
- Explicitly mention that the Azure portal is accessible from any OS, but highlight cross-platform command-line alternatives for automation and scripting.
- Provide links to official documentation for both Azure CLI and PowerShell resource group deletion.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/includes/cache-entra-access.md
...s/azure-cache-for-redis/includes/cache-entra-access.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page primarily describes enabling Microsoft Entra ID authentication using the Azure portal, which is a GUI-centric workflow often associated with Windows environments. It does not provide any command-line examples (e.g., Azure CLI, PowerShell, or Bash), and the only reference to CLI usage is a link to further documentation, without any direct examples. There are no Linux-specific instructions or screenshots, and the workflow implicitly assumes a Windows/GUI-first approach.
Recommendations
- Add explicit Azure CLI examples for enabling Microsoft Entra ID authentication, including commands that can be run on Linux, macOS, or Windows.
- Include screenshots or instructions for using the Azure CLI or other cross-platform tools.
- Clearly state that the Azure portal is web-based and platform-agnostic, if applicable, to avoid the impression of Windows bias.
- Where possible, provide parity between GUI and CLI instructions to ensure Linux users are equally supported.
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/includes/redis-cache-resource-group-clean-up.md
...-redis/includes/redis-cache-resource-group-clean-up.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation only provides instructions for deleting Azure resources via the Azure portal (a web UI), without mentioning or providing examples for command-line alternatives such as Azure CLI or PowerShell. This implicitly favors users who are more familiar with graphical interfaces, which are more common in Windows environments, and omits parity for Linux users who may prefer or require CLI-based instructions.
Recommendations
- Add Azure CLI examples for deleting resource groups and resources, as the CLI is cross-platform and widely used on Linux.
- If PowerShell examples are provided, ensure Azure CLI examples are given equal prominence and appear before or alongside PowerShell.
- Explicitly mention that the Azure portal is accessible from any OS, but provide command-line alternatives for users who prefer or require them.
- Include links to official documentation for both Azure CLI and PowerShell resource deletion commands.
Azure Change Tracking Inventory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-change-tracking-inventory/create-data-collection-rule.md
...ange-tracking-inventory/create-data-collection-rule.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on using the Azure portal and JSON templates for creating Data Collection Rules, without providing any platform-specific command-line examples. However, the instructions and screenshots implicitly assume a Windows-centric workflow (e.g., downloading files, using the Azure portal UI), and there are no references to Linux-specific tools, shell commands, or guidance for users who may prefer or require CLI-based deployment (such as using Azure CLI or Bash). There is also no mention of PowerShell, but the absence of Linux examples or parity is notable.
Recommendations
- Add Azure CLI and/or Bash examples for creating and deploying Data Collection Rules, especially for Linux users.
- Explicitly mention that the process can be performed on any OS, and provide guidance for non-Windows environments.
- Include references or links to documentation for automating DCR deployment using cross-platform tools (e.g., Azure CLI, ARM templates via CLI).
- Ensure screenshots and instructions are not Windows-centric (e.g., avoid assumptions about file dialogs or UI elements that differ on Linux/Mac).
Azure Edge Hardware Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-edge-hardware-center/azure-edge-hardware-center-troubleshoot-order.md
...enter/azure-edge-hardware-center-troubleshoot-order.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides troubleshooting steps exclusively through the Azure portal UI, with no mention of command-line alternatives. There are no examples using Azure CLI, Bash, or PowerShell. Where resource provider registration is referenced, only portal-based instructions are given, which may be more familiar to Windows users. There is no mention of Linux-specific tools or CLI workflows, and no parity for users who prefer or require command-line access, which is common in Linux environments.
Recommendations
- Add Azure CLI examples for registering resource providers and managing subscriptions, as the CLI is cross-platform and widely used on Linux.
- Include Bash shell command examples where relevant, especially for automation scenarios.
- Explicitly mention that all steps can be performed from any OS via the Azure portal, but provide parity with CLI instructions.
- If PowerShell is referenced in related documents, ensure Azure CLI/Bash equivalents are also provided.
- Add a section summarizing both portal and command-line approaches for common troubleshooting tasks.
Azure Fluid Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/includes/sign-in-extensions.md
...icles/azure-fluid-relay/includes/sign-in-extensions.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation focuses exclusively on using Visual Studio Code (VS Code) for Azure sign-in, which is a tool more commonly associated with Windows environments. There are no examples or instructions for signing into Azure using Linux-native tools or command-line interfaces, and no mention of alternatives such as the Azure CLI or platform-specific guidance for Linux users.
Recommendations
- Add instructions for signing into Azure using the Azure CLI, which is cross-platform and widely used on Linux.
- Explicitly mention that VS Code is available on Linux and macOS, or provide platform-specific notes if there are differences.
- Include screenshots or terminal commands relevant to Linux environments.
- Provide parity by listing both GUI (VS Code) and CLI (Azure CLI) methods for signing in to Azure.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-azure-developer-cli.md
...functions/create-first-function-azure-developer-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation generally provides cross-platform instructions and examples, including explicit sections for Linux/macOS, Windows (bash), and Windows (Cmd) when relevant (e.g., Python virtual environment activation). However, there is a subtle Windows bias in the ordering of examples, with 'command prompt' and 'PowerShell' often mentioned before Linux terminals, and Windows-specific tools and patterns (such as 'func.exe', 'cmd', and PowerShell) are sometimes referenced or prioritized. The use of 'command prompt' and 'PowerShell' as default terms, and the inclusion of Windows-specific instructions before Linux equivalents in some places, indicate a mild Windows-first bias. All major steps are covered for Linux, but the ordering and terminology could be more neutral.
Recommendations
- Standardize on 'terminal' as the primary term, with platform-specific clarifications as needed.
- When presenting multiple platform instructions, consistently list Linux/macOS first, or group all platforms equally.
- Avoid using Windows-specific tool names (e.g., 'func.exe') in generic instructions; use 'func' unless the extension is required.
- Ensure that all code and command examples are present for both Linux and Windows, and that Linux examples are not omitted or placed after Windows ones.
- Where possible, provide bash/zsh examples before Windows cmd/PowerShell, or present them in parallel tabs.
- Review for any implicit assumptions of Windows environments (e.g., file paths, environment variable syntax) and provide cross-platform equivalents.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/dedicated-plan.md
...s/blob/main/articles/azure-functions/dedicated-plan.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates a Windows bias by linking exclusively to the Windows-specific App Service pricing page and by referencing App Service plans in a way that prioritizes Windows terminology and resources. There are no explicit Linux or cross-platform examples, and the documentation does not mention Linux-specific considerations or provide parity in links or terminology.
Recommendations
- Include links to both Windows and Linux App Service pricing pages, or use a platform-neutral pricing link.
- Explicitly mention that App Service plans support both Windows and Linux, and highlight any differences or considerations for Linux users.
- Provide examples or notes for Linux users where platform-specific behavior may differ (e.g., Always On, scaling, or custom images).
- Review terminology to ensure it is platform-neutral and does not implicitly prioritize Windows.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/develop-python-worker-extensions.md
...es/azure-functions/develop-python-worker-extensions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates mild Windows bias in a few areas. In the virtual environment activation section, Windows instructions (using Powershell) are presented alongside Linux, but the Windows command uses Powershell syntax (.venv\Scripts\Activate.ps1) rather than the more common cmd.exe syntax (.venv\Scripts\activate.bat). Additionally, the Windows instructions are present and explicit, but Linux instructions are not always given equal detail or context. The use of Visual Studio Code as a prerequisite is cross-platform, but no mention is made of Linux-specific editors or shell environments. Overall, the documentation is mostly neutral but does show a slight preference for Windows patterns in some command examples.
Recommendations
- Provide both Windows (cmd.exe and Powershell) and Linux/macOS command examples wherever OS-specific instructions are needed.
- Ensure Linux instructions are presented with equal detail and clarity as Windows instructions, including troubleshooting notes for common Linux issues.
- Consider mentioning Linux-native editors (e.g., Vim, Nano) or shell environments in prerequisites, or clarify that Visual Studio Code is cross-platform.
- Where possible, use OS-agnostic commands and highlight platform differences only when necessary.
- Explicitly state that all steps are supported on Linux and macOS, and provide links to platform-specific documentation if available.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-code-constraints.md
...unctions/durable/durable-functions-code-constraints.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation provides code examples for multiple languages, including PowerShell, and references Windows-specific tools and patterns (e.g., PowerShell cmdlets like Get-Date, New-Guid). PowerShell is included as a first-class language tab alongside C#, JavaScript, Python, and Java, which is uncommon in cross-platform cloud documentation. The guidance for GUID/UUID generation and date/time APIs specifically mentions PowerShell cmdlets and .NET APIs, which are primarily relevant to Windows environments. There are no explicit Linux shell (e.g., Bash) examples or references, and the documentation does not mention Linux-specific tools or patterns.
Recommendations
- Add Linux shell (e.g., Bash) examples where relevant, especially for scripting scenarios.
- Clarify that PowerShell is available cross-platform, but also provide parity for Linux-native tools and patterns.
- When referencing command-line tools, mention both Windows (PowerShell) and Linux (Bash, sh) equivalents.
- Consider reordering or grouping language tabs so that Windows-specific languages/tools (PowerShell) do not appear to be prioritized over Linux-native options.
- Explicitly state cross-platform support for all language examples, and provide guidance for Linux users where differences exist.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-create-portal.md
...e-functions/durable/durable-functions-create-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Kudu console (which is Windows-centric in its UI and terminology) for package installation and file uploads. All examples for interacting with the Azure portal use Kudu's CMD interface, with no mention of Linux-native tools, Bash, or cross-platform alternatives. There are no examples or instructions for Linux or macOS users, nor is there guidance for using the Bash console or other platform-agnostic methods.
Recommendations
- Include instructions and screenshots for using the Bash console in Kudu, which is available for Linux-based function apps.
- Explicitly mention that Kudu is available for both Windows and Linux function apps, and clarify any differences in the interface or commands.
- Provide alternative examples using Bash commands (e.g., using Bash instead of CMD in Kudu, or using Azure CLI for package installation and file uploads).
- Add a note or section for Linux/macOS users, highlighting any platform-specific steps or differences.
- Avoid using Windows-specific terminology (such as CMD) exclusively; instead, show both CMD and Bash options where applicable.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-configure-managed-identity.md
...urable/durable-functions-configure-managed-identity.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Microsoft-centric tools and workflows (Visual Studio, Visual Studio Code, Azure CLI) for local authentication, and by providing configuration steps and screenshots exclusively from the Azure portal (a web interface, but often associated with Windows workflows). There are no explicit Linux-specific examples, nor are cross-platform command-line alternatives (such as Bash or Linux-native tools) mentioned. The documentation does not provide parity for Linux users in terms of example commands, environment variable configuration, or role assignment workflows outside the Azure portal.
Recommendations
- Include Linux-specific examples for local development, such as using Bash scripts or environment variables.
- Mention and provide examples for using Azure CLI on Linux for role assignments and managed identity configuration.
- Clarify that Visual Studio Code and Azure CLI are cross-platform, and provide explicit instructions for Linux users.
- Add screenshots or terminal commands demonstrating configuration steps on Linux systems.
- Reference Linux-native editors and workflows (e.g., Vim, nano, gedit) for editing configuration files.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-packages.md
.../azure-functions/durable/durable-functions-packages.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page presents .NET (a Windows-centric technology) as the primary runtime, with detailed package instructions for .NET in-process and .NET isolated users before mentioning other platforms. PowerShell, another Windows-first technology, is given explicit mention and migration guidance, while Linux-specific tools, package managers, or examples are absent. There are no Linux-specific instructions, nor are Linux-first runtimes (e.g., Python, Node.js) given equal prominence or example depth.
Recommendations
- Add explicit Linux usage examples, such as referencing package installation via pip (Python), npm (Node.js), or Maven (Java), including command-line instructions for Linux shells.
- Provide parity in configuration instructions for non-.NET platforms, including details on how to configure storage providers for Python, Node.js, and Java.
- Include a section or callout for Linux users, addressing common setup patterns, file locations, and environment differences.
- Balance the order of presentation so that non-Windows runtimes (Python, Node.js, Java) are described with equal detail and not only after .NET.
- If PowerShell is mentioned, also mention Bash or other Linux-native scripting environments where relevant.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-sub-orchestrations.md
...ctions/durable/durable-functions-sub-orchestrations.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation provides language examples for C#, JavaScript, Python, Java, and PowerShell. PowerShell is included as a first-class example, which is primarily a Windows-centric shell and scripting language. There is a specific note about PowerShell support and SDKs, but there are no equivalent notes or guidance for Bash, sh, or other Linux-native shells. No Linux-specific tools or patterns are mentioned. The inclusion of PowerShell as a main example and the absence of Linux shell examples or guidance indicates a Windows bias.
Recommendations
- Add equivalent examples using Bash or other Linux-native shells if shell scripting examples are relevant.
- If PowerShell is included due to its cross-platform support, clarify this and provide Linux installation guidance.
- Include notes or guidance for Linux users, such as using Azure CLI or Bash for orchestration scripting, where applicable.
- Balance PowerShell-specific notes with Linux shell or cross-platform scripting notes to avoid the perception of Windows bias.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-unit-testing.md
...re-functions/durable/durable-functions-unit-testing.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides only C#/.NET in-process examples, with all code samples and testing frameworks (xUnit, moq) focused on the .NET ecosystem. There is no mention of Linux-specific tools, cross-platform test runners, or guidance for running tests on Linux. The use of localhost URLs and .NET-centric libraries may implicitly favor Windows environments, and there are no explicit instructions or examples for Linux users.
Recommendations
- Add explicit guidance for running unit tests on Linux, including any required dependencies or differences in setup.
- Mention and provide examples for running xUnit tests using cross-platform .NET Core CLI commands (e.g., 'dotnet test') rather than assuming Visual Studio or Windows-based workflows.
- Clarify that all tools and frameworks used (xUnit, moq) are cross-platform and provide links or instructions for installing them on Linux.
- Include a note or section on running Durable Functions unit tests in Linux environments, possibly with Docker or WSL, to ensure parity.
- If possible, provide equivalent examples or references for other supported languages/runtimes (e.g., Python, JavaScript) that are popular on Linux.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0010.md
...tions/errors-diagnostics/diagnostic-events/azfd0010.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation suggests switching to Windows as the primary workaround for timezone support, without offering Linux-specific alternatives or examples. There are no Linux-friendly solutions or guidance, and the only actionable recommendation is to use Windows.
Recommendations
- Provide Linux-compatible workarounds or alternatives for timezone handling, such as using UTC or handling time zone conversion within the application code.
- Include explicit examples or references for Linux users, clarifying what is and isn't supported and how to achieve common scenarios.
- Avoid recommending Windows as the only solution; instead, present it as one of several options, with equal emphasis on Linux approaches.
- Link to or describe best practices for time zone management in Linux-based Azure Functions.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-documentdb-output.md
...zure-functions/functions-bindings-documentdb-output.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on .NET/C# examples and NuGet packages, which are most commonly used on Windows. There are no examples or guidance for Linux-based development environments, such as using Azure Functions with Python, Node.js, or other languages, nor are there any references to Linux-specific tools or workflows. All code samples and setup instructions assume a Windows-centric development stack.
Recommendations
- Add examples for other supported languages (e.g., Python, JavaScript/Node.js) to demonstrate cross-platform usage.
- Include instructions for setting up Azure Functions projects on Linux (e.g., using VS Code, CLI, or Docker), not just .NET in-process worker model.
- Reference package managers and installation steps relevant to Linux (e.g., pip for Python, npm for Node.js) alongside NuGet.
- Clarify that Azure Functions and DocumentDB bindings are supported on both Windows and Linux, and provide parity in documentation.
- Add troubleshooting or environment setup notes for Linux users, such as permissions, environment variables, or common issues.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-mcp.md
...ain/articles/azure-functions/functions-bindings-mcp.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias by only providing an Azure CLI example for retrieving the system key, without mentioning or providing equivalent commands for common Linux shells (e.g., Bash) or cross-platform alternatives. There are no explicit PowerShell examples, but the use of Azure CLI is more common on Windows, and no Linux-specific tools or shell commands are referenced. No Linux-specific installation or usage notes are present, and the documentation does not clarify cross-platform compatibility for local development tools.
Recommendations
- Provide explicit Bash and/or cross-platform shell examples for retrieving the system key, in addition to or instead of Azure CLI.
- Clarify that Azure CLI is cross-platform and provide installation links or notes for Linux/macOS users.
- Add notes or examples for running Azure Functions Core Tools on Linux, including any prerequisites or common troubleshooting steps.
- Ensure that all command-line examples are tested and work on both Windows and Linux environments.
- Where relevant, mention Linux package managers (e.g., apt, yum, brew) for installing dependencies.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-assistantpost-input.md
...tions/functions-bindings-openai-assistantpost-input.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation provides dedicated PowerShell examples and configuration details, including a function.json and run.ps1, but does not offer equivalent Linux shell (e.g., Bash) examples or mention Linux-specific tools or patterns. This may unintentionally favor Windows users by assuming PowerShell as the default scripting environment for operational tasks, while omitting parity for Linux users.
Recommendations
- Add equivalent Bash or shell script examples alongside PowerShell for operational tasks, such as invoking the function or managing configuration.
- Clarify that PowerShell examples can be run cross-platform, but also provide Linux-native alternatives where appropriate.
- Mention Linux tools or patterns (e.g., environment variable configuration via .env files, use of curl or wget for HTTP requests) in relevant sections.
- Ensure that all configuration steps (such as editing function.json) are described in a way that is platform-agnostic, or provide platform-specific instructions for both Windows and Linux.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-java-gradle.md
.../azure-functions/functions-create-first-java-gradle.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation exhibits a Windows bias by specifying 'os = windows' in the Gradle configuration without mentioning Linux or cross-platform alternatives. The runtime example defaults to Windows, and there is no discussion of Linux deployment or configuration, despite Java 21 being supported only on Linux. The instructions and examples do not address Linux-specific considerations or parity, and the Azure portal workflow is presented without mention of CLI alternatives that may be more common on Linux.
Recommendations
- Add explicit examples and instructions for deploying to Linux by showing 'os = linux' in the Gradle configuration and discussing any differences.
- Mention that Java 21 is supported only on Linux and provide guidance for users who wish to use this version.
- Include notes or sections on verifying deployments and managing function apps using Azure CLI or other cross-platform tools, not just the Azure portal.
- Ensure that all steps and screenshots are platform-neutral or provide alternatives for both Windows and Linux environments.
- Clarify any platform-specific requirements or limitations, especially for local development and deployment.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-maven-intellij.md
...les/azure-functions/functions-create-maven-intellij.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation shows a mild Windows bias, primarily by referencing Windows as the default or first platform in key steps (e.g., suggesting 'Windows-Java 17' as the platform during Azure Function App creation) and using Windows-centric terminology (e.g., referencing 'Settings/Preferences' dialog with Windows keyboard shortcuts). There are no explicit Linux or macOS examples, and Linux is only mentioned in passing (e.g., Java 21 support). However, the instructions are largely cross-platform due to the use of IntelliJ IDEA and Maven, which are available on all major OSes.
Recommendations
- When referencing platform selection (e.g., 'Platform: Windows-Java 17'), provide Linux and macOS equivalents, or clarify that Linux and macOS are supported and how to select them.
- Include keyboard shortcuts and navigation instructions for macOS and Linux alongside Windows (e.g., mention Cmd+, for Preferences on macOS).
- If there are any OS-specific steps (such as setting JAVA_HOME), provide explicit instructions or links for Linux/macOS users.
- Where possible, use neutral language (e.g., 'Preferences' instead of 'Settings/Preferences') and avoid defaulting to Windows-first terminology.
- Add a note in the prerequisites or relevant sections confirming that all steps are valid for Linux and macOS, and highlight any differences.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-private-site-access.md
...zure-functions/functions-create-private-site-access.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias by exclusively guiding users to create a Windows Server VM, with no mention of Linux VM alternatives or examples. All screenshots and instructions for VM creation are Windows-centric, and there are no Linux-specific steps or parity in the walkthrough. This may unintentionally suggest that Windows is the default or preferred platform for this scenario, potentially alienating Linux users.
Recommendations
- Include instructions and screenshots for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
- Explicitly mention that either Windows or Linux VMs can be used for accessing Azure Functions within a virtual network.
- Provide parity in examples for connecting to the VM (e.g., SSH for Linux, RDP for Windows) and clarify Bastion supports both.
- Where VM OS selection is discussed, present Windows and Linux options equally, not Windows-first.
- Add troubleshooting or notes relevant to Linux users (e.g., browser access, command-line tools).
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-use-nat-gateway.md
...es/azure-functions/functions-how-to-use-nat-gateway.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by explicitly recommending Windows as the operating system for the function app and providing no guidance or examples for Linux-based deployments. There are no Linux-specific instructions, notes, or parity checks, and the only runtime stack mentioned is .NET. This may lead Linux users to believe the tutorial is not applicable to them or that Linux is not supported.
Recommendations
- Provide explicit instructions and notes for both Windows and Linux operating systems when creating the function app, including any differences in configuration or limitations.
- Include examples or screenshots for Linux-based function apps where the Azure portal UI or workflow differs.
- Clarify whether the tutorial steps and code samples are applicable to Linux, and if not, specify any limitations or required changes.
- Mention Linux as a supported option in the prerequisites and throughout the tutorial, ensuring parity in recommendations.
- If there are platform-specific behaviors (e.g., outbound IP address handling), document them clearly for both Windows and Linux.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reliable-event-processing.md
...azure-functions/functions-reliable-event-processing.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation does not provide explicit examples or instructions for either Windows or Linux environments, but it does reference .NET/C#-specific libraries (e.g., Polly) and does not mention Linux-specific tools, patterns, or code samples. There are no PowerShell or Windows command-line examples, but the focus on C# and Azure-centric tools may implicitly favor Windows developers. No Linux-first or cross-platform parity is demonstrated.
Recommendations
- Include code samples in multiple languages (e.g., Python, JavaScript) that are popular on Linux, not just C#.
- Reference cross-platform retry and resilience libraries (e.g., Tenacity for Python, or libraries for Node.js) alongside Polly.
- Explicitly mention that Azure Functions and Event Hubs triggers are supported on both Windows and Linux, and provide any Linux-specific considerations if applicable.
- Add examples or links for deploying and managing Azure Functions from Linux environments (e.g., using Azure CLI/Bash scripts).
- Ensure that all guidance (such as error handling and circuit breaker patterns) is language- and platform-agnostic, or provide parity across platforms.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/monitor-functions-reference.md
...rticles/azure-functions/monitor-functions-reference.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation page demonstrates a bias toward Windows by omitting Linux-specific monitoring examples and by noting that certain metrics are unavailable on Linux Consumption plans without providing Linux alternatives or workarounds. The documentation implicitly assumes Windows as the default environment, with Linux support mentioned only as an exception.
Recommendations
- Provide explicit Linux examples and guidance for monitoring Azure Functions on Linux Consumption plans.
- Clearly indicate which metrics and features are supported on Linux, and suggest alternative monitoring strategies or tools for unsupported metrics.
- Ensure that Linux and Windows are presented with equal prominence, including parallel documentation sections or tabs for both platforms.
- Add troubleshooting or FAQ sections addressing common Linux-specific monitoring limitations and solutions.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/run-functions-from-deployment-package.md
...ure-functions/run-functions-from-deployment-package.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation consistently mentions Windows paths and deployment patterns before Linux equivalents (e.g., 'c:\home\site\wwwroot' before '/home/site/wwwroot'), and references Windows-specific tools and terminology (e.g., MSDeploy, c: drive paths). There are no explicit Linux command-line examples or Linux-first workflows, and the guidance is generally Windows-centric, with Linux support described as exceptions or alternatives.
Recommendations
- Alternate the order of Windows and Linux paths and examples to avoid always listing Windows first.
- Provide Linux-specific command-line examples (e.g., using Bash, zip, or Linux-native tools) alongside or before Windows/Powershell equivalents.
- Reference Linux deployment patterns and tools (such as SCP, rsync, or Azure CLI on Linux) where appropriate.
- Clarify when a feature or setting behaves differently on Linux, and provide Linux-first guidance where Linux is the primary or only supported platform (e.g., Consumption plan).
- Avoid exclusive references to Windows tools like MSDeploy; mention Linux alternatives or clarify cross-platform options.
- Include screenshots or UI walkthroughs from both Windows and Linux environments where relevant.
Azure Health Insights
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-health-insights/includes/example-inference-follow-up-communication-json-request.md
...example-inference-follow-up-communication-json-request.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page references 'Powerscribe', a proprietary radiology dictation/transcription tool that is primarily Windows-based, and mentions faxing resultsâa workflow more common in Windows-centric healthcare environments. No Linux or cross-platform alternatives or examples are provided, and the only tool mentioned is Windows-specific.
Recommendations
- Include examples or references to cross-platform or Linux-compatible tools for radiology report transmission and dictation (e.g., open-source PACS viewers, Linux-based fax solutions, or HL7 messaging tools).
- Provide sample workflows or code snippets that demonstrate interoperability with Linux systems.
- Mention alternatives to Powerscribe that are available on Linux or web platforms.
- Avoid assuming Windows-only workflows (such as faxing via Windows drivers) and describe platform-agnostic approaches.
Azure Health Insights
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-health-insights/use-containers.md
.../main/articles/azure-health-insights/use-containers.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits mild Windows bias. Windows-specific requirements (such as Docker needing to support Linux containers) are mentioned before any Linux equivalents. The page refers to PowerShell and Azure CLI scripts for automation, but does not provide equivalent Bash or Linux shell script examples. There is no explicit Linux example for automation, and Windows terminology (e.g., 'host computer', 'Ctrl+C' for stopping containers) is used throughout, though most commands are cross-platform.
Recommendations
- Add explicit Linux/Bash shell script examples for automating resource deployment and container configuration, alongside PowerShell.
- Mention Linux prerequisites and troubleshooting steps with equal prominence as Windows (e.g., Docker installation/configuration on Linux).
- Clarify line continuation differences for both Windows (PowerShell) and Linux (Bash), giving examples for each.
- Use neutral terminology (e.g., 'host system' instead of 'host computer') and clarify cross-platform steps where relevant.
- Provide troubleshooting and stopping instructions for both Windows (Ctrl+C) and Linux (e.g., SIGINT, kill commands).
Azure Large Instances
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/configure-azure-service-health-alerts.md
...rge-instances/configure-azure-service-health-alerts.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes configuring Azure Service Health alerts via the Azure portal GUI, which is a cross-platform web interface. However, it does not mention or provide examples for command-line or automation options, such as using Azure CLI, PowerShell, or REST API. There is an implicit Windows bias because, in Azure documentation, PowerShell is often the first or only automation example, and Linux users may expect Azure CLI or bash examples. The absence of any CLI or automation guidance means Linux users are not equally supported.
Recommendations
- Add Azure CLI examples for configuring Service Health alerts, as Azure CLI is cross-platform and widely used by Linux users.
- If PowerShell examples are added, ensure Azure CLI or REST API equivalents are also provided.
- Explicitly mention that the Azure portal is accessible from any OS, but provide automation options for users who prefer or require command-line tools.
- Include links to official documentation for configuring alerts via Azure CLI, PowerShell, and REST API.
Azure Large Instances
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/faq.md
...e-docs/blob/main/articles/azure-large-instances/faq.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page for Azure Large Instances FAQ demonstrates a subtle Windows bias. All operational guidance, troubleshooting, and alerting instructions reference the Azure portal and Service Health alerts, which are typically accessed via web UI or Windows-centric tools. There are no examples or mentions of Linux-specific tools, command-line interfaces, or automation patterns (such as Azure CLI or Bash scripting). No PowerShell commands are shown, but the absence of Linux alternatives and the general assumption of portal usage suggest a Windows-first approach.
Recommendations
- Include examples using Azure CLI commands for common tasks (e.g., registering resource providers, configuring alerts), which are cross-platform and widely used on Linux.
- Mention Linux-compatible monitoring and alerting tools (such as integration with Nagios, Zabbix, or Prometheus) for customers who prefer open-source solutions.
- Provide guidance for automation using Bash scripts or other Linux shell environments alongside portal instructions.
- Explicitly state that all instructions are applicable on both Windows and Linux, or clarify any platform-specific steps.
- Add troubleshooting steps or examples that use Linux-native tools (e.g., curl, jq) for interacting with Azure APIs.
Azure Large Instances
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/find-your-subscription-id.md
...les/azure-large-instances/find-your-subscription-id.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation only describes how to find the subscription ID using the Azure portal, which is a web-based GUI. It does not provide any command-line examples or alternatives, such as using Azure CLI or PowerShell. While the instructions are not explicitly Windows-specific, the lack of CLI examples can be seen as a bias towards Windows/GUI users, as Linux users often prefer or require CLI instructions.
Recommendations
- Add Azure CLI examples for finding the subscription ID, as Azure CLI is cross-platform and widely used on Linux.
- If mentioning PowerShell, ensure Azure CLI instructions are given equal prominence and appear before or alongside PowerShell examples.
- Clarify that the portal method works on all platforms, but also provide command-line alternatives for users who may not use the GUI.
Azure Large Instances
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/what-is-azure-large-instances.md
...azure-large-instances/what-is-azure-large-instances.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is generally neutral but exhibits subtle Windows bias by omitting Linux-specific operational examples and by not providing parity in management tooling references. While it mentions Red Hat Enterprise Linux (RHEL) as the OS, there are no Linux command-line examples, nor are Linux-native tools or patterns (e.g., SSH, Linux scripting, or Linux-based management) discussed. The documentation also references Azure management via the portal but does not clarify cross-platform CLI or scripting options, which may leave Linux users underserved.
Recommendations
- Add Linux-specific operational examples, such as using SSH for access, Linux command-line tools for management, and scripting examples (e.g., Bash).
- Explicitly mention cross-platform management tools (e.g., Azure CLI, which is available on Linux, macOS, and Windows) and provide sample commands.
- If referencing Azure portal or management patterns, clarify that these are OS-agnostic or provide Linux-specific alternatives where appropriate.
- Include references to Linux-native backup, monitoring, and automation tools that could be used with Azure Large Instances.
- Ensure that any future examples or troubleshooting steps include both Windows and Linux approaches, or are clearly cross-platform.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-daemon-app.md
...b/main/articles/azure-maps/how-to-secure-daemon-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by listing 'Windows Service' as a primary example of a daemon application, while not mentioning Linux equivalents such as 'systemd service' or 'Linux daemon.' There are no explicit Linux or cross-platform examples provided for hosting or configuring daemon applications, nor are Linux-specific tools or patterns referenced. The instructions and screenshots focus exclusively on Azure Portal and general Azure concepts, without addressing Linux hosting scenarios or command-line examples (e.g., systemd, bash, etc.).
Recommendations
- Include Linux-specific examples for hosting daemon applications, such as referencing 'systemd service' alongside 'Windows Service.'
- Add instructions or code samples for configuring authentication and secrets retrieval in Linux environments (e.g., using bash, curl, or systemd service files).
- Provide parity in terminology and examples, ensuring both Windows and Linux hosting scenarios are addressed equally.
- Where possible, include cross-platform SDK usage or REST API calls from both Windows and Linux perspectives.
- Explicitly mention Linux as a supported environment for daemon applications in Azure Maps, and link to relevant Linux documentation.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-device-code.md
.../main/articles/azure-maps/how-to-secure-device-code.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by referencing 'Desktop app' scenarios and providing instructions and links that implicitly target Windows environments. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools or patterns mentioned. The guidance assumes use of Microsoft Authentication Library (MSAL) and desktop application flows, which are typically associated with Windows, without clarifying Linux compatibility or providing Linux-centric instructions.
Recommendations
- Add explicit Linux examples for device code flow authentication, including command-line usage and sample code for common Linux languages (e.g., Python, Bash).
- Clarify that MSAL libraries are available for Linux and provide installation instructions for Linux environments.
- Include screenshots or instructions for registering applications and configuring authentication using Linux tools (e.g., Azure CLI, cross-platform editors).
- Reference cross-platform or Linux-specific documentation where relevant, and avoid assuming a desktop/Windows environment in examples and terminology.
- Mention and demonstrate how to make REST API calls using Linux-native tools (e.g., curl, wget) in addition to generic HTTP clients.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/power-bi-visual-conversion.md
...main/articles/azure-maps/power-bi-visual-conversion.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page assumes the use of Power BI Desktop, which is only available on Windows. There are no mentions of Linux or cross-platform alternatives, nor are there instructions or guidance for users on Linux or macOS. All examples and migration steps are implicitly Windows-centric due to Power BI Desktop's platform limitation.
Recommendations
- Explicitly state that Power BI Desktop is only available on Windows, and clarify options for Linux/macOS users (e.g., using Power BI Service, remote desktop solutions, or alternatives).
- If possible, provide guidance for users who need to perform these tasks from non-Windows environments, such as using Power BI Service or other supported methods.
- Mention any known limitations or workarounds for Linux/macOS users regarding map visual migration.
- Consider including a note about platform support at the beginning of the article to set expectations for cross-platform users.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-configure-nfsv41-domain.md
...pp-files/azure-netapp-files-configure-nfsv41-domain.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias by presenting Azure PowerShell commands as the primary method for registering and checking the NFSv4.1 ID domain feature, with Azure CLI (which is more cross-platform and Linux-friendly) only mentioned secondarily in a note. The main configuration and troubleshooting examples are Linux-focused, but the initial management steps are Windows-centric.
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell commands for feature registration and status checking.
- Explicitly state that all management steps can be performed from Linux or macOS using Azure CLI, and provide corresponding commands.
- Where possible, use neutral language (e.g., 'using Azure CLI or PowerShell') and avoid defaulting to Windows tooling.
- Consider including a table or section comparing PowerShell and CLI commands for common tasks to help users on different platforms.
- Review other sections for similar patterns and ensure Linux-first or parity in all procedural steps.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-considerations.md
...etapp-files/application-volume-group-considerations.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through the use of Windows-centric links and examples. For instance, the reference to 'Create a PPG using the Azure portal' links specifically to the Windows VM documentation, with no mention of Linux VM equivalents or examples. There are no Linux-specific instructions, examples, or references, despite SAP HANA commonly running on Linux. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.
Recommendations
- Add explicit references and links to Linux VM documentation, such as 'Create a PPG using the Azure portal for Linux VMs'.
- Include Linux-specific examples and instructions wherever VM or resource creation is discussed.
- Ensure that all procedural steps (e.g., VM pinning, proximity placement group creation) are covered for both Windows and Linux environments.
- Review all cross-references and ensure Linux parity in linked articles and guides.
- Consider a dedicated section or callouts for Linux users, especially in SAP HANA contexts where Linux is the primary OS.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-cmd-ref-details.md
...rticles/azure-netapp-files/azacsnap-cmd-ref-details.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page provides command-line examples for the Azure Application Consistent Snapshot tool but does not specify or show any Linux-specific usage, shell, or output. There is no mention of Linux environments, and all examples are generic or reference Azure Large Instance (which is typically Windows-based), with no explicit Linux context or parity. The documentation does not clarify whether the tool or commands are cross-platform, nor does it provide Linux-specific guidance or troubleshooting.
Recommendations
- Explicitly state whether the azacsnap tool and commands are supported on Linux, and if so, provide at least one example run on a Linux system (e.g., Ubuntu, RHEL).
- Include Linux shell (bash) output examples, especially if there are differences in output or behavior compared to Windows/Azure Large Instance.
- Mention any Linux-specific prerequisites, environment variables, or configuration file locations if applicable.
- Clarify in the introduction or a compatibility section which platforms are supported and highlight any differences in usage or output.
- If the tool is not supported on Linux, explicitly state this to avoid confusion.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md
...-netapp-files-quickstart-set-up-account-create-volumes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity between Azure Portal, PowerShell, Azure CLI, ARM Template, and Terraform for all major steps. However, there is a subtle Windows bias: PowerShell examples are given their own dedicated sections, and PowerShell is mentioned before Azure CLI in several places. There is no explicit mention of Linux-specific shell usage (e.g., Bash), nor are there any Linux-specific command-line patterns or troubleshooting notes. The CLI examples are generic and could be run from Bash, but this is not clarified. The documentation also refers to 'PowerShell Cloud Shell' but does not mention Bash Cloud Shell, which is available and commonly used by Linux users.
Recommendations
- Explicitly mention that Azure CLI commands can be run from Bash (Linux/macOS) or Windows Command Prompt/PowerShell.
- Add examples or notes for Bash Cloud Shell usage where PowerShell Cloud Shell is referenced.
- Ensure that Azure CLI is mentioned before or alongside PowerShell in introductory sentences to avoid Windows-first ordering.
- Consider adding troubleshooting notes or tips relevant to Linux environments (e.g., file permissions, environment variables).
- Where variables are defined for CLI, show both Bash and PowerShell syntax if relevant.
- Clarify that all command-line steps are cross-platform unless a step is Windows-specific.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-application-volume-oracle-azure-resource-manager.md
...igure-application-volume-oracle-azure-resource-manager.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes deployment using the Azure Portal GUI, which is most commonly accessed from Windows environments and is illustrated with Windows-style screenshots. There are no examples or instructions for deploying via CLI tools such as Azure CLI, Bash, or PowerShell, nor is there any mention of Linux-specific workflows or tools. This may disadvantage Linux users who prefer or require command-line automation.
Recommendations
- Add step-by-step instructions for deploying the ARM template using Azure CLI (az deployment group create) with Bash examples.
- Include PowerShell examples if relevant, but ensure Linux/Bash parity by presenting Bash or cross-platform CLI examples first.
- Mention that the Azure Portal is accessible from any OS, and clarify that the instructions are not Windows-specific.
- Provide sample commands for validating and deploying the template from Linux/macOS terminals.
- Link to documentation on using ARM templates with Azure CLI and Bash for Linux users.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/convert-nfsv3-nfsv41.md
...in/articles/azure-netapp-files/convert-nfsv3-nfsv41.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation shows a bias toward Windows by providing Azure PowerShell commands as the primary example for feature registration, with Azure CLI only mentioned secondarily and without explicit command examples. There are no Linux-specific CLI examples for feature registration, and the initial registration steps are presented with PowerShell syntax. However, the main NFS conversion workflow and client-side examples are Linux-focused, using Linux commands and mount options.
Recommendations
- Provide explicit Azure CLI examples (with full command syntax) for feature registration and status checking alongside PowerShell examples.
- List Azure CLI commands before or alongside PowerShell commands to avoid the impression of Windows-first bias.
- Clarify that all client-side steps and examples are Linux-based, and add a note if Windows NFS clients are not supported or relevant.
- Where possible, include Bash or shell script equivalents for any automation steps currently shown only in PowerShell.
- Ensure parity in all command-line examples by always showing both PowerShell and CLI (and/or Bash) alternatives.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-region-replication-delete.md
.../azure-netapp-files/cross-region-replication-delete.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides instructions primarily through GUI interactions (e.g., right-clicking, selecting menu items) that are typical of Windows environments, without mentioning CLI or Linux-native methods. There are no examples using Linux tools, shell commands, or cross-platform Azure CLI/PowerShell alternatives. The screenshots and terminology (right-click, select, etc.) suggest a Windows-centric approach, and Linux users may not find guidance for their workflows.
Recommendations
- Add equivalent instructions using Azure CLI and/or REST API, which are cross-platform and commonly used on Linux.
- Include examples for deleting replications and volumes using shell commands (bash), and clarify any differences in workflow for Linux users.
- Explicitly mention that the GUI steps can be performed from any OS via the Azure Portal, or provide OS-agnostic language.
- Where screenshots are used, note that the interface is accessible from any browser, regardless of OS.
- Consider adding a section titled 'Command-line steps (Linux/Mac/Windows)' to ensure parity and inclusivity.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-integration.md
...ob/main/articles/azure-netapp-files/faq-integration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation tends to mention Windows examples and use cases before Linux equivalents. For instance, in the section about mounting Azure NetApp Files volumes, Windows VMs are mentioned first for both NFS and SMB, and only Windows VMs are mentioned for SMB. There are no explicit Linux command examples or detailed Linux instructions, which may leave Linux users with less guidance.
Recommendations
- Ensure that Linux examples and use cases are mentioned alongside or before Windows examples, especially for common operations like mounting NFS or SMB shares.
- Provide explicit instructions or references for mounting Azure NetApp Files SMB shares on Linux VMs, if supported, or clarify if it is not supported.
- Include command-line examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., mount commands) where relevant.
- Review the order of OS mentions to avoid consistently prioritizing Windows over Linux.
- Add links to Linux-specific documentation or troubleshooting guides where appropriate.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-default-individual-user-group-quotas.md
...p-files/manage-default-individual-user-group-quotas.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation displays a Windows bias by providing detailed quota target formats for SMB (Windows) and dual-protocol volumes using SMB, while only briefly mentioning NFS (Linux/Unix) without example formats or further explanation. The SMB (Windows) format is described in detail and appears before the NFS (Linux) format in dual-protocol guidance. There are no Linux-specific command-line or tool examples, and the documentation does not reference Linux administration patterns or tools.
Recommendations
- Provide example quota target formats for NFS (Linux/Unix) users, including typical UID/GID values and how to obtain them on Linux systems.
- Include Linux command-line examples (e.g., using 'id', 'getent', or other relevant tools) for determining user/group IDs for quota assignment.
- Balance the order of protocol descriptions so that NFS (Linux/Unix) and SMB (Windows) are presented with equal prominence and detail.
- Reference Linux administration tools or patterns where appropriate, especially in sections discussing quota management for NFS volumes.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/object-rest-api-onelake.md
...articles/azure-netapp-files/object-rest-api-onelake.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references the 'on-premises data gateway', which is primarily a Windows-only tool, without mentioning Linux alternatives or providing guidance for Linux users. There are no examples or instructions for Linux environments, and the documentation implicitly assumes a Windows setup.
Recommendations
- Explicitly state the platform requirements for the on-premises data gateway, including its lack of Linux support.
- If possible, provide or reference alternative solutions for Linux environments, such as Azure Data Factory Integration Runtime (if supported) or containerized gateway options.
- Add a note for Linux users about current limitations and any workarounds or roadmap for Linux support.
- Ensure future documentation includes parity for Linux users, with examples and instructions relevant to both Windows and Linux platforms.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-node-get-started-server.md
...es/relay-hybrid-connections-node-get-started-server.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation refers to running npm install from a 'Node command prompt', which is a Windows-specific term, and does not provide any Linux or cross-platform equivalent. There are no explicit Linux instructions or examples, and the only command-line context is Windows-oriented.
Recommendations
- Replace 'Node command prompt' with a cross-platform term such as 'terminal' or 'command line'.
- Explicitly state that the instructions work on Windows, Linux, and macOS.
- Add a note or example showing the npm install command in a Linux or macOS terminal.
- Ensure that any references to command-line environments are platform-neutral or provide alternatives for each major OS.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/reestablish-deleted-volume-relationships.md
...tapp-files/reestablish-deleted-volume-relationships.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation primarily provides Azure PowerShell examples for feature registration, with PowerShell commands shown first and in detail. Azure CLI (which is cross-platform and preferred on Linux) is only mentioned briefly in text, with no explicit command examples. There are no Linux-specific instructions or screenshots, and the workflow assumes familiarity with Windows-centric tools.
Recommendations
- Provide explicit Azure CLI command examples (e.g., 'az feature register ...') alongside PowerShell, not just as a mention.
- List Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Include notes or sections for Linux/macOS users, especially for command-line operations.
- Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific differences.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/restore-single-file-backup.md
...icles/azure-netapp-files/restore-single-file-backup.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation demonstrates a Windows bias by providing Azure PowerShell commands first and in detail for feature registration, with Azure CLI (which is more cross-platform and Linux-friendly) only mentioned briefly in text and without explicit command examples. No Linux-specific tools or shell examples are provided.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell examples for all steps, not just a mention.
- Consider including Bash or shell script equivalents where applicable, especially for registration steps.
- Ensure that cross-platform (Linux/macOS) users are addressed equally in all command-line instructions.
- If screenshots or UI elements are OS-specific, clarify their applicability or provide Linux/macOS equivalents.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-restore-file-client.md
...es/azure-netapp-files/snapshots-restore-file-client.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Linux and Windows client instructions for restoring files from Azure NetApp Files snapshots. However, the Windows section includes additional GUI-based restore options (such as Previous Versions tab) and multiple screenshots, while the Linux section is limited to basic command-line usage. Windows-specific tools and patterns (GUI, Previous Versions) are highlighted, and the Windows section is more visually detailed.
Recommendations
- Expand the Linux section to include alternative restore methods, such as using file managers (e.g., Nautilus, Dolphin) to access .snapshot directories via GUI, if supported.
- Add screenshots for the Linux workflow to match the visual detail of the Windows section.
- Mention Linux desktop environments and how hidden directories can be revealed, similar to the Windows 'show hidden items' step.
- If available, describe integration with Linux backup/restore tools or file versioning features.
- Ensure parity in the depth of explanation and visual aids between Linux and Windows instructions.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/solutions-benefits-azure-netapp-files-sql-server.md
...es/solutions-benefits-azure-netapp-files-sql-server.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively discusses SQL Server deployment scenarios, cost analysis, and performance metrics using Azure NetApp Files, but all examples, benchmarks, and tooling references are centered on SQL Serverâa Windows-centric database. There are no references to Linux-based SQL Server deployments, nor examples or comparisons involving Linux tools, commands, or environments. The documentation implicitly assumes Windows as the platform, omitting Linux parity in both technical details and practical guidance.
Recommendations
- Include explicit guidance and examples for deploying SQL Server on Linux with Azure NetApp Files.
- Reference Linux-compatible benchmarking tools (e.g., sysbench, fio) alongside SSB and perfmon.
- Discuss any differences or considerations for SQL Server on Linux (e.g., supported distributions, configuration steps, performance characteristics).
- Add links to documentation for creating NFS volumes in Azure NetApp Files, not just SMB.
- Where VM instance types are discussed, clarify that both Windows and Linux VMs are supported and note any differences.
- Provide cost and performance comparisons for SQL Server on Linux VMs versus Windows VMs using Azure NetApp Files.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/test-disaster-recovery.md
.../articles/azure-netapp-files/test-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references the 'Azure Application Consistent Snapshot tool' (AzAcSnap), which is primarily a Windows-based tool, without mentioning Linux alternatives or providing Linux-specific guidance. There are no explicit examples or instructions for Linux environments, such as using native Linux snapshot tools or mounting NFS volumes on Linux VMs. The steps and tooling implicitly assume a Windows-centric workflow.
Recommendations
- Include information about creating application-consistent snapshots on Linux, such as using pre/post scripts with AzAcSnap (if supported) or alternative Linux-native tools.
- Provide explicit instructions or examples for mounting/unmounting Azure NetApp Files volumes on Linux VMs (e.g., using mount commands for NFS/CIFS).
- Mention and link to documentation for Linux-based disaster recovery testing workflows, ensuring parity with Windows guidance.
- Clarify if AzAcSnap supports Linux, and if not, suggest equivalent Linux solutions or workarounds.
- Ensure that both Windows and Linux environments are addressed equally in all steps, especially where OS-specific actions are required.
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 â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation focuses exclusively on creating a .NET Framework console application using Visual Studio, a Windows-centric IDE, and provides step-by-step instructions tailored for Windows users. There are no examples or guidance for Linux users, such as using .NET Core/SDK on Linux, alternative editors, or cross-platform development workflows.
Recommendations
- Add instructions for creating a .NET (Core/SDK) console application using the command line (dotnet CLI), which works on Linux, macOS, and Windows.
- Include examples for installing the NuGet package via the dotnet CLI, not just through Visual Studio.
- Mention alternative editors (e.g., VS Code) and how to set up the project on Linux.
- Clarify that the code sample works cross-platform and provide explicit steps for Linux users.
- Consider providing shell commands and Linux-specific notes where relevant.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-dotnet-api-overview.md
...-relay/relay-hybrid-connections-dotnet-api-overview.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides only .NET/C# code samples and does not mention or provide examples for Linux environments, cross-platform usage, or alternative tools. There is an implicit Windows-first bias due to the exclusive focus on .NET and lack of guidance for Linux users.
Recommendations
- Add explicit statements clarifying that the .NET Standard APIs and code samples are cross-platform and can be used on Linux and macOS, not just Windows.
- Include Linux-specific instructions or examples, such as how to run the code using .NET Core/SDK on Linux, and any platform-specific considerations.
- Mention and link to any relevant Linux tools or command-line patterns (e.g., using dotnet CLI on Linux) where appropriate.
- If there are platform-specific authentication or networking considerations (e.g., firewall, proxy), provide guidance for both Windows and Linux.
- Consider providing sample scripts or Dockerfiles for running the examples in a Linux container environment.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/volume-delete.md
...blob/main/articles/azure-netapp-files/volume-delete.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides only Azure Portal (GUI) instructions and omits any command-line examples. While it mentions unmounting the volume and removing it from automounter configurations (which are Linux-relevant), it does not provide explicit Linux (e.g., Bash/CLI) or Windows (e.g., PowerShell) command examples. However, the lack of CLI examples, especially for Linux users, and the use of GUI-centric steps (which are more familiar to Windows users) indicate a subtle Windows-first and missing Linux example bias.
Recommendations
- Add Azure CLI and/or Azure PowerShell examples for deleting a volume, with both Linux (Bash) and Windows (PowerShell) command syntax.
- Include explicit Linux commands for unmounting (e.g., `umount /mount/point`) and updating `fstab`.
- Provide parity in instructions by showing both GUI and command-line methods, and ensure Linux and Windows users are equally supported.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/volume-hard-quota-guidelines.md
...les/azure-netapp-files/volume-hard-quota-guidelines.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates a Windows bias in several ways. In the VM-level monitoring section, Windows examples (Explorer, dir command) are presented before Linux (df command), and with more screenshots and detailed steps. In the CLI/PowerShell section, PowerShell screenshots are used exclusively for command examples, even though Azure CLI is cross-platform and commonly used on Linux. There is no demonstration of Linux shell usage for Azure CLI commands, nor are there Bash examples or screenshots. The documentation also references Windows tools (Explorer, PowerShell) more prominently than Linux equivalents.
Recommendations
- Present Linux examples alongside Windows examples, not after them, and with equal detail and screenshots.
- Include Azure CLI command examples and screenshots from a Linux shell (e.g., Bash), not just PowerShell.
- Add instructions for using Azure CLI on Linux, including installation and usage in native Linux environments.
- When describing monitoring or management steps, alternate the order of Windows and Linux instructions, or present them in parallel.
- Ensure parity in troubleshooting and FAQ sections by including Linux-specific guidance where relevant.
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 â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation assumes the use of Visual Studio and the .NET Framework, both of which are traditionally Windows-centric. All instructions for creating the project and managing NuGet packages are given using Visual Studio GUI steps, with no mention of cross-platform alternatives (e.g., .NET Core/SDK CLI, Visual Studio Code, or JetBrains Rider). There are no examples or guidance for Linux or macOS users, nor any mention of how to set up or run the sample outside of a Windows/Visual Studio environment.
Recommendations
- Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
- Specify that the code works with .NET Core/.NET 5+ and not just .NET Framework, or clarify any limitations.
- Provide alternative steps for adding NuGet packages using the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
- Mention and provide examples for using cross-platform editors like Visual Studio Code.
- Explicitly state platform requirements and test the instructions on Linux/macOS to ensure parity.
- If any features are Windows-only, clearly document them and suggest workarounds or alternatives for Linux users.
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 â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by instructing users to create a console application specifically in Visual Studio, a Windows-centric IDE, and by referencing .NET Framework, which is primarily supported on Windows. There are no instructions or examples for creating the application on Linux or using cross-platform tools like .NET Core/SDK, nor is there mention of alternative editors or package management approaches suitable for Linux environments.
Recommendations
- Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
- Mention and provide examples for using Visual Studio Code or other cross-platform editors.
- Reference .NET Core or .NET 6+ instead of .NET Framework, as these are cross-platform.
- Include Linux-specific package installation steps (e.g., using 'dotnet add package') alongside or before Visual Studio steps.
- Clarify that the code and Azure Relay SDK are cross-platform, and provide explicit instructions for running on Linux.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/move-across-regions.md
.../blob/main/articles/azure-relay/move-across-regions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes moving an Azure Relay namespace using the Azure portal, with terminology and screenshots that are Windows-centric (e.g., ZIP file extraction, file navigation, and UI patterns familiar to Windows users). There are no examples or instructions for performing these steps via cross-platform command-line tools (such as Azure CLI, which runs on Linux, macOS, and Windows), nor is PowerShell mentioned, but the absence of Linux/macOS alternatives or parity is notable. All instructions assume use of the Azure portal, which is platform-agnostic but the workflow and file handling described are more familiar to Windows users.
Recommendations
- Add equivalent instructions for moving an Azure Relay namespace using Azure CLI commands, which are cross-platform.
- Include examples of extracting and editing the template.json file using Linux/macOS tools (e.g., unzip, nano, vim).
- Clarify that the Azure portal can be used from any OS, and provide tips for users on Linux/macOS for file handling and navigation.
- If possible, provide PowerShell and Bash script examples for automating the move process.
- Ensure screenshots and terminology are not exclusively Windows-centric (e.g., avoid references to Windows file paths or UI conventions).
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-exceptions.md
...ocs/blob/main/articles/azure-relay/relay-exceptions.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing .NET exception types, APIs, and configuration patterns, which are primarily relevant to Windows environments. There are no examples or guidance for Linux users, alternative SDKs, or cross-platform considerations. No Linux-specific troubleshooting steps, tools, or code samples are provided.
Recommendations
- Include examples and troubleshooting steps for Linux environments, such as using the Azure CLI or SDKs in Python/Node.js.
- Mention cross-platform SDKs and provide links or examples for non-.NET languages.
- Clarify when guidance is specific to .NET/Windows and offer Linux equivalents where possible.
- Add troubleshooting steps that reference common Linux networking tools (e.g., curl, netstat, iptables) for diagnosing connectivity issues.
- Provide parity in code samples and configuration advice for both Windows and Linux users.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/relay-hybrid-connections-http-requests-dotnet-get-started.md
...ay-hybrid-connections-http-requests-dotnet-get-started.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation assumes and requires Visual Studio (a Windows-centric IDE) for all examples, without mentioning or providing alternatives for Linux users. There are no instructions or examples for developing or running the .NET applications on Linux (e.g., using VS Code, JetBrains Rider, or the dotnet CLI). The prerequisites and steps are Windows-focused, leading to a lack of parity for Linux developers.
Recommendations
- Add instructions for setting up the development environment on Linux, such as installing the .NET SDK and using VS Code or the dotnet CLI.
- Provide Linux-specific steps for creating, building, and running the server and client applications (e.g., using 'dotnet new console', 'dotnet run').
- Mention cross-platform editors (VS Code, Rider) as alternatives to Visual Studio.
- Clarify that the .NET code and Azure Relay features are cross-platform, and explicitly state that the tutorial can be followed on Linux and macOS.
- Include screenshots or terminal output from Linux environments where appropriate.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-cloud-shell.md
...les/azure-resource-manager/bicep/deploy-cloud-shell.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents both Azure CLI (Bash) and PowerShell examples, but PowerShell is mentioned before Bash in several places (e.g., 'Select either PowerShell or Bash', image alt-text), and the 'Next steps' section lists PowerShell resources before CLI ones. This ordering subtly prioritizes Windows/PowerShell workflows. However, both Bash (Linux) and PowerShell examples are provided, so there is not a complete absence of Linux parity.
Recommendations
- List Bash (Azure CLI) before PowerShell when presenting options, to avoid implicit prioritization of Windows tools.
- Use 'Bash or PowerShell' consistently instead of 'PowerShell or Bash' in instructions and image alt-text.
- Alternate the order of CLI and PowerShell examples in 'Next steps' or group them together to show equal support.
- Explicitly state that both Bash (Linux) and PowerShell (Windows) are supported equally in Cloud Shell.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-null-forgiving.md
...zure-resource-manager/bicep/operator-null-forgiving.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page references Azure CLI and Azure PowerShell as the tools to run the examples, listing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and does not mention Linux-native shells or deployment methods. There are no explicit Linux examples or references to Bash, and PowerShell is mentioned before any Linux equivalent.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Provide example commands for deploying Bicep files using Bash or other Linux-native shells.
- List Azure CLI before Azure PowerShell when suggesting deployment tools, as CLI is more platform-agnostic.
- Add a note or section clarifying that all examples are platform-independent unless otherwise stated.
- Consider including a Linux-specific 'Next steps' bullet, such as using Bash with Azure CLI.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operators-access.md
...icles/azure-resource-manager/bicep/operators-access.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates a subtle Windows bias by mentioning Azure PowerShell before Azure CLI in the 'Next steps' section and by not providing any explicit Linux/macOS-specific guidance or examples. All command-line references are platform-neutral but default to Windows-centric tools and order. There are no explicit Linux examples or mentions of using Bicep on Linux/macOS, nor are there any references to shell environments other than PowerShell.
Recommendations
- When referencing deployment tools, mention Azure CLI before Azure PowerShell, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that all examples and tools are cross-platform unless otherwise noted.
- Add a note or section clarifying that Bicep and the Azure CLI are fully supported on Linux/macOS, and provide links to relevant installation guides for those platforms.
- Where possible, provide example commands for both Azure CLI (bash/zsh) and Azure PowerShell, or clarify that the steps are identical across platforms.
- Avoid implying that PowerShell is the default or primary method for deployment unless there is a technical reason.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-protect-commandtoexecute-secrets.md
.../bicep/linter-rule-protect-commandtoexecute-secrets.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation references the Windows Custom Script Extension before the Linux equivalent and links to the Windows documentation first. There are no explicit Linux-specific examples or commands, and the pattern of mentioning Windows tools before Linux ones suggests a Windows-first bias.
Recommendations
- Mention both Windows and Linux Custom Script Extension documentation together, or list Linux first in some instances to balance ordering.
- Provide explicit examples or notes for both Windows and Linux scenarios, especially if there are differences in usage.
- Ensure parity in documentation links and guidance for both platforms.
- Consider adding a Linux-specific example or clarifying if the example provided is cross-platform.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-use-stable-vm-image.md
...ource-manager/bicep/linter-rule-use-stable-vm-image.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation only provides examples using Windows Server VM images (including both the failing and fixed cases), without any mention or examples of Linux-based images. This presents a Windows-first bias and omits Linux parity in usage examples.
Recommendations
- Add equivalent examples using popular Linux VM images (e.g., Ubuntu, CentOS) to demonstrate the rule's applicability across platforms.
- Explicitly mention that the rule applies to both Windows and Linux VM images.
- Where possible, alternate the order of examples or provide both Windows and Linux examples side-by-side to avoid platform bias.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operators-numeric.md
...cles/azure-resource-manager/bicep/operators-numeric.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page demonstrates a mild Windows bias by mentioning Azure PowerShell (a Windows-centric tool) before Azure CLI and by referencing Visual Studio Code (which, while cross-platform, is often associated with Windows) as the primary editor for Bicep files. No explicit Linux examples or Linux-specific tools are provided, and the deployment instructions do not clarify parity or differences for Linux users.
Recommendations
- List Azure CLI before Azure PowerShell when suggesting deployment tools, as Azure CLI is more platform-neutral and widely used on Linux.
- Explicitly mention that all examples work on Linux, macOS, and Windows, and provide a sample Azure CLI command for deploying a Bicep file.
- Include a note or section on using alternative editors (such as Vim or VS Code on Linux) for authoring Bicep files.
- If referencing PowerShell, also mention Bash or shell equivalents where relevant.
- Ensure that all instructions and examples are validated on Linux platforms and clarify any OS-specific requirements.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/tutorial-resource-onboarding.md
...nager/custom-providers/tutorial-resource-onboarding.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes deployment using the Azure portal UI, which is most accessible and familiar to Windows users. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), and no mention of Linux or cross-platform tools. All screenshots and instructions are portal-centric, which may disadvantage Linux users who often prefer or require CLI-based workflows.
Recommendations
- Add Azure CLI examples for deploying the ARM template, including commands for parameter input and deployment verification.
- Include Bash script snippets for common tasks, such as copying the template and deploying it from the terminal.
- If PowerShell examples are added, ensure Azure CLI or Bash equivalents are provided and shown first or side-by-side.
- Mention that the Azure portal is cross-platform, but highlight CLI-based workflows for users on Linux or macOS.
- Provide links to official Azure CLI documentation for template deployment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/microsoft-compute-sizeselector.md
...managed-applications/microsoft-compute-sizeselector.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a schema example that exclusively uses Windows values for 'osPlatform' and 'imageReference', without showing equivalent Linux values or examples. While the remarks mention that 'osPlatform' can be either Windows or Linux, all concrete examples and defaults are Windows-centric.
Recommendations
- Add a parallel schema example using 'osPlatform': 'Linux' and a representative Linux 'imageReference' (e.g., Ubuntu or CentOS).
- Explicitly show both Windows and Linux options in sample code and outputs.
- Where possible, alternate the order of Windows and Linux mentions, or present them together, to avoid implicit prioritization.
- Clarify in remarks or notes that all features and options are equally supported for Linux, and provide links to relevant Linux image references.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/microsoft-compute-usernametextbox.md
...aged-applications/microsoft-compute-usernametextbox.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page describes a UI element supporting both Windows and Linux user names, but the primary schema example and regex validation pattern are tailored for Windows (alphanumeric only, which is typical for Windows user names). The 'osPlatform' property in the schema is set to 'Windows', and there is no equivalent Linux example or Linux-specific validation pattern provided. Linux is only mentioned in passing, and no Linux-centric usage or validation is demonstrated.
Recommendations
- Provide a schema example with 'osPlatform' set to 'Linux', including a Linux-appropriate regex pattern and validation message.
- Add remarks or a table describing the differences in built-in validation between Windows and Linux user names.
- Ensure that both Windows and Linux usage patterns are equally represented in examples and documentation sections.
- Consider including a sample output or UI screenshot for a Linux user name scenario.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/create-private-link-access-portal.md
...anager/management/create-private-link-access-portal.md
Medium Priority
View Details â
Detected Bias Types
portal_only
missing_linux_example
Summary
The documentation exclusively describes how to create and manage Azure Private Links using the Azure portal, without providing any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). This approach omits Linux-centric workflows and tools, which are commonly used by Linux users and administrators.
Recommendations
- Add Azure CLI examples for each step, as the Azure CLI is cross-platform and widely used on Linux.
- If relevant, include Bash script snippets to automate the process for Linux users.
- Explicitly mention that the steps can also be performed using command-line tools, and provide links to relevant documentation for Azure CLI and PowerShell.
- Ensure that any references to command-line tools do not prioritize PowerShell or Windows tools over cross-platform alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/delete-resource-group.md
...e-resource-manager/management/delete-resource-group.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for deleting resource groups and resources using PowerShell, Azure CLI, Portal, and Python. PowerShell examples are consistently presented first, which may indicate a Windows-first bias. While Azure CLI is cross-platform and included, there are no explicit Linux shell (e.g., Bash) or scripting examples, and no mention of Linux-specific tools or workflows. The documentation does not provide Linux-specific context or parity in the ordering or depth of examples.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first to reflect cross-platform parity.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash scripts for common deletion tasks.
- Add a section or note highlighting Linux/macOS usage patterns, such as using Bash scripting or integrating with Linux automation tools.
- Where PowerShell-specific syntax is used, provide equivalent Bash or shell scripting examples to ensure Linux users are equally supported.
- Review the documentation to ensure that no implicit assumption is made that users are on Windows, and clarify any platform-specific requirements.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resources-cli.md
...re-resource-manager/management/manage-resources-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is generally cross-platform, using Azure CLI and shell scripting compatible with both Linux and Windows. However, there is a notable Windows-first bias in the 'Deploy a template' section, where the primary link for creating ARM templates references a Visual Studio Code quickstart with a PowerShell tab, and PowerShell is mentioned in the URL tab parameter. There are no explicit Linux-only examples or references to Linux-specific tools/editors (e.g., Vim, nano), and the documentation does not mention Bash or Linux shell environments, which may implicitly favor Windows users.
Recommendations
- Provide explicit mention that the CLI examples work in both Bash (Linux/macOS) and PowerShell (Windows), or show both shell environments where relevant.
- In the 'Deploy a template' section, include links to quickstarts or guides using Linux-native editors (e.g., Vim, nano) or the Azure CLI in Bash.
- Avoid referencing PowerShell tabs or examples as the default in cross-platform documentation; instead, use Bash or a neutral shell.
- Add a note clarifying that all scripts are compatible with Linux, macOS, and Windows (with WSL or Git Bash), and provide troubleshooting tips for each OS if needed.
- When linking to external resources, ensure parity by including both Windows and Linux-focused guides.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-to-azure-button.md
...e-resource-manager/templates/deploy-to-azure-button.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a PowerShell example for URL encoding but does not offer equivalent Linux/macOS (e.g., bash, curl, or Python) examples. This creates a bias towards Windows users and may hinder Linux users who are unfamiliar with PowerShell.
Recommendations
- Add a bash example using 'python3 -c', 'jq', or 'perl' for URL encoding.
- Mention common Linux tools (e.g., 'curl', 'urlencode', or 'python3') alongside PowerShell.
- Wherever a command-line example is given, provide both Windows (PowerShell) and Linux/macOS (bash) equivalents.
- Clarify that the PowerShell example is for Windows and provide a Linux/macOS alternative.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md
...ement/move-limitations/app-service-move-limitations.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Azure portal (a GUI tool most familiar to Windows users) and not providing any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). There are no Linux-specific instructions or examples, and no mention of cross-platform tools or terminal-based workflows. The only tool mentioned for diagnostics and migration is the Azure portal, which is browser-based and often associated with Windows-centric workflows.
Recommendations
- Add Azure CLI examples for moving App Service resources, as the CLI is cross-platform and widely used on Linux.
- Include Bash script snippets for common operations, such as finding the original resource group or moving resources.
- Mention PowerShell only alongside Azure CLI, and provide parity in examples for both tools.
- Reference command-line alternatives for all portal-based steps, ensuring Linux users can follow along without relying on the GUI.
- Explicitly state that all operations can be performed from Linux, macOS, or Windows environments using the Azure CLI.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-grid-custom-topics.md
...ment/relocation/relocation-event-grid-custom-topics.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and examples, with no mention of command-line alternatives such as Azure CLI, PowerShell, or REST API. While this avoids explicit Windows tool bias, it implicitly favors Windows users by not providing Linux-friendly command-line instructions. There are no examples for Linux users or guidance on using cross-platform tools, and the workflow assumes graphical interaction typical of Windows environments.
Recommendations
- Add step-by-step instructions for relocating Event Grid custom topics using Azure CLI, which is cross-platform and widely used on Linux.
- Include PowerShell examples for parity, but ensure Azure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
- Reference REST API methods for advanced users who may prefer scripting or automation, regardless of OS.
- Explicitly state that the Azure portal is accessible from any OS, but provide alternatives for users who prefer or require command-line workflows.
- Add notes or links to documentation on installing and using Azure CLI on Linux and macOS.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-grid-domains.md
...management/relocation/relocation-event-grid-domains.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure portal (GUI) for all instructions, which is most commonly accessed from Windows environments and does not mention command-line alternatives such as Azure CLI, PowerShell, or Bash. There are no examples or guidance for Linux users or for automation via CLI tools, which are preferred in many Linux and cross-platform scenarios.
Recommendations
- Add equivalent instructions using Azure CLI commands for all major steps (exporting templates, deploying resources, deleting domains/resource groups).
- Include examples for both Windows (PowerShell) and Linux/macOS (Bash) environments where scripting or command-line actions are possible.
- Mention cross-platform tools (Azure CLI, REST API) before or alongside portal-based instructions to ensure parity.
- Add notes or links to documentation for automating these tasks in CI/CD pipelines, which are often run on Linux agents.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-event-hub-cluster.md
.../management/relocation/relocation-event-hub-cluster.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure portal for all steps, which is a web-based tool but often associated with Windows workflows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-native tools or patterns. The instructions and screenshots are tailored to the portal experience, which may be more familiar to Windows users. There is no guidance for users who prefer automation or scripting, which is common in Linux environments.
Recommendations
- Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux.
- Include examples for exporting and deploying Resource Manager templates using command-line tools (e.g., az group export, az deployment group create).
- Mention PowerShell and Bash alternatives if scripting is required, and provide sample scripts for both.
- Clarify that the Azure portal is web-based and accessible from any OS, but offer parity for users who prefer command-line or automated workflows.
- Ensure screenshots and terminology do not assume a Windows environment (e.g., avoid references to Windows file paths or Windows-specific UI elements).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-virtual-machine-scale-sets.md
...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a GUI tool most commonly used on Windows), and mentioning PowerShell as an example IAC tool, but does not provide any Linux-specific examples, CLI commands, or guidance for Linux users. There are no references to Bash, Linux shell scripting, or Linux-native tools. The instructions for exporting and editing templates are portal-centric, which is less accessible for Linux users who may prefer CLI or automation.
Recommendations
- Add explicit Azure CLI examples for all steps, especially for exporting, editing, and deploying templates.
- Include instructions for performing key actions (such as setting instance count to 0, exporting templates, and deploying resources) using Bash or Linux shell scripting.
- Mention Linux-native tools and workflows alongside PowerShell, and provide parity in examples.
- Clarify that all steps can be performed on Linux, Mac, or Windows, and provide cross-platform guidance where relevant.
- Ensure screenshots and step-by-step instructions are not exclusively portal-based; provide CLI alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/resource-manager-personal-data.md
...e-manager/management/resource-manager-personal-data.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation consistently lists Windows PowerShell cmdlets before Azure CLI commands when describing how to manage deployments, resource groups, and tags. This ordering may suggest a preference for Windows tooling. Additionally, there are no Linux-specific shell examples or references to Linux-native patterns, and PowerShell is highlighted as a primary interface, which is more commonly used on Windows.
Recommendations
- Alternate the order of examples so that Azure CLI commands (cross-platform) are listed before or alongside PowerShell cmdlets.
- Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though available cross-platform).
- Provide example usage for both Bash (Linux/macOS) and PowerShell (Windows), especially for command-line operations.
- Add notes or sections highlighting Linux usage patterns, such as scripting with Bash or using native Linux tools in conjunction with Azure CLI.
- Review and update documentation to ensure equal visibility and accessibility for Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-resources.md
...les/azure-resource-manager/management/tag-resources.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates a Windows bias by mentioning Azure PowerShell and REST API as primary programmatic methods for tag operations, with PowerShell referenced before CLI or Linux-native tools. In the 'Next steps' section, Azure PowerShell is listed before Python and ARM templates, and the CLI is only referenced in limitations, not as a primary method. There are no explicit Linux shell or Bash examples, and PowerShell is highlighted as a main automation tool, which may disadvantage Linux users.
Recommendations
- Ensure Azure CLI examples and references are presented alongside or before PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Add explicit Bash or shell scripting examples for common tagging operations.
- When listing programmatic or automation options, alternate the order (e.g., CLI, PowerShell, REST) or group them as 'cross-platform tools' and 'Windows-specific tools'.
- Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux environments.
- Where possible, provide links to Linux-specific guides or documentation for tagging resources.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-outputs.md
...icles/azure-resource-manager/templates/copy-outputs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation references Azure PowerShell before Azure CLI when discussing version requirements for supporting zero count in copy loops. The 'Next steps' section links only to a PowerShell deployment guide, omitting equivalent Linux-first or CLI-focused guides. There are no explicit Linux or cross-platform examples or instructions, and the CLI is mentioned only after PowerShell.
Recommendations
- When listing supported tools or version requirements, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- In the 'Next steps' section, add links to documentation for deploying ARM templates using Azure CLI and Bash, not just PowerShell.
- Where possible, provide cross-platform or CLI-based examples and instructions, or clarify that the steps apply equally to Linux, macOS, and Windows.
- Explicitly state that both Azure CLI and PowerShell are cross-platform, and provide guidance for users on Linux systems.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/best-practices.md
...les/azure-resource-manager/templates/best-practices.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page shows mild Windows bias. It references PowerShell-specific deployment behavior and parameter naming conflicts, and discusses the PowerShell cmdlet New-AzResourceGroupDeployment without mentioning equivalent Azure CLI or Linux-native tools. In the section on connecting to virtual machines, Windows connection methods (RDP, WinRM) are listed before Linux, and two Windows-specific links are provided versus one for Linux. There are no explicit Linux shell or Azure CLI examples, and the only mention of Linux is in a link to 'Connect to a Linux VM.'
Recommendations
- When discussing parameter naming conflicts, mention both PowerShell and Azure CLI behaviors, and provide equivalent examples for Azure CLI (e.g., az deployment group create).
- In sections referencing deployment commands, include both PowerShell and Azure CLI examples, or clarify that the behavior applies to both.
- When listing connection methods for VMs, alternate or balance the order of Windows and Linux examples, and provide parity in the number of links for each platform.
- Add examples or references for Linux-native tools and workflows, such as Bash scripting or Azure CLI usage, alongside PowerShell examples.
- Review the documentation for other subtle Windows-first language or assumptions, and ensure Linux users are equally addressed.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-cloud-shell.md
...azure-resource-manager/templates/deploy-cloud-shell.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents both Azure CLI (Bash) and PowerShell examples for deploying ARM templates in Cloud Shell, but PowerShell (a Windows-centric tool) is consistently mentioned alongside or immediately after Bash. Visuals and instructions frequently reference toggling between Bash and PowerShell, and 'PowerShell' is often listed first or equally with Bash, despite Bash being the default and more common shell for Linux users. The 'Next steps' section links to both CLI and PowerShell guides, but PowerShell is given equal prominence, which may reinforce Windows-centric patterns.
Recommendations
- Prioritize Bash/Azure CLI instructions and visuals before PowerShell, reflecting the default Linux shell experience in Cloud Shell.
- Explicitly state that Bash/Azure CLI is cross-platform and the default for Cloud Shell, while PowerShell is optional.
- Add notes or sections highlighting Linux-specific workflows or considerations, such as file paths, permissions, or scripting differences.
- Ensure that all examples and screenshots default to Bash unless PowerShell is specifically required.
- Review and adjust the order of 'Next steps' links to feature CLI/Bash resources first, followed by PowerShell as an alternative.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-history.md
...azure-resource-manager/templates/deployment-history.md
Medium Priority
View Details â
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 listed before Azure CLI in every section. There are no Linux shell (bash) or scripting examples, nor any mention of Linux-specific tools or patterns. The documentation assumes PowerShell is universally available, which may disadvantage Linux users who typically use bash or other shells.
Recommendations
- Add bash shell examples for Azure CLI commands to demonstrate usage in Linux environments.
- Explicitly mention that PowerShell examples are primarily for Windows users, and Azure CLI examples are cross-platform.
- Consider providing scripting examples using bash or zsh for common deployment tasks.
- Clarify tool availability and installation instructions for both Windows and Linux users.
- Ensure that Azure CLI examples are listed before or alongside PowerShell examples to avoid Windows-first ordering.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and cleanup, but consistently lists PowerShell as an equal alternative to CLI rather than emphasizing cross-platform parity. The use of PowerShell (which is traditionally associated with Windows, though now cross-platform) and the mention of Windows-style keyboard shortcuts (ALT + SHIFT + F) and the integrated terminal shortcut (ctrl + `) may be more familiar to Windows users. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Bash or shell scripting. The CLI is listed first, but the parity is not fully emphasized.
Recommendations
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and clarify that CLI commands work on Linux/macOS as well as Windows.
- Add Linux/macOS-specific keyboard shortcuts for formatting and opening the terminal in VS Code (e.g., CMD + SHIFT + I for formatting on macOS).
- Include a brief note or section for users on Linux/macOS, confirming that all steps are supported on those platforms.
- Consider including Bash shell script examples for deployment and cleanup, or at least mention that Azure CLI commands can be run in Bash.
- Avoid implying that PowerShell is the default or preferred method unless it is truly cross-platform and commonly used on all platforms.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-outputs.md
...rce-manager/templates/template-tutorial-add-outputs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Azure PowerShell instructions before Azure CLI, and the CLI example uses Bash-style syntax but does not explicitly mention Linux or macOS. There are no explicit Linux/macOS-specific instructions, and the prerequisites mention Azure PowerShell before Azure CLI. No Linux-specific tools or shell examples are provided, and the only editor mentioned is Visual Studio Code, which is cross-platform.
Recommendations
- Present Azure CLI instructions before PowerShell, or provide both side-by-side to avoid implying a Windows-first workflow.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes if needed.
- Include Linux/macOS-specific instructions or troubleshooting notes where relevant (e.g., file path syntax, environment variable usage).
- Consider mentioning other popular editors available on Linux, or clarify that Visual Studio Code is cross-platform.
- Add a note that both Azure PowerShell and Azure CLI are available on all major platforms, and users can choose their preferred tool.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-create-multiple-instances.md
...mplates/template-tutorial-create-multiple-instances.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is listed as the only prerequisite editor, which is cross-platform but often associated with Windows. In deployment instructions, PowerShell is mentioned before Bash/CLI, and PowerShell examples are provided alongside CLI examples. The Azure portal instructions use Windows-centric UI terms (e.g., 'File > Open File'), and the file upload screenshot is from the Azure portal, which is most commonly used on Windows. However, Linux/CLI examples are present and not omitted.
Recommendations
- Explicitly mention that Visual Studio Code is available on Linux and macOS, or suggest alternative editors (e.g., vim, nano) for Linux users.
- Present Bash/CLI instructions before PowerShell, or alternate the order to avoid implicit prioritization.
- Include screenshots or instructions for Linux file navigation/upload where relevant.
- Clarify that the Azure portal and Cloud Shell are cross-platform and accessible from any OS.
- Add a note that all steps can be performed on Linux, macOS, or Windows, and highlight any OS-specific differences if they exist.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-use-managed-identity.md
...n/articles/azure-signalr/howto-use-managed-identity.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure Portal UI for all configuration steps and does not provide any command-line examples (such as Azure CLI or PowerShell). While this avoids explicit Windows tools, the Azure Portal UI is more commonly associated with Windows workflows and is less scriptable or automatable, which can disadvantage Linux users or those preferring CLI-based automation. There are no Linux-specific instructions or parity examples for managing identities via CLI, nor are cross-platform automation options discussed.
Recommendations
- Add Azure CLI examples for all major steps (e.g., assigning managed identities, configuring upstream settings, setting Key Vault policies). The Azure CLI is cross-platform and would benefit Linux users.
- If PowerShell examples are added, ensure Azure CLI equivalents are always present and shown first or side-by-side.
- Explicitly mention that all portal-based steps can be performed via CLI, and link to relevant CLI documentation.
- Include a section or callout for automation and scripting, referencing cross-platform tools and patterns.
- Where screenshots are used, consider adding CLI command snippets as alternatives for users who do not use the portal.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/overview.md
...les/azure-resource-manager/troubleshooting/overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page shows a mild Windows bias by mentioning Azure PowerShell before Azure CLI when discussing error details and troubleshooting commands. PowerShell commands are referenced first, and in more detail, which may suggest a preference for Windows tooling. There are no explicit Linux-only examples or tools, and the CLI is only mentioned after PowerShell. No Linux-specific troubleshooting patterns or tools are highlighted.
Recommendations
- Present Azure CLI examples and commands before or alongside Azure PowerShell to avoid implying a preference for Windows tools.
- Include explicit Linux/macOS troubleshooting scenarios or notes where relevant.
- Ensure parity in the depth of explanation and linking for both Azure CLI and PowerShell commands.
- Mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Where possible, provide Bash shell examples in addition to PowerShell.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-custom-domain.md
...lob/main/articles/azure-signalr/howto-custom-domain.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally uses Azure Portal UI instructions, which are cross-platform, but in the few places where command-line examples are given, the PowerShell/Windows example is presented before the Bash/Linux example. The PowerShell example uses 'curl.exe', which is specific to Windows, and the Bash example is only provided as a secondary tab. There are no Linux-specific tools or command-line patterns mentioned before their Windows equivalents.
Recommendations
- Present Bash/Linux examples before or alongside PowerShell/Windows examples, or default to Bash for cross-platform parity.
- Use cross-platform command-line tools (e.g., 'curl' instead of 'curl.exe') in examples.
- When providing tabbed examples, consider making Bash the default or at least equal in prominence to PowerShell.
- Explicitly mention that all portal-based instructions are OS-agnostic to reassure Linux users.
- Where relevant, add CLI (az cli) examples, which are cross-platform, to supplement or replace PowerShell-specific instructions.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-service-tags.md
...blob/main/articles/azure-signalr/howto-service-tags.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes configuration steps using the Azure Portal GUI, which is most familiar to Windows users and does not provide any command-line examples (such as Azure CLI, PowerShell, or bash scripts). There are no Linux-specific instructions or parity for users who prefer or require command-line or non-GUI workflows, which are common in Linux environments.
Recommendations
- Add Azure CLI examples for configuring network security group rules using service tags, as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are provided, ensure Azure CLI/bash equivalents are also included and presented with equal prominence.
- Explicitly mention that the Azure Portal is web-based and platform-agnostic, but provide alternative instructions for users who prefer command-line tools.
- Include references or links to documentation for automating these tasks on Linux systems.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-howto-authorize-managed-identity.md
...re-signalr/signalr-howto-authorize-managed-identity.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by referencing the Azure portal and Visual Studio as primary configuration and authentication methods, with no explicit Linux or cross-platform command-line examples (e.g., Azure CLI or Bash scripting). There are no Linux-specific instructions or examples, and the only local development authentication methods mentioned are Visual Studio, Azure CLI, and Azure PowerShell, with Visual Studio listed first. No Linux shell or editor is referenced, and no explicit Bash or cross-platform CLI commands are provided for configuring managed identities or role assignments.
Recommendations
- Add explicit Azure CLI examples for configuring managed identities and role assignments, and show their usage in both Windows and Linux shells.
- Include Bash shell examples for setting environment variables and configuring local.settings.json, highlighting cross-platform compatibility.
- Mention and provide examples for common Linux editors (e.g., nano, vim) when editing configuration files.
- Clarify that all configuration steps can be performed on Linux, macOS, or Windows, and avoid listing Visual Studio or Azure portal as the only or primary methods.
- When referencing authentication in local development, mention VS Code and cross-platform tools alongside Visual Studio.
- Ensure that any PowerShell or Windows-specific instructions are accompanied by equivalent Bash/Linux commands.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-azure-functions-csharp.md
...e-signalr/signalr-quickstart-azure-functions-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. While most commands are cross-platform (using bash), the prerequisites and tooling references (such as Azure Functions Core Tools and Visual Studio Code) do not explicitly mention Linux or macOS compatibility, nor do they provide Linux-specific instructions or troubleshooting. The storage emulator reference points to Azurite, which is cross-platform, but does not clarify installation steps for Linux. The documentation also omits explicit Linux/macOS examples for environment setup, storage emulator usage, and does not mention alternative editors or shell environments.
Recommendations
- Explicitly state that Azure Functions Core Tools and Visual Studio Code are available on Linux and macOS, and provide download links for those platforms.
- Add Linux/macOS-specific setup instructions, including installation commands for Azure Functions Core Tools and Azurite (e.g., using npm or package managers).
- Include troubleshooting notes or links for common Linux/macOS issues (such as permissions, path differences, or shell compatibility).
- Mention alternative editors (such as Vim, Emacs, or JetBrains Rider) to avoid implicit bias toward Visual Studio Code.
- When referencing the storage emulator, provide clear instructions for installing and running Azurite on Linux/macOS, and clarify that it is the recommended cross-platform solution.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-quickstart-dotnet-core.md
...ticles/azure-signalr/signalr-quickstart-dotnet-core.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation avoids explicit Windows bias in most areas, emphasizing cross-platform tools like the .NET Core CLI and Visual Studio Code, which are available on Windows, macOS, and Linux. However, there are subtle 'windows_first' and 'missing_linux_example' biases: the documentation does not provide any Linux- or macOS-specific instructions, terminal commands, or screenshots, and all output examples (e.g., localhost URL, output logs) are generic or implicitly Windows-centric. There are no mentions of Linux-specific tools, nor are there any terminal/shell commands shown in Bash or zsh, and the resource cleanup steps reference the Azure Portal UI only, not CLI or cross-platform alternatives.
Recommendations
- Explicitly mention and provide example commands for Linux/macOS terminals (e.g., Bash/zsh) where appropriate, especially for running dotnet CLI commands.
- Include sample output from Linux/macOS terminals to demonstrate parity.
- Add instructions for using the Azure CLI (az) to create and delete resources, as an alternative to the Azure Portal UI.
- Where screenshots are shown, consider including at least one from a Linux environment.
- If any troubleshooting steps are OS-specific, call out differences for Linux/macOS users.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/arc-enable-guest-management.md
...n/articles/azure-vmware/arc-enable-guest-management.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing VMware Tools (which is often associated with Windows management patterns) and providing only Azure Portal and Azure CLI instructions, with no explicit Linux or cross-platform command-line examples. There are no Linux-specific instructions, nor is there mention of Linux guest agent installation or management. The documentation assumes the use of tools and workflows common in Windows-centric environments.
Recommendations
- Add explicit examples and instructions for enabling guest management and installing extensions on Linux VMs, including any Linux-specific prerequisites or troubleshooting steps.
- Clarify whether the steps and tools (such as VMware Tools and the Azure CLI command) are equally applicable to Linux guests, and provide any necessary Linux-specific flags or considerations.
- Include sample commands for Linux shells (bash) where relevant, and mention any differences in the process for Linux vs. Windows VMs.
- Reference Linux guest agent documentation or provide links to Linux-specific extension management guides.
- Ensure that any screenshots or UI walkthroughs show both Windows and Linux VM scenarios, if applicable.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/azure-security-integration.md
...in/articles/azure-vmware/azure-security-integration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing a security analytics rule example and query that specifically targets Windows server sign-in failures, with no equivalent example for Linux systems. The only concrete scenario described is for Windows, and there are no Linux-specific queries, event types, or guidance. The documentation does mention 'Operating system' as a field when adding servers, but does not provide any Linux-focused instructions, examples, or queries. This may lead Linux users to feel unsupported or unclear about how to implement similar monitoring for their systems.
Recommendations
- Add equivalent Linux-focused examples, such as a scheduled query rule for failed SSH login attempts or other common Linux authentication events.
- Include sample KQL queries for Linux security events (e.g., parsing Syslog or auditd events) alongside the Windows example.
- Explicitly mention support for Linux VMs in the integration steps, and provide any Linux-specific prerequisites or considerations.
- Wherever possible, present both Windows and Linux examples in parallel to ensure parity and inclusivity.
- Clarify in the 'Create rules to identify security threats' section that similar rules can be created for Linux, and link to relevant documentation or provide sample queries.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-azure-monitor-for-resource-health-for-azure-vmware-solution.md
...-monitor-for-resource-health-for-azure-vmware-solution.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes how to create and manage Azure Monitor resource health alert rules using the Azure Portal GUI, which is a cross-platform web interface. However, there are no examples or instructions for performing these tasks using command-line tools such as Azure CLI, PowerShell, or ARM templates. When command-line automation is omitted, Windows users may default to PowerShell, while Linux users typically use Azure CLI. The absence of CLI or automation examples means Linux users (and those preferring scripting/automation) are underserved.
Recommendations
- Add equivalent instructions for creating and managing resource health alert rules using Azure CLI commands, which are cross-platform and commonly used on Linux.
- If relevant, provide ARM template or Bicep examples for infrastructure-as-code scenarios.
- If including PowerShell examples, ensure Azure CLI examples are presented alongside or before them.
- Explicitly mention that all portal steps are platform-agnostic, but provide links or sections for automation via CLI or templates to ensure Linux parity.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-customer-managed-keys.md
...ticles/azure-vmware/configure-customer-managed-keys.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently presents Azure Portal (web UI) instructions first, followed by Azure CLI examples. There are no explicit Windows-only tools (e.g., PowerShell) or Windows command-line examples, but the absence of any Linux-specific instructions or considerations (such as Bash vs. CMD differences, or Linux shell nuances) means Linux users are not directly addressed. The CLI examples use Bash-style syntax, which is compatible with Linux, but this is not clarified. There are no references to Linux tools, nor is there guidance for users on Linux environments, leading to a subtle bias toward Windows-centric workflows.
Recommendations
- Explicitly state that the Azure CLI examples are cross-platform and can be run on Linux, macOS, or Windows.
- Add a note clarifying that Bash syntax is used in CLI examples, and provide equivalent examples for users running Azure CLI in Windows CMD or PowerShell if relevant.
- Include troubleshooting or prerequisite notes specific to Linux environments, such as package installation commands for Azure CLI on Linux.
- Where UI instructions are given, clarify that the Azure Portal is web-based and platform-agnostic, to avoid the impression of Windows bias.
- Consider adding a 'Platform support' section to reassure Linux users that all steps are supported on their OS.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-azure-vmware-solution.md
.../articles/azure-vmware/deploy-azure-vmware-solution.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing the creation and use of a Windows virtual machine for network validation, with no mention of Linux alternatives. All VM examples and links point to Windows-specific resources, and there are no Linux or cross-platform command-line examples provided.
Recommendations
- Include parallel instructions and links for creating and using a Linux virtual machine in Azure for network validation.
- Provide Linux-based examples for connecting to the Azure VMware Solution, such as using SSH or Linux-native tools.
- Ensure that references to VM creation and management are platform-neutral or include both Windows and Linux options.
- Where screenshots or portal instructions are given, clarify that the steps apply to both Windows and Linux VMs, or provide Linux-specific screenshots as well.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/disable-internet-access.md
.../main/articles/azure-vmware/disable-internet-access.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation does not provide any OS-specific command-line examples or instructions, but it implicitly assumes a GUI-based workflow (Azure portal) and does not mention or provide parity for Linux-based tools or automation (e.g., Azure CLI, Bash scripts). There is also a lack of PowerShell or Windows-specific bias, but the absence of Linux/CLI examples can be considered a subtle 'windows_first' or GUI-first bias.
Recommendations
- Add examples using Azure CLI commands (which are cross-platform and commonly used on Linux) to perform the same tasks described in the portal workflow.
- Explicitly mention that the steps can be performed from any OS via the Azure portal, or provide automation options for both Windows (PowerShell) and Linux (Bash/CLI).
- Include references or links to documentation for performing these tasks via automation or scripting, ensuring parity for Linux users.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/enable-vmware-cds-with-azure.md
.../articles/azure-vmware/enable-vmware-cds-with-azure.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently references Azure VMs and configuration steps using the Azure portal, with examples such as 'Sign in to Azure VM' and 'ping from JSVM1', but does not provide any Linux-specific instructions or examples. All VM references are generic (e.g., JSVM1, JSVM2) but implicitly assume Windows usage, as there is no mention of Linux tools, commands, or alternative OS-specific steps. The documentation does not offer parity for Linux users in terms of example commands (e.g., ping, firewall configuration) or troubleshooting steps.
Recommendations
- Include explicit Linux VM examples alongside Windows VM references, such as using Ubuntu or CentOS images in Azure.
- Provide Linux-specific instructions for verifying connectivity (e.g., using 'ping' or 'curl' from a Linux shell), and clarify any OS-specific differences in network configuration.
- Mention Linux firewall configuration (e.g., using iptables or ufw) where relevant, in addition to Azure portal-based steps.
- Add troubleshooting steps for common Linux networking issues in the context of VPN and SNAT setup.
- Where VM examples are given, specify both Windows and Linux VM creation and verification steps to ensure cross-platform parity.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/manage-arc-enabled-azure-vmware-solution.md
...ure-vmware/manage-arc-enabled-azure-vmware-solution.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides command examples for both Windows and Linux-based management VMs when activating the Python environment, but the Windows example is listed first. For subsequent commands (az CLI usage), no OS-specific examples are given, which is acceptable since az CLI is cross-platform. However, there is a slight bias in presenting Windows instructions before Linux, and there are no Linux-specific troubleshooting tips or additional context for Linux users.
Recommendations
- Alternate the order of OS examples so that sometimes Linux is presented first.
- Add explicit notes or troubleshooting tips for Linux users (e.g., file permissions, path differences, SSH key handling).
- Ensure parity in examples: if a Windows-specific tool or pattern is mentioned, provide the Linux equivalent.
- Consider including a table or section summarizing OS-specific steps side-by-side for clarity.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/logs-via-logic-app.md
.../blob/main/articles/azure-vmware/logs-via-logic-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation demonstrates a mild Windows bias. The only hosting plan specifically mentioned is the default Windows plan (Workflow Standard WS1), with its Windows-centric resources and terminology. No Linux hosting plans or Linux-specific configuration details are referenced. The workflow and certificate management steps are described in a way that assumes a Windows-style environment (e.g., .cer files, environment variable naming conventions), and there is no mention of Linux equivalents or considerations for Linux-based log management servers. All examples and screenshots are from the Azure portal, which is platform-agnostic, but the text references Windows defaults and does not provide Linux parity.
Recommendations
- Explicitly mention Linux hosting plans for Logic Apps, if available, and provide guidance for selecting them.
- Include examples or notes for Linux-based log management servers (e.g., syslog-ng, rsyslog) and how to configure integration.
- Reference Linux certificate formats (e.g., .pem) and provide instructions for both Windows (.cer) and Linux (.pem) certificate management.
- Clarify environment variable configuration for Linux-based deployments, if applicable.
- Add troubleshooting tips or configuration notes for users running log management servers on Linux, including firewall and networking considerations.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-disable-local-auth.md
.../articles/azure-web-pubsub/howto-disable-local-auth.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation demonstrates a bias toward Windows by only referencing the Azure portal (a web-based tool), Azure Resource Manager templates, and Azure Policyâall of which are platform-agnostic but are typically accessed via the Azure portal, which is often associated with Windows-centric workflows. There are no examples using cross-platform command-line tools such as Azure CLI or Azure PowerShell, and there are no Linux-specific instructions or screenshots. This omission may disadvantage Linux users who prefer or require command-line or automation-based workflows.
Recommendations
- Add Azure CLI examples for turning off local authentication, as Azure CLI is cross-platform and widely used on Linux.
- Include Azure PowerShell examples for parity, but ensure CLI examples are presented first or alongside PowerShell.
- Explicitly mention that all steps can be performed from any OS via the Azure portal, and clarify that the portal is web-based and not Windows-specific.
- Provide screenshots or terminal output from Linux environments where relevant.
- Consider adding a section on automating this process using bash scripts or other Linux-native tools.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/native-connect-private-cloud-previous-edition.md
...mware/native-connect-private-cloud-previous-edition.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation does not provide any OS-specific command-line examples, but it does reference Azure tools and workflows that are typically accessed via the Azure Portal or Azure CLI. There is no explicit mention of Windows-only tools (such as PowerShell), but there are also no Linux-specific instructions or examples. The documentation assumes use of the Azure Portal or generic Azure workflows, which are cross-platform, but omits any CLI or automation examples that could be relevant for Linux users.
Recommendations
- Add Azure CLI examples for each step, as the CLI is cross-platform and widely used on Linux.
- If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are also provided.
- Explicitly mention that all steps can be performed from any OS using the Azure Portal or Azure CLI.
- Include a note about automation options available for both Windows and Linux environments.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/native-internet-connectivity-design-considerations.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/native-internet-connectivity-design-considerations.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation page does not provide any OS-specific command-line examples, but it does show a bias toward Windows/Azure-native tools and patterns. It exclusively references Azure Firewall and Azure route tables (UDR), which are more familiar to Windows/Azure administrators, without mentioning or providing parity for Linux-centric tools or CLI workflows. There are no Linux-specific examples or mentions of how to perform equivalent tasks using Linux tools or interfaces.
Recommendations
- Include examples using Azure CLI and PowerShell, and ensure that Azure CLI (which is cross-platform and Linux-friendly) examples are provided alongside or before PowerShell examples.
- Mention how to configure routing and firewall rules using Linux-based appliances (e.g., iptables, nftables) or popular open-source NVAs (like pfSense, VyOS), and provide links or brief instructions.
- Explicitly state that the guidance applies regardless of the underlying OS, and provide references to Linux documentation for network configuration where appropriate.
- If screenshots or diagrams show Azure Portal UI, consider also showing equivalent CLI commands for cross-platform parity.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/native-role-assignment.md
...b/main/articles/azure-vmware/native-role-assignment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation describes manual role assignment for Azure VMware Solution using only Azure Portal GUI steps, which are typically accessed via a web browser on Windows. There is no mention of command-line alternatives such as Azure CLI or PowerShell, nor are Linux-specific instructions or examples provided. This may disadvantage users who prefer or require automation or command-line access, especially on Linux or macOS platforms.
Recommendations
- Add equivalent instructions using Azure CLI commands, which are cross-platform and work on Linux, macOS, and Windows.
- Include PowerShell examples if relevant, but ensure Azure CLI examples are presented first or alongside them.
- Explicitly state that the Azure Portal is accessible from any OS via a browser, and provide links to CLI documentation for users who prefer non-GUI workflows.
- Where possible, provide sample scripts for automating role assignments, and clarify OS compatibility.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/netapp-files-with-azure-vmware-solution.md
...zure-vmware/netapp-files-with-azure-vmware-solution.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation mentions both Linux and Windows VMs as supported, but when describing mounting and mapping shares, it provides more detail for Windows/SMB (e.g., Active Directory setup) and omits concrete Linux/NFS commands or examples. No Linux-specific mount instructions or command-line examples are given, while Windows/SMB mapping is described in more detail. This results in a subtle Windows-first and missing Linux example bias.
Recommendations
- Add explicit Linux NFS mount instructions, including example mount commands (e.g., using 'mount' or '/etc/fstab' entries) for mounting Azure NetApp Files volumes on Linux VMs.
- Provide parity in detail for both Windows (SMB) and Linux (NFS) share mapping, ensuring both are covered with step-by-step instructions.
- Include troubleshooting tips or common issues for Linux clients, similar to any provided for Windows.
- Where possible, present Linux and Windows instructions side-by-side or in clearly separated sections to emphasize equal support.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/remove-arc-enabled-azure-vmware-solution-vsphere-resources-from-azure.md
...led-azure-vmware-solution-vsphere-resources-from-azure.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation presents Windows uninstall instructions before Linux, and the Windows uninstall section references Control Panel and Programs and Features, which are Windows-specific tools. There is no evidence of missing Linux examples, but the ordering and tool references show a mild Windows bias.
Recommendations
- Present Linux and Windows instructions in parallel or in the order most common among the user base, or clarify the ordering rationale.
- Where possible, provide cross-platform command-line alternatives for Windows (e.g., using PowerShell or command prompt) to match the Linux CLI approach.
- Ensure that Linux instructions are as detailed as Windows instructions (e.g., mention removing agent directories if applicable).
- Consider adding a table of contents or section headers that make it easy for both Windows and Linux users to find their relevant instructions quickly.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/self-service-maintenance-orchestration.md
...azure-vmware/self-service-maintenance-orchestration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes using the Azure portal GUI for maintenance scheduling, with no mention of command-line or automation options. There are no examples for Linux users (e.g., Azure CLI, Bash scripts), nor is there mention of cross-platform tools. The structure and language implicitly assume a Windows-centric workflow, as is common in Azure VMware Solution docs.
Recommendations
- Add examples using Azure CLI commands for scheduling and rescheduling maintenance, which are accessible from both Windows and Linux environments.
- Mention and provide sample scripts for automation using Bash or PowerShell, highlighting cross-platform compatibility.
- Explicitly state whether these operations can only be performed via the portal or if there are REST API/CLI alternatives, and provide links or examples as appropriate.
- Ensure that any screenshots or step-by-step instructions are supplemented with equivalent command-line instructions for Linux users.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/restore-azure-netapp-files-vms.md
...rticles/azure-vmware/restore-azure-netapp-files-vms.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently presents instructions and examples using the VMware vSphere web client GUI and vCenter terminology, which are platform-agnostic but heavily oriented toward Windows-based administrative workflows. There are no command-line examples (PowerShell or otherwise), but also no Linux CLI or automation examples. The only CLI instructions are for the maintenance console, which appears to be a custom interface, not a standard shell. There are no references to Linux tools, shell commands, or Linux-specific workflows, and no mention of how to perform these tasks from Linux environments or with Linux automation tools.
Recommendations
- Add equivalent Linux-based workflows or CLI examples (e.g., using SSH, shell scripts, or VMware's Linux command-line tools such as govc or ovftool) for restoring VMs and VMDKs.
- Explicitly state platform requirements and clarify whether the vSphere web client and maintenance console are accessible from Linux systems.
- Provide automation examples using cross-platform tools (such as REST APIs, Ansible, or Python scripts) to ensure parity for Linux administrators.
- Include notes or sections addressing common Linux administrative environments and how to perform restore operations without relying on Windows-centric GUIs.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/tutorial-delete-private-cloud.md
...articles/azure-vmware/tutorial-delete-private-cloud.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides instructions exclusively for the Azure portal (web UI) and does not include any command-line examples. There is no mention of Linux tools, CLI, or PowerShell, but the absence of Azure CLI or Bash examples (which are common for Linux users) means Linux users are not equally served. The documentation implicitly assumes use of the portal, which is platform-agnostic but often associated with Windows-first workflows.
Recommendations
- Add Azure CLI examples for deleting an Azure VMware Solution private cloud, as the Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are added in the future, ensure Bash/Azure CLI equivalents are also provided.
- Explicitly mention that the portal can be accessed from any OS/browser to clarify platform neutrality.
- Provide links to relevant Azure CLI documentation for users who prefer command-line operations.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/tutorial-expressroute-global-reach-private-cloud.md
...re/tutorial-expressroute-global-reach-private-cloud.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes steps using the Azure portal GUI and does not provide any command-line examples for either Windows (PowerShell) or Linux (CLI). However, the workflow and terminology (e.g., 'on-premises edge router') are generic, but there is a subtle Windows-first bias: the absence of Linux-specific instructions or CLI examples, and the lack of mention of Linux tools or patterns for ExpressRoute management. There are no references to Linux commands, shell scripts, or cross-platform automation, nor is there guidance for users who may prefer CLI over GUI, which is common in Linux environments.
Recommendations
- Add Azure CLI and/or PowerShell command examples for each step, and ensure parity by including both Windows (PowerShell) and Linux (Azure CLI, Bash) instructions.
- Explicitly mention that ExpressRoute management can be performed via CLI on Linux and provide links to relevant documentation.
- Include troubleshooting steps or verification commands that can be run on Linux systems (e.g., using curl, traceroute, or iproute2 tools) to verify connectivity.
- Clarify that the Azure portal is cross-platform, but provide alternatives for users who prefer command-line or automation approaches.
- Add references to Linux-based network management tools and patterns where appropriate.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-use-managed-identity.md
...rticles/azure-web-pubsub/howto-use-managed-identity.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure Portal UI for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). While this avoids explicit Windows-only tools, the lack of CLI examples can disadvantage Linux users, who often prefer or require command-line automation. Additionally, there is no mention of Linux-specific workflows or tools, and any references to command-line management (e.g., Azure CLI) are absent.
Recommendations
- Add Azure CLI examples for all major steps, such as enabling managed identity, assigning user/system identities, and configuring event handlers. Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are added in the future, ensure Azure CLI or Bash equivalents are always provided and presented first or side-by-side.
- Explicitly mention that all portal-based instructions are platform-agnostic, but provide links or references to CLI documentation for users who prefer command-line workflows.
- Include a section or callout for automation scenarios, highlighting how Linux users can script these operations using Azure CLI.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-web-pubsub-write-upstream-server.md
...e-web-pubsub/howto-web-pubsub-write-upstream-server.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently presents Windows-specific instructions (using 'set' for environment variables) before mentioning Linux/macOS equivalents (using 'export'), both in the main language samples and in the tunnel tool section. In several places, the Linux/macOS instructions are only given as comments or after the Windows example, and there are no Linux-specific shell or tool usage examples (e.g., no bash scripts, systemd, or Linux-native patterns). The documentation does not provide parity in terms of Linux-first or Linux-specific guidance.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than as comments or afterthoughts.
- Provide explicit bash/zsh commands for environment setup, not just as comments.
- Include Linux-native troubleshooting tips (e.g., systemd service setup, common Linux firewall issues).
- Add examples of running the upstream server as a background process or service on Linux.
- Ensure all CLI and code samples use cross-platform patterns (e.g., avoid 'set' in favor of 'export' or show both explicitly).
- Where possible, mention Linux tools or patterns (such as using curl for testing endpoints, or journalctl for logs).
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/includes/web-pubsub-add-role-assignments.md
...web-pubsub/includes/web-pubsub-add-role-assignments.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation primarily describes the role assignment process using the Azure Portal, which is a cross-platform web interface, but in the 'To learn more' section, Azure PowerShell is listed before Azure CLI. This ordering can be interpreted as a subtle Windows-first or PowerShell-heavy bias, as Azure CLI is generally more cross-platform and Linux-friendly, while PowerShell is more associated with Windows environments. No explicit Linux examples or Linux-specific tools are mentioned.
Recommendations
- List Azure CLI before Azure PowerShell in the 'To learn more' section to reflect cross-platform parity.
- Explicitly mention that both Azure CLI and PowerShell are available on all major platforms, and provide guidance for users on Linux.
- Consider adding a brief example or link for performing the role assignment using Azure CLI directly in the main steps, not just in the 'To learn more' section.
- If possible, provide a table or section comparing how to perform the task using both CLI and PowerShell, highlighting cross-platform options.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/quickstart-use-sdk.md
...b/main/articles/azure-web-pubsub/quickstart-use-sdk.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is given equal prominence to Bash, and is mentioned in prerequisites and throughout the guide. There is a slight Windows bias in the explicit inclusion of PowerShell examples and instructions, while Linux-specific shells or tools (e.g., zsh, fish) are not mentioned. The guide does not provide Windows-only tools, but the parity between Bash and PowerShell may suggest a prioritization of Windows users, as PowerShell is primarily a Windows shell (though available on Linux).
Recommendations
- Clarify that Bash instructions work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- Add explicit notes about running Bash commands on Linux/macOS, and provide troubleshooting tips for those platforms.
- Consider including examples for other common Linux shells if relevant (e.g., zsh), or at least mention their compatibility.
- Ensure that all prerequisites and steps are equally clear for Linux users, including installation instructions for dependencies on Linux.
- If PowerShell is included for Windows parity, consider adding a note that Bash is the default shell on most Linux distributions.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/quickstarts-push-messages-from-server.md
...re-web-pubsub/quickstarts-push-messages-from-server.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation demonstrates a mild Windows bias, primarily in the Java section, where directory creation and navigation commands use Windows-style syntax (e.g., `mkdir pubsub` and `cd pubsub` in a `cmd` block, and Maven commands chained with `&`, which is a Windows shell operator). Additionally, the Java quickstart uses `cmd` and `console` blocks with Windows-centric instructions, and does not provide explicit Linux/Unix alternatives. However, most other language sections (JavaScript, Python, C#) use cross-platform Bash commands and avoid Windows-specific tools or PowerShell examples. No explicit PowerShell or Windows-only tools are used, and Linux examples are present for most workflows.
Recommendations
- For Java sections, provide both Windows (`cmd`) and Linux/macOS (`bash` or `sh`) command examples, especially for Maven commands. For example, use `&&` for Unix shells and `&` for Windows, or note the difference.
- Avoid using Windows-style command prompts (`cmd`) exclusively; use neutral or dual syntax blocks where possible.
- Explicitly state that the instructions work on both Windows and Linux/macOS, and clarify any differences in command syntax.
- Where possible, use cross-platform commands and avoid shell-specific chaining operators.
- Add a note or section for Linux/macOS users in the Java quickstart, especially for project setup and execution commands.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/reference-server-sdk-csharp.md
...ticles/azure-web-pubsub/reference-server-sdk-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on .NET and NuGet, which are traditionally associated with Windows environments. All code examples are in C#, and installation instructions use the dotnet CLI without mentioning cross-platform compatibility or Linux-specific instructions. There are no references to Linux tools, package managers, or shell environments, nor are there any examples or troubleshooting steps tailored for Linux users.
Recommendations
- Explicitly mention that .NET Core and the dotnet CLI are cross-platform and supported on Linux and macOS, not just Windows.
- Provide installation instructions for .NET SDK on Linux (e.g., using apt, yum, or snap).
- Include example commands for installing the package on Linux systems.
- Add troubleshooting steps or logging setup instructions for Linux environments (e.g., using Bash or Linux-specific log viewers).
- Clarify that the SDK and examples work on Linux and macOS, and provide sample code or screenshots from those platforms.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/socket-io-howto-integrate-web-app.md
.../azure-web-pubsub/socket-io-howto-integrate-web-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for compressing files, but Bash is presented first. However, the PowerShell example is included, which is positive. There is a slight 'windows_first' bias in that the PowerShell example is given equal prominence, and the documentation does not mention Linux-specific tools beyond Bash, nor does it discuss platform-specific deployment considerations. The rest of the guide uses Azure CLI, which is cross-platform, and the prerequisites mention Azure CLI or Cloud Shell, both of which are platform-agnostic.
Recommendations
- Ensure that Linux/Bash examples are always presented before or at least equally with PowerShell/Windows examples.
- Explicitly mention that all steps work on Linux, macOS, and Windows, and clarify any platform-specific differences.
- Include a note about using Bash on Windows (e.g., via WSL or Git Bash) for users who may not have PowerShell.
- If possible, provide a table summarizing commands for Bash, PowerShell, and any other relevant shells.
- Add troubleshooting tips for common platform-specific issues (e.g., file permissions on Linux).
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/socket-io-serverless-tutorial-python.md
...ure-web-pubsub/socket-io-serverless-tutorial-python.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by using Windows-style path separators (e.g., 'azurite\debug.log'), referencing 'command prompt' terminology, and omitting explicit Linux/macOS equivalents for commands and file paths. There are no PowerShell-specific commands, but the instructions and examples assume a Windows environment, especially in the Azurite emulator section. No Linux-specific setup or troubleshooting is mentioned, and commands are not shown with Linux-style paths or shell conventions.
Recommendations
- Provide explicit Linux/macOS instructions alongside Windows steps, especially for file paths and shell commands (e.g., use './azurite/debug.log' for Linux/macOS).
- Use cross-platform terminology such as 'terminal' instead of 'command prompt', or clarify when instructions differ.
- Add notes or tabs for Linux/macOS users where setup or command syntax differs (e.g., Azurite startup, file paths).
- Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, npm global installs).
- Review all code and command examples to ensure they are platform-agnostic or provide both Windows and Linux/macOS variants.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-pub-sub-messages.md
...articles/azure-web-pubsub/tutorial-pub-sub-messages.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation generally provides cross-platform instructions, with most shell commands shown in Bash and explicit notes for Windows users. However, there is a subtle Windows bias: Windows command shells and tools are mentioned first or as the default in several places, and some directory creation commands for Java use Windows-style (cmd) syntax. The guidance for setting environment variables also references Windows ('set') before Linux ('export'). There are no missing Linux examples, but the documentation sometimes assumes Windows as the primary environment.
Recommendations
- When referencing both Windows and Linux commands, list Linux/Bash instructions first, as Bash is more common in cross-platform and cloud environments.
- For directory creation and navigation, provide both Bash and Windows (cmd.exe) command blocks, or clarify which is being used in each code block.
- When mentioning environment variable setting, give equal prominence to both 'export' (Linux/macOS) and 'set' (Windows), or provide a table showing both.
- Where possible, use neutral, platform-agnostic language (e.g., 'command shell' instead of 'Windows command shell'), and clarify that all steps are supported on both platforms.
- Add explicit notes or tabs for PowerShell if relevant, or clarify that Azure CLI commands work identically on all platforms.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-elastic-san-backup-support-matrix.md
...cles/backup/azure-elastic-san-backup-support-matrix.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively references the Azure portal for configuration, restore, and management operations, without mentioning or providing examples for command-line tools such as Azure CLI, PowerShell, or REST API. While no explicit Windows tools are named, the lack of Linux-oriented instructions or parity (e.g., Azure CLI examples) suggests a subtle 'windows_first' and 'missing_linux_example' bias. This may disadvantage users who prefer or require Linux-based workflows or automation.
Recommendations
- Add instructions and examples for configuring, restoring, and managing Elastic SAN backup using Azure CLI, which is cross-platform and widely used on Linux.
- Include REST API references or examples for backup operations to support automation and platform neutrality.
- If PowerShell examples are provided elsewhere, ensure Azure CLI equivalents are given alongside.
- Explicitly mention cross-platform support and tools in the documentation introduction to signal parity.
- Consider adding a 'Tabs' UI for code examples (Portal, CLI, PowerShell, REST API) to improve accessibility for all users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-policy-configure-diagnostics.md
.../articles/backup/azure-policy-configure-diagnostics.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation exclusively describes how to configure Vault Diagnostics settings using the Azure Portal GUI, with no mention of command-line or automation approaches such as Azure CLI, PowerShell, or scripting. There are no examples or guidance for Linux users or for using cross-platform tools. The workflow and screenshots are oriented toward the Azure Portal, which is commonly used on Windows, and there is no mention of Linux-specific considerations or parity in automation.
Recommendations
- Add Azure CLI examples for assigning the built-in policy and triggering remediation tasks, as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are provided in the future, ensure that equivalent Azure CLI or REST API examples are also included.
- Mention that all steps can be performed from any OS via the Azure Portal, but highlight automation options for Linux users.
- Include a section on automating policy assignments and remediation using scripts, with sample code for both Azure CLI and PowerShell.
- Explicitly state that the process is OS-agnostic when using the Azure Portal, and provide links to documentation for command-line automation.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-manage-cli.md
...ob/main/articles/backup/backup-azure-sql-manage-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently references SQL Server databases and VM/container/resource names that imply Windows environments (e.g., 'mssqlserver', 'testSQLVM'), but does not explicitly mention or provide examples for Linux-based SQL Server VMs. There are no notes or examples addressing Linux-specific considerations, nor is there guidance for users running SQL Server on Linux VMs. All CLI examples use generic Azure CLI commands, but the context and naming conventions are Windows-centric.
Recommendations
- Add explicit guidance and examples for managing SQL Server databases on Linux-based Azure VMs, including any differences in resource naming, backup/restore processes, or prerequisites.
- Include a note clarifying that the Azure CLI commands work for both Windows and Linux SQL Server VMs, and highlight any platform-specific caveats.
- Provide example resource/container names for Linux SQL Server VMs, or show parallel examples for both Windows and Linux environments.
- Mention any Linux-specific requirements (e.g., SQL Server version, agent installation, permissions) for Azure Backup.
- Ensure that terminology and instructions are inclusive of both Windows and Linux SQL Server VM scenarios.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-enhanced-policy.md
...in/articles/backup/backup-azure-vms-enhanced-policy.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed PowerShell examples for configuring Enhanced backup policies, with step-by-step cmdlets and explanations. The PowerShell section is significantly more extensive than the Azure CLI section, which is more concise and lacks equivalent depth. There are no Linux-specific shell (bash) examples, nor is there mention of Linux tools or patterns. The order of presentation places PowerShell before CLI, suggesting a Windows-first approach.
Recommendations
- Add bash shell examples for Azure CLI commands, showing usage in typical Linux environments.
- Include notes or examples for scripting backup policy management on Linux, such as using cron jobs or shell scripts.
- Balance the depth of CLI and PowerShell sections, providing equally detailed walkthroughs for CLI users.
- Explicitly mention cross-platform compatibility of CLI commands, and clarify any differences in behavior or prerequisites between Windows and Linux.
- Consider reordering sections to present CLI before PowerShell, or interleave examples to emphasize parity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-rm-template-samples.md
...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a comprehensive list of Azure Resource Manager and Bicep templates for backup scenarios but demonstrates a Windows bias by including a template specifically for deploying a Windows Server VM with backup enabled, while there are no equivalent examples for Linux VMs. Additionally, the SQL Server backup example is limited to SQL Gallery images, which are typically Windows-based, and there is no mention of Linux-based database backup scenarios.
Recommendations
- Add examples and templates for deploying and backing up Linux VMs, such as Ubuntu or CentOS, with Azure Backup enabled.
- Include backup scenarios for Linux-based databases (e.g., MySQL, PostgreSQL) running on Azure VMs.
- Ensure that for every Windows-specific template or example, there is a Linux equivalent provided or referenced.
- Explicitly mention cross-platform compatibility in descriptions, clarifying when templates are Windows-only or also support Linux.
- Consider adding a section summarizing OS support for each template to help users quickly identify applicability.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-overview.md
...s/blob/main/articles/backup/offline-backup-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively references Microsoft Azure Backup Server (MABS), System Center Data Protection Manager (DPM), and the MARS Agentâall Windows-based backup solutions. There are no examples, instructions, or mentions of Linux-based backup agents, tools, or workflows. The utilities and processes described (such as BitLocker encryption and the custom utility for disk preparation) are also Windows-centric, with no Linux equivalents or alternatives provided.
Recommendations
- Include information about Linux-based backup agents or supported third-party tools for Linux environments, if available.
- Provide explicit instructions or examples for performing offline backup from Linux servers, including any required utilities or scripts.
- Mention Linux-compatible disk encryption options (e.g., LUKS) if BitLocker is not available.
- Clarify platform support for each backup method (e.g., specify if only Windows servers are supported, or if Linux is also supported).
- If Linux is not supported, explicitly state this to set expectations for cross-platform users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-tutorial.md
...main/articles/backup/blob-backup-configure-tutorial.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page shows a moderate Windows bias. In the 'Related content' section, Azure PowerShell is listed before Azure CLI, which is more cross-platform and Linux-friendly. There is also a dedicated link for restoring using Azure PowerShell, but no equivalent first-party Linux shell (e.g., Bash) or scripting examples are highlighted. The main tutorial focuses on the Azure Portal, which is platform-agnostic, but the supplementary content leans toward Windows tools.
Recommendations
- List Azure CLI examples before or alongside Azure PowerShell to avoid implying Windows-first workflows.
- Add explicit Bash or Linux shell examples where possible, especially in the 'Related content' section.
- Ensure that all command-line examples are provided for both Azure PowerShell and Azure CLI, with equal prominence.
- Consider including a note about cross-platform compatibility and linking to documentation that highlights Linux/macOS usage.
- If REST API usage is mentioned, provide sample curl commands or scripts that can be run from Linux environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-quick.md
...ob/main/articles/backup/blob-backup-configure-quick.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a restore method before Azure CLI, and by referencing PowerShell-specific instructions. There is no explicit mention of Linux-specific tools or examples, and the ordering suggests a preference for Windows-centric workflows.
Recommendations
- Ensure that Azure CLI examples are given equal prominence and ordering as Azure PowerShell, especially since CLI is cross-platform.
- Add explicit Linux usage notes or examples, such as running Azure CLI commands on Linux or macOS.
- Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash equivalents for Linux users.
- Review included content (such as blob-backup-azure-portal-configure-backup.md) for similar biases and update to include Linux-friendly instructions.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-azure-file-share-rest-api.md
...in/articles/backup/manage-azure-file-share-rest-api.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page references Azure PowerShell and the Azure portal before Azure CLI, and includes HTTP response headers showing Microsoft-IIS and ASP.NET, which are Windows technologies. There are no explicit Linux shell examples or Linux-specific guidance, and the order of tool mentions puts Windows tools first.
Recommendations
- List Azure CLI before or alongside Azure PowerShell and the Azure portal when mentioning alternative management tools.
- Add explicit Linux shell (bash/curl) examples for REST API calls to demonstrate parity with Windows/PowerShell usage.
- Avoid including HTTP response headers that reference Windows-specific technologies (e.g., Microsoft-IIS, ASP.NET) unless relevant to the API consumer.
- Where possible, provide cross-platform command-line examples (e.g., both PowerShell and bash/curl) for common operations.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-aks.md
...ure-docs/blob/main/articles/backup/quick-backup-aks.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure portal UI for configuration steps and does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell). While the Azure portal is cross-platform, the lack of CLI or script-based instructions can disadvantage Linux users or those who prefer automation. Additionally, the only explicit mention of command-line tools is in the 'Next step' section, where Azure CLI is listed after the portal, indicating a 'windows_first' or GUI-first bias. There are no Linux-specific considerations, nor are there examples using Bash or other Linux-native tools.
Recommendations
- Add step-by-step instructions for configuring AKS backup using Azure CLI, with example commands.
- Provide Bash script examples for common backup and restore operations.
- Ensure that CLI/script-based instructions are presented alongside or before portal-based steps to support automation and Linux users.
- Explicitly mention that the Azure portal is accessible from any OS, but highlight CLI alternatives for headless or automated environments.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-instance-troubleshoot.md
...cles/backup/sap-hana-database-instance-troubleshoot.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation refers exclusively to 'Azure VM' and does not specify or provide examples for either Windows or Linux platforms, despite SAP HANA being primarily a Linux workload. There are no command-line examples (e.g., Bash, PowerShell), but the absence of Linux-specific troubleshooting steps, tools, or filesystem commands (other than a brief mention of ext3/xfs) suggests a lack of Linux parity. The troubleshooting steps focus on Azure roles and permissions without addressing common Linux administrative tasks relevant to SAP HANA backup/restore scenarios.
Recommendations
- Explicitly state that SAP HANA is supported and typically deployed on Linux Azure VMs, and clarify if any steps differ for Linux vs. Windows.
- Add Linux-specific troubleshooting steps and examples, such as checking disk mounts, file system types, and using Bash commands to verify disk status.
- Include sample Bash commands for checking managed identity assignments, disk attachment, and file system compatibility.
- Reference Linux tools and patterns (e.g., systemctl for service status, lsblk for disk info) where appropriate.
- Ensure that any links to troubleshooting scripts or guides include Linux/Bash variants, not just PowerShell or Windows-centric scripts.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/security-overview.md
...re-docs/blob/main/articles/backup/security-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Microsoft Azure Recovery Services (MARS) agent for on-premises backups, which is a Windows-only tool. There are no examples, mentions, or guidance for Linux-based on-premises backup agents or scenarios. This omission may lead Linux users to feel unsupported or unclear about their backup options.
Recommendations
- Include information about Linux-based backup options for on-premises servers, such as Azure Backup Server (MABS), System Center Data Protection Manager (DPM), or third-party solutions supported by Azure.
- Provide explicit examples or references for backing up Linux servers, including any supported agents, scripts, or integration patterns.
- Clarify in the 'Security features to help protect hybrid backups' section how Linux servers can be protected, and if not supported, state this explicitly and link to alternative guidance.
- Ensure parity in documentation by mentioning both Windows and Linux scenarios where relevant, especially in hybrid backup contexts.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-configure-backup-aks.md
.../main/articles/backup/tutorial-configure-backup-aks.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure portal UI for configuration steps and does not provide any command-line examples. While it mentions the Azure CLI in the 'Next step' section, all instructions and screenshots focus on the portal, which is more commonly used on Windows. There are no examples using Linux-native tools or shell commands, and no mention of how to perform these tasks using the CLI or automation scripts, which are preferred by many Linux users.
Recommendations
- Add parallel instructions and examples using the Azure CLI for each major configuration step, including relevant command snippets.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide guidance for non-portal users.
- Include at least one end-to-end example using shell scripting or YAML for automation, which is common in Linux environments.
- Balance screenshots and examples between the portal and CLI to ensure parity for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-cross-region-restore.md
.../main/articles/backup/tutorial-cross-region-restore.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows-first bias by exclusively providing instructions for configuring and running Cross Region Restore using the Azure Portal UI, which is a graphical interface commonly associated with Windows workflows. There are no examples or guidance for performing these operations using Linux-friendly tools such as the Azure CLI, Bash scripts, or REST APIs. This omission makes it less accessible for Linux users or those who prefer command-line automation.
Recommendations
- Add equivalent step-by-step instructions using the Azure CLI for all major operations (enabling Cross Region Restore, viewing backup instances, restoring to secondary region).
- Include Bash script examples for automating Cross Region Restore tasks.
- Reference relevant REST API documentation and provide example API calls.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows environments using cross-platform tools.
- Ensure screenshots and UI references are supplemented with CLI or API output examples.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-restore-disk.md
...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_reference
Summary
The documentation page is primarily focused on Azure CLI usage, which is cross-platform, and most examples are generic and applicable to both Windows and Linux environments. However, there is evidence of Windows bias: the only reference to alternative tooling is a link to a PowerShell-based tutorial, and the cross-zonal restore section links to a Windows VM creation article before mentioning general availability zones. There are no Linux-specific examples, nor is there mention of Linux-specific considerations or parity with Windows tooling.
Recommendations
- Add explicit Linux examples or considerations, such as restoring Linux VMs with specific configurations (e.g., SSH keys, OS disk types).
- Include references to Linux VM documentation (e.g., creating Linux VMs in availability zones) alongside or before Windows equivalents.
- If mentioning PowerShell, also mention Bash or other Linux-native scripting options for parity.
- Clarify that all CLI commands are cross-platform and provide notes on any OS-specific differences in restore behavior or prerequisites.
- Where links to Windows documentation are provided, ensure equivalent Linux documentation is also linked.
Baremetal Infrastructure
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/workloads/nc2-on-azure/architecture.md
...-infrastructure/workloads/nc2-on-azure/architecture.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and CLI as management options, but does not mention or provide examples for Linux-specific tools or workflows. All examples and terminology are Azure-centric, with no mention of Linux-native management patterns, tools, or command-line environments. There are no Linux shell (bash) examples, nor references to Linux-based automation or integration approaches.
Recommendations
- Explicitly mention Linux management options alongside PowerShell and CLI, such as Bash, Azure CLI on Linux, or automation via Linux shell scripts.
- Provide example commands for both Windows (PowerShell) and Linux (bash/CLI) environments when describing deployment or management workflows.
- Reference Linux-native tools or integration patterns (e.g., Ansible, Terraform, SSH) where appropriate.
- Clarify that Azure CLI is cross-platform and provide usage examples in both Windows and Linux contexts.
- Add a section or note on Linux compatibility and best practices for managing NC2 on Azure from Linux systems.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-linux-rdp.md
.../main/articles/bastion/bastion-connect-vm-linux-rdp.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by requiring the use of RDP (a protocol and toolset traditionally associated with Windows environments) for connecting to Linux VMs, and referencing xrdp as a necessary component. There are no examples or mentions of Linux-native remote desktop protocols (such as VNC or X11 forwarding), nor are Linux-specific client tools or command-line examples provided. The documentation assumes RDP as the default/only method, which may not reflect common Linux administration practices.
Recommendations
- Provide examples of connecting to Linux VMs using native Linux remote desktop protocols (e.g., VNC, X11 forwarding) alongside RDP.
- Include Linux command-line examples for installing and configuring xrdp, and mention alternative Linux remote desktop solutions.
- Clarify why RDP is chosen over other protocols for Linux, and discuss the pros/cons for Linux administrators.
- Add instructions for connecting from Linux client machines (not just via Azure portal), including open-source RDP clients.
- Ensure parity in documentation by referencing both Windows and Linux tools and workflows where applicable.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-scale-set.md
.../main/articles/bastion/bastion-connect-vm-scale-set.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides instructions for connecting to a VM scale set using Azure Bastion exclusively through the Azure portal, with no mention of Linux-specific workflows, SSH, or command-line alternatives. The UI flow and terminology (e.g., 'RDP' anchor, 'Connect' button) are more familiar to Windows users. There are no examples or guidance for Linux users or those preferring SSH connections.
Recommendations
- Add instructions or examples for connecting to Linux VM instances using SSH via Azure Bastion, including both portal and CLI workflows.
- Explicitly mention that the process applies to both Windows and Linux VMs, and clarify any differences in the connection experience.
- Provide screenshots or examples showing SSH username/password or key-based authentication for Linux VMs.
- Include Azure CLI and/or PowerShell examples for users who prefer command-line access, ensuring parity between Windows and Linux scenarios.
- Avoid UI terminology that is specific to Windows (such as 'RDP') unless also covering SSH and Linux workflows.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-connect-vm-ssh-linux.md
.../main/articles/bastion/bastion-connect-vm-ssh-linux.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation page is generally focused on connecting to Linux VMs via Azure Bastion through the Azure portal, which is a cross-platform web interface. However, there is a recurring bias in the guidance for storing SSH keys in Azure Key Vault: the instructions and links reference PowerShell (a Windows-centric tool) first and do not provide explicit Linux/Unix shell (Bash) or cross-platform CLI examples. The linked quick-create guide for Key Vault uses PowerShell, and the recommendation to use 'PowerShell or Azure CLI' always lists PowerShell first, with no Bash-specific or Linux-native instructions. There are no explicit Linux command-line examples for common tasks, and the documentation does not mention or show parity for Linux users in these steps.
Recommendations
- Provide explicit Azure CLI (Bash) examples for creating and managing Azure Key Vault resources and secrets, and ensure these are presented alongside or before PowerShell examples.
- Update links such as 'Create a key vault' to point to both PowerShell and Azure CLI quickstart guides, or to a landing page that lets users choose their preferred platform.
- When referencing command-line tools, use 'Azure CLI' as the default or present it before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Add notes or sections clarifying that all steps can be performed from Linux/macOS terminals using Azure CLI, and provide sample commands.
- Review all instructions to ensure that Linux users are not implicitly directed to use Windows-centric tools or workflows.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-sku-comparison.md
...s/blob/main/articles/bastion/bastion-sku-comparison.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation presents VM connectivity options with Windows (RDP) and Linux (SSH) side by side, but lists Windows RDP connectivity before Linux SSH, and does not provide any platform-specific examples or guidance for Linux users. There is no mention of Linux tools, patterns, or command-line usage (e.g., SSH from Linux terminal), nor are Linux-specific workflows or troubleshooting steps included. The documentation does not show bias in terms of exclusive Windows tools or PowerShell-heavy examples, but the ordering and lack of Linux-centric examples indicate a subtle Windows-first bias.
Recommendations
- Provide explicit Linux usage examples, such as connecting via SSH from a Linux terminal or using Linux-native RDP clients.
- Include Linux-specific troubleshooting tips and best practices for Bastion connectivity.
- Balance the ordering of Windows and Linux features/examples in tables and descriptions, or alternate which platform is listed first.
- Reference Linux command-line tools (e.g., ssh, rdesktop, xfreerdp) where appropriate, alongside Windows tools.
- Add links to Linux documentation or guides for remote desktop and SSH connectivity through Azure Bastion.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/bastion-vm-copy-paste.md
...cs/blob/main/articles/bastion/bastion-vm-copy-paste.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively describes copy and paste functionality for Windows virtual machines, with no mention of Linux VMs or their specific requirements, behaviors, or examples. All instructions, prerequisites, and examples are focused on Windows, omitting Linux parity.
Recommendations
- Add a section for Linux VMs, detailing any differences in copy/paste behavior, prerequisites, and supported scenarios.
- Include Linux-specific examples and screenshots, such as using the clipboard in common Linux desktop environments (e.g., GNOME, KDE) when accessed via Bastion.
- Clarify whether the described Bastion clipboard features work identically for Linux VMs, and note any limitations or additional configuration steps required.
- If there are differences in keyboard shortcuts or clipboard integration for Linux, document them explicitly.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-host-arm-template.md
.../main/articles/bastion/quickstart-host-arm-template.md
Medium Priority
View Details â
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 RDP connection guides are linked. There are no examples or guidance for Linux VM deployment or SSH connections via Bastion, and no Linux-specific instructions or parity in the workflow.
Recommendations
- Add links to Linux VM quickstart guides in the 'Next steps' section, such as 'Quickstart: Create a Linux virtual machine in the Azure portal'.
- Include a link or section for connecting to a Linux VM using Azure Bastion (SSH), e.g., 'Connect to a Linux VM using Azure Bastion'.
- Ensure that examples and guidance are provided for both Windows and Linux scenarios throughout the documentation, not just in supplementary links.
- Review the documentation for any implicit assumptions of a Windows environment and clarify that Bastion supports both Windows (RDP) and Linux (SSH) connections.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-get-resource-counts.md
.../blob/main/articles/batch/batch-get-resource-counts.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page provides only C#/.NET code samples for counting task and node states in Azure Batch, with no Linux-specific examples, CLI commands, or cross-platform scripting options. While it mentions REST and other languages, no concrete examples are given. The exclusive use of .NET code (commonly associated with Windows environments) and lack of Linux/CLI examples indicate a Windows-first and missing Linux example bias.
Recommendations
- Add Azure CLI and Azure PowerShell examples for each operation, as both are cross-platform and widely used on Linux.
- Include REST API usage examples with curl or HTTPie commands to demonstrate platform-agnostic approaches.
- Provide Python SDK code samples, as Python is popular for automation on Linux.
- Explicitly mention that the .NET SDK can be used on Linux, if relevant, and provide instructions for doing so.
- Ensure that all code samples are balanced between Windows and Linux-friendly tools and languages.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-create-new-endpoint.md
...docs/blob/main/articles/cdn/cdn-create-new-endpoint.md
Medium Priority
View Details â
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 tooling, it implicitly favors Windows users by omitting CLI-based workflows (such as Azure CLI or Azure PowerShell), which are commonly used on Linux and macOS. There are no Linux-specific instructions or parity examples.
Recommendations
- Add Azure CLI examples for creating CDN profiles and endpoints, as the Azure CLI is cross-platform and widely used on Linux.
- If including PowerShell examples, ensure Azure CLI equivalents are provided and shown first or side-by-side.
- Mention that all steps can be performed from any OS using the Azure Portal, but highlight CLI options for users who prefer or require command-line workflows.
- Include a section or links to documentation for automating these tasks via CLI or scripts, which is important for Linux users.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/native-client.md
...azure-docs/blob/main/articles/bastion/native-client.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias in its examples and connection instructions. Windows native client scenarios are listed before Linux equivalents in both the connection table and the 'Next steps' section. There is a lack of explicit Linux configuration or example screenshots, and Linux instructions are less prominent or detailed compared to Windows. The page also references Windows-specific tools (RDP) before their Linux counterparts (SSH), and links for Windows are presented before Linux.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which platform is listed first in tables and instructions.
- Include Linux-specific screenshots and configuration steps where Windows screenshots are shown.
- Ensure 'Next steps' links for Linux are given equal prominence and order as Windows links.
- Provide explicit examples for connecting from Linux native clients, including command-line usage and any GUI tools commonly used on Linux.
- Mention and document Linux-specific considerations, such as SSH key management and file transfer tools, with equal detail as Windows RDP scenarios.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/session-monitoring.md
...-docs/blob/main/articles/bastion/session-monitoring.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation focuses exclusively on using the Azure Portal GUI for session monitoring and management, without providing any command-line examples. There is an implicit Windows bias as the Azure Portal is often associated with Windows-centric workflows, and there are no references to Linux tools, CLI commands, or cross-platform automation (e.g., Azure CLI, Bash, or PowerShell). No Linux-specific guidance or parity is offered.
Recommendations
- Add Azure CLI and/or PowerShell command examples for session monitoring and management to support automation and cross-platform usage.
- Explicitly mention that the Azure Portal is web-based and accessible from any OS, including Linux and macOS.
- Provide examples or references for managing Bastion sessions via REST API or scripting, with sample commands for both Bash (Linux/macOS) and PowerShell (Windows).
- Include notes or links to Linux-friendly tools and workflows where applicable.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/troubleshoot.md
.../azure-docs/blob/main/articles/bastion/troubleshoot.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation displays a mild Windows bias by prioritizing Windows-specific troubleshooting scenarios (such as domain-joined VM sign-in) and referencing Windows authentication patterns. However, it does provide a Linux/SSH example for key generation and does not exclusively use Windows tools or PowerShell. There is a lack of parity in addressing Linux-specific troubleshooting scenarios, such as connecting to Linux VMs with Azure Bastion or handling Linux authentication issues.
Recommendations
- Add troubleshooting examples and Q&A for common Linux VM connectivity issues, such as SSH authentication failures, username formats, and file transfer specifics for Linux.
- Include Linux domain-joined or Microsoft Entra joined VM scenarios if supported, or explicitly state limitations.
- When discussing domain-joined VM sign-in, provide parity by mentioning Linux VM authentication methods and any differences in Azure Bastion behavior.
- Ensure that any references to tools or patterns (such as RDP or username formats) are balanced with Linux equivalents (e.g., SSH, Linux username formats).
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/account-move.md
...cs/azure-docs/blob/main/articles/batch/account-move.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes using the Azure Portal (a web UI) for all steps and does not provide any command-line examples. While this avoids explicit Windows tool bias (such as PowerShell), it implicitly favors Windows users by omitting CLI-based workflows (e.g., Azure CLI, Bash scripts) that are common and preferred on Linux and macOS. There are no examples or instructions for performing these tasks via cross-platform tools, and no mention of Linux-specific considerations.
Recommendations
- Add parallel instructions and examples for moving a Batch account using the Azure CLI (az batch, az group deployment, etc.), which is cross-platform and widely used on Linux.
- Include sample Bash scripts or command-line snippets for exporting, modifying, and deploying ARM templates.
- Explicitly mention that all steps can be performed on Linux/macOS using the Azure CLI, and provide links to relevant CLI documentation.
- If PowerShell is referenced in other related docs, ensure Bash/Azure CLI equivalents are always provided.
- Clarify that the Azure Portal is web-based and platform-agnostic, but offer alternatives for users who prefer or require command-line automation.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-aad-auth.md
.../azure-docs/blob/main/articles/batch/batch-aad-auth.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive use of Azure Portal UI instructions and screenshots, which are tailored to the Windows-centric Azure Portal experience. There are no examples or instructions for Linux command-line tools (such as Azure CLI or PowerShell Core on Linux), nor are there references to Linux-specific workflows or authentication patterns. All code examples are platform-neutral (.NET and Python), but the setup and configuration steps assume use of the Azure Portal, which is most commonly accessed from Windows environments.
Recommendations
- Add equivalent instructions for registering applications, managing secrets, and assigning RBAC roles using Azure CLI and/or Azure PowerShell, which are available cross-platform.
- Include Linux shell (bash) examples for authentication flows, such as using environment variables or CLI commands to retrieve tenant IDs, client IDs, and secrets.
- Provide screenshots or terminal output examples from Linux environments where relevant.
- Explicitly mention that all steps can be performed from Linux or macOS using CLI tools, and link to relevant documentation.
- Ensure parity in code samples by showing how to use authentication libraries in Linux environments, including any OS-specific considerations.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-management-dotnet.md
...cs/blob/main/articles/batch/batch-management-dotnet.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation exclusively provides C#/.NET code examples and references to the .NET library, with no mention of Linux-specific usage, cross-platform development, or equivalent command-line or scripting examples (e.g., Bash, CLI). The sample project and all code snippets are tailored to Windows-centric development environments, implicitly prioritizing Windows users and omitting guidance for Linux developers.
Recommendations
- Add equivalent examples using Azure CLI or Bash scripts for common tasks (e.g., creating/deleting Batch accounts, managing keys, checking quotas), which are natively cross-platform and widely used on Linux.
- Explicitly mention that the .NET SDK and C# code can be used on Linux (e.g., with .NET Core/SDK on Linux) and provide setup instructions for Linux environments.
- Include references or links to Python or other cross-platform SDKs for Batch Management, with example code snippets.
- Ensure that any sample projects or GitHub repositories referenced include instructions for running on Linux, or provide alternative samples for Linux users.
- Where possible, balance the order of presentation so that cross-platform or Linux-friendly tools (e.g., Azure CLI, REST API) are mentioned alongside or before Windows-specific approaches.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md
...ified-compute-node-communication-model-migration-guide.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation mentions RDP connectivity before SSH when discussing diagnostic access to nodes, which prioritizes the Windows method over the Linux equivalent. Additionally, there are no concrete examples or instructions for either platform, but the order and phrasing suggest a Windows-first perspective. There are no PowerShell-heavy sections or exclusive mentions of Windows tools, but the lack of Linux-specific examples or parity in example order is notable.
Recommendations
- Present SSH connectivity before or alongside RDP when discussing diagnostic access, to reflect equal support for Linux nodes.
- Include explicit examples or instructions for both Windows (RDP) and Linux (SSH) connectivity.
- Ensure any agent or tool references clarify usage for both platforms, with equal detail.
- Review other documentation pages linked from this one to ensure Linux parity in examples and troubleshooting steps.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-role-based-access-control.md
...main/articles/batch/batch-role-based-access-control.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page describes Azure Batch RBAC concepts and procedures exclusively using the Azure portal UI, without mentioning command-line or automation approaches. There are no examples using Azure CLI, PowerShell, or REST API. While PowerShell is not directly referenced, the absence of Azure CLI or Linux-oriented instructions means the documentation implicitly favors Windows users (who are more likely to use the portal or PowerShell), and does not provide parity for Linux users who typically use Azure CLI or REST API.
Recommendations
- Add step-by-step instructions for assigning RBAC roles using Azure CLI, including full command examples.
- Include PowerShell examples for parity, but ensure Azure CLI examples are presented first or alongside PowerShell.
- Reference REST API documentation for role assignment and provide sample requests.
- Explicitly mention that all procedures can be performed from Linux, macOS, or Windows using Azure CLI or REST API.
- Add a table or section comparing methods (Portal, CLI, PowerShell, REST) for assigning roles, with links to relevant documentation.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/error-handling.md
.../azure-docs/blob/main/articles/batch/error-handling.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. In the 'Connect to compute nodes' section, instructions for connecting to Windows nodes (via RDP) are mentioned before Linux nodes (via SSH), and RDP is described in more detail. There are no explicit troubleshooting examples or tool references for Linux (e.g., examining Linux logs or using Linux-native commands), and the event log examination is mentioned generically without Linux equivalents. The page lacks concrete Linux-specific troubleshooting steps or examples.
Recommendations
- Provide Linux-specific troubleshooting examples, such as examining syslog, dmesg, or application logs in /var/log.
- Mention SSH connection steps and tools (e.g., using ssh command-line, Putty, etc.) with equal detail as RDP.
- Include references to Linux-native commands for node investigation (e.g., ps, top, journalctl) alongside Windows event log examination.
- Ensure that instructions for both OS types are presented in parallel, rather than Windows-first ordering.
- Add examples of handling exit codes and errors specific to Linux environments.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/network-security-perimeter.md
...blob/main/articles/batch/network-security-perimeter.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides step-by-step instructions for associating an Azure Batch account with a network security perimeter using the Azure portal, PowerShell, and Azure CLI. PowerShell instructions are given before Azure CLI, and there are detailed PowerShell code examples. This ordering and emphasis may indicate a Windows-first and PowerShell-heavy bias. However, Azure CLI (cross-platform) instructions are present and complete, and there are no exclusive references to Windows-only tools or missing Linux examples.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, to encourage non-Windows users.
- Consider adding Bash script examples or references to automation using Bash for Linux users.
- Where possible, provide parity in screenshots or UI walkthroughs for Azure Cloud Shell (which supports both Bash and PowerShell).
- Review language to ensure it does not imply PowerShell is the default or preferred method.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/tutorial-batch-functions.md
...s/blob/main/articles/batch/tutorial-batch-functions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation primarily uses the Azure portal for all steps and does not provide command-line examples for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, where OS-specific details are mentioned (e.g., VM image selection, start task commands), the examples use Ubuntu and Bash commands, not Windows. There is no explicit Windows bias in the form of PowerShell-heavy content or exclusive mention of Windows tools. However, the absence of any Linux CLI (e.g., Azure CLI) or cross-platform command-line examples means Linux users are not fully supported, and the portal-based workflow may be more familiar to Windows users.
Recommendations
- Add Azure CLI examples for creating Batch pools, jobs, and blob containers, showing both Windows and Linux command-line usage.
- Include Bash scripts for common tasks (e.g., uploading files, retrieving results) to support Linux users.
- Explicitly mention that the portal-based workflow is cross-platform, and provide links to Linux-friendly tools (e.g., Azure CLI, Storage Explorer for Linux).
- Where code or commands are shown (e.g., for the start task), clarify that they are for Ubuntu nodes, and provide Windows equivalents if relevant.
- Add a section or appendix with PowerShell and Bash equivalents for all major steps to ensure parity.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-custom-ssl.md
...cs/azure-docs/blob/main/articles/cdn/cdn-custom-ssl.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing the Azure portal (a web GUI) and does not provide any command-line examples. There are no instructions or examples using cross-platform tools such as Azure CLI, PowerShell, or Bash scripts. This omission leaves Linux and automation-focused users without guidance for non-GUI or non-Windows environments.
Recommendations
- Add Azure CLI examples for all major steps (enabling/disabling HTTPS, certificate management, domain validation) to provide parity for Linux and macOS users.
- If PowerShell examples are added, ensure equivalent Bash/Azure CLI commands are also present and shown first or side-by-side.
- Reference automation and scripting options (e.g., REST API, ARM templates, Bicep) for users who prefer or require non-GUI workflows.
- Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and link to relevant cross-platform documentation.
- Include troubleshooting steps or notes relevant to Linux environments, such as certificate format handling or DNS tools.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-pop-list-api.md
.../azure-docs/blob/main/articles/cdn/cdn-pop-list-api.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation does not provide any platform-specific examples or commands, but it references a downloadable IP list (from microsoft.com) that is typically provided as a CSV or XML file, often with usage patterns and tooling more familiar to Windows users. There are no explicit examples for retrieving or parsing the IP list using Linux tools (e.g., curl, wget, grep, jq), nor are there any PowerShell or Windows command examples. However, the lack of Linux-specific guidance or parity in examples constitutes a subtle Windows bias.
Recommendations
- Add explicit examples for retrieving and parsing the IP list using common Linux command-line tools (e.g., curl, wget, grep, awk, jq).
- Provide sample scripts or command snippets for both Windows (PowerShell) and Linux (bash) environments.
- Clarify the format of the downloadable IP list and suggest cross-platform tools for parsing it.
- Ensure that references to tools or methods are balanced between Windows and Linux, or are platform-agnostic where possible.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-purge-endpoint.md
...zure-docs/blob/main/articles/cdn/cdn-purge-endpoint.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation only describes how to purge an Azure CDN endpoint using the Azure Portal, a graphical tool primarily accessed via web browsers, which are equally available on Windows, Linux, and macOS. However, there are no command-line examples provided (such as Azure CLI, PowerShell, or REST API usage). The 'Next steps' section links to the REST API, but there are no explicit Linux-friendly (e.g., Azure CLI, Bash) examples or instructions. There is also no mention of PowerShell, but the absence of Linux-specific command-line examples may disadvantage Linux users who prefer CLI workflows.
Recommendations
- Add examples for purging a CDN endpoint using the Azure CLI, which is cross-platform and commonly used on Linux.
- Provide sample REST API calls using curl or HTTPie, with example commands that can be run from a Linux shell.
- If PowerShell examples are added in the future, ensure that Azure CLI or Bash equivalents are also included and presented with equal prominence.
- Explicitly mention that all operations can be performed from any OS via the Azure Portal, and highlight CLI options for users who prefer command-line tools.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/create-profile-endpoint-terraform.md
...main/articles/cdn/create-profile-endpoint-terraform.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence and is included as a dedicated tab, which may indicate a slight Windows bias. There are no explicit Linux shell examples (e.g., bash), and the CLI instructions use variable assignment syntax compatible with bash but do not clarify Linux usage. PowerShell is featured as a first-class option, which may not be relevant for Linux users. No Windows-specific tools are mentioned, but the lack of explicit Linux shell instructions and the inclusion of PowerShell suggest a mild Windows-first orientation.
Recommendations
- Add explicit bash/Linux shell examples for verification steps, clarifying compatibility and usage on Linux/macOS.
- Clearly indicate which instructions are cross-platform and which are Windows-specific.
- Consider providing a 'Linux/macOS' tab alongside 'Azure CLI' and 'Azure PowerShell' to ensure parity.
- Mention that Azure CLI is available on all platforms and provide installation guidance for Linux/macOS if appropriate.
- Review variable assignment syntax to ensure it is correct for both bash and PowerShell, or provide separate examples.
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/tier-migration.md
...cs/azure-docs/blob/main/articles/cdn/tier-migration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation references updating DevOps scripts to use the new API, Azure PowerShell module, and CLI commands, but only mentions PowerShell (a Windows-centric tool) explicitly. There are no Linux-specific tools, commands, or examples provided, nor is there mention of Bash, Azure CLI on Linux, or cross-platform scripting. The documentation assumes familiarity with Windows tooling and does not provide parity for Linux users.
Recommendations
- Explicitly mention Azure CLI (az) commands alongside PowerShell, and provide examples for both.
- Include Bash or shell scripting examples for common migration tasks.
- Clarify that migration can be performed from any OS, and link to cross-platform tooling documentation.
- Ensure that any references to scripting or automation cover both Windows and Linux environments equally.
Certification
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/certification/edge-secured-core-devices.md
...in/articles/certification/edge-secured-core-devices.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation lists only devices running Windows 10/11 IoT Enterprise as Edge Secured-core certified, with no mention of Linux or other operating systems. This suggests a bias toward Windows, both in terms of supported platforms and examples provided.
Recommendations
- Include information about Edge Secured-core certification for devices running Linux or other operating systems, if available.
- Clarify in the introduction whether Linux-based devices are eligible or supported for Edge Secured-core certification.
- If Linux support is not available, explicitly state this to avoid confusion and to set expectations for cross-platform users.
- Consider adding a section or table for Linux (and other OS) devices if/when they become certified, to improve parity and inclusivity.
Certification
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/certification/overview.md
...zure-docs/blob/main/articles/certification/overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by explicitly stating support for Windows IoT Enterprise and Azure Sphere OS, while Linux support is only mentioned as a future possibility. There are no examples, instructions, or resources for Linux users, and the focus is primarily on Windows-based solutions.
Recommendations
- Add clear timelines and details for Linux support to set expectations for Linux users.
- Include equivalent Linux examples, instructions, or guidance where possible, even if support is in preview or limited.
- Reference Linux tools, patterns, or certification processes alongside Windows equivalents to ensure parity.
- Regularly update the documentation to reflect progress on Linux support and provide migration or preparation guidance for Linux device builders.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/get-started/new-storage.md
...b/main/articles/cloud-shell/get-started/new-storage.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents both Bash (Linux) and PowerShell (Windows) options for Cloud Shell, but PowerShell is often mentioned alongside or immediately after Bash, and some examples (such as the 'Azure drive' and 'Get-AzCommand') are PowerShell-specific features not available in Bash. The 'Next steps' section lists PowerShell before CLI, subtly prioritizing Windows tools.
Recommendations
- Ensure that Bash (Linux) examples are presented first or in parallel with PowerShell examples, especially in introductory sections.
- Avoid referencing PowerShell-specific features (like the Azure drive) without Linux/Bash equivalents or clearly marking them as PowerShell-only.
- In the 'Next steps' section, alternate the order of PowerShell and CLI links or group them together to avoid implicit prioritization.
- Where possible, provide Bash/Linux equivalents for any PowerShell-specific workflows or commands.
- Explicitly state that both Bash and PowerShell are fully supported, and clarify any differences in capabilities or features.
Cloud Services Extended Support
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-portal.md
...icles/cloud-services-extended-support/deploy-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates Windows bias primarily in the 'Related content' section, where deployment alternatives are listed as Azure PowerShell, ARM template, and Visual Studio. Both PowerShell and Visual Studio are Windows-centric tools, and PowerShell is mentioned before ARM templates (which are cross-platform). There are no explicit Linux CLI or Bash examples, nor is the Azure CLI (which is cross-platform and popular on Linux) mentioned as an alternative deployment method.
Recommendations
- Add instructions and examples for deploying Cloud Services (extended support) using Azure CLI, which is cross-platform and widely used on Linux.
- List cross-platform tools (such as Azure CLI and ARM templates) before Windows-specific tools (PowerShell, Visual Studio) to avoid implicit prioritization.
- Include explicit references to Linux workflows, such as uploading deployment packages from Linux systems, and clarify that the Azure portal and ARM templates are OS-agnostic.
- If possible, provide screenshots or examples from Linux environments to demonstrate parity.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/overview.md
.../azure-docs/blob/main/articles/cloud-shell/overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page for Azure Cloud Shell presents both Bash and PowerShell as available shell options, but PowerShell is consistently mentioned alongside or before Bash, and links to Azure PowerShell documentation are given equal prominence to Azure CLI. The integrated editor is described in the context of Azure CLI or Azure PowerShell, with no mention of Bash scripting or Linux-native tools. There are no explicit Linux-only examples or tools highlighted, and the documentation does not provide parity in discussing Linux workflows or tools.
Recommendations
- Explicitly mention Bash and Linux-native tools (e.g., sed, grep, vim, nano) as available and supported in Cloud Shell.
- Provide links to Bash scripting documentation or Linux command-line guides alongside PowerShell references.
- When listing access points or features, alternate the order of Bash and PowerShell to avoid implicit prioritization.
- In the editor section, mention editing and running Bash scripts as a first-class scenario.
- Add examples or references that showcase Linux command-line workflows in Cloud Shell.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/deployment.md
...docs/blob/main/articles/cloud-shell/vnet/deployment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for key operations (resource group and virtual network creation, getting Container Instance ID), but PowerShell is consistently mentioned before CLI in lists and examples. This ordering, along with the explicit mention of PowerShell in command examples and links, suggests a subtle Windows-first bias. There are no Linux-specific tools or patterns referenced, and Bash is only mentioned as a shell choice, not in example commands.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples and links, or list CLI first to balance representation.
- Explicitly mention Linux environments and Bash usage in command examples where relevant.
- Include screenshots or walkthroughs using Bash/CLI on Linux, not just PowerShell or portal UI.
- Add notes clarifying that all CLI commands work on Linux, macOS, and Windows.
- Where possible, provide Bash script snippets for automation alongside PowerShell equivalents.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/security/how-to-support-multiple-users.md
.../cloud-shell/security/how-to-support-multiple-users.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page provides only Azure Portal (GUI) instructions for managing storage accounts and file shares, without any command-line examples. There are no examples using Azure CLI, Bash, or PowerShell, but the lack of Linux (CLI) examples is notable given that Cloud Shell is often used in Bash environments. The instructions follow a GUI workflow, which is more familiar to Windows users, and do not mention or prioritize Linux-native tools or workflows.
Recommendations
- Add Azure CLI (az) command-line examples for increasing file share quota and assigning roles, as these are cross-platform and commonly used in Linux environments.
- Explicitly mention that the steps can be performed in both Bash and PowerShell Cloud Shell environments, and provide equivalent CLI commands.
- If possible, provide PowerShell examples as well, but ensure that Azure CLI (Bash-friendly) examples are given equal or higher prominence.
- Clarify that the Azure Portal is platform-agnostic, but supplement GUI instructions with CLI alternatives to support Linux users.
- Consider adding a section or callout for automation using scripts, which is a common pattern for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/analytics/logs/call-metrics-log-schema.md
...ces/concepts/analytics/logs/call-metrics-log-schema.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits a mild Windows bias. In the sample data, 'DeviceOsName' is set to 'Windows' and 'DeviceBrowser' to 'Edge', with no examples for Linux or macOS. The platform and OS examples and sample logs focus exclusively on Windows, and there are no Linux-specific instructions, tools, or sample data. While the documentation is generally OS-agnostic in its explanations, the absence of Linux (or macOS) examples and the use of Windows as the default in sample data suggest a 'windows_first' and 'missing_linux_example' bias.
Recommendations
- Add sample log entries that use Linux and macOS as 'DeviceOsName' and browsers such as Chrome or Firefox to demonstrate cross-platform support.
- Where platform or OS is mentioned (e.g., in tables or examples), include Linux and macOS alongside Windows to reinforce parity.
- If there are any platform-specific considerations for collecting or analyzing logs (e.g., using Azure CLI on Linux), mention them explicitly.
- Ensure that any referenced tools or dashboards are confirmed to work on Linux and macOS, and note any differences if they exist.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/call-automation/azure-communication-services-azure-cognitive-services-integration.md
...nication-services-azure-cognitive-services-integration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exhibits a mild Windows bias by referencing Windows in resource creation links (e.g., '?tabs=windows') and not providing any Linux-specific or cross-platform examples. All instructions are portal-based with no CLI, PowerShell, or Bash examples, but where platform is mentioned, Windows is referenced first or exclusively. There are no explicit Linux or macOS instructions, nor are there any screenshots or guidance for non-Windows users.
Recommendations
- Remove or supplement Windows-specific links (e.g., '?tabs=windows') with Linux/macOS equivalents or a platform selector.
- Add Azure CLI and/or Bash examples for resource creation and management steps, alongside portal instructions.
- Explicitly state that the instructions are platform-agnostic or provide notes for Linux/macOS users where relevant.
- Include screenshots or references that reflect non-Windows environments if applicable.
- Ensure that any referenced tools or commands (e.g., for role assignments or identity management) have cross-platform guidance.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/call-logs-azure-monitor-access.md
...on-services/concepts/call-logs-azure-monitor-access.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes accessing logs via the Azure Portal web interface, which is platform-agnostic but implicitly Windows-first due to the lack of command-line or automation examples. There are no examples using cross-platform tools (e.g., Azure CLI, Bash, or PowerShell Core), nor are there instructions for accessing logs from Linux environments.
Recommendations
- Add Azure CLI examples for enabling and accessing logs, which work on both Windows and Linux.
- Include sample Bash scripts for downloading logs from the storage account.
- Mention PowerShell Core (cross-platform) if providing PowerShell examples, and ensure parity with Bash/CLI.
- Explicitly state that the Azure Portal can be accessed from any OS, and provide links to CLI documentation for automation scenarios.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/european-union-data-boundary.md
...tion-services/concepts/european-union-data-boundary.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation references a resource management link with a query parameter 'tabs=windows', suggesting that Windows is the default or primary platform for examples. There are no explicit Linux or cross-platform examples or instructions, and no mention of Linux tools or parity. This may unintentionally signal that Windows is the preferred or only supported environment.
Recommendations
- Provide equivalent Linux (and macOS, if relevant) examples or instructions alongside Windows examples.
- Ensure that cross-platform instructions are clearly marked and that platform-specific tabs (e.g., 'tabs=windows', 'tabs=linux') are available where applicable.
- Avoid defaulting to Windows in links or code samples; instead, present platform options equally.
- Review linked quickstarts and ensure Linux parity in resource management and CLI instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/email/email-headers.md
...communication-services/concepts/email/email-headers.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides only .NET (C#) code examples and instructs users to run the application using the 'dotnet run' command, which is cross-platform but most commonly associated with Windows development. There are no examples or instructions for Linux-specific tools, shell commands, or alternative SDKs (such as Python or Node.js), and no mention of Linux-specific considerations.
Recommendations
- Add examples using other SDKs (e.g., Python, Node.js) that are popular on Linux.
- Include instructions for running the code on Linux (e.g., using bash, mentioning prerequisites for Linux environments).
- Explicitly state that 'dotnet run' works on Linux and macOS, and provide any Linux-specific troubleshooting tips if applicable.
- Consider adding a section or note about using the Azure Communication Services Email API from Linux environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/identifiers/identifiers-net.md
...vices/concepts/includes/identifiers/identifiers-net.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively provides C# code samples and references to .NET APIs, which are most commonly used on Windows. There is no mention of Linux-specific tools, patterns, or alternative SDKs, nor are there any examples for Linux environments or cross-platform usage. The documentation implicitly assumes a Windows/.NET development environment and does not address Linux parity.
Recommendations
- Include examples using cross-platform SDKs (e.g., JavaScript/TypeScript, Python) that run natively on Linux.
- Add explicit notes or sections about Linux compatibility and usage, including any required dependencies or setup steps.
- Reference CLI tools (such as Azure CLI) and REST API usage with curl or other Linux-native tools.
- Clarify that the APIs and SDKs are cross-platform where applicable, and provide guidance for Linux developers.
- Provide sample code that can be executed on Linux (e.g., bash scripts, Python, Node.js) alongside C#/.NET examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/enable-closed-captions.md
...on-services/concepts/interop/enable-closed-captions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation demonstrates a Windows bias by listing 'Windows' before other platforms when describing SDK availability and by referencing Teams policies using PowerShell modules without mentioning Linux or cross-platform alternatives. There are no explicit Linux examples or tools mentioned, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
- When listing supported platforms (e.g., SDKs), use a neutral or rotating order, or explicitly mention Linux support if available.
- If referencing Teams policies via PowerShell modules, also mention or link to cross-platform management options (such as Microsoft Graph API or Teams Admin Center web UI), and clarify if PowerShell is required or if alternatives exist.
- Include explicit Linux support statements or examples where relevant, especially for SDK usage or policy management.
- Review the documentation for any implicit assumptions of a Windows environment and add clarifications or alternatives for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/monitor-logs-metrics.md
...ervices/concepts/interop/guest/monitor-logs-metrics.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page references Microsoft Teams Admin Center and Teams Call Quality Dashboard as primary tools for log review, which are web-based but are typically associated with Windows-centric administration workflows. There are no explicit examples or instructions for accessing logs or metrics via Linux tools, command-line interfaces, or cross-platform methods. No PowerShell commands are given, but the absence of Linux-specific guidance or CLI/API usage suggests a Windows bias.
Recommendations
- Include examples or instructions for accessing Azure logs and metrics using cross-platform tools such as Azure CLI or REST APIs.
- Mention and provide examples for Linux users on how to retrieve and analyze logs, e.g., using az command-line tool or curl.
- Clarify whether the Teams Admin Center and Call Quality Dashboard are accessible and fully functional from non-Windows platforms.
- Add references to documentation or tools that are platform-agnostic for log analysis.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-provisioning.md
.../interop/tpe/teams-phone-extensibility-provisioning.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Teams administration and provisioning processes that are typically performed using Windows-centric tools (e.g., cmdlets, Teams Admin roles) without providing equivalent Linux or cross-platform examples. There is no mention of Linux-compatible tools, CLI alternatives, or guidance for non-Windows environments, and all procedural descriptions assume the use of Microsoft-centric (often Windows-based) administration interfaces.
Recommendations
- Include examples using cross-platform tools such as Azure CLI, Microsoft Graph API via curl or other Linux-friendly methods, and PowerShell Core (pwsh) where applicable.
- Explicitly mention whether provisioning and authorization steps can be performed from Linux or macOS environments, and provide instructions for those platforms.
- Add sample commands or scripts for Linux environments, such as bash scripts or REST API calls using curl.
- Clarify any platform dependencies for Teams administration tasks and suggest alternatives for non-Windows users.
- Ensure that all referenced tools and processes are accessible from Linux and document any limitations or required workarounds.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/govern-meeting-experience.md
...ts/interop/virtual-visits/govern-meeting-experience.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Microsoft 365 and Teams administrative tools, which are typically managed via Windows-centric interfaces (such as Teams Admin Center, PowerShell, or Microsoft 365 portal). There are no explicit examples or instructions for Linux users, nor is there mention of cross-platform command-line tools or APIs that could be used from Linux environments. The documentation implicitly assumes a Windows administrative environment.
Recommendations
- Include explicit instructions or references for managing Teams policies and meeting options via cross-platform tools such as the Microsoft Graph API, which can be accessed from Linux.
- If PowerShell is required, mention PowerShell Core (pwsh), which is available on Linux, and provide examples for installing and using it.
- Clarify whether administrative tasks can be performed via web interfaces accessible from Linux browsers, and note any limitations.
- Add Linux-specific notes or examples where relevant, especially for automation or scripting tasks.
- Where possible, provide REST API examples (e.g., using curl or HTTP requests) for policy and meeting management.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/includes/user-facing-diagnostics-android.md
...eo-calling/includes/user-facing-diagnostics-android.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and Android-focused, but there are subtle Windows biases. Some mitigation steps reference 'device manager' for enabling microphones, which is a Windows-specific tool, without mentioning Linux or macOS equivalents. There are no explicit Linux examples or references to Linux-specific tools or workflows, and the only platform-specific guidance is for Windows and macOS.
Recommendations
- When referencing device management (e.g., enabling microphones), include Linux equivalents such as using 'alsamixer', 'pavucontrol', or relevant system settings.
- Provide parity in troubleshooting steps for Linux (and other platforms) wherever Windows or macOS tools are mentioned.
- Explicitly state if a diagnostic or mitigation step is platform-specific, and offer alternatives for other platforms.
- Consider adding a table or section summarizing how to perform common device management tasks (e.g., enabling/disabling microphones or cameras) on Windows, Linux, and macOS.
- Review all mitigation steps for implicit platform assumptions and generalize or diversify instructions to cover Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/sdk-options.md
...rticles/communication-services/concepts/sdk-options.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page shows a moderate Windows bias, primarily in the SDK platform support section. Windows platforms and tools (.NET, UWP, WinUI3) are described in greater detail and listed before Linux and macOS equivalents. There is a lack of parity in platform-specific guidance, with Windows-specific deployment and support notes (e.g., unpackaged app not supported) and more granular versioning for Windows. No explicit Linux or macOS examples, troubleshooting, or deployment notes are provided. However, the SDKs themselves are cross-platform and Linux is mentioned as supported for .NET Standard 2.0.
Recommendations
- Add explicit Linux and macOS platform support tables and troubleshooting sections, similar to the detailed Windows/.NET support section.
- Provide Linux/macOS-specific deployment notes, including known issues, best practices, and supported distributions/versions.
- Ensure that any Windows-specific limitations (e.g., unpackaged app support) are matched with equivalent notes for Linux/macOS where relevant.
- Include Linux/macOS examples or references in sections discussing SDK usage, especially where OS-specific behavior or setup may differ.
- Consider listing cross-platform support (Linux, macOS, Windows) together, or in alphabetical order, rather than Windows-first.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/about-call-types.md
...vices/concepts/voice-video-calling/about-call-types.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias in the 'Video quality' section, where Windows is listed as a first-class platform alongside WebJS, iOS, and Android, and is the only desktop OS called out. No Linux desktop support or examples are mentioned, and there is no indication of parity for Linux users. There are no explicit PowerShell or Windows command-line examples, but the omission of Linux as a supported platform or in examples suggests a bias toward Windows environments.
Recommendations
- Explicitly mention Linux support (or lack thereof) in the 'Video quality' table and other relevant sections.
- If Linux is supported, add a column for Linux in the video quality table and provide details.
- If Linux is not supported, clarify this in the documentation to set user expectations.
- Include examples or guidance for Linux users where appropriate, or reference cross-platform SDK usage.
- Review all sections to ensure Linux is considered alongside Windows, especially in platform capability tables.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/network-requirements.md
...s/concepts/voice-video-calling/network-requirements.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a mild Windows bias by listing 'native Windows, Android, and iOS SDKs' bandwidth requirements, but does not mention Linux as a supported native platform or provide Linux-specific guidance. There are no explicit Linux examples, tools, or troubleshooting steps, and Windows is mentioned before other platforms. No PowerShell or Windows-only tools are referenced, but Linux is notably absent from native SDK and optimization discussions.
Recommendations
- Explicitly state Linux support status for native SDKs. If Linux is supported, add Linux to the bandwidth requirements table and provide relevant guidance.
- Include Linux-specific examples or troubleshooting steps where appropriate, especially in sections discussing firewall configuration, NAT, and VPN.
- When listing platforms (e.g., 'native Windows, Android, and iOS SDKs'), use a more inclusive order or clarify why Linux is omitted.
- Reference common Linux tools (e.g., iptables, nftables, systemd-resolved) alongside Windows equivalents in network and firewall configuration sections.
- Provide parity in optimization guidance, such as mentioning Linux VPN clients and Linux QoS configuration tools.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-csharp.md
...tomation/includes/audio-streaming-quickstart-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias primarily by referencing Windows-first resources (e.g., the 'Create an Azure Communication Services resource' link uses '?tabs=windows') and by omitting explicit Linux examples or instructions. All code samples are in C# (cross-platform), but there are no Linux-specific setup steps, troubleshooting notes, or parity in referenced documentation. The only external WebSocket documentation linked is Windows-focused.
Recommendations
- Provide Linux-specific instructions or examples, especially for setting up the WebSocket server and installing dependencies.
- Update prerequisite links to include Linux tabs or provide parity for Linux and macOS users.
- Reference cross-platform or Linux-focused WebSocket documentation in addition to (or instead of) Windows-specific resources.
- Add troubleshooting notes or tips relevant to Linux environments (e.g., common firewall, permissions, or .NET runtime issues).
- Explicitly state that the C# code samples are cross-platform and note any OS-specific considerations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-js.md
...l-automation/includes/audio-streaming-quickstart-js.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific resources first and omitting Linux-specific instructions or examples. In the prerequisites, the link to creating an Azure Communication Services resource uses a Windows tab by default, and there is no mention of Linux or cross-platform setup. Additionally, the WebSocket documentation link points to a Windows Azure Web Sites blog post, with no Linux equivalent or general guidance. All code examples are platform-neutral (JavaScript), but supporting instructions and references are Windows-centric.
Recommendations
- Provide Linux-specific or cross-platform instructions and links in the prerequisites, such as a Linux tab for resource creation.
- Include documentation or blog links for setting up WebSocket servers on Linux (e.g., using Node.js on Ubuntu or other distributions).
- Ensure all referenced guides and quickstarts have parity between Windows and Linux, or explicitly mention cross-platform compatibility.
- Add a note clarifying that all JavaScript examples are platform-independent and can be run on both Windows and Linux environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-csharp.md
...ll-automation/includes/play-audio-quickstart-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a subtle Windows bias. In the prerequisites, links and instructions reference Windows first (e.g., resource creation link uses '?tabs=windows'), and there are no explicit Linux-specific instructions or examples. All command-line and SDK usage examples are OS-agnostic, but there are no Linux shell or cross-platform environment setup examples. No mention is made of Linux-specific considerations, tools, or troubleshooting.
Recommendations
- Provide explicit Linux (and macOS) instructions or tabs alongside Windows for resource creation and environment setup.
- Ensure all links that use '?tabs=windows' also have Linux and macOS equivalents, or clarify that instructions are cross-platform.
- Add notes or sections on using the .NET SDK and NuGet on Linux (e.g., using dotnet CLI on Ubuntu, installing dependencies).
- Include troubleshooting tips or common issues for Linux users, if any.
- Review all examples and ensure that none assume a Windows environment (e.g., file paths, shell commands).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-with-ai-csharp.md
.../call-automation/includes/play-audio-with-ai-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exhibits a Windows-first bias, particularly in the prerequisites section where links and instructions reference Windows tabs and do not provide explicit Linux equivalents. There are no Linux-specific examples or guidance, and the only command-line example is generic (dotnet), but the resource creation links default to Windows. No mention is made of Linux-specific considerations, tools, or troubleshooting.
Recommendations
- Provide explicit Linux instructions and examples alongside Windows, especially for resource creation and setup steps.
- Ensure that documentation links (such as quickstarts) include tabs or pivots for Linux and macOS, not just Windows.
- Mention any Linux-specific requirements or troubleshooting tips, such as installing .NET on Linux, using bash/zsh, or file path conventions.
- Where possible, include screenshots or terminal output from Linux environments to demonstrate parity.
- Review and update all references to ensure that Linux users are equally supported and not required to adapt Windows-centric instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-with-ai-java.md
...os/call-automation/includes/play-audio-with-ai-java.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the prerequisites section, where links and instructions reference Windows first (e.g., resource creation links with '?tabs=windows' and no mention of Linux/Mac equivalents). There are no explicit Linux-specific instructions or examples, and the documentation does not clarify cross-platform compatibility for commands or tools. However, the main code and build instructions (Java, Maven) are inherently cross-platform.
Recommendations
- Update prerequisite links to include or reference Linux/Mac instructions or ensure the default is platform-neutral.
- Explicitly state that all command-line and Maven instructions are cross-platform, and provide examples of running them on Linux/Mac terminals if any differences exist.
- Where links use '?tabs=windows', either add or point to Linux/Mac tabs, or clarify that the instructions are the same for all platforms.
- Add a note in the prerequisites or setup section confirming support for Linux/Mac and any platform-specific requirements or caveats.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-action-quickstart-csharp.md
...omation/includes/recognize-action-quickstart-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias primarily in the prerequisites section, where links and instructions reference Windows first (e.g., resource creation links with '?tabs=windows'), and there are no explicit Linux-specific instructions or examples. All command-line and code examples are platform-agnostic (using 'dotnet'), but there is no mention of Linux-specific considerations, nor are there any Linux/macOS terminal screenshots or package manager alternatives. The documentation assumes familiarity with .NET and NuGet, which are cross-platform, but does not provide parity in guidance for Linux users.
Recommendations
- Provide explicit instructions or links for Linux users in the prerequisites, such as resource creation guides with Linux tabs or pivots.
- Include Linux/macOS terminal screenshots or clarify that all 'dotnet' commands work identically on Linux and macOS.
- Mention any Linux-specific dependencies or troubleshooting steps, if applicable.
- Ensure that all links (such as resource creation) default to a neutral or platform-agnostic view, or provide clear tabs for both Windows and Linux.
- If there are any platform-specific behaviors or requirements (e.g., for installing .NET or NuGet), reference official Linux installation guides.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-ai-action-how-to-csharp.md
...tomation/includes/recognize-ai-action-how-to-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a Windows bias by referencing Windows first in resource creation links (e.g., 'tabs=windows' in quickstart URLs) and does not provide any Linux-specific instructions or examples. All command-line and SDK usage examples are platform-agnostic (using dotnet CLI and C#), but there are no explicit Linux or macOS instructions, troubleshooting notes, or parity checks. The documentation assumes familiarity with Windows-centric patterns and omits Linux equivalents or considerations.
Recommendations
- Update quickstart/resource creation links to include Linux/macOS tabs or clarify that the instructions apply to all platforms.
- Explicitly mention that the dotnet CLI commands work on Linux/macOS and provide any platform-specific prerequisites (e.g., installing .NET SDK on Linux).
- Add troubleshooting notes or environment setup instructions for Linux (e.g., file path formats, permissions, or common issues).
- Ensure that all referenced guides and pivots include Linux/macOS options, not just Windows.
- Consider including a short section or callout for Linux/macOS users to highlight any differences or confirm parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/secure-webhook-endpoint-csharp.md
...-automation/includes/secure-webhook-endpoint-csharp.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation provides only C#/.NET examples and references to NuGet packages, which are primarily associated with Windows development environments. There are no examples or guidance for validating JWTs in webhook callbacks using Linux-centric tools, languages, or frameworks (e.g., Python, Node.js, Java, or command-line utilities commonly used on Linux).
Recommendations
- Add equivalent JWT validation examples using popular Linux-friendly languages and frameworks such as Python (with PyJWT), Node.js, or Java.
- Mention cross-platform package managers and libraries, not just NuGet.
- Clarify that the JWT validation process is platform-agnostic and provide links or references to Linux/open-source tool documentation.
- If possible, provide command-line or script-based validation examples (e.g., using curl and jq) to demonstrate platform neutrality.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/record-every-call.md
...-services/how-tos/call-automation/record-every-call.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a Windows-first bias by linking to Windows-specific Azure CLI installation instructions and not providing explicit Linux/macOS equivalents. All setup and CLI instructions assume parity but do not clarify or provide Linux-specific guidance, which may confuse or hinder Linux users.
Recommendations
- Provide installation links for Azure CLI for all major platforms (Windows, Linux, macOS) in the prerequisites section.
- Explicitly mention that Visual Studio Code and ngrok are cross-platform, and provide any Linux/macOS-specific notes if needed.
- Where commands or tools differ between platforms (e.g., Azure CLI installation, environment variable handling), include platform-specific tabs or notes.
- Review all links and ensure they do not default to Windows-specific documentation unless appropriate.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-android.md
...ling-sdk/includes/capabilities/capabilities-android.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page introduces the capabilities feature for the Azure Communication Services Call API and explicitly states usage 'for Windows' before providing code examples. There are no references to Linux, macOS, or cross-platform usage, nor are there examples or instructions for non-Windows environments. The language and structure suggest a Windows-centric approach, with no parity for Linux users.
Recommendations
- Remove or rephrase 'for Windows' unless the feature is truly Windows-exclusive. If cross-platform, clarify applicability.
- Add explicit examples or instructions for Linux (and macOS, if supported), including any platform-specific setup or code differences.
- Mention platform compatibility in the introduction, and provide guidance for users on non-Windows systems.
- If there are platform-specific limitations, document them clearly and provide alternative approaches or workarounds for Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-ios.md
.../calling-sdk/includes/capabilities/capabilities-ios.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation explicitly refers to using the capabilities feature 'for Windows' and does not mention Linux or provide Linux-specific examples or guidance. All code examples are platform-neutral (Swift), but the introductory text and context focus solely on Windows, omitting Linux parity.
Recommendations
- Clarify whether the feature is available on Linux and, if so, provide equivalent instructions or examples for Linux.
- Avoid phrasing such as 'for Windows' unless the feature is truly Windows-exclusive; otherwise, use platform-neutral language.
- If the feature is not supported on Linux, explicitly state this to inform users.
- If Linux is supported, add a section or examples demonstrating usage or any platform-specific considerations for Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-web.md
...s/closed-captions/closed-captions-teams-interop-web.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows-first bias, particularly in the prerequisites section, where links and instructions reference Windows-specific tabs or pivots (e.g., '?tabs=windows') without mention of Linux or cross-platform alternatives. There are no explicit Linux examples or guidance for Linux users, and no mention of Linux-specific tools or considerations, despite the cross-platform nature of Azure Communication Services.
Recommendations
- Update prerequisite links to include Linux (and macOS) tabs or pivots, or provide platform-agnostic instructions where possible.
- Explicitly mention that the SDK and features are cross-platform, and provide confirmation or examples for Linux environments if supported.
- Ensure that all quickstart and resource creation guides referenced are available and linked for Linux users.
- Review and update any referenced documentation to ensure Linux parity in setup and usage instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/teams-interopability/teams-interopability-android.md
...s/teams-interopability/teams-interopability-android.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation includes a direct reference to a Windows-specific SDK installation guide and does not mention Linux or provide Linux-specific installation instructions or examples. The '[!INCLUDE [Install SDK](../install-sdk/install-sdk-windows.md)]' directive points only to Windows, indicating Windows-first bias and missing Linux parity.
Recommendations
- Provide parallel Linux installation instructions or an SDK installation guide for Linux, and include it alongside or before the Windows instructions.
- If cross-platform SDKs are supported, clarify this in the documentation introduction and link to both Windows and Linux installation guides.
- Add Linux-specific usage notes or troubleshooting tips if there are platform differences.
- Ensure that code examples and setup instructions are not platform-specific or, if they are, provide equivalent Linux examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/teams-interopability/teams-interopability-ios.md
...ludes/teams-interopability/teams-interopability-ios.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page includes an 'Install SDK' section that links specifically to a Windows installation guide, with no mention of Linux or cross-platform alternatives. There are no Linux-specific instructions or examples, and the initial setup appears to assume a Windows environment.
Recommendations
- Provide equivalent SDK installation instructions for Linux and macOS, or link to a cross-platform installation guide.
- Explicitly mention platform compatibility and requirements for the SDK and APIs.
- Include Linux/macOS-specific examples or notes where relevant, especially for environment setup and permissions.
- Ensure that referenced guides (such as 'install-sdk-windows.md') have parallel documentation for other platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/chat-sdk/archive-chat-threads.md
...tion-services/how-tos/chat-sdk/archive-chat-threads.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by linking to chat message listing instructions with a 'tabs=windows' parameter, suggesting Windows is the default or primary platform. There are no explicit Linux or cross-platform examples, and no mention of Linux-specific tools or commands. The documentation does not provide parity for Linux users, nor does it clarify if the instructions are cross-platform.
Recommendations
- Provide explicit Linux and macOS examples or clarify that the instructions are cross-platform.
- Use neutral or platform-agnostic links and code snippets, or include tabs for Windows, Linux, and macOS where relevant.
- Mention and demonstrate use of cross-platform tools (e.g., Azure CLI, REST API) instead of assuming a Windows environment.
- Review all links and references to ensure they do not default to Windows-specific instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/event-grid/view-events-request-bin.md
...services/how-tos/event-grid/view-events-request-bin.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by linking to Azure CLI installation instructions specifically for Windows in both the pre-requisites and configuration steps, without mentioning or providing equivalent instructions for Linux or macOS. There are no examples or guidance for Linux users, and the CLI installation link defaults to Windows, suggesting a Windows-first approach.
Recommendations
- Include installation instructions for Azure CLI on Linux and macOS, or link to the cross-platform installation guide.
- Explicitly mention that Azure CLI is cross-platform and provide guidance for users on different operating systems.
- Add notes or examples for common Linux shell environments (e.g., bash, zsh) where relevant.
- Ensure screenshots and step-by-step instructions are not Windows-centric, or provide alternatives for other platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/router-sdk/azure-function.md
...nication-services/how-tos/router-sdk/azure-function.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation does not explicitly show Windows-specific tools or commands, but it implicitly exhibits Windows bias by only providing C# code examples (commonly associated with Windows development) and not offering equivalent examples in languages or tools more familiar to Linux users (such as Python, JavaScript, or Bash). There are no references to Linux-specific workflows, and the instructions for inspecting the deployed function mention the Azure portal without mentioning CLI alternatives, which may be more common among Linux users.
Recommendations
- Provide code examples in additional languages commonly used on Linux, such as Python or JavaScript, alongside C#.
- Include instructions for inspecting and managing Azure Functions using the Azure CLI or Azure Functions Core Tools, not just the Azure portal.
- Explicitly mention that Azure Functions can be developed and deployed from Linux environments and provide links or notes about cross-platform development.
- Where possible, show terminal/command-line examples for configuration steps, not just SDK or portal-based instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-javascript.md
...ssaging/whatsapp/includes/common-setting-javascript.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides only Windows-specific commands (setx) for setting environment variables, with no equivalent Linux/macOS examples. Windows tools and workflows (Visual Studio, setx) are mentioned exclusively or before any cross-platform alternatives. There is no guidance for Linux or macOS users on setting environment variables, which may hinder non-Windows developers.
Recommendations
- Add Linux/macOS equivalents for setting environment variables, e.g., 'export VAR=value' for Bash/zsh.
- Include cross-platform instructions or a table showing commands for Windows (cmd/PowerShell), Linux, and macOS.
- Mention non-Windows editors (e.g., VS Code) alongside Visual Studio when discussing restarting IDEs.
- Review referenced links to ensure Linux/macOS instructions are present and clearly indicated.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-net.md
...nced-messaging/whatsapp/includes/common-setting-net.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides only C# code examples and references to the Azure portal, with no mention of Linux-specific tools, CLI commands, or cross-platform alternatives. There are no Linux shell or cross-platform code samples, and the workflow assumes use of the Azure portal, which is platform-agnostic but often more familiar to Windows users. No PowerShell-specific commands are present, but the lack of Linux or bash equivalents and the exclusive use of C# (commonly associated with Windows development) indicate a Windows-first and missing Linux example bias.
Recommendations
- Add code examples in additional languages commonly used on Linux, such as Python or JavaScript, especially for command-line or scripting tasks.
- Provide CLI (e.g., Azure CLI) or bash shell command examples for authentication and resource management, alongside or instead of portal instructions.
- Explicitly mention that the SDK and instructions are cross-platform, and provide guidance for Linux/macOS users where workflows may differ.
- Include screenshots or instructions for accessing resources from non-Windows environments if there are differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/interactive/messages-quickstart-interactive-messages-net.md
...active/messages-quickstart-interactive-messages-net.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Visual Studio (a Windows-centric IDE) first in both the prerequisites and code execution instructions. The 'Run the code' section provides detailed steps for Visual Studio (Windows) before mentioning the .NET CLI, but does not provide any Linux-specific instructions or examples (e.g., using VS Code on Linux, or running .NET CLI commands in a Linux shell). There are no references to Linux tools, shell commands, or Linux-specific environment setup.
Recommendations
- Add explicit instructions for running the code on Linux, such as using the .NET CLI in a Bash shell.
- Include VS Code as a cross-platform IDE in the 'Run the code' section, with Linux-specific steps.
- Mention installation and setup steps for .NET on Linux (e.g., using apt-get or yum).
- Provide example commands for building and running the code in a Linux terminal.
- Clarify that the .NET CLI instructions apply equally to Windows, Linux, and macOS, and provide sample terminal output for Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/reactions/messages-quickstart-reaction-messages-net.md
...reactions/messages-quickstart-reaction-messages-net.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Visual Studio (a Windows-centric IDE) first in the 'Run the code' section, providing keyboard shortcuts specific to Windows, and omitting explicit Linux or macOS instructions for running .NET code. There are no examples or guidance for Linux-specific development environments, nor are there instructions for running the sample code on Linux terminals or with Linux-specific tools.
Recommendations
- Add explicit instructions for running the code on Linux and macOS, including terminal commands and any required environment setup.
- Include Linux-friendly IDEs (e.g., JetBrains Rider, MonoDevelop) or mention that Visual Studio Code and .NET CLI are cross-platform.
- Provide keyboard shortcuts for building and running code in Visual Studio Code and .NET CLI on Linux/macOS, or clarify that the commands work across platforms.
- Consider adding a note or section highlighting cross-platform compatibility of the .NET SDK and sample code.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-python.md
...tart-make-an-outbound-call-using-callautomation-python.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation shows mild Windows bias by mentioning Visual Studio Code and Visual Studio as the only editors/IDEs for running the code, with Visual Studio (a Windows-specific tool) given a dedicated section. There are no explicit Linux or cross-platform editor instructions, and the instructions for running the code in Visual Studio appear before any mention of running from a generic terminal. However, most command-line examples use Bash syntax and Python, which are cross-platform.
Recommendations
- Add explicit instructions for running the code from a generic terminal (e.g., Bash or CMD) on both Windows and Linux/macOS.
- Include examples or mention of popular Linux/macOS editors (e.g., PyCharm, VS Code on Linux, or simply using the terminal).
- Clarify that Visual Studio Code is cross-platform and provide Linux/macOS installation links.
- If providing a Visual Studio section, also provide a section for running from the command line on Linux/macOS.
- Ensure that any tool or workflow mentioned (such as DevTunnels) is available and supported on Linux/macOS, and provide platform-specific notes if there are differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/includes/chat-csharp.md
...tion-services/quickstarts/chat/includes/chat-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a mild Windows bias by listing Windows tools (cmd, PowerShell) before Bash when suggesting console windows, and by recommending Visual Studio as the only IDE without mentioning cross-platform alternatives. There are no explicit Linux-specific instructions or examples, and the setup steps assume familiarity with Windows-centric development environments.
Recommendations
- When listing console options, alternate the order or explicitly mention Bash/terminal first to balance platform representation.
- Mention Visual Studio Code as a cross-platform alternative to Visual Studio, and provide a link to its download page.
- Add a note clarifying that all dotnet CLI commands work identically on Linux, macOS, and Windows.
- If there are any platform-specific steps (e.g., environment variables, file paths), provide Linux/macOS equivalents.
- Consider including a short section or callout for Linux/macOS users, confirming that the instructions are cross-platform.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/includes/chat-logic-app.md
...n-services/quickstarts/chat/includes/chat-logic-app.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Power Automate and Azure Logic Apps, which are primarily Windows-centric tools. All examples and instructions are given in the context of these graphical workflow tools, with no mention of Linux-native equivalents, CLI, or cross-platform scripting options. There are no Linux-specific instructions, nor any parity examples for Linux users.
Recommendations
- Include equivalent instructions for Linux users, such as using Azure CLI, REST API, or SDKs (Python, Node.js, etc.) to perform the same operations.
- Provide examples for automating Communication Services tasks using cross-platform tools and scripting languages.
- Explicitly mention platform requirements and alternatives for users who do not use Windows or Power Automate.
- Add a section comparing workflow automation options on Linux (e.g., Azure Functions, Logic Apps via REST, etc.) and how to achieve similar results.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-dot-net.md
...cludes/create-azure-managed-domain-resource-dot-net.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation page provides only C#/.NET SDK code examples and references to the Azure portal for resource management. There are no explicit Linux or cross-platform command-line examples (such as Azure CLI or Bash), and the authentication guidance refers to a link that defaults to command-line instructions but does not specify Bash or Linux terminal usage. The SDK and tooling focus is on .NET, which is cross-platform but historically Windows-centric. No PowerShell-specific commands are present, but there is a lack of parity for Linux users who may prefer CLI or Bash scripts.
Recommendations
- Add Azure CLI (az) command examples for all resource management operations alongside the C# SDK examples.
- Explicitly mention that .NET Core SDK and the Azure SDK are cross-platform and provide Bash/Linux terminal equivalents for authentication and environment variable setup.
- Include instructions or links for managing resources using Bash scripts or shell commands, not just the Azure portal.
- Where environment variables are used (e.g., AZURE_SUBSCRIPTION_ID), show both Windows (set) and Linux (export) syntax.
- Clarify that all examples work on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux-specific issues if any.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-az-cli.md
...kstarts/email/includes/create-email-resource-az-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by linking exclusively to the Windows installation instructions for Azure CLI in the prerequisites, without mentioning or providing links for Linux or macOS. All command-line examples use Azure CLI, which is cross-platform, but there is no explicit guidance or reassurance for Linux/macOS users, nor are there any examples or notes about platform differences.
Recommendations
- Add links to Azure CLI installation instructions for Linux and macOS alongside the Windows link in the prerequisites.
- Include a note stating that Azure CLI commands work on Windows, Linux, and macOS, and mention any platform-specific considerations if relevant.
- Consider providing example commands or screenshots from a Linux terminal to demonstrate parity.
- Avoid using 'azurepowershell-interactive' as the code block language if the commands are Azure CLI, to prevent confusion with PowerShell (which is Windows-centric). Use 'azurecli' or 'bash' where appropriate.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-dot-net.md
...starts/email/includes/create-email-resource-dot-net.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively provides C#/.NET examples and references to the Azure portal, without mentioning or providing parity for Linux-specific workflows, tools, or shell environments. There are no examples for Linux command-line tools (e.g., Bash, Azure CLI), and the authentication and environment variable setup steps implicitly assume familiarity with Windows or .NET-centric workflows.
Recommendations
- Add Azure CLI and Bash examples for authentication, resource creation, and management tasks, alongside the C#/.NET SDK examples.
- Explicitly mention that the .NET SDK and Azure CLI are cross-platform and provide instructions for Linux and macOS users where relevant.
- Include examples of setting environment variables in Bash (Linux/macOS) as well as in PowerShell/Command Prompt (Windows).
- Reference Linux-friendly tools and workflows (e.g., using the Azure CLI in a terminal) in parallel with Azure portal and .NET SDK options.
- Ensure that any links to SDK downloads or authentication guides highlight cross-platform compatibility and provide platform-specific instructions if needed.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-sender-username-resource-az-cli.md
...ail/includes/create-sender-username-resource-az-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a Windows bias by linking only to the Windows-specific Azure CLI installation guide and not mentioning Linux or macOS installation options. All command-line examples use the Azure CLI, which is cross-platform, but the installation instructions and links are Windows-first. No Linux-specific instructions or terminal conventions are provided.
Recommendations
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside the Windows link.
- Clarify that the Azure CLI commands work on all supported platforms (Windows, Linux, macOS).
- Use neutral or cross-platform code block labels (e.g., 'bash', 'sh', or 'azurecli') instead of 'azurepowershell-interactive', which may imply PowerShell/Windows bias.
- Add a note or section for Linux/macOS users, including any platform-specific considerations (e.g., use of single vs. double quotes, environment variable syntax).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-sender-username-resource-dot-net.md
...il/includes/create-sender-username-resource-dot-net.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing C#/.NET examples and referencing environment variable usage without platform-specific guidance. There are no examples or instructions for Linux users (e.g., Bash, CLI commands, or Linux-specific environment variable setting), nor is there mention of cross-platform tooling or parity in workflow. The authentication section references a Microsoft Learn page that defaults to command-line instructions but does not clarify Linux usage.
Recommendations
- Add explicit instructions and code examples for setting environment variables on Linux/macOS (e.g., export AZURE_SUBSCRIPTION_ID=...) alongside Windows methods.
- Include Azure CLI or Bash script examples for authentication and resource management to complement the C#/.NET samples.
- Mention cross-platform compatibility of the .NET SDK and clarify any OS-specific steps or differences.
- Provide links to Linux/macOS-specific documentation for SDK installation and usage.
- Where possible, show parity in tooling (e.g., PowerShell vs Bash/CLI) and avoid assuming a Windows-first workflow.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-python.md
...rvices/quickstarts/email/includes/send-email-python.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows-first bias by providing only Windows-style commands for activating the Python virtual environment (e.g., '.\Scripts\activate') and omitting the equivalent Linux/macOS commands (e.g., 'source ./bin/activate'). No explicit Linux or macOS instructions or examples are provided for environment setup, which may confuse or hinder non-Windows users.
Recommendations
- Add Linux/macOS equivalents for all terminal commands, especially for virtual environment activation (e.g., 'source ./bin/activate' for bash/zsh).
- Wherever a command is platform-specific, use tabbed sections or callouts to show both Windows and Linux/macOS instructions.
- Explicitly mention that the instructions apply to all platforms, and clarify any platform-specific differences.
- Review the documentation for other subtle Windows-centric assumptions (e.g., path separators, command syntax) and address them for cross-platform clarity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/attachments-java.md
...email/send-email-advanced/includes/attachments-java.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a code example that uses a Windows-style file path ('C:/attachment.txt') without mentioning or showing a Linux/macOS equivalent. There are no examples or notes for Linux users, which may cause confusion or extra effort for those on non-Windows platforms.
Recommendations
- Include a Linux/macOS file path example (e.g., '/home/user/attachment.txt') alongside the Windows example.
- Add a note clarifying that file paths are platform-specific and users should adjust them accordingly.
- Consider providing a cross-platform code snippet or guidance on detecting the operating system and setting file paths appropriately.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/email-object-model-net.md
...send-email-advanced/includes/email-object-model-net.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides only .NET/C# code examples, which are most commonly used on Windows platforms. There is no mention of Linux-compatible SDKs, alternative programming languages, or cross-platform usage considerations. Console.WriteLine and .NET SDK references implicitly prioritize Windows development environments.
Recommendations
- Include examples using cross-platform languages or frameworks (e.g., Python, Java, Node.js) that are commonly used on Linux.
- Explicitly mention that the .NET SDK is cross-platform and can be used on Linux and macOS, with instructions or links for Linux setup.
- Provide sample commands or troubleshooting steps for Linux environments (e.g., using Bash, Linux terminal).
- Reference Linux email clients or tools alongside Outlook when discussing header recognition.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/attachments-net.md
.../email/send-email-advanced/includes/attachments-net.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a file path example using Windows-style paths (e.g., C:\Users\Documents\attachment.pdf) and does not mention or provide examples for Linux or macOS file paths. There are no Linux-specific instructions or notes, and the only example given could confuse or exclude Linux users.
Recommendations
- Include Linux/macOS file path examples (e.g., /home/user/attachment.pdf) alongside the Windows example.
- Add a note clarifying that file paths should be adapted to the user's operating system.
- Ensure that code samples and instructions are cross-platform or provide OS-specific variants where necessary.
- Explicitly mention that the .NET SDK and dotnet CLI are cross-platform and can be used on Linux/macOS as well as Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/send-email-smtp-oauth.md
...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when describing where to run commands. There are no Linux-specific instructions, troubleshooting tips, or examples, and the guidance assumes parity without verifying Linux-specific nuances (e.g., package installation, environment setup).
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites and instructions.
- Provide Linux/macOS-specific instructions for installing .NET Core and MailKit, including package manager commands (e.g., apt, yum, brew).
- List Bash first or equally alongside Windows consoles when referencing command-line usage.
- Add troubleshooting notes for common Linux issues (e.g., permissions, firewall, OpenSSL dependencies).
- Include screenshots or terminal output examples from Linux environments.
- Clarify any platform-specific differences in SMTP connectivity or authentication.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/create-event-subscription-az-cli.md
...ts/events/includes/create-event-subscription-az-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by linking to the Windows-specific Azure CLI installation guide in the prerequisites, without mentioning or linking to Linux or macOS installation instructions. All command-line examples use the cross-platform Azure CLI, which is good, but there are no explicit Linux or macOS installation or usage examples, nor is there mention of platform-specific considerations.
Recommendations
- Update the Azure CLI installation link to point to the general installation page or include links for Windows, Linux, and macOS.
- Explicitly mention that the Azure CLI commands work on all supported platforms (Windows, Linux, macOS).
- Optionally, provide a short note or example showing command execution in a Linux/macOS shell, or clarify that the examples are platform-agnostic.
- Avoid defaulting to Windows-specific links or instructions in cross-platform documentation.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/register-event-grid-resource-provider.md
...ents/includes/register-event-grid-resource-provider.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation exclusively describes how to register the Event Grid resource provider using the Azure portal (a GUI tool), which is most commonly used on Windows. There are no examples or instructions for performing the same task using cross-platform tools such as the Azure CLI or Azure PowerShell, which are commonly used on Linux and macOS. This omission results in a bias towards Windows users.
Recommendations
- Add instructions for registering the Event Grid resource provider using the Azure CLI, which works on Linux, macOS, and Windows.
- Include Azure PowerShell examples, clarifying that PowerShell Core is cross-platform.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide command-line alternatives for automation and parity.
- Ensure that future documentation sections provide both GUI and CLI-based instructions to support all platforms equally.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-az-cli.md
...identity/includes/access-tokens/access-token-az-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation exhibits a Windows-first bias in several areas. Installation instructions for the Azure CLI link directly to the Windows-specific page, and in environment variable setup sections, Windows instructions are consistently presented before macOS and Linux. The use of Windows-specific tools (e.g., setx) is highlighted, and Visual Studio is referenced as the default editor example, reinforcing a Windows-centric perspective. However, Linux and macOS instructions are present and technically complete.
Recommendations
- Provide a cross-platform Azure CLI installation link or mention all OS options equally, rather than linking only to the Windows installer.
- Rotate or randomize the order of OS tabs (Windows, macOS, Linux) or default to a neutral/cross-platform tab to avoid always presenting Windows first.
- When referencing editors or IDEs, include popular cross-platform or Linux editors (e.g., VS Code, JetBrains IDEs, Vim) alongside Visual Studio.
- Ensure that all command-line examples and environment variable instructions are equally detailed and visible for Linux and macOS, not just Windows.
- Consider adding a short note at the start of environment variable sections stating that instructions are available for all major OSes, to reinforce parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/entra-id/support-entra-id-users-net.md
...entity/includes/entra-id/support-entra-id-users-net.md
Medium Priority
View Details â
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 how to create a new C# application. There are no explicit Linux-specific instructions, examples, or troubleshooting notes, and no mention of Linux tools or patterns. All commands are platform-agnostic (dotnet CLI), but the lack of Linux-specific context or parity in examples may hinder Linux users.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows consoles (cmd, PowerShell) when describing command-line usage.
- Add explicit notes or examples for Linux users, such as verifying .NET SDK installation on Linux, using environment variables in Bash, and opening files with Linux editors (e.g., nano, vim).
- Include troubleshooting tips for common Linux issues (e.g., permissions, path differences).
- Clarify that all commands work cross-platform and provide links to .NET installation guides for Linux and macOS.
- Mention Linux-specific package managers or installation steps if relevant.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/create-resource-az-cli.md
...ervices/quickstarts/includes/create-resource-az-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by linking only to the Windows-specific Azure CLI installation instructions and not mentioning or linking to Linux or macOS equivalents. All command-line examples use the Azure CLI, which is cross-platform, but there is no explicit mention or guidance for Linux or macOS users. The installation link and lack of platform parity in instructions may confuse or exclude non-Windows users.
Recommendations
- Provide installation links for Azure CLI on all supported platforms (Windows, Linux, macOS), or use a platform-agnostic link.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS terminals.
- If there are any platform-specific considerations (e.g., shell differences), mention them or provide examples for Bash/zsh as well as PowerShell.
- Avoid using the 'azurepowershell-interactive' code block type if the commands are not PowerShell-specific; use a more neutral code block or clarify that the commands are shell-agnostic.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/create-resource-net.md
...n-services/quickstarts/includes/create-resource-net.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides only C#/.NET code examples and instructions for interacting with Azure Communication Services, with no explicit mention of Linux-specific workflows, shell commands, or cross-platform considerations. Steps for setting environment variables and retrieving subscription IDs reference the Azure portal (web UI), which is platform-neutral, but there are no CLI examples (e.g., Azure CLI or Bash) that would be familiar to Linux users. All code assumes a Windows/.NET development environment, and there are no PowerShell-specific commands, but the lack of Linux/Bash equivalents or explicit cross-platform guidance results in a Windows-first and missing-Linux-example bias.
Recommendations
- Add Azure CLI (az) command examples for common tasks such as retrieving the subscription ID, creating service principals, and managing resource groups.
- Provide Bash shell commands for setting environment variables, in addition to the implicit Windows/PowerShell approach.
- Explicitly mention that the .NET SDK and examples work on Linux, and link to .NET Core installation instructions for Linux distributions.
- Include at least one end-to-end example using the Azure CLI and Bash to demonstrate parity for Linux users.
- Clarify that all portal-based instructions are platform-agnostic, and offer CLI alternatives where possible.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/network-security-perimeter.md
...ion-services/quickstarts/network-security-perimeter.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by linking exclusively to Windows installation instructions for Azure CLI and omitting Linux-specific guidance or examples. All command-line examples use Azure CLI, which is cross-platform, but there is no mention of Linux installation, shell usage, or parity checks. The page does not reference PowerShell or Windows-only tools directly, but the installation instructions and context assume a Windows-first audience.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS, not just Windows.
- Clarify that all Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes if needed (e.g., quoting, environment variables).
- Include examples or screenshots using Linux shells (bash/zsh) and terminal environments.
- Review and update any referenced documentation links to ensure Linux parity and visibility.
- If mentioning Cloud Shell, clarify that it is OS-agnostic and available in browser for all platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/receive-sms-js.md
...on-services/quickstarts/sms/includes/receive-sms-js.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias by instructing users to run the Azure Function locally using 'F5' in Visual Studio Code, a shortcut that is only available in the Windows/macOS GUI version of VS Code and not in headless or terminal-only Linux environments. There are no explicit Linux-specific instructions or terminal-based alternatives for running or debugging the function. However, the rest of the instructions (ngrok, Azure CLI) are cross-platform and use bash commands, which are Linux-friendly. No PowerShell or Windows-only tools are used, but the lack of Linux-specific guidance or parity in the local run/debug instructions is a notable omission.
Recommendations
- Add instructions for running the Azure Function locally using the command line (e.g., 'func start' or 'npm start') for Linux users who may not use the VS Code GUI.
- Clarify that 'F5' is a Visual Studio Code GUI shortcut and provide alternative steps for users on Linux or those using VS Code in a headless environment.
- Explicitly state that all CLI and ngrok commands work on Linux, and provide any Linux-specific troubleshooting tips if relevant.
- Consider adding a section or callout box for Linux users to ensure parity and inclusivity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-net.md
...ces/quickstarts/rooms/includes/rooms-quickstart-net.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page shows mild Windows bias. In the 'Create a new C# application' section, Windows shells (cmd, PowerShell) are mentioned before Bash, and no Linux-specific instructions or examples are provided. All command-line examples use the generic 'dotnet' CLI, which is cross-platform, but there are no explicit Linux or macOS instructions, troubleshooting tips, or environment-specific notes. The documentation assumes parity but does not demonstrate it.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
- Add explicit notes or sections for Linux/macOS users, such as verifying .NET installation, common permissions issues, or differences in environment setup.
- Include example commands for installing .NET Core on Linux/macOS, or link to relevant platform-specific installation guides.
- Provide troubleshooting tips for common Linux/macOS issues (e.g., executable permissions, path issues).
- Clarify that all dotnet CLI commands work identically on Linux/macOS, or call out any known differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/manage-rooms-call.md
...cation-services/quickstarts/rooms/manage-rooms-call.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by linking to quickstarts and conceptual documentation with Windows-specific tabs or pivots, such as 'tabs=windows' and 'platform-azcli'. There are no explicit Linux or cross-platform CLI examples, and no mention of Linux-specific tools or instructions. All code samples are language SDK-based and platform-agnostic, but supporting links and instructions default to Windows, omitting Linux parity.
Recommendations
- Add explicit Linux instructions and examples alongside Windows, especially for setup, CLI usage, and environment configuration.
- Ensure all quickstart and concept links include Linux tabs or pivots, or provide platform-neutral guidance.
- Mention cross-platform compatibility for SDKs and clarify any OS-specific requirements or differences.
- Where CLI or shell commands are referenced, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Audit all linked documentation to ensure Linux parity and avoid defaulting to Windows-first navigation.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/sms-opt-out-api-csharp.md
...ces/quickstarts/sms/includes/sms-opt-out-api-csharp.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides only a C# code sample and references the .NET Core SDK, which, while cross-platform, is more commonly associated with Windows development. There are no examples or instructions for using Linux-specific tools, shells, or scripting languages (e.g., Bash, curl), nor is there mention of how to run the sample on Linux or macOS. The documentation implicitly assumes a Windows-centric development environment.
Recommendations
- Add equivalent code samples or instructions using Bash and curl to demonstrate how to interact with the Opt-Out API from Linux environments.
- Explicitly mention that .NET Core SDK is cross-platform and provide guidance or links for installing and running it on Linux and macOS.
- Include examples using other common cross-platform languages (e.g., Python) to broaden accessibility.
- Ensure that any command-line instructions or environment setup steps are shown for both Windows (e.g., PowerShell, CMD) and Linux/macOS (e.g., Bash).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/number-lookup-net.md
...es/quickstarts/telephony/includes/number-lookup-net.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation uses generic terms like 'terminal or command window' but implicitly assumes a Windows-centric development environment by not providing explicit Linux (or macOS) shell examples or addressing platform-specific differences. All command-line instructions use .NET CLI commands, which are cross-platform, but there is no mention of Linux-specific considerations (e.g., shell syntax, environment variable setup, or package manager alternatives). The documentation does not provide any Linux- or macOS-specific guidance or examples, and the phrase 'command window' is more familiar to Windows users.
Recommendations
- Explicitly mention that all commands work on Windows, Linux, and macOS, and clarify that 'terminal' refers to Bash/zsh/etc. on Linux/macOS and 'command window' or 'PowerShell' on Windows.
- Provide Linux/macOS-specific notes where relevant, such as how to set environment variables (e.g., 'export VAR=VALUE' for Bash vs. 'set VAR=VALUE' for Windows CMD).
- Include example commands for both Windows and Linux/macOS where differences exist (e.g., path separators, environment variable syntax).
- Use more inclusive language, such as 'open a terminal (Command Prompt, PowerShell, or Bash)' instead of 'terminal or command window'.
- Add troubleshooting notes for common cross-platform issues (e.g., permissions, executable paths).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/voice-routing-sdk-csharp.md
...kstarts/telephony/includes/voice-routing-sdk-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias by listing Windows shells (Command Prompt, PowerShell) before Bash when instructing users to open a console window. No Linux-specific tools or commands are missing, but the ordering and mention of Windows environments first may subtly prioritize Windows users. All command-line examples use .NET CLI, which is cross-platform, and no exclusive Windows tools are used.
Recommendations
- List Bash (Linux/macOS) first or equally with Command Prompt and PowerShell when mentioning console options.
- Explicitly state that all commands work on Linux, macOS, and Windows.
- Consider providing a short note or section for Linux/macOS users, confirming parity and any OS-specific considerations (such as package managers or environment setup).
- Use neutral phrasing such as 'In a terminal window (such as Bash, Command Prompt, or PowerShell)...' to avoid implicit prioritization.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/closed-captions/closed-captions-android.md
...ng/includes/closed-captions/closed-captions-android.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias primarily in the prerequisites and resource management sections. Links to resource creation and cleanup explicitly reference Windows tabs or pivots, and there is no mention of Linux or cross-platform equivalents. All code examples are Android/Java-specific (which is neutral), but platform-specific instructions and links default to Windows, with no Linux guidance or parity.
Recommendations
- Update prerequisite and cleanup links to include Linux or cross-platform tabs/pivots, or provide explicit Linux instructions where relevant.
- Ensure that any platform-specific instructions (e.g., for Azure CLI, resource management) are presented for both Windows and Linux, or clarify when steps are platform-agnostic.
- Review and update quickstart/resource links to avoid defaulting to Windows, or provide a selector for the user's platform.
- Add a note clarifying that the steps are applicable to both Windows and Linux unless otherwise specified.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/custom-teams-endpoint/voice-video-calling-cte-javascript.md
...m-teams-endpoint/voice-video-calling-cte-javascript.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by recommending the MSI installer for Node.js and linking to resource creation instructions with a Windows-specific tab. There are no explicit Linux instructions or examples for installing Node.js, creating resources, or running the sample, even though all steps are cross-platform. The documentation does not mention Linux package managers or provide parity for Linux users.
Recommendations
- Provide Linux-specific instructions for installing Node.js (e.g., using apt, yum, or other package managers).
- Ensure resource creation links default to a neutral or cross-platform tab, or explicitly mention Linux/macOS options.
- Add notes or examples confirming that all steps work on Linux and macOS, and highlight any platform-specific differences if they exist.
- Avoid recommending Windows-only installers (MSI) without mentioning alternatives for other platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-teams-interop-group-calls.md
...video-calling/get-started-teams-interop-group-calls.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation demonstrates a mild Windows bias. It references the Azure portal (which is cross-platform but often perceived as Windows-centric) and, more notably, requires Teams users to be 'Enterprise Voice enabled' with a link to a PowerShell-based guide. The Teams deployment link also points to a Microsoft documentation page that is Windows-focused. There are no explicit Linux or macOS-specific instructions, nor are there alternative command-line examples (e.g., Bash, Azure CLI) for enabling Teams features. However, the main code samples and instructions are platform-neutral (JavaScript, npx, browser-based), and no PowerShell or cmd commands are directly shown.
Recommendations
- Provide explicit instructions or links for enabling Teams features (like Enterprise Voice) using cross-platform tools such as Azure CLI or Microsoft Graph API, if available.
- Clarify that the Azure portal and Teams administration can be accessed from any OS/browser, not just Windows.
- If PowerShell is required, mention that PowerShell Core is available on Linux/macOS and provide installation guidance.
- Add notes or examples for Linux/macOS users where administrative tasks (e.g., Teams user setup) may differ.
- Ensure that all prerequisite links and instructions are inclusive of non-Windows environments, or at least acknowledge platform differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-video-constraints.md
...s/voice-video-calling/get-started-video-constraints.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides platform-specific guidance for Windows, Android, iOS, and Web, but does not include any examples or guidance for Linux. Additionally, 'Windows' is listed as a primary platform, while Linux is omitted, which may suggest a bias toward Windows environments.
Recommendations
- Add a dedicated Linux section or clarify Linux support, especially for desktop or web scenarios where Linux is relevant.
- If the Web/JavaScript example is intended to cover Linux, explicitly state this to avoid confusion.
- Ensure that Linux users are not excluded by providing parity in examples, troubleshooting, and platform pivots.
- Consider listing platforms in a neutral or alphabetical order to avoid implicit prioritization.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-closed-captions.md
...oice-video-calling/get-started-with-closed-captions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides platform-specific guidance for web, Windows, Android, and iOS, but omits Linux as a platform. Additionally, resource cleanup instructions reference Windows tabs and do not mention Linux equivalents, suggesting a Windows-first approach and missing Linux parity.
Recommendations
- Add a Linux-specific pivot or section if the SDK or service supports Linux clients.
- Include Linux examples for resource cleanup, such as CLI commands or instructions relevant to Linux environments.
- Ensure parity in sample links and next steps by providing Linux-relevant samples or guidance.
- Clarify platform support in the introduction, explicitly stating whether Linux is supported or not.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-real-time-text.md
...voice-video-calling/get-started-with-real-time-text.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page shows a mild Windows bias by listing Windows (C#) terminology and class names before Linux or cross-platform equivalents, and by using Windows-specific naming conventions (e.g., 'Details' vs. 'Info') in tables. There is no explicit mention of Linux or Linux-specific instructions, and the C# example is labeled as 'Windows', which may imply C# is only for Windows, even though .NET Core is cross-platform.
Recommendations
- Clarify that C#/.NET examples are cross-platform and not limited to Windows. Consider labeling the C# section as 'C# (.NET)' instead of 'Windows (C#)'.
- In naming convention tables, include Linux or cross-platform terminology if applicable, or clarify that the differences are between .NET and mobile SDKs, not OS-specific.
- Ensure that examples and terminology do not imply that certain languages or SDKs are exclusive to Windows when they are not.
- If there are Linux-specific considerations or examples (e.g., for .NET on Linux), include them to ensure parity.
- Review and update documentation to use platform-neutral language where possible, especially in class/property naming and section headers.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-voice-video-calling-custom-teams-client.md
...t-started-with-voice-video-calling-custom-teams-client.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides platform-specific quickstart guides for web, Windows, Android, and iOS, but does not mention or provide examples for Linux desktop environments. Additionally, resource cleanup instructions reference Windows tabs, with no mention of Linux equivalents, suggesting a Windows-first approach and a lack of Linux parity.
Recommendations
- Add explicit Linux desktop instructions or examples, especially for Electron or other common Linux desktop frameworks.
- Ensure resource cleanup instructions include Linux-specific tabs or CLI examples (e.g., Bash, Azure CLI on Linux).
- Review referenced samples and guides to confirm Linux compatibility and provide Linux-specific guidance where needed.
- Consider including a 'platform-linux' pivot zone alongside existing platform pivots.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-csharp.md
...cludes/call-recording-samples/call-recording-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively provides C#/.NET code samples and instructs users to download the .NET SDK, which is traditionally associated with Windows development. There are no examples or instructions for Linux users, such as using .NET on Linux, alternative SDKs, or cross-platform CLI usage. No mention is made of Linux-specific tools, shell commands, or environment setup, and the documentation implicitly assumes a Windows-centric development environment.
Recommendations
- Explicitly mention that .NET and the Azure Communication Services SDK are cross-platform and can be used on Linux and macOS as well as Windows.
- Provide installation instructions for the .NET SDK on Linux (e.g., using apt-get, yum, or snap).
- Include code samples or instructions for running the sample app on Linux, such as using the dotnet CLI in a bash shell.
- Add troubleshooting tips or notes for Linux users, such as file permissions or environment variables.
- Reference Linux-compatible tools for event handling and webhooks, and clarify that Azure Event Grid and related APIs are OS-agnostic.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-java.md
...includes/call-recording-samples/call-recording-java.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the file path example for downloading recordings, which uses Windows-style backslashes (e.g., '.\%s.%s'). There are no explicit Linux or cross-platform file path examples, nor is there mention of Linux-specific considerations or alternatives. All code samples and instructions are platform-neutral Java, but the only file system example assumes Windows conventions.
Recommendations
- Provide file path examples for both Windows (e.g., '.\\%s.%s') and Linux/macOS (e.g., './%s.%s') when showing how to save downloaded files.
- Add a note clarifying that the Path API in Java is cross-platform, and users should use platform-appropriate path separators.
- Explicitly mention that the sample code works on Linux/macOS as well as Windows, and highlight any OS-specific considerations (such as file permissions or path formats).
- Include troubleshooting tips for common Linux issues (e.g., permissions, case sensitivity, environment variables) if relevant.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/get-started/get-started-javascript.md
...calling/includes/get-started/get-started-javascript.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a subtle Windows bias by recommending the Windows MSI installer for Node.js in the prerequisites, without mentioning Linux installation methods. No explicit Linux or cross-platform installation instructions are provided, and no Linux-specific considerations are discussed. All command-line instructions use generic 'console' or 'terminal' language, which is good, but the only installation method mentioned is Windows-centric.
Recommendations
- In the prerequisites, provide installation instructions or links for Node.js on Linux (e.g., using apt, yum, or nvm) alongside the Windows MSI installer.
- Explicitly state that the instructions are cross-platform and can be followed on Linux, macOS, or Windows.
- Where possible, use neutral language such as 'terminal' instead of 'command window', and clarify that all commands work in Bash, PowerShell, or CMD.
- Add a note or section for Linux users, mentioning any platform-specific considerations (e.g., installing build tools or dependencies for Node.js native modules).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-call-info.md
...e-video-calling/references/how-to-collect-call-info.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation instructs users to obtain the ACS resource ID via the Azure Portal, which is a web-based GUI commonly used on Windows. There are no examples or instructions for obtaining this information via cross-platform tools (e.g., Azure CLI or REST API), and no mention of Linux-friendly methods. All screenshots and instructions assume use of the portal, which may not be ideal for Linux or CLI-centric users.
Recommendations
- Add instructions for obtaining the ACS resource ID using the Azure CLI (az communication) with example commands.
- Include REST API methods for retrieving resource IDs for users who prefer scripting or automation.
- Clarify that the Azure Portal is web-based and can be used from any OS, but provide parity with CLI/API examples.
- Ensure screenshots and instructions do not assume a specific OS unless necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-javascript.md
...ices/samples/includes/call-automation-ai-javascript.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation shows evidence of Windows bias by referencing Windows-specific tabs in prerequisite links and by instructing users to open a PowerShell window to run the application, without mentioning Linux or cross-platform alternatives (e.g., Bash, Terminal). There are no explicit Linux examples or instructions, and the default assumption is a Windows environment.
Recommendations
- Provide parallel instructions for Linux/macOS users, such as opening a terminal instead of PowerShell.
- Avoid referencing Windows-specific tabs or provide links that default to a neutral or cross-platform view.
- Explicitly state that the commands (e.g., npm run dev, devtunnel) work on all platforms and show examples in both PowerShell and Bash if there are differences.
- Mention any platform-specific prerequisites or troubleshooting steps for Linux/macOS users.
- Use neutral language like 'terminal' or 'command prompt' instead of 'PowerShell window' unless a Windows-only step is required.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-csharp.md
...services/samples/includes/call-automation-ai-csharp.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation page demonstrates a bias towards Windows by referencing Windows-specific tabs in prerequisite links and not providing explicit Linux instructions or examples. The setup and run instructions assume familiarity with .NET and do not mention cross-platform compatibility or provide Linux/macOS-specific guidance. There are no Linux-specific examples or troubleshooting tips, and the linked resources often default to Windows tabs.
Recommendations
- Ensure that all prerequisite links and quickstart guides include Linux/macOS tabs and that these are referenced or highlighted equally with Windows.
- Explicitly state that the sample can be run on Linux and macOS, and provide any platform-specific instructions if needed (e.g., installing .NET SDK on Linux).
- Include Linux/macOS shell commands or notes where relevant, especially for environment setup and running the application.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences, .NET installation).
- Review linked documentation to ensure parity in instructions and examples for all supported platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-python.md
...services/samples/includes/call-automation-ai-python.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows mild Windows bias, primarily by linking to resource creation guides with a '?tabs=windows' parameter and not explicitly providing Linux-specific instructions or examples. While the main setup and run instructions use cross-platform commands (pip, python, bash), there is no mention of Linux or macOS alternatives in the prerequisites or setup steps. The phrase 'run it from PowerShell, a command prompt, or a Unix terminal' is inclusive, but the linked resources default to Windows instructions.
Recommendations
- Provide explicit Linux/macOS tabs or links in prerequisite resource creation steps, or ensure links default to a neutral or platform-agnostic view.
- Add a note or section confirming that all commands work on Linux/macOS, and mention any platform-specific considerations.
- Where possible, include Linux/macOS screenshots or terminal output to reinforce parity.
- Review all links for '?tabs=windows' and either remove the tab parameter or add equivalent Linux/macOS tabs.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/audio-quality-enhancements/includes/web.md
...s/tutorials/audio-quality-enhancements/includes/web.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its browser support statements and lack of Linux-specific guidance. All examples and instructions focus on Chrome and Edge desktop browsers, which are most commonly used on Windows. There is no mention of Linux compatibility, Linux browsers (such as Firefox), or platform-specific considerations for Linux users. No Linux command-line or environment examples are provided, and the documentation does not address whether the features work on Linux systems or how to troubleshoot on Linux.
Recommendations
- Explicitly state whether audio effects features are supported on Linux desktop environments and browsers (e.g., Chrome on Ubuntu, Fedora, etc.).
- Add Linux-specific examples or troubleshooting steps, such as verifying support on Linux Chrome/Edge or handling permissions and device selection on Linux.
- Mention any known limitations or differences when using the SDK on Linux versus Windows (e.g., browser APIs, hardware support).
- Include guidance for Linux users on installing dependencies, configuring audio devices, or resolving common issues.
- Consider referencing or testing with Linux browsers beyond Chrome and Edge, such as Firefox, and document compatibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/contact-center.md
...les/communication-services/tutorials/contact-center.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its use of Windows-specific tabs and pivots in quickstart links (e.g., '?tabs=windows'), and by referencing Windows-centric technologies (UWP) before or instead of Linux alternatives. There are no explicit Linux or cross-platform examples provided, and Linux tools, patterns, or instructions are absent throughout the page.
Recommendations
- Add Linux-specific tabs and pivots to quickstart links, ensuring parity with Windows examples.
- Include examples and instructions for running Azure Communication Services components on Linux environments.
- Reference cross-platform technologies (such as Electron, .NET MAUI, or web-based solutions) alongside or before Windows-specific ones.
- Explicitly mention Linux compatibility and provide troubleshooting steps for Linux users.
- Ensure that architectural diagrams and feature tables clarify platform support, including Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/call-duration.md
...cles/communication-services/tutorials/call-duration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides platform-specific guidance for Android, iOS, and Windows, but does not mention or provide examples for Linux. This omission suggests a bias towards Windows and mobile platforms, with Linux desktop support not addressed. Additionally, the Windows section is present without any mention of Linux, which may lead Linux developers to feel unsupported.
Recommendations
- Add a Linux-specific section or clarify Linux support status for the Calling SDKs.
- If the SDK supports Linux (e.g., via Electron, .NET Core, or other cross-platform frameworks), provide explicit Linux examples or instructions.
- If Linux is not supported, clearly state this in the documentation to set developer expectations.
- Ensure future documentation includes parity for all major desktop platforms, not just Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/hmac-header-csharp.md
...tion-services/tutorials/includes/hmac-header-csharp.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation demonstrates a mild Windows bias by listing Windows tools (cmd, PowerShell) before Bash when suggesting console environments, and by requiring Visual Studio for development without mentioning cross-platform alternatives. All examples use .NET CLI, which is cross-platform, but the setup instructions and tool recommendations prioritize Windows environments.
Recommendations
- List Bash or terminal first, or mention all environments equally when suggesting where to run commands.
- Explicitly state that Visual Studio Code or JetBrains Rider can be used as cross-platform alternatives to Visual Studio.
- Clarify that the .NET CLI and all code examples work on Windows, Linux, and macOS.
- Add a note that .NET SDK installation instructions are available for all platforms, with a link to official documentation.
- Avoid implying that only Windows tools are supported or required for the tutorial.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-ios-tutorial.md
.../tutorials/includes/twilio-to-acs-chat-ios-tutorial.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a Windows-first bias in the prerequisites by linking only to Windows-specific Azure CLI installation instructions and using a resource creation link with a Windows tab. There are no Linux or macOS equivalents or mentions for these steps, despite the iOS development context. All other code examples are platform-agnostic (Swift/iOS), but the setup steps assume Windows.
Recommendations
- Provide installation instructions for Azure CLI on Linux and macOS, or link to the cross-platform installation guide.
- Use a neutral or platform-appropriate tab (e.g., macOS, Linux) for resource creation links, or mention all supported platforms.
- Explicitly state that the Azure CLI and other tools are available on multiple platforms, and provide guidance for non-Windows users.
- Review all prerequisite steps to ensure parity for Linux and macOS developers, especially given the iOS development focus.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/url-shortener-csharp.md
...on-services/tutorials/includes/url-shortener-csharp.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides only C#/.NET and Azure Function examples, with all instructions and code samples tailored to the .NET ecosystem. There are no Linux-specific instructions, shell commands, or examples for other platforms or languages. The workflow assumes Visual Studio Code and .NET, which are cross-platform, but there is no explicit mention or demonstration of Linux-specific workflows, nor are there bash or Linux shell equivalents for setup or deployment. The only command-line example is 'dotnet add package', which is cross-platform, but the overall focus is on the Windows/.NET stack. The documentation does not mention or show Linux-specific tools, nor does it provide parity for Linux users in setup or troubleshooting.
Recommendations
- Add explicit instructions for Linux users, such as using bash/zsh for running the Azure Function locally and installing dependencies.
- Include examples for deploying and running the Azure Function using Linux-native tools and workflows (e.g., using Azure CLI in bash, or running with 'func host start' in a Linux terminal).
- Mention and show how to install the .NET SDK and Azure Functions Core Tools on Linux.
- Clarify that Visual Studio Code and .NET are cross-platform, and provide any Linux-specific caveats or troubleshooting tips.
- If possible, provide equivalent examples in other languages or frameworks popular on Linux (e.g., Node.js/Express, Python/Flask) or link to such resources.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/virtual-visits/extend-teams/before-and-after-appointment.md
...al-visits/extend-teams/before-and-after-appointment.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively references Microsoft-centric tools and platforms such as Power Automate, Logic Apps, Microsoft Graph API, and Azure Communication Services. There are no examples or mentions of Linux-native tools, open-source alternatives, or command-line automation (e.g., bash scripting, curl, or Linux scheduling tools). All automation and extensibility examples are built around the Microsoft ecosystem, which is most familiar to Windows users. No Linux-specific guidance or parity is provided.
Recommendations
- Include examples using cross-platform or Linux-native tools, such as demonstrating how to trigger flows or send messages using bash scripts, curl, or Python scripts with Microsoft Graph API.
- Mention and provide guidance for using REST APIs directly from Linux environments, including authentication and example commands.
- Highlight any CLI tools (such as Azure CLI) that are available on Linux and show how they can be used to perform similar tasks.
- Clarify that Power Automate and Logic Apps are web-based and accessible from any OS, and provide explicit instructions for Linux users where relevant.
- Consider referencing open-source workflow automation tools (e.g., n8n, Node-RED) that can integrate with Microsoft services for Linux users.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/create-confidential-vm-from-compute-gallery.md
...mputing/create-confidential-vm-from-compute-gallery.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows-specific scenarios (such as creating images from Windows confidential VMs with disk encryption) are mentioned explicitly, while Linux equivalents are not described in similar detail. In the steps for generalizing a VHD, the link to Linux instructions is provided after the Windows link, and no Linux-specific examples or considerations are given elsewhere. There are no command-line examples (e.g., PowerShell or Bash), but the narrative and links tend to prioritize or exclusively mention Windows workflows.
Recommendations
- Add explicit Linux scenarios and examples, such as creating images from Linux confidential VMs with disk encryption.
- Ensure Linux links and instructions are presented alongside or before Windows equivalents where applicable.
- Include Linux-specific considerations, such as differences in generalization, encryption, and supported OS features.
- If command-line examples are added, provide both Bash/Azure CLI and PowerShell examples for parity.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/key-rotation-offline.md
...rticles/confidential-computing/key-rotation-offline.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes key rotation using the Azure Portal GUI, which is a cross-platform web interface, but does not provide any command-line examples. There are no references to PowerShell, Windows tools, or CLI commands, but the lack of Azure CLI or Bash examples means Linux users do not have parity with Windows users who may be more accustomed to GUI or PowerShell workflows.
Recommendations
- Add Azure CLI examples for key rotation, including commands to stop VMs, update Disk Encryption Sets, and select keys.
- Provide Bash script snippets for automating key rotation tasks.
- Explicitly mention that the Azure Portal is cross-platform, but supplement with CLI instructions for users who prefer or require command-line workflows.
- Ensure that any future examples include both Azure CLI (Linux/macOS) and PowerShell (Windows) where relevant.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/migrate-nested-confidential-vms.md
...fidential-computing/migrate-nested-confidential-vms.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively describes migration steps using the Azure Portal GUI, which is most commonly used on Windows systems. There are no CLI, Powershell, or Bash examples, nor are Linux-specific tools or workflows mentioned. The screenshots and instructions assume a graphical interface, which is less common for Linux users who often prefer command-line automation.
Recommendations
- Add equivalent migration instructions using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
- Include examples for Powershell and Bash scripts to automate the migration process.
- Explicitly mention that the Azure Portal is accessible from any OS, but provide parity for users who prefer command-line or automated workflows.
- Reference Linux-friendly tools and patterns, such as using SSH, Bash scripting, or cloud-init for post-migration configuration.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-integrate-security-operations-create-api-microsoft-graph-security.md
...ecurity-operations-create-api-microsoft-graph-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal and Microsoft-centric tools (Logic Apps, Microsoft Entra, Outlook, Power Automate, Power Apps) without mentioning or providing examples for Linux-based workflows, CLI usage, or cross-platform alternatives. All step-by-step instructions and examples assume use of the Azure portal, which is most commonly accessed via Windows environments, and there are no references to Linux tools, shell scripts, or platform-neutral automation methods.
Recommendations
- Include examples for using Azure Logic Apps and Microsoft Graph Security connector via Azure CLI, PowerShell, and Bash to demonstrate cross-platform compatibility.
- Explicitly mention that the Azure portal and Logic Apps Designer can be accessed from Linux and macOS browsers, and provide any platform-specific caveats.
- Add references or links to documentation for automating these workflows from Linux environments, such as using REST APIs with curl or scripting with Python.
- Provide sample workflows or automation scripts that can be run from Linux terminals, not just through the Azure portal UI.
- Ensure parity in documentation by listing Linux-compatible tools and approaches alongside Microsoft/Windows-specific ones.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-native-recurrence.md
...in/articles/connectors/connectors-native-recurrence.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation primarily references Windows-centric resources and patterns, such as linking to Microsoft's Windows time zone documentation and using 'Pacific Standard Time' as a time zone example. The only external time zone reference is to a Windows documentation page. There are no explicit Linux or cross-platform examples, and no mention of Linux time zone formats (e.g., IANA/Olson database names like 'America/Los_Angeles'). However, there are no PowerShell-specific examples, nor are there CLI commands or scripts that are Windows-only. The bias is subtle but present in the prioritization of Windows documentation and terminology.
Recommendations
- Include references to cross-platform or Linux time zone resources, such as the IANA time zone database (e.g., https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
- When providing time zone examples, include both Windows (e.g., 'Pacific Standard Time') and IANA/Olson (e.g., 'America/Los_Angeles') names, and clarify which are supported by Logic Apps.
- If possible, clarify whether Logic Apps supports only Windows time zone IDs or also IANA/Olson IDs, and provide guidance for Linux users.
- Avoid linking exclusively to Windows documentation for concepts that are cross-platform (e.g., time zones).
- Add a note or section addressing cross-platform considerations, especially for users deploying or managing Logic Apps from Linux environments.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/authentication-entra.md
...b/main/articles/container-apps/authentication-entra.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively uses the Azure Portal (a web UI) for all configuration steps and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell or CMD, but there is also a lack of parity for Linux users, as no CLI (e.g., Azure CLI, Bash) instructions are provided. This can disadvantage users who prefer or require command-line automation, which is common in Linux environments.
Recommendations
- Add Azure CLI examples for all major configuration steps, such as app registration, setting authentication providers, and managing secrets.
- Explicitly mention that all steps can be performed via the Azure CLI or ARM templates, and link to relevant documentation.
- Where possible, provide Bash shell command examples alongside portal instructions to support Linux users and automation scenarios.
- Include a section summarizing cross-platform options for performing the tasks described, highlighting both portal and CLI approaches.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/communicate-between-microservices.md
...es/container-apps/communicate-between-microservices.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every command, ensuring cross-platform coverage. However, PowerShell (and thus Windows) examples are consistently present and, in some sections (notably the 'Deploy front end application'), the PowerShell instructions are more verbose and detailed than the Bash equivalents. The PowerShell workflow uses more Azure PowerShell-specific cmdlets and objects, which are primarily relevant to Windows users. Bash examples are generally simpler and use Azure CLI directly, but the PowerShell sections may give the impression of Windows primacy due to their length and detail.
Recommendations
- Ensure Bash and PowerShell instructions are equally detailed, especially in complex deployment steps.
- Add explicit notes clarifying that Bash instructions are suitable for Linux and macOS users, and PowerShell for Windows users.
- Where possible, provide parity in workflow complexity between Bash and PowerShell, so Linux users do not feel their instructions are less complete.
- Consider including a table or section summarizing cross-platform command equivalence for quick reference.
- Avoid using advanced PowerShell-specific patterns (like custom object creation) unless a Bash/Linux equivalent is also provided or explained.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/dapr-functions-extension.md
...in/articles/container-apps/dapr-functions-extension.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both PowerShell and curl examples for key API interactions and log queries, but consistently lists PowerShell examples before curl. This ordering implicitly prioritizes Windows tooling and patterns, even though the Azure CLI and curl are cross-platform. No Linux-specific tools or shell examples (e.g., bash scripts) are provided, and PowerShell is given equal or greater prominence than curl, which may be less familiar to Linux users.
Recommendations
- Present curl (Linux/macOS) examples before PowerShell examples, or side-by-side, to avoid implicit prioritization.
- Explicitly note that all CLI and curl commands work on Linux, macOS, and Windows, and clarify any platform-specific differences.
- Add bash script examples or references for common tasks, especially for log queries and API calls.
- Avoid using PowerShell-specific syntax (e.g., @{} for headers) without explanation or Linux equivalents.
- Include a note in the prerequisites or introduction about cross-platform compatibility and tool availability.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/deploy-visual-studio-code.md
...n/articles/container-apps/deploy-visual-studio-code.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation demonstrates a bias towards Windows by only providing instructions and examples using Visual Studio Code's GUI and command palette, which are presented in a way that closely aligns with Windows workflows. There are no examples or instructions for deploying via Linux-native tools, CLI, or terminal commands, nor is there mention of Linux-specific considerations or parity. The documentation implicitly assumes a Windows or at least a GUI-centric environment.
Recommendations
- Include equivalent instructions for deploying to Azure Container Apps using the Azure CLI or Bash terminal, which are common on Linux.
- Explicitly mention that Visual Studio Code and its extensions are available on Linux and macOS, and note any platform-specific differences if they exist.
- Provide examples or links for performing the same deployment steps using Linux-native tools (e.g., Azure CLI, Docker CLI) outside of Visual Studio Code.
- Add a section or callout for Linux users, highlighting any differences or additional steps required.
- Ensure that screenshots and keyboard shortcuts are not Windows-specific (e.g., avoid only referencing <kbd>F1</kbd> if it behaves differently on Linux/macOS).
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/deploy-artifact.md
...s/blob/main/articles/container-apps/deploy-artifact.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, ensuring cross-platform coverage. However, PowerShell (Windows) examples are always presented immediately after Bash, and the use of PowerShell tabs throughout may subtly reinforce Windows as a primary platform. There are no Linux-specific tools or troubleshooting steps, and no mention of Linux distributions or shell alternatives beyond Bash. The file path in the 'Run the project locally' section uses backslashes (Windows style), which may confuse Linux users.
Recommendations
- Explicitly mention Linux and macOS compatibility in the prerequisites and throughout the guide.
- Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, package installation).
- Use forward slashes in file paths for Bash examples to match Linux/macOS conventions.
- Consider presenting Bash (Linux/macOS) examples before PowerShell (Windows), or clarify that Bash is suitable for both Linux and macOS.
- Add notes about differences in environment variable syntax between shells/platforms.
- If possible, include a section or tab for macOS-specific instructions, especially for Java and Maven installation.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/dotnet-overview.md
...s/blob/main/articles/container-apps/dotnet-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Visual Studio as the first deployment tutorial and omitting explicit Linux-oriented tooling or examples. There are no PowerShell commands or Windows-specific tools mentioned directly, but the lack of Linux CLI examples and the prioritization of Visual Studio (a primarily Windows IDE) in deployment guidance suggest a Windows-first perspective. There is no mention of Linux-native workflows, such as using VS Code, Bash, or Docker CLI commands on Linux, nor are there examples tailored to Linux environments.
Recommendations
- Add explicit Linux deployment examples, such as using Azure CLI or Docker CLI from a Bash shell.
- Include guidance for deploying from VS Code or other cross-platform editors, not just Visual Studio.
- Provide sample commands and configuration steps for both Windows and Linux environments.
- Clarify that all steps can be performed on Linux, and highlight any platform-specific considerations.
- Balance tutorial links so that Linux-first or cross-platform options appear alongside or before Windows-centric ones.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/java-component-logs.md
...ob/main/articles/container-apps/java-component-logs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for querying logs via Azure CLI, but PowerShell is consistently listed second and uses Windows-centric variable assignment syntax. The use of 'SET' for Bash variable assignment is incorrect and more typical of Windows CMD, suggesting a Windows-first approach. There is no mention of Linux-specific tools or troubleshooting, and the CLI examples do not use native Linux conventions (e.g., 'export' for environment variables).
Recommendations
- Use correct Bash syntax for variable assignment (e.g., 'export WORKSPACE_ID=<WORKSPACE_ID>') instead of 'SET', which is a Windows CMD command.
- Provide Linux-specific troubleshooting steps or notes where relevant.
- Ensure Bash examples use idiomatic Linux shell commands and are listed first if targeting cross-platform users.
- Consider including examples using other popular Linux shells (e.g., zsh) if relevant.
- Explicitly state cross-platform compatibility and highlight any OS-specific differences in CLI usage.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/key-vault-certificates-manage.md
...ticles/container-apps/key-vault-certificates-manage.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses the Azure portal UI for all steps, which is primarily accessed via web browsers on Windows, and does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell). There are no Linux-specific instructions, nor are cross-platform CLI patterns shown. The only mention of command-line tooling is a brief reference to Azure CLI for App Service certificates, but no example is given. This results in a Windows-first and GUI-centric bias, with missing parity for Linux or CLI users.
Recommendations
- Add Azure CLI and/or PowerShell command examples for all major steps, including enabling managed identity, assigning roles, and importing certificates.
- Explicitly mention that all steps can be performed on Linux, macOS, and Windows using CLI tools.
- Provide Bash shell examples for Linux users.
- Include links to cross-platform CLI documentation where relevant.
- Clarify any platform-specific limitations, if present, for portal or CLI usage.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/migrate-functions.md
...blob/main/articles/container-apps/migrate-functions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exhibits Windows bias primarily in the prerequisites section, where the Azure CLI installation link points to the Windows-specific instructions and no Linux or cross-platform alternatives are mentioned. No explicit Linux or macOS examples or instructions are provided, and no platform-specific differences are discussed. All command-line examples use Azure CLI, which is cross-platform, but the lack of Linux parity in installation guidance may hinder non-Windows users.
Recommendations
- Update the Azure CLI installation link to point to the cross-platform installation page or provide links for Windows, Linux, and macOS.
- Explicitly state that all Azure CLI commands work on Windows, Linux, and macOS.
- If there are any platform-specific considerations (e.g., environment variable syntax, file paths), mention them or provide examples.
- Consider adding a note or section for Linux/macOS users to ensure parity and inclusivity.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/quota-requests.md
...cs/blob/main/articles/container-apps/quota-requests.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively describes quota requests using the Azure Portal (a web-based GUI) and does not mention or provide examples for command-line tools such as Azure CLI or Azure PowerShell. This approach implicitly favors users accustomed to GUI workflows, which are more common in Windows environments, and omits parity for Linux users who may prefer or require CLI-based instructions.
Recommendations
- Add equivalent instructions for requesting quota changes using the Azure CLI, which is cross-platform and widely used on Linux.
- If PowerShell examples are relevant, ensure Azure CLI examples are provided first or alongside them.
- Explicitly state that the Azure Portal is web-based and accessible from any OS, but also provide links or steps for CLI-based workflows.
- Include screenshots or code snippets demonstrating quota requests via CLI commands to support Linux and automation-focused users.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/revisions-manage.md
.../blob/main/articles/container-apps/revisions-manage.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for each command, with Bash examples first. However, the PowerShell examples use Azure PowerShell cmdlets (e.g., Get-AzContainerAppRevision, Update-AzContainerApp), which are Windows-centric and less commonly used on Linux. In some cases, PowerShell examples simply call the Azure CLI, but the documentation still presents PowerShell as a primary workflow. There are no Linux-specific shell examples (e.g., zsh, fish), and no mention of native Linux tools or scripting patterns. The documentation assumes parity between Bash and PowerShell, but the heavy use of PowerShell cmdlets and the presence of PowerShell tabs throughout indicates a Windows bias.
Recommendations
- Clarify that Azure PowerShell cmdlets are primarily supported on Windows, and that Bash/CLI examples are cross-platform.
- Consider providing additional Linux-native shell examples (e.g., zsh, fish) or scripting patterns where relevant.
- Where PowerShell examples simply invoke the Azure CLI, note that these commands are identical to Bash and can be run in any shell.
- Add a short section explaining the cross-platform availability of Azure CLI and PowerShell, and recommend Azure CLI for Linux/macOS users.
- If possible, provide examples using only the Azure CLI for maximum cross-platform compatibility, and move PowerShell examples to a secondary position or appendix.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/staging-resources.md
...articles/cyclecloud/common-issues/staging-resources.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses on Azure CycleCloud resource staging issues but does not provide any platform-specific examples or troubleshooting steps. However, it references the Azure portal UI (which is most commonly accessed from Windows environments) and omits any command-line examples (such as Azure CLI or PowerShell), nor does it mention Linux tools or workflows. The lack of Linux-specific guidance or parity in examples constitutes a subtle Windows bias.
Recommendations
- Add Azure CLI examples for checking and configuring Storage Account hierarchical namespace and permissions, which are platform-agnostic and widely used on Linux.
- Include PowerShell examples if relevant, but ensure they are presented alongside equivalent Azure CLI commands.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to cross-platform tools.
- Describe how to access and modify Storage Account settings using command-line tools, not just the Azure portal UI.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/samples.md
...zure-docs/blob/main/articles/container-apps/samples.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page lists Azure Container Apps samples, with a strong emphasis on .NET/ASP.NET Core, Orleans, and Blazor Server applications, which are traditionally associated with Windows development. These samples are presented first and in greater number compared to Linux-native or open-source technology samples (e.g., Drupal, Java, Node.js). There is no explicit mention of Linux-specific tools, deployment patterns, or examples, nor are there references to Linux shell commands or containerization workflows common in Linux environments. The ordering and selection of samples suggest a Windows/.NET-first bias, and the lack of Linux-specific guidance or parity in examples further reinforces this.
Recommendations
- Add more samples featuring Linux-native technologies (e.g., Python, Go, Ruby, PHP beyond Drupal) and deployment scenarios.
- Include explicit Linux shell (bash) deployment instructions or scripts alongside any PowerShell or Windows-centric guidance.
- Balance the ordering of samples so that Linux/open-source technologies are presented alongside .NET/Windows samples, not after them.
- Highlight containerization workflows common in Linux environments, such as Docker Compose, Kubernetes YAML, or CLI commands.
- Provide guidance on using Azure CLI from Linux terminals, and reference Linux-based development environments in sample documentation.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/tutorial-scaling.md
.../blob/main/articles/container-apps/tutorial-scaling.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring cross-platform parity for core tasks. However, in the 'Send requests' section, the Bash example uses standard Linux utilities (seq, xargs, curl), while the PowerShell example uses advanced PowerShell constructs (runspaces, Invoke-WebRequest), which are more complex and less familiar to Linux users. Additionally, the PowerShell examples are always presented after Bash, but the explanations and links for Bash commands are more detailed, with Linux man page links, while the PowerShell section only links to a Microsoft blog. There is a slight bias towards Windows/PowerShell in the complexity and depth of the PowerShell examples, but overall, Linux is well represented.
Recommendations
- Ensure that the explanations and documentation links for PowerShell commands are as detailed as those for Bash (e.g., link to official PowerShell documentation for each cmdlet used).
- Consider providing simpler PowerShell alternatives for sending concurrent requests, or note that the Bash example can be run in WSL on Windows for parity.
- Explicitly mention that all Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash examples can be run in WSL or Git Bash on Windows.
- Add a short section at the start clarifying that both Bash and PowerShell are supported, and users can choose their preferred shell.
- Where possible, provide a cross-platform (Python or Node.js) script for sending concurrent requests, to avoid shell-specific complexity.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/service-connector.md
...blob/main/articles/container-apps/service-connector.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides instructions using the Azure Portal and Azure CLI, which are both cross-platform tools. However, there is a subtle Windows bias: the CLI examples do not mention Linux or macOS shells, nor do they provide any Bash-specific guidance or troubleshooting. There are no references to Linux-specific tools, nor are there any screenshots or examples that show Linux environments. The documentation does not mention or address potential differences in CLI usage or authentication flows on Linux/macOS versus Windows. Additionally, the CLI instructions assume the user is familiar with the Azure CLI, which is available on all platforms, but there is no explicit mention of Linux or macOS, and the browser-based authentication flow is described in a way that may be more familiar to Windows users.
Recommendations
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, and provide any platform-specific notes if relevant.
- Include Bash shell examples or troubleshooting tips for Linux/macOS users (e.g., handling environment variables, file paths, or authentication issues).
- Add screenshots or terminal examples from a Linux shell to visually reinforce cross-platform support.
- Mention installation instructions or prerequisites for the Azure CLI on Linux/macOS, or link to relevant documentation.
- If there are any differences in authentication flows or required dependencies on Linux/macOS, call them out in the documentation.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/sessions.md
...ure-docs/blob/main/articles/container-apps/sessions.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Hyper-V, a Windows-based virtualization technology, as the foundation for session isolation. There is no mention of Linux-based isolation technologies (such as KVM, gVisor, or Kata Containers) or how sessions are isolated when running on Linux hosts. The documentation links to Windows Server Hyper-V documentation and does not provide Linux equivalents or alternatives, implicitly prioritizing Windows technologies.
Recommendations
- Clarify whether Hyper-V is used for session isolation regardless of the underlying host OS, or if alternative Linux-based isolation technologies are used in Linux environments.
- If Linux-based isolation is supported, mention and briefly describe the relevant technology (e.g., KVM, gVisor, Kata Containers) and provide links to their documentation.
- Avoid linking exclusively to Windows/Hyper-V documentation; provide balanced references to both Windows and Linux isolation technologies where applicable.
- Include a section or note explaining how session isolation works on Linux-based Azure infrastructure, if supported.
- Ensure that examples, descriptions, and technical explanations are platform-agnostic or provide parity between Windows and Linux where possible.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/token-store.md
...-docs/blob/main/articles/container-apps/token-store.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure Portal GUI for tasks such as generating a SAS URL and managing secrets, which is typically associated with a Windows-centric workflow. There are no CLI or cross-platform examples for generating the SAS URL or managing secrets, and no mention of Linux tools or command-line alternatives. The only CLI example provided is for the Azure CLI, which is cross-platform, but it appears after several portal-based steps.
Recommendations
- Add Azure CLI and/or Azure PowerShell examples for generating a SAS URL and managing secrets, making it clear these commands work on all platforms.
- Include Linux/macOS-specific instructions or screenshots where appropriate, or clarify that the Azure Portal is accessible from any OS.
- Mention and link to documentation for performing these tasks using the Azure CLI or PowerShell, and consider presenting CLI examples before or alongside portal instructions.
- Explicitly state that all steps can be performed on Linux, macOS, and Windows, and avoid implying a Windows-only workflow.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/troubleshoot-storage-mount-failures.md
.../container-apps/troubleshoot-storage-mount-failures.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page exclusively references the Azure Portal's graphical interface for troubleshooting, which is more commonly associated with Windows workflows. There are no examples or instructions for troubleshooting storage mount failures using Linux-native tools, CLI commands (such as Azure CLI), or shell scripting, which are common in Linux environments. No Linux-specific troubleshooting steps or examples are provided.
Recommendations
- Add troubleshooting steps using the Azure CLI (az) for users who prefer command-line interfaces, common in Linux environments.
- Include examples of checking mount points and storage connectivity from within a Linux-based container using shell commands (e.g., ls, mount, df, etc.).
- Provide parity in instructions for both portal (GUI) and CLI-based workflows, ensuring Linux users are equally supported.
- Mention and link to Linux troubleshooting tools and patterns (e.g., viewing logs with tail/cat, checking /etc/fstab, etc.) where relevant.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/troubleshoot-target-port-settings.md
...es/container-apps/troubleshoot-target-port-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on troubleshooting target port settings using the Azure Portal UI, without providing any command-line examples. There is no mention of Linux tools, CLI commands, or cross-platform approaches (such as Azure CLI or Bash). The absence of Linux-specific or cross-platform instructions, and the reliance on a graphical interface (which is more common in Windows-centric workflows), indicates a bias toward Windows users and leaves Linux users without parity.
Recommendations
- Add Azure CLI examples for diagnosing and troubleshooting port settings, including commands that can be run in Bash or any terminal.
- Include Linux-native troubleshooting steps, such as using curl, netstat, or docker commands to verify port exposure and application listening ports.
- Provide PowerShell and Bash script snippets side-by-side where relevant.
- Explicitly mention that the Azure Portal is cross-platform accessible, but supplement with CLI-based instructions for users who prefer or require command-line tools.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/automate/automation-ingest-usage-details-overview.md
...g/automate/automation-ingest-usage-details-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Microsoft Excel as the primary tool for opening CSV cost details files, without mentioning Linux-native alternatives. There are no command-line or scripting examples for data ingestion, and no mention of Linux tools (e.g., awk, grep, csvkit) or cross-platform approaches. The absence of PowerShell-specific instructions means the bias is not overt, but the default assumption of Excel and lack of Linux parity is notable.
Recommendations
- Explicitly mention Linux-compatible tools for opening and processing CSV files, such as LibreOffice Calc, csvkit, or spreadsheet applications available on Linux.
- Provide cross-platform command-line examples for ingesting and analyzing cost details data, using tools like Python, Bash, or csvkit.
- Clarify that the instructions are applicable regardless of operating system, and avoid defaulting to Windows-centric applications.
- If automation is discussed, include sample scripts for both PowerShell (Windows) and Bash (Linux).
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/automate/automation-overview.md
...ost-management-billing/automate/automation-overview.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation does not provide any platform-specific automation examples or scripts, but it does mention Power BI and SQL/Azure Synapse as recommended tools for data analysis and reporting, which are traditionally more Windows-centric. There are no examples or recommendations for Linux-native tools (e.g., bash scripting, Python, or open-source alternatives), nor are there any Linux-specific usage patterns or automation guidance. The lack of Linux examples and alternative tooling suggests a bias toward Windows environments.
Recommendations
- Add example workflows using Linux-native tools (e.g., bash, Python, jq) for API calls and data processing.
- Include guidance for ingesting and analyzing cost data using open-source databases (e.g., PostgreSQL) and visualization tools (e.g., Grafana).
- Provide sample scripts for both Windows (PowerShell) and Linux (bash, curl, Python) to demonstrate parity.
- Mention cross-platform data pipeline options (e.g., Apache Airflow, dbt) alongside Azure Data Factory.
- Clarify that the APIs can be used from any OS and provide links to SDKs or CLI tools that work on Linux.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/automate/get-small-usage-datasets-on-demand.md
...billing/automate/get-small-usage-datasets-on-demand.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by recommending the use of Excel for data analysis after download, without mentioning Linux-friendly alternatives. There are no platform-specific code examples (e.g., PowerShell, Bash), but the only tool referenced for post-processing is Excel, which is primarily a Windows application. No Linux tools or workflows (such as pandas, LibreOffice Calc, csvkit, or command-line utilities) are suggested, and no Linux-specific examples are provided.
Recommendations
- Add examples of analyzing downloaded CSV data using Linux-compatible tools such as pandas (Python), LibreOffice Calc, csvkit, or command-line utilities like awk and grep.
- Explicitly mention cross-platform alternatives to Excel for data analysis.
- Include sample workflows or scripts for Linux environments (e.g., Bash, Python) to demonstrate how to process and analyze the downloaded cost data.
- Ensure that any referenced tooling or post-processing steps are platform-neutral or provide parity between Windows and Linux.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/automate/tutorial-seed-historical-cost-dataset-exports-api.md
...e/tutorial-seed-historical-cost-dataset-exports-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation lists PowerShellâs Invoke-RestMethod as a popular way to query the API before mentioning curl, which is the most common tool on Linux/macOS. PowerShell is a Windows-centric tool, and its placement before curl may suggest a Windows-first bias. No Linux-specific shell examples (e.g., bash, curl command-line usage) are provided, and no mention of Linux terminal usage is made. The only command-line example given is generic HTTP, not tailored to either platform, but the tool recommendations favor Windows.
Recommendations
- List curl before PowerShell in the 'popular ways to query the API' section to reflect Linux parity.
- Provide explicit curl command-line examples for Linux/macOS users.
- Include bash script examples for automating API calls.
- Mention Linux terminal usage alongside Windows/PowerShell.
- Consider adding notes or links for Linux users on authentication and scripting best practices.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/billing-tags.md
...articles/cost-management-billing/costs/billing-tags.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides instructions exclusively for the Azure portal, which is platform-agnostic, but does not mention or provide examples for command-line or automation approaches (such as Azure CLI, PowerShell, or REST API). However, there is an implicit Windows bias in that the only navigation instructions are for the web portal, and there is no mention of Linux-friendly tools or automation methods. Additionally, the documentation does not clarify whether the steps differ on non-Windows platforms or in cross-platform shells.
Recommendations
- Add examples for applying billing tags using Azure CLI, which is cross-platform and widely used on Linux.
- If PowerShell examples are provided, ensure Azure CLI equivalents are also included and shown first or side-by-side.
- Mention that the Azure portal is accessible from any OS, but also provide automation options for users who prefer command-line tools.
- Clarify if there are any platform-specific considerations or limitations.
- Include REST API examples for advanced automation scenarios.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/cost-mgt-alerts-monitor-usage-spending.md
...illing/costs/cost-mgt-alerts-monitor-usage-spending.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the Azure portal and REST API for management, without mentioning or providing examples for Linux command-line tools (such as Azure CLI or Bash scripting). There are no Linux-specific instructions, and no cross-platform command-line examples are given. The documentation implicitly assumes use of GUI tools or Windows-centric workflows.
Recommendations
- Add Azure CLI examples for creating and managing cost alerts and budgets, as the CLI is cross-platform and widely used on Linux.
- Include Bash or shell scripting examples for automating cost alert monitoring, in addition to REST API references.
- Explicitly state that all features are accessible from Linux, macOS, and Windows, and provide parity in instructions for non-Windows users.
- Where screenshots or navigation steps are given for the Azure portal, consider also providing equivalent command-line instructions.
- Mention and link to documentation for cross-platform tools (e.g., Azure CLI, PowerShell Core) where relevant.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/quick-acm-cost-analysis.md
...st-management-billing/costs/quick-acm-cost-analysis.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias by exclusively referencing Power BI as the tool for advanced reporting and data analysis, without mentioning or providing parity for Linux-compatible alternatives. There are no command-line examples (e.g., PowerShell or Bash), but the only advanced reporting workflow described relies on a Microsoft-centric, Windows-first tool. No Linux-specific tools or cross-platform open-source alternatives are mentioned, and there are no instructions for users on Linux systems.
Recommendations
- Mention and provide examples for cross-platform or Linux-friendly tools for advanced reporting (e.g., using Python with pandas, Jupyter Notebooks, or open-source BI tools like Apache Superset or Metabase).
- Clarify whether Power BI can be used on Linux (e.g., via Power BI web or through supported APIs), and provide guidance for Linux users.
- Include examples of exporting cost data and analyzing it with command-line tools or scripts (e.g., using curl/wget to fetch API data, then process with jq, awk, or Python).
- Explicitly state that the workflows described are platform-agnostic if that is the case, or provide platform-specific guidance where necessary.
- Add a section or note addressing Linux/macOS users, outlining their options for cost analysis and reporting.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/add-change-subscription-administrator.md
...illing/manage/add-change-subscription-administrator.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively references the Azure portal for administrative actions and does not provide any command-line examples, such as Azure CLI or PowerShell. While this avoids explicit Windows tool bias, the lack of Linux-specific or cross-platform command-line instructions (e.g., Azure CLI) means users on Linux or macOS are not given parity in guidance. The portal-centric approach implicitly favors Windows users, as the Azure portal experience is most commonly associated with Windows environments.
Recommendations
- Add examples using Azure CLI for assigning roles and managing subscriptions, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include PowerShell examples if relevant, but always provide Azure CLI equivalents and present them together or with CLI first to avoid Windows-first bias.
- Explicitly mention that all steps can be performed from any OS using the Azure portal, but highlight command-line alternatives for automation and scripting.
- Provide links to documentation on installing and using Azure CLI on Linux and macOS.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/cloud-subscription.md
...s/cost-management-billing/manage/cloud-subscription.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively references Microsoft-centric tools and portals (e.g., Azure portal) for managing cloud subscriptions, with no mention of Linux command-line tools, cross-platform CLI usage, or non-Windows management patterns. All examples and instructions assume use of the Azure portal, which is most commonly accessed via Windows environments, and there is no parity for Linux or cross-platform users.
Recommendations
- Include Azure CLI examples for managing cloud subscriptions, highlighting usage on Linux and macOS.
- Reference cross-platform management tools (e.g., Azure CLI, REST API) alongside or before portal-based instructions.
- Add explicit notes or sections for Linux users, such as how to view and manage subscriptions from a Linux shell.
- Ensure that any screenshots or step-by-step instructions are supplemented with equivalent command-line instructions.
- Mention that the Azure portal is accessible from any OS, but provide alternatives for users who prefer or require CLI or automation.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/create-enterprise-subscription.md
...ement-billing/manage/create-enterprise-subscription.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes and illustrates the process of creating an Enterprise Agreement subscription using the Azure portal, with all screenshots and instructions based on the web UI. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there references to Linux or cross-platform tooling. The only programmatic mention is a link to another page, without clarifying if cross-platform tools are supported. The overall flow assumes a GUI-first, Windows-centric user experience, which may disadvantage Linux or automation-focused users.
Recommendations
- Add Azure CLI examples for creating an Enterprise Agreement subscription, as the CLI is cross-platform and widely used on Linux.
- If PowerShell examples are provided, ensure Azure CLI or Bash equivalents are also included and presented with equal prominence.
- Clarify in the 'Create programmatically' section which tools (Azure CLI, REST API, PowerShell) are supported and provide direct, cross-platform examples.
- Mention that all portal steps are accessible from any OS with a supported browser, but highlight automation options for Linux users.
- Include a table or section comparing portal, CLI, and API methods for subscription creation, with links or inline examples for each.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/create-free-services.md
...cost-management-billing/manage/create-free-services.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation repeatedly uses Windows virtual machines as the only example when describing free services, without mentioning Linux VM options. There are no examples or references to creating Linux-based resources, which may give the impression that only Windows VMs are available or recommended for free tier usage.
Recommendations
- Include examples of both Windows and Linux virtual machines when describing free services (e.g., mention that B1S Linux VMs are also available for free).
- Explicitly state that users can choose either Windows or Linux images for free VMs, and provide guidance or screenshots for both.
- Avoid using only 'Windows' in examples; alternate or combine with Linux to ensure parity.
- If there are differences in free tier availability between Windows and Linux VMs, clarify them for transparency.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/create-subscription-request.md
...nagement-billing/manage/create-subscription-request.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes using the Azure portal (a web interface) and does not provide any command-line examples. While this avoids explicit Windows tool bias (e.g., PowerShell), it implicitly favors Windows users by not mentioning or providing parity for Linux command-line tools (such as Azure CLI or Bash scripting). There are no Linux-specific instructions or examples, nor any cross-platform command-line alternatives.
Recommendations
- Add examples for creating subscriptions using Azure CLI, which is cross-platform and widely used on Linux.
- Include Bash scripting examples for automating subscription creation, where applicable.
- Explicitly mention that the Azure portal is accessible from any OS, but provide links or instructions for users who prefer command-line or automation approaches.
- Ensure that any references to programmatic creation include both PowerShell and Azure CLI (or REST API) examples, with equal prominence.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/find-tenant-id-domain.md
...ost-management-billing/manage/find-tenant-id-domain.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively describes how to find the tenant ID and primary domain using the Azure portal, a web-based tool that is platform-agnostic but often associated with Windows-centric workflows. There are no command-line examples (such as Azure CLI or PowerShell), but the absence of Linux-specific instructions (e.g., Azure CLI commands) means Linux users are not provided with parity for non-GUI workflows.
Recommendations
- Add Azure CLI examples for finding the tenant ID and primary domain, which work cross-platform (Windows, Linux, macOS).
- If mentioning PowerShell, also provide Bash/Azure CLI equivalents.
- Clarify that the Azure portal is accessible from any modern browser on any OS, to avoid the perception of Windows bias.
- Consider including REST API examples for automation scenarios.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/manage-azure-credits.md
...cost-management-billing/manage/manage-azure-credits.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes management of Azure credit resources using the Azure portal GUI, which is a cross-platform web interface but is often perceived as Windows-centric due to its historical association and lack of command-line alternatives. There are no examples or instructions for managing credit resources using CLI tools such as Azure CLI or Azure PowerShell, nor are there any Linux-specific workflows or references. This omission may disadvantage users who prefer or require command-line or automation approaches, especially on Linux or macOS platforms.
Recommendations
- Add equivalent instructions for managing credit resources using Azure CLI commands, which are cross-platform and widely used on Linux.
- Include Azure PowerShell examples, but clarify that both Windows and Linux users can use PowerShell Core.
- Explicitly state that all operations can be performed from any OS using the portal, but highlight command-line alternatives for automation and scripting.
- Provide sample scripts for moving, viewing, and managing credit resources using Azure CLI and PowerShell, and note any OS-specific considerations.
- Ensure that references to tools and workflows do not imply Windows as the default platform, and mention Linux and macOS compatibility where relevant.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/manage-azure-discount.md
...ost-management-billing/manage/manage-azure-discount.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation exclusively uses the Azure portal (a web GUI) for all management tasks and does not provide any command-line examples (such as Azure CLI, PowerShell, or REST API). While the portal is cross-platform, the lack of CLI or script-based instructions is a common pattern in Windows-centric documentation, as Windows users are more likely to use GUIs. There is no mention of Linux-specific tools, nor are there examples using Azure CLI (which is popular among Linux users). The documentation also refers to 'updating tools and scripts' but does not specify or provide examples for either PowerShell or Azure CLI, missing an opportunity for parity.
Recommendations
- Add Azure CLI examples for all resource management tasks (moving, viewing, deleting, tagging, etc.), as CLI is widely used on Linux and macOS.
- Include PowerShell examples for parity, but ensure CLI examples are presented first or alongside PowerShell.
- Explicitly mention that all operations can be performed via CLI, REST API, or SDKs, and link to relevant documentation.
- Clarify that the Azure portal is web-based and cross-platform, but provide alternatives for users who prefer command-line or automation.
- Where 'update tools and scripts' is mentioned, provide concrete examples for both PowerShell and Azure CLI.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/manage-billing-access.md
...ost-management-billing/manage/manage-billing-access.md
Medium Priority
View Details â
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 for managing billing access, such as using Azure CLI or PowerShell. While it avoids explicit Windows tools, it implicitly favors Windows by omitting Linux-friendly CLI instructions and by referencing graphical workflows that are most familiar to Windows users. There is no mention of Linux-specific tools, nor are cross-platform command-line approaches (like Azure CLI) demonstrated.
Recommendations
- Add examples using Azure CLI for assigning roles and managing billing access, as Azure CLI is cross-platform and works on both Windows and Linux.
- Include PowerShell examples if relevant, but always provide Azure CLI equivalents and present them before or alongside PowerShell to avoid Windows-first bias.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows using Azure CLI.
- Provide links to documentation on installing and using Azure CLI on Linux.
- Clarify that the Azure portal is accessible from any OS, but highlight command-line alternatives for automation and scripting.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/manage-billing-across-tenants.md
...gement-billing/manage/manage-billing-across-tenants.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively references the Azure portal and Microsoft admin center web interfaces, which are most commonly accessed from Windows environments. There are no examples or instructions for managing billing tenants using command-line tools or automation, such as Azure CLI, PowerShell, or REST APIs. Furthermore, there is no mention of Linux-specific tools, nor are cross-platform command-line options provided. The documentation implicitly assumes a Windows-centric workflow by focusing solely on GUI navigation and omitting Linux parity.
Recommendations
- Add examples for managing billing tenants using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include REST API references or sample calls for key operations (adding tenants, assigning roles, moving subscriptions) to enable automation from any OS.
- If PowerShell examples are added, also provide equivalent Azure CLI commands to ensure Linux and macOS users are supported.
- Explicitly mention that all portal-based steps can be performed from any OS with a supported browser, and clarify any OS-specific limitations if they exist.
- Provide troubleshooting steps or notes for users accessing the Azure portal from Linux environments, if applicable.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/manage-consumption-commitment.md
...gement-billing/manage/manage-consumption-commitment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively references the Azure portal (web UI) for all management actions and does not provide command-line examples. There is no mention of PowerShell, Windows tools, or CLI commands, but the absence of Azure CLI or bash examples means Linux users are not given parity in instructions. The portal is platform-agnostic, but the lack of CLI guidance is a subtle bias toward Windows users, who are more likely to use the portal or PowerShell by default.
Recommendations
- Add Azure CLI examples for moving, viewing, tagging, and deleting MACC resources, as the CLI is cross-platform and widely used on Linux.
- Explicitly mention that all actions can be performed via Azure CLI or REST API, and provide links or code snippets.
- Ensure that any future examples include both PowerShell and Azure CLI commands, with CLI examples shown first or side-by-side.
- Clarify that the Azure portal is accessible from any OS, but highlight command-line alternatives for automation and scripting.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/mca-request-billing-ownership.md
...gement-billing/manage/mca-request-billing-ownership.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes and illustrates the billing ownership transfer process using the Azure portal UI, with no mention of command-line tools, scripts, or automation options. There are no references to Powershell, but also no mention of Azure CLI, Bash, or Linux-specific workflows. All instructions assume use of the Azure portal, which is platform-agnostic, but the absence of CLI or automation examples (which are often used on Linux) creates an implicit Windows/UI-first bias.
Recommendations
- Add equivalent instructions for performing billing ownership transfers using the Azure CLI, which is cross-platform and widely used on Linux.
- Include example commands for common tasks (e.g., creating or approving transfer requests) using Azure CLI or REST API.
- Explicitly mention that all portal-based steps can be performed from any OS, and provide links to CLI documentation for users who prefer automation or non-GUI workflows.
- If Powershell is not relevant, clarify that both Azure CLI and Powershell can be used for automation, and provide parity in examples for both where applicable.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/programmatically-create-subscription-enterprise-agreement.md
...grammatically-create-subscription-enterprise-agreement.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents REST, PowerShell, and Azure CLI examples for all major operations, but PowerShell is consistently listed before Azure CLI in tab order and example sections. There are references to installing PowerShell modules and using PowerShellGet, which are Windows-centric tools. No explicit Linux-only examples or shell scripts are provided, and PowerShell is given equal or greater prominence than Azure CLI, which is cross-platform. There is no mention of Linux-specific considerations or alternative shell scripting approaches.
Recommendations
- List Azure CLI examples before PowerShell in tab order and example sections, as CLI is natively cross-platform.
- Explicitly mention that both Azure CLI and PowerShell are available on Linux, macOS, and Windows, and provide installation links for each platform.
- Add bash or shell script examples for common operations to demonstrate Linux-native workflows.
- Avoid references to Windows-specific tools (e.g., PowerShellGet) without noting Linux/macOS alternatives or cross-platform installation instructions.
- Include a note or section on platform compatibility for all tools mentioned, clarifying usage on Linux and macOS.
- Where possible, use generic terms like 'command line' rather than 'PowerShell' when referring to cross-platform operations.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/software-costs-not-included.md
...nt-billing/savings-plan/software-costs-not-included.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation focuses exclusively on Windows VM software costs and does not mention Linux or other operating systems. All examples and meter tables are for Windows Server or generic 'Cloud Services' licenses, with no discussion of Linux equivalents or clarification that Linux VMs do not incur these software charges. This may lead to confusion for Linux users and gives the impression that only Windows scenarios are relevant.
Recommendations
- Explicitly state whether Linux VMs incur any software meter charges under savings plans, and clarify if Linux VMs are exempt.
- Add a section or table for Linux VM software meters, even if to confirm that there are none.
- Provide parity in examples and explanations for both Windows and Linux users.
- Consider adding a comparison table showing differences in software costs between Windows and Linux VMs under savings plans.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/charge-back-usage.md
...t-management-billing/reservations/charge-back-usage.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively demonstrates how to access Azure Reservation cost data using the Azure Portal and REST API, without providing any platform-specific command-line examples. However, all navigation and screenshots are based on the Azure Portal, which is most commonly accessed from Windows environments. There are no examples or guidance for Linux users (e.g., using Azure CLI, Bash scripting, or PowerShell Core on Linux), nor is there mention of Linux tools or workflows. This may implicitly prioritize Windows-centric workflows and leaves out parity for Linux users.
Recommendations
- Add examples using Azure CLI commands (az consumption usage list, az costmanagement query, etc.) for retrieving reservation and amortized cost data, with sample Bash scripts.
- Include instructions or scripts that can be run on Linux/macOS terminals, not just portal navigation.
- Mention that the Azure Portal and REST API are cross-platform, and clarify that all instructions apply equally regardless of OS.
- Provide sample code snippets for downloading and processing CSV files using common Linux tools (e.g., curl, wget, jq, awk).
- If PowerShell is referenced in other related docs, ensure PowerShell Core (cross-platform) is used, and provide Bash equivalents.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/determine-reservation-purchase.md
...billing/reservations/determine-reservation-purchase.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing only Windows-centric tools (such as Power BI and the Azure portal) for analysis and recommendations, with no mention of Linux-compatible tools or command-line workflows. There are no examples or guidance for users who may want to analyze usage data using Linux tools (e.g., bash, awk, jq) or open-source alternatives. The documentation assumes a GUI-based, Windows-oriented workflow, which may exclude Linux users or those preferring CLI-based analysis.
Recommendations
- Include examples of how to analyze the Azure usage file using common Linux command-line tools (e.g., grep, awk, jq, pandas in Python).
- Mention open-source or cross-platform alternatives to Power BI, such as using Jupyter Notebooks, pandas, or other data analysis tools available on Linux.
- Provide sample scripts (in bash, Python, etc.) for filtering and processing the usage data to determine reservation needs.
- Explicitly state that the Azure portal and APIs are accessible from any OS, and offer guidance for users who prefer CLI or programmatic access.
- Add a section or callout for Linux/macOS users, highlighting any differences or tips for performing the analysis on those platforms.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/fabric-capacity.md
...ost-management-billing/reservations/fabric-capacity.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively references the Azure portal (a web-based GUI) for all operations and does not mention or provide any examples using command-line tools such as Azure CLI, PowerShell, or scripting interfaces. There are no Linux-specific instructions or examples, nor is there any mention of cross-platform automation options. The focus on the Azure portal and lack of CLI or API examples can be considered a bias toward Windows-centric workflows, as many Linux users prefer or require command-line or automation-friendly approaches.
Recommendations
- Add Azure CLI examples for all major operations (purchasing, managing, exchanging, and refunding reservations), as Azure CLI is cross-platform and widely used on Linux.
- If relevant, provide PowerShell examples, but always present Azure CLI first or alongside PowerShell to ensure Linux parity.
- Mention and link to REST API documentation for users who wish to automate reservation management.
- Explicitly state that all operations can be performed from Linux, macOS, or Windows using Azure CLI or REST API, not just the Azure portal.
- Include screenshots or terminal output from Linux environments where possible to reinforce cross-platform support.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/nutanix-bare-metal.md
...-management-billing/reservations/nutanix-bare-metal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively references the Azure portal and Azure-specific purchasing patterns, with no mention of Linux tools, CLI, or cross-platform automation methods. All instructions assume use of the web portal and do not provide examples for Linux users (e.g., Azure CLI, Bash, or automation via REST API). There is no evidence of PowerShell-specific bias, but the overall approach is Windows-centric by omission of Linux alternatives.
Recommendations
- Add step-by-step instructions for purchasing reservations using Azure CLI, which is cross-platform and commonly used on Linux.
- Include examples of automating reservation management via REST API or ARM templates, which are platform-agnostic.
- Explicitly mention that the Azure portal is accessible from any OS, but provide parity for users who prefer command-line or scriptable interfaces.
- Where relevant, provide Bash shell examples alongside any PowerShell or portal instructions.
- Clarify any platform-specific requirements or limitations, if they exist.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/calculate-ea-savings-plan-savings.md
...ling/savings-plan/calculate-ea-savings-plan-savings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively demonstrates the calculation process using Microsoft Excel, a Windows-centric tool, and all step-by-step instructions reference Excel-specific UI elements and workflows. There are no examples or guidance for performing the same calculations using Linux-native tools (such as LibreOffice Calc, Gnumeric, or command-line utilities like awk/csvkit), nor is there mention of how to adapt the process for non-Windows environments. The language and screenshots reinforce a Windows-first approach, potentially excluding Linux users or those preferring open-source alternatives.
Recommendations
- Add parallel instructions for performing the calculations using LibreOffice Calc or other cross-platform spreadsheet applications.
- Include examples of how to process and analyze the CSV data using command-line tools available on Linux (e.g., awk, csvkit, pandas in Python).
- Provide screenshots and UI references for non-Excel spreadsheet applications.
- Explicitly state that the process can be performed on any OS and mention alternative tools for Linux/macOS users.
- Consider including downloadable sample scripts (e.g., Python, shell) to automate the calculation for users who prefer not to use a GUI.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/manage-savings-plan.md
...management-billing/savings-plan/manage-savings-plan.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes management of Azure savings plans via the Azure Portal UI, with no mention of command-line tools or automation options. There are no examples using Azure CLI, Bash, or PowerShell, but the UI navigation and terminology are strongly aligned with Windows-centric patterns (e.g., 'left menu', 'top navigation bar', 'Home'). No Linux-specific tools, commands, or automation approaches are provided, and the documentation does not address cross-platform or headless management scenarios.
Recommendations
- Add equivalent Azure CLI (az) command examples for all major actions (e.g., updating scope, changing auto-renewal, delegating RBAC roles).
- If PowerShell examples are added, ensure Bash/Azure CLI equivalents are also included and presented with equal prominence.
- Mention and link to relevant REST API documentation for automation and cross-platform use.
- Clarify that all actions can be performed from any OS via the Azure Portal, but highlight CLI and API options for users who prefer or require non-GUI workflows.
- Review UI terminology to ensure it is not Windows-specific (e.g., avoid 'left menu' if possible, or clarify that the UI may look different on different platforms/browsers).
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/scope-level/sql-server-hadr-licenses.md
...gement-billing/scope-level/sql-server-hadr-licenses.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation page focuses exclusively on the Azure SQL Virtual Machine configuration, referencing the HADR benefit selection via the portal UI. There are no examples or guidance for Linux-based SQL Server deployments, nor are command-line alternatives (such as Azure CLI or Bash) provided. The documentation implicitly assumes a Windows-centric environment by only referencing the portal and SQL Server, which is most commonly associated with Windows, without acknowledging Linux scenarios.
Recommendations
- Include explicit guidance or examples for configuring HADR benefit on Linux-based SQL Server VMs.
- Provide Azure CLI and/or Bash command examples for selecting the HADR benefit, in addition to or instead of portal screenshots.
- Clarify whether the described process applies equally to both Windows and Linux SQL Server VMs, and note any differences.
- Reference Linux-specific documentation or considerations where relevant.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-billing/billing-troubleshoot-azure-payment-issues.md
...t-billing/billing-troubleshoot-azure-payment-issues.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates mild Windows bias by referencing Microsoft Edge and Internet Explorer (Windows-centric browsers) and linking to a Microsoft Edge-specific support article for private browsing. No Linux-specific browsers or troubleshooting steps are mentioned, and the browser troubleshooting section assumes the user is on Windows. There are no command-line examples, so no PowerShell bias is present, but the guidance does not address Linux or cross-platform users explicitly.
Recommendations
- Include browser troubleshooting steps for popular Linux browsers, such as Firefox and Chrome, and provide links to their private/incognito mode documentation.
- Use more platform-neutral language when referring to browsers (e.g., 'open a private browsing session in your browser of choice').
- If referencing Microsoft Edge, clarify that users can use any supported browser and provide equivalent instructions for non-Windows platforms.
- Add a note acknowledging that Azure portal access and troubleshooting steps apply to users on Windows, Linux, and macOS, and provide platform-agnostic guidance where possible.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-billing/troubleshoot-ea-billing-issues-usage-file-pivot-tables.md
...troubleshoot-ea-billing-issues-usage-file-pivot-tables.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias by exclusively providing instructions and screenshots for Microsoft Excel, a Windows-centric tool, and referencing Windows keyboard shortcuts. There are no examples or guidance for Linux users or alternative spreadsheet applications (such as LibreOffice Calc or Google Sheets), nor are Linux-specific tools or workflows mentioned.
Recommendations
- Include equivalent instructions and screenshots for popular Linux spreadsheet applications, such as LibreOffice Calc.
- Mention alternative keyboard shortcuts for non-Windows platforms (e.g., Linux, macOS).
- Add a section or note explaining how to perform the same data manipulation tasks using Linux command-line tools (e.g., csvkit, pandas, awk) for users who may not use GUI spreadsheet applications.
- Clarify that the process is not limited to Excel and provide explicit steps for other platforms to ensure parity.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-subscription/troubleshoot-azure-sign-up.md
...roubleshoot-subscription/troubleshoot-azure-sign-up.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides browser troubleshooting steps that mention Chrome and Microsoft Edge, but does not mention Firefox or other browsers common on Linux. There are no examples or troubleshooting steps that reference Linux-specific tools, environments, or patterns. All instructions and screenshots are platform-neutral except for browser settings, which are Windows-centric.
Recommendations
- Include troubleshooting steps for Firefox and other browsers commonly used on Linux, especially for cookie settings.
- Explicitly state that the Azure portal is accessible from Linux and macOS, and that the troubleshooting steps apply regardless of OS, unless otherwise noted.
- If there are any platform-specific issues (e.g., with browser compatibility or certificate stores), document them for Linux users.
- Add a note or section addressing common Linux-specific sign-up issues, if any exist.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-subscription/troubleshoot-sign-in-issue.md
...roubleshoot-subscription/troubleshoot-sign-in-issue.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by listing Microsoft Edge (a Windows-centric browser) first in all browser-related troubleshooting steps and providing detailed instructions for Edge and Chrome, but omitting Linux-specific browsers (such as Firefox) and failing to mention Linux-specific troubleshooting steps. There are no examples or instructions tailored for Linux users, nor is there any mention of Linux tools or patterns.
Recommendations
- Include instructions for popular Linux browsers such as Firefox (e.g., how to clear cache/cookies, use private browsing).
- Add troubleshooting steps relevant to Linux environments, such as checking for issues with desktop environments or network settings.
- Ensure browser instructions are cross-platform and not ordered with Windows-centric options first; consider alphabetical or usage-based ordering.
- Explicitly mention that steps apply to all operating systems, or provide OS-specific sections where necessary.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/cluster-references/environment-reference.md
...cyclecloud/cluster-references/environment-reference.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation is heavily Azure-centric, focusing exclusively on Azure Resource Manager (ARM) templates and related constructs. There are no examples or references to Linux-specific tools, deployment patterns, or cross-platform considerations. All examples use Azure-native paths and features, with no mention of Linux command-line tools, shell scripting, or non-Windows workflows.
Recommendations
- Add examples showing how to interact with CycleCloud and ARM templates using Linux shell commands (e.g., curl, az CLI in bash).
- Include references or links to Linux-friendly tools and scripting patterns for managing templates and deployments.
- Explicitly mention cross-platform compatibility and provide guidance for users working from Linux environments.
- If relevant, provide parity in documentation for Linux-based automation (e.g., using bash scripts to upload templates, manage resources, etc.).
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/download-azure-daily-usage.md
...ement-billing/understand/download-azure-daily-usage.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page predominantly describes usage and download procedures via the Azure portal UI, which is platform-agnostic, but when command-line instructions are given, only Azure CLI examples are provided. There is no mention of Linux-specific patterns, nor are there any examples using Linux shell tools or scripts. The page does not reference PowerShell, but it also does not provide parity for Linux users in terms of CLI usage, such as bash scripting, curl/wget, or automation patterns common on Linux. The overall structure and screenshots are Windows-centric (Azure portal UI), and there is no explicit guidance for Linux environments.
Recommendations
- Include Linux shell (bash) examples for downloading and processing usage files, such as using curl, wget, or az CLI in bash scripts.
- Add notes or sections describing how to automate downloads and post-processing on Linux systems, including sample scripts for parsing CSV files.
- Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux.
- Provide parity in troubleshooting and support guidance for Linux users, such as common issues with CLI on Linux.
- Where screenshots are used, clarify that the Azure portal is accessible from any OS, and consider including Linux desktop browser screenshots for inclusivity.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/pay-bill.md
...rticles/cost-management-billing/understand/pay-bill.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation describes how to pay Azure bills using the Azure portal and various payment methods, but all instructions and examples are centered around the Azure portal web interface. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), but where platform-specific tools or automation might be relevant, only the Azure portal is mentioned. There is no mention of Linux-specific tools, nor any parity for Linux users in terms of automation or scripting. The documentation implicitly assumes a GUI-first, likely Windows-centric workflow, and does not address Linux users' needs for command-line or cross-platform automation.
Recommendations
- Add Azure CLI examples for common billing operations (e.g., viewing invoices, making payments) to provide parity for Linux and macOS users.
- If PowerShell automation is supported for billing tasks, ensure Azure CLI or Bash equivalents are also documented and presented equally.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, but also provide links or guidance for users who prefer or require command-line tools.
- Include a section or links to automation options for Linux users, such as using REST APIs or scripting with curl/wget.
- Review related documentation to ensure Linux and macOS users are not excluded from advanced or automated billing workflows.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/understand-usage.md
...cost-management-billing/understand/understand-usage.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias by recommending Microsoft Excel as the primary tool for opening the usage and charges CSV file, mentioning it before 'another spreadsheet application.' There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-native tools (e.g., LibreOffice Calc, csvkit, or command-line parsing with awk/cat/grep). However, the bias is not severe as the documentation is mostly conceptual and does not provide step-by-step examples limited to Windows or PowerShell.
Recommendations
- Explicitly mention Linux-compatible spreadsheet tools such as LibreOffice Calc or Google Sheets alongside Microsoft Excel.
- Provide examples or references for viewing and processing CSV files using Linux command-line tools (e.g., cat, less, awk, csvkit).
- Ensure that any future step-by-step instructions include both Windows and Linux methods for downloading, opening, and analyzing the usage and charges file.
- Avoid listing Microsoft Excel first; instead, use neutral phrasing like 'You can open your usage and charges CSV file in a spreadsheet application such as Microsoft Excel, LibreOffice Calc, or Google Sheets.'
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/understand-azure-marketplace-charges.md
...ing/understand/understand-azure-marketplace-charges.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation exclusively describes how to manage Azure external service charges using the Azure portal, which is a graphical web interface. There are no command-line examples or automation instructions for any platform. However, there is an implicit Windows bias because the Azure portal and its screenshots are typically captured from a Windows environment, and no mention is made of Linux tools, CLI, or automation options that are commonly used on Linux or cross-platform environments. There are also no PowerShell-specific examples, but the absence of Azure CLI or REST API instructions means Linux users are underserved.
Recommendations
- Add Azure CLI examples for viewing, downloading, and paying invoices, as well as for managing external service resources. The Azure CLI is cross-platform and commonly used on Linux.
- Include REST API references or examples for users who want to automate billing and resource management tasks.
- Mention that all portal operations can be performed from any OS with a web browser, and clarify that the portal is not Windows-specific.
- Provide links to documentation for PowerShell, Azure CLI, and REST API equivalents for all portal actions described.
- Add screenshots or notes that reflect usage from non-Windows environments, or clarify that the portal UI is consistent across platforms.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/azure-credentials.md
...articles/cyclecloud/common-issues/azure-credentials.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation provides instructions using the Azure CLI, which is cross-platform, but all credential update steps reference the Azure portal (a web UI) and do not mention Linux-specific tools or command-line alternatives for credential management. There are no explicit Linux shell examples or guidance for users who may prefer or require non-GUI workflows.
Recommendations
- Add Linux shell (bash) command-line examples for updating credentials, such as using az CLI commands in bash.
- Explicitly mention that Azure CLI is cross-platform and provide instructions for installing and using it on Linux.
- Include guidance for users who may not have access to the Azure portal GUI, such as headless server environments.
- Ensure parity by referencing both Windows and Linux workflows where applicable.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/unavailable-sku.md
...n/articles/cyclecloud/common-issues/unavailable-sku.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references UI navigation steps (e.g., 'Settings', 'Azure types') without clarifying whether these are for the Azure Portal, a Windows-specific tool, or cross-platform. There are no CLI-based examples (such as Azure CLI or PowerShell), and no Linux-specific guidance or parity is provided. The absence of command-line examples or explicit Linux instructions may disadvantage Linux users.
Recommendations
- Add Azure CLI examples for checking available VM sizes and regions (e.g., using 'az vm list-sizes' or 'az vm list-skus').
- Clarify whether the instructions refer to the Azure Portal (which is cross-platform) or a Windows-only tool.
- If PowerShell examples are added, ensure equivalent Azure CLI (Linux-friendly) commands are also provided.
- Explicitly mention that the Azure Portal is accessible from any OS, if that is the intended interface.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/updating-scalesets.md
...rticles/cyclecloud/common-issues/updating-scalesets.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively describes resolving quota issues using graphical tools (Cluster page UI, Azure portal), which are more commonly used in Windows environments. There are no examples or instructions for performing these checks or quota requests using command-line tools (such as Azure CLI), which are preferred in Linux workflows.
Recommendations
- Add instructions for checking VM quotas using Azure CLI (az vm list-usage, az quota commands) with example commands.
- Include steps for requesting quota increases via CLI or REST API, not just through the portal.
- Ensure that both GUI and CLI methods are presented, with CLI examples given equal prominence.
- Mention that the CLI methods work cross-platform (Windows, Linux, macOS).
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/download-cluster-templates.md
...main/articles/cyclecloud/download-cluster-templates.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page exhibits mild Windows bias by highlighting Microsoft HPC Pack (a Windows-specific job scheduler) in the template table, including a direct link to a PowerShell-based overview for HPC Pack, and referencing Windows tools before Linux equivalents. There are no explicit Linux command examples, but most templates are cross-platform or Linux-oriented. The documentation does not provide Linux-specific instructions or examples, and the only scheduler with a Microsoft/Windows focus (HPC Pack) is given prominence with a PowerShell documentation link.
Recommendations
- Add explicit Linux command-line examples (e.g., bash, shell) for template import and management alongside any Windows/PowerShell instructions.
- Ensure that Linux-oriented schedulers (Slurm, HTCondor, OpenPBS, Grid Engine) are given equal prominence, with direct links to their documentation and usage guides.
- Avoid linking to Windows/PowerShell documentation before Linux equivalents; provide both or alternate their order.
- Include notes or sections on platform compatibility and any differences in usage between Windows and Linux environments.
- Where possible, provide parity in tooling references, ensuring Linux tools (e.g., bash scripts, Linux CLI) are mentioned and demonstrated.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/add-node-array.md
...blob/main/articles/cyclecloud/how-to/add-node-array.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation page does not provide explicit Windows or PowerShell examples, but it does lack Linux-specific command-line examples or references. The only CLI example uses the CycleCloud CLI, which is cross-platform, but there is no mention of Linux-specific workflows, tools, or shell commands. There are also no references to Linux editors or environment considerations, and the template editing instructions are generic. The absence of Linux-specific guidance or examples may make the documentation less accessible to Linux users.
Recommendations
- Add explicit Linux shell command examples for editing and importing the cluster template (e.g., using nano, vim, or cat for editing).
- Clarify that the CycleCloud CLI commands work on Linux, macOS, and Windows, and provide example commands for each platform if there are differences.
- Mention common Linux tools or workflows for managing template files (e.g., using bash scripts for automation).
- If there are any platform-specific prerequisites or behaviors (such as file paths or permissions), document them explicitly.
- Consider including screenshots or terminal output from a Linux environment to improve parity.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/plan-your-deployment.md
...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows/Azure-centric tools and patterns, such as Azure Bastion, VPN Gateway, and Azure-specific networking constructs, without mentioning or providing guidance for Linux-native or open-source alternatives. There are no examples or instructions for Linux command-line tools, SSH, or cross-platform access methods, and all access scenarios assume Azure-native solutions.
Recommendations
- Provide examples or mention how to access CycleCloud Workspace for Slurm using standard SSH from Linux or macOS clients, not just via Azure Bastion or VPN Gateway.
- Include guidance for users who may want to use open-source VPN solutions (e.g., OpenVPN, WireGuard) instead of Azure VPN Gateway.
- Clarify whether Linux users can use native tools (e.g., SSH, SCP) to connect to the environment, and provide instructions or references.
- If possible, add a section or note on cross-platform access patterns, ensuring that both Windows and Linux users are supported equally.
- Mention any Linux-specific prerequisites or considerations for deploying or managing the environment.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/install-arm.md
...cs/blob/main/articles/cyclecloud/how-to/install-arm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows a mild Windows bias by mentioning Windows users and their shell options before Linux users, and by not providing explicit Linux-specific examples or instructions. While the Azure CLI is cross-platform and the SSH key generation is shown with Unix-style commands, Linux-specific guidance is minimal and often referenced only via external links. There are no PowerShell-specific examples, but the structure and order of instructions prioritize Windows users.
Recommendations
- Present Linux and Windows shell options in parallel, rather than listing Windows first.
- Provide explicit Linux (and macOS) instructions for shell access, such as using the default terminal or bash.
- Include Linux-specific examples and troubleshooting tips directly in the documentation, rather than linking out.
- Clarify that all CLI commands work on both Windows and Linux, and note any OS-specific differences if they exist.
- Consider adding a short section or callout for macOS users as well, to ensure parity across all major platforms.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/htcondor.md
...s/azure-docs/blob/main/articles/cyclecloud/htcondor.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation generally presents a Linux-centric workflow (CentOS images, Linux paths, Linux commands) but includes Windows-specific configuration options and paths in the configuration reference table. In several cases, Windows equivalents are mentioned after Linux defaults, and some options are marked as Windows-only. However, there are no explicit PowerShell or Windows command-line examples, and the primary usage examples are Linux-based.
Recommendations
- Provide explicit examples for both Linux and Windows environments where configuration paths or behaviors differ (e.g., show both /mnt/condor_data and C:\All Services\condor_local in context).
- Clarify in each configuration option table entry when a setting is platform-specific, and group or label them accordingly.
- If Windows is supported for HTCondor on CycleCloud, include at least one end-to-end example using a Windows image and relevant commands.
- Ensure that any Windows-only options (such as htcondor.ignore_hyperthreads) are clearly separated or highlighted to avoid confusion.
- Consider adding a section summarizing platform-specific considerations for both Linux and Windows users.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/images.md
...ocs/azure-docs/blob/main/articles/cyclecloud/images.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based examples for specifying images (e.g., 'cycle.image.win2022', Windows Server URNs, and 'Windows 2022 DataCenter' labels) while omitting equivalent Linux examples. Although the supported image table lists both Linux and Windows images, the usage examples and guidance focus exclusively on Windows, with no demonstration of Linux image configuration.
Recommendations
- Include Linux-based examples alongside Windows examples for specifying images, such as 'cycle.image.ubuntu22' or 'Alma Linux 8'.
- Alternate the order of examples or provide parallel examples for both Windows and Linux to avoid implicit prioritization.
- Add explicit guidance or notes for Linux users, such as how to specify Ubuntu or SLES images, and any Linux-specific considerations.
- Ensure that documentation sections referencing image configuration provide equal coverage for both Windows and Linux operating systems.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/slurm-3.md
...cs/azure-docs/blob/main/articles/cyclecloud/slurm-3.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation demonstrates a moderate Windows/Azure bias. It exclusively references Azure-specific tools (e.g., azslurm CLI, CycleCloud), and all examples and workflows are built around these tools. There are no references to native Linux tools or generic Slurm commands outside the Azure context. While all command-line examples use bash and Slurm commands (which are Linux-native), the documentation assumes the use of Azure CycleCloud and its tooling, which is primarily designed for Azure (and often managed from Windows environments). There are no PowerShell examples, but the documentation does not mention or provide parity for non-Azure Linux environments or tools.
Recommendations
- Add examples and instructions for using standard Slurm commands and workflows outside of the Azure/CycleCloud context, to help users familiar with generic Linux/Slurm environments.
- Clarify which steps are Azure/CycleCloud-specific and which are standard Slurm operations, possibly providing side-by-side examples.
- Mention and, where possible, provide guidance for users running Slurm on native Linux environments without Azure CycleCloud.
- If possible, reference or link to documentation for running Slurm on non-Azure platforms to provide context and alternatives.
- Ensure that Linux-native tools and workflows are not overshadowed by Azure-specific tooling, and explain any differences in behavior or configuration.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-virtual-network-configuration.md
...ssis-integration-runtime-virtual-network-configuration.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the Azure portal UI and, in the related content, linking to a PowerShell-based guide for joining Azure-SSIS IR to a virtual network. There are no examples or instructions for performing these tasks using Linux-friendly tools such as Azure CLI, nor are there references to Bash scripting or cross-platform automation methods.
Recommendations
- Add equivalent Azure CLI (az) command examples for all portal-based steps, ensuring Linux and macOS users can follow along without relying on PowerShell.
- Include references or links to documentation for performing these tasks using cross-platform tools (e.g., Azure CLI, REST API).
- Where PowerShell is mentioned in related content, provide parity by linking to or creating guides for Azure CLI and/or Bash.
- Explicitly state that all operations can be performed on Linux, macOS, and Windows, and clarify any platform-specific limitations.
- Consider including screenshots or terminal output from Linux environments to reinforce cross-platform support.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/change-data-capture-troubleshoot.md
...icles/data-factory/change-data-capture-troubleshoot.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows/SQL Server bias by exclusively providing troubleshooting steps and examples for SQL Server (a Microsoft/Windows-centric database), using T-SQL and system stored procedures (e.g., sys.sp_cdc_enable_db), and referencing Azure SQL Database as a sink. There are no examples or guidance for Linux-based databases (e.g., PostgreSQL, MySQL) or for using command-line tools common on Linux. No Linux-specific troubleshooting or parity is addressed.
Recommendations
- Include troubleshooting steps and examples for popular Linux-based databases that support CDC, such as PostgreSQL or MySQL.
- Provide equivalent command-line examples using Linux tools (e.g., psql, mysql CLI) where applicable.
- Mention and link to documentation for enabling CDC on non-SQL Server sources, especially open-source databases commonly used on Linux.
- Clarify in the introduction if the CDC resource only supports SQL Server, or expand support and documentation to other platforms.
- Add notes or sections for Linux users, including any differences in setup, permissions, or troubleshooting steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-concur.md
...cs/blob/main/articles/data-factory/connector-concur.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by explicitly stating that the connector supports only Windows versions for the self-hosted integration runtime, with no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or parity guidance for non-Windows users.
Recommendations
- Clearly state whether Linux-based self-hosted integration runtime is supported or not. If not, provide a roadmap or alternatives for Linux users.
- If possible, add instructions or references for setting up the integration runtime on Linux (if/when supported).
- Include explicit notes or guidance for users on non-Windows platforms, such as using Docker containers or other cross-platform solutions.
- Ensure that all examples and prerequisites mention both Windows and Linux (or clarify platform limitations) to avoid excluding Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-informix.md
.../blob/main/articles/data-factory/connector-informix.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation assumes the Integration Runtime host is a Windows machine by referencing ODBC DSN setup and the Informix Client SDK, but does not clarify or provide guidance for Linux-based Integration Runtime hosts. There are no Linux-specific instructions or examples for setting up the ODBC driver or DSN, and all setup steps implicitly target Windows environments.
Recommendations
- Explicitly state whether Self-hosted Integration Runtime is supported on Linux, and if so, provide equivalent setup instructions for Linux hosts.
- Add Linux-specific guidance for downloading and installing the Informix ODBC driver and configuring DSN on Linux (e.g., editing odbc.ini).
- Include example connection strings and troubleshooting tips relevant to Linux environments.
- Clarify any platform limitations or differences in supported features between Windows and Linux Integration Runtime hosts.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-hubspot.md
...s/blob/main/articles/data-factory/connector-hubspot.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page shows evidence of Windows bias by referencing Windows support for the self-hosted integration runtime and linking to a Windows-specific prerequisites article. There are no explicit Linux or cross-platform instructions, and no Linux-specific examples or parity notes are provided.
Recommendations
- Explicitly state whether the self-hosted integration runtime supports Linux, and if so, provide a link to Linux installation instructions.
- If Linux is supported, add Linux-specific prerequisites and troubleshooting notes alongside the Windows references.
- Include examples or screenshots for Linux environments where relevant (e.g., service installation, configuration).
- If Linux is not supported, clearly state this limitation to set user expectations.
- Review and update all references to ensure parity in tool and OS support, mentioning Linux and macOS where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-odbc.md
...docs/blob/main/articles/data-factory/connector-odbc.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page shows evidence of Windows bias by exclusively referencing Windows-centric tools and patterns, such as requiring a 64-bit ODBC driver and using system DSN setup on the Integration Runtime machine, without mentioning Linux equivalents or providing Linux-specific instructions. The troubleshooting section refers to Integration Runtime Configuration Manager, which is a Windows-only tool, and there are no examples or guidance for Linux environments, such as using unixODBC or configuring DSNs on Linux.
Recommendations
- Add explicit instructions and examples for installing and configuring ODBC drivers and DSNs on Linux (e.g., using unixODBC).
- Clarify whether Self-hosted Integration Runtime is supported on Linux and provide setup steps if so.
- Include troubleshooting guidance for Linux environments, such as using command-line tools (isql, odbcinst) for testing connections.
- Mention cross-platform considerations for connection strings and authentication, noting any OS-specific differences.
- Ensure screenshots and UI references are not exclusively Windows-centric, or provide Linux alternatives where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-business-warehouse-open-hub.md
...a-factory/connector-sap-business-warehouse-open-hub.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by requiring the installation of the SAP .NET Connector (a Windows-only component) and does not mention or provide guidance for Linux-based integration runtimes. There are no Linux-specific instructions, examples, or troubleshooting steps, and all setup steps implicitly assume a Windows environment.
Recommendations
- Provide guidance for Linux users, including supported alternatives to the SAP .NET Connector or clarify platform limitations.
- If Linux is not supported, explicitly state this early in the prerequisites section to set user expectations.
- If possible, document cross-platform options (e.g., Java connectors, ODBC/JDBC alternatives) for SAP BW integration.
- Add troubleshooting and setup steps relevant to Linux environments if/when support is available.
- Ensure future examples and instructions are platform-agnostic or include both Windows and Linux variants where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-data-lake.md
...data-factory/connector-troubleshoot-azure-data-lake.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation page shows a mild Windows bias by referencing 'network monitor (netmon) trace', which is a Windows-specific tool, and does not provide equivalent Linux troubleshooting guidance or examples. There are no command-line examples, but the only tool mentioned for network tracing is Windows-based, and no Linux alternatives are suggested.
Recommendations
- When suggesting network tracing, mention cross-platform tools such as Wireshark or tcpdump, and provide instructions or links for both Windows and Linux environments.
- If referencing a tool like 'netmon', clarify that it is Windows-specific and suggest Linux equivalents.
- Include troubleshooting steps or examples that are applicable to both Windows and Linux self-hosted integration runtime scenarios.
- Review the documentation for other implicit Windows assumptions and ensure Linux users are equally supported.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-dynamics-dataverse.md
...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references XrmToolBox, a Windows-only tool, as a recommended troubleshooting utility without mentioning Linux alternatives or providing cross-platform guidance. No command-line examples or troubleshooting steps are given for Linux or macOS users. The documentation assumes access to Windows tools and does not address Linux environments.
Recommendations
- Provide alternative troubleshooting tools or methods that are available on Linux (e.g., using curl, Postman, or cross-platform SDKs) for testing Dynamics connections.
- Explicitly state the platform requirements for XrmToolBox and suggest equivalent steps for Linux users.
- Include command-line examples for common troubleshooting tasks using PowerShell (for Windows) and Bash/curl (for Linux/macOS) where relevant.
- Add a section addressing troubleshooting from non-Windows environments, including any limitations or workarounds.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-improvements.md
...actory/continuous-integration-delivery-improvements.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides command-line examples using Windows-style paths (e.g., C:\DataFactories\DevDataFactory) and does not offer equivalent Linux/macOS examples (e.g., /home/user/DataFactories/DevDataFactory). All explicit CLI examples use Windows path conventions, which may confuse or exclude Linux users. However, the YAML pipeline example does specify 'ubuntu-latest' as the build agent, indicating Linux compatibility, but this is not reflected in the CLI usage examples.
Recommendations
- Provide CLI examples using both Windows (C:\...) and Linux/macOS (/home/... or ~/...) path formats for all commands.
- Explicitly state that the npm commands work cross-platform and mention any OS-specific considerations.
- Add a note or section clarifying how Linux/macOS users should adapt the examples (e.g., path separators, environment variables).
- Where screenshots or images show Windows UI or file paths, consider adding Linux equivalents or clarifying that the process is OS-agnostic.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-manual-promotion.md
...ry/continuous-integration-delivery-manual-promotion.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively describes manual promotion of Resource Manager templates using the Azure Portal GUI, which is a platform-agnostic web interface but is often associated with Windows-centric workflows. There are no examples or mentions of command-line alternatives (such as Azure CLI or PowerShell), and no explicit Linux/macOS guidance or parity. The lack of CLI examples may disadvantage Linux users who prefer or require non-GUI automation.
Recommendations
- Add Azure CLI examples for exporting and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are added, ensure Azure CLI or Bash equivalents are also provided.
- Explicitly mention that the Azure Portal is accessible from any OS, to clarify platform neutrality.
- Include links or references to automation approaches (e.g., using az deployment group create) for users who prefer scripting or non-GUI workflows.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-overview.md
...icles/data-factory/data-migration-guidance-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation mentions Windows Installer (MSI) as a method for secured service-to-service integration but does not mention Linux equivalents or alternatives. No Linux-specific tools, authentication mechanisms, or examples are provided. The documentation lacks parity in describing how Linux users would perform the same secured integration or installation steps.
Recommendations
- Include Linux-specific installation and authentication options (e.g., using .tar.gz packages, systemd services, or Linux service principals).
- Mention cross-platform alternatives to Windows Installer (MSI), such as scripts or package managers (apt, yum) for Linux environments.
- Provide examples or references for Linux-based deployments and authentication flows.
- Ensure that all platform-specific tools or methods are presented together, or that Linux options are mentioned alongside Windows ones.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-customer-managed-key.md
...n/articles/data-factory/enable-customer-managed-key.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell and Azure CLI for enabling Key Vault properties, but does not provide any Linux-specific examples or mention Linux tools explicitly. The UI instructions and screenshots are all based on the Azure Portal, which is platform-agnostic, but there is no parity in command-line examples for Linux users. The only command-line tools mentioned (PowerShell and Azure CLI) are listed together, but PowerShell is mentioned first, which may imply a Windows-first approach. There are no bash or shell script examples, and no explicit guidance for Linux users.
Recommendations
- Provide explicit bash/Azure CLI examples for Linux users, especially for enabling Key Vault properties and managing permissions.
- When listing command-line options, alternate the order (e.g., mention Azure CLI before PowerShell in some sections) or clarify that both are cross-platform.
- Include notes or sections that highlight Linux/macOS compatibility and any platform-specific considerations.
- Where possible, add screenshots or terminal snippets from Linux environments to demonstrate parity.
- Explicitly mention that Azure CLI is cross-platform and provide installation links for Linux/macOS.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/guidance-for-byod-approach.md
...in/articles/data-factory/guidance-for-byod-approach.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively references the Self-Hosted Integration Runtime (SHIR), which is only available for Windows, and provides no mention of Linux support, alternatives, or examples. All installation and configuration steps implicitly assume a Windows environment, and there are no Linux equivalents or guidance for cross-platform scenarios.
Recommendations
- Explicitly state that SHIR is only available on Windows, and clarify platform limitations at the start of the documentation.
- If possible, provide guidance or references for Linux-based alternatives (such as Azure IR, or third-party integration runtimes) for users on non-Windows platforms.
- Include a comparison table or section outlining platform support for SHIR and connectors.
- If Linux support is planned or available in preview, mention this and link to relevant resources.
- For each step involving installation or configuration, specify the platform context (e.g., 'On your Windows machine...') to avoid ambiguity.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-change-data-capture-resource-with-schema-evolution.md
...-to-change-data-capture-resource-with-schema-evolution.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides step-by-step instructions for using Azure Data Factory's UI and Azure SQL Database as a source, with all examples and screenshots referencing Azure Data Studio and T-SQL. There are no explicit references to Windows-specific tools like PowerShell, but the only SQL client shown is Azure Data Studio (which is cross-platform but often associated with Windows), and there are no examples or guidance for Linux command-line tools, scripting, or alternative SQL clients. No Linux-specific instructions or parity examples are provided.
Recommendations
- Add explicit examples for performing schema changes using Linux-native tools, such as running T-SQL via sqlcmd in a Linux shell.
- Mention that Azure Data Studio is available on Linux and macOS, or provide alternative client options (e.g., DBeaver, Beekeeper Studio) for non-Windows users.
- Include command-line examples for validating Delta Lake files using tools like Azure CLI, Databricks CLI, or Python scripts, which are common on Linux.
- Clarify that all steps can be performed from Linux environments and provide screenshots or terminal snippets from Linux where appropriate.
- If any step requires a Windows-only tool, suggest equivalent Linux alternatives or note cross-platform compatibility.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/domain-and-outbound-port-requirements-external.md
...udes/domain-and-outbound-port-requirements-external.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page references only Azure services and patterns that are closely associated with Windows environments (e.g., *.core.windows.net, *.database.windows.net), without mentioning Linux-specific tools, commands, or considerations. There are no examples or guidance for Linux users, nor are there references to Linux networking tools or configuration steps.
Recommendations
- Add examples or notes for configuring outbound ports and domain access on Linux systems (e.g., using iptables, firewalld, or ufw).
- Mention any Linux-specific considerations for self-hosted integration runtime, such as service management commands (systemctl) or log file locations.
- If the integration runtime supports Linux, explicitly state so and provide parity in setup and troubleshooting instructions.
- Include cross-platform command examples (e.g., both PowerShell and Bash) for common tasks related to the documented features.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/agent-to-agent-overview.md
...ob/main/articles/api-center/agent-to-agent-overview.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate parity for Linux or cross-platform usage. There are no explicit Windows or PowerShell examples, but the absence of any mention of Linux tools, commands, or considerations may leave Linux users uncertain about support or usage patterns.
Recommendations
- Add explicit statements clarifying that the agent registry and related features are platform-agnostic, or specify supported platforms.
- Provide examples or references for registering and managing agents using both Windows and Linux environments, if applicable.
- If any CLI or scripting is involved in agent registration or management, include both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Mention any platform-specific prerequisites or considerations to ensure Linux users are equally informed.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-web-application-firewall.md
...tive-directory-b2c/partner-web-application-firewall.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only Azure Portal (GUI) instructions and does not include any command-line examples. There are no explicit Windows or PowerShell examples, nor are Windows-specific tools mentioned. However, there is a lack of parity for Linux users, as no CLI (Azure CLI, Bash, or cross-platform scripting) examples are provided, which are commonly used on Linux and macOS. This omission can disadvantage Linux users who prefer or require command-line automation.
Recommendations
- Add Azure CLI examples for all major steps (e.g., creating a WAF policy, associating with Front Door, enabling logging, switching modes).
- Where possible, provide both Portal (GUI) and CLI instructions side-by-side.
- Explicitly mention that all steps can be performed using Azure CLI or PowerShell, and provide links to relevant cross-platform documentation.
- Ensure that any scripts or automation snippets are provided in Bash/Azure CLI (cross-platform) as well as PowerShell if needed.
- Clarify that the Azure CLI is available on Windows, Linux, and macOS, and provide installation instructions if appropriate.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/inject-vnet-v2.md
...cs/blob/main/articles/api-management/inject-vnet-v2.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides instructions for updating the hosts file for DNS testing, mentioning the Windows path (%SystemDrive%\drivers\etc\hosts) before the Linux/macOS equivalent (/etc/hosts). No PowerShell-heavy examples or exclusive use of Windows tools are present, and Linux is acknowledged, but the ordering suggests a mild Windows-first bias.
Recommendations
- List Linux/macOS hosts file location before or alongside the Windows path to avoid implicit prioritization.
- Provide explicit examples for both Windows and Linux/macOS when referencing file paths or commands.
- Consider including screenshots or step-by-step instructions for both platforms if relevant.
- Review other sections for similar ordering or tool references to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-connect-to-azure-storage.md
...cles/app-service/configure-connect-to-azure-storage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows examples and instructions before Linux equivalents, as seen in the order of the code pivots. There is no explicit Linux bias, but the structure prioritizes Windows scenarios.
Recommendations
- Present Linux and Windows pivots in parallel or randomize their order to avoid implicit prioritization.
- Add a short introductory note clarifying that both Windows and Linux are equally supported.
- Ensure that Linux examples are as detailed and accessible as Windows examples.
- Consider starting with a neutral overview or a platform-agnostic section before splitting into OS-specific instructions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/build-settings-azure-portal-2.md
...al-nodejs-mongodb-app/build-settings-azure-portal-2.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides instructions for entering a setting using a generic 'dialog', but does not specify or provide examples for Linux environments, CLI usage, or platform-specific differences. There is no explicit Windows bias, but the lack of Linux-specific guidance may disadvantage Linux users.
Recommendations
- Add instructions or examples for setting SCM_DO_BUILD_DURING_DEPLOYMENT using the Azure CLI or in Linux environments.
- Clarify whether the 'dialog' refers to a cross-platform UI or a Windows-specific interface.
- Include parity examples for both Windows and Linux users, such as command-line steps for each.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-azure-portal-3.md
...-nodejs-mongodb-app/deploy-local-git-azure-portal-3.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate how to set up a Git remote on either Windows or Linux. This omission can lead to implicit bias if future steps only cover Windows or PowerShell workflows, or if Linux users are left without guidance.
Recommendations
- Add explicit instructions and examples for setting up a Git remote on both Windows (using PowerShell or Command Prompt) and Linux (using Bash).
- Ensure that any future steps include both Windows and Linux command-line examples side by side.
- Mention common tools for both platforms (e.g., Git Bash for Windows, Terminal for Linux) to help users identify the appropriate workflow.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-change-site-root-1.md
...orial-php-mysql-app/azure-portal-change-site-root-1.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides instructions without specifying platform-specific steps or examples. There is no mention of Windows or Linux tools, but the absence of any Linux-specific guidance or examples may leave Linux users uncertain about platform differences or requirements.
Recommendations
- Explicitly state whether the instructions apply equally to both Windows and Linux App Service plans.
- If there are platform-specific differences in the Configuration or General settings tabs, provide separate guidance or screenshots for Linux and Windows.
- Add a note clarifying any features or settings that behave differently on Linux versus Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-local-git-azure-portal-3.md
...thon-postgresql-app/deploy-local-git-azure-portal-3.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation references copying the Git Clone URI for later use but does not provide any platform-specific instructions or examples. However, there is an implicit bias due to the absence of Linux-specific guidance or examples, such as command-line instructions for setting up a Git remote on Linux or macOS.
Recommendations
- Add explicit examples for setting up a Git remote using Linux/macOS command-line tools (e.g., git remote add origin <Git Clone Uri>).
- Ensure parity by including both Windows (PowerShell, CMD) and Linux/macOS (bash, zsh) instructions where relevant.
- Clarify that the instructions apply to all platforms, or provide links to platform-specific setup guides.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/ip-address-change-inbound.md
...main/articles/app-service/ip-address-change-inbound.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it implicitly assumes users interact with the Azure portal via a web browser. There are no Windows-specific tools or PowerShell commands mentioned, nor are there Linux equivalents. However, the absence of any CLI-based instructions (such as Azure CLI or Bash examples) means Linux users are not given parity with potential Windows users who might expect PowerShell or GUI instructions.
Recommendations
- Add Azure CLI examples for finding the inbound IP address, which can be run on Linux, macOS, or Windows.
- Explicitly mention that the steps can be performed from any OS via the web portal, or provide platform-agnostic alternatives.
- If PowerShell instructions are added in the future, ensure equivalent Bash/Azure CLI examples are included for Linux users.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-use-service-config-file.md
...laywright-workspaces/how-to-use-service-config-file.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation shows a subtle Windows bias in its configuration examples: in both the TypeScript and C# code samples, the operating system is set to Windows (ServiceOS.WINDOWS and OSPlatform.Windows) in the example code, even though the default value is Linux. The Windows option is listed before Linux in the available options, and the example code uses Windows as the value, which may suggest a preference or prioritization of Windows over Linux. However, Linux is supported and documented, and the default is Linux, so the bias is not strong but present in example ordering and emphasis.
Recommendations
- Provide example code using Linux as the OS value, or alternate between Windows and Linux in examples to show parity.
- List Linux before Windows in the available options, especially since Linux is the default.
- Add a note explicitly stating that both Windows and Linux are equally supported and that Linux is the default/recommended for most users.
- Ensure that any platform-specific instructions or troubleshooting steps are provided for both Windows and Linux environments.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-components.md
.../application-gateway/application-gateway-components.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page lists Azure PowerShell as the first option for creating an Application Gateway, before mentioning Azure CLI. This ordering may suggest a Windows-centric bias, as PowerShell is traditionally associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux and macOS. No explicit Linux-only examples or tools are missing, but the ordering could imply preference.
Recommendations
- List Azure CLI before Azure PowerShell when presenting cross-platform instructions, as CLI is natively supported on Linux, macOS, and Windows.
- Explicitly mention that both Azure CLI and PowerShell are available on all major platforms, and provide parity in examples for both.
- Consider adding examples or links for ARM templates or Terraform, which are platform-agnostic and popular in Linux environments.
- Review other documentation pages linked from this one to ensure Linux parity in walkthroughs and examples.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-upgrade.md
...cs/blob/main/articles/automanage/automanage-upgrade.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any OS-specific examples, commands, or instructions. However, it implicitly assumes a generic VM management workflow without mentioning or demonstrating Linux-specific tools, commands, or considerations. There are no references to Windows-specific tools either, but the lack of Linux parity (e.g., shell commands, Linux onboarding nuances) may leave Linux users underserved.
Recommendations
- Add explicit instructions or examples for both Windows and Linux VMs, including any differences in the upgrade process.
- Include sample commands for Linux environments (e.g., Bash/CLI) where relevant, especially for automation or scripting.
- Clarify if there are OS-specific prerequisites, limitations, or behaviors during the upgrade process.
- Mention any Linux-specific tools or patterns (such as cloud-init, systemd, or relevant Azure Linux VM extensions) if applicable.
- Ensure screenshots and UI references are representative of both Windows and Linux VM management experiences.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/move-automanaged-vms.md
.../blob/main/articles/automanage/move-automanaged-vms.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it references UI actions (e.g., 'Automanage blade') without mentioning CLI or automation options. There are no examples for Linux users, such as using Azure CLI, Bash, or Linux tooling, nor is there mention of Powershell or Windows-specific tools. However, the lack of Linux/CLI examples may disadvantage users who prefer or require non-Windows workflows.
Recommendations
- Add instructions for performing the same actions using Azure CLI, which is cross-platform and commonly used on Linux.
- Include examples or references for automating the process via scripts (Bash, Powershell), making it clear that both Windows and Linux users are supported.
- Explicitly mention that the process can be performed on any platform, and provide parity in documentation for both GUI and CLI workflows.
- If Powershell or Windows tools are referenced in related articles, ensure Linux equivalents are also mentioned or linked.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/includes/automation-dsc-linux-retirement-announcement.md
...cludes/automation-dsc-linux-retirement-announcement.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page mentions the retirement of Azure Automation DSC for Linux but does not provide any examples, guidance, or alternatives for Linux users. The focus is solely on the announcement, with no parity for Linux usage or migration steps, which may leave Linux users without clear direction.
Recommendations
- Include migration guidance specifically for Linux users, such as steps to transition to the guest configuration feature of Azure Policy.
- Provide Linux-specific examples or references to equivalent tools and workflows.
- Ensure that documentation updates address the needs of both Windows and Linux audiences, especially when announcing feature retirements.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/automation-region-dns-records.md
...les/automation/how-to/automation-region-dns-records.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is largely neutral and platform-agnostic, focusing on DNS records and Azure Automation configuration. However, there is a subtle Windows-first bias in the instructions for obtaining the Automation Account ID, which reference the Azure portal UI and do not mention CLI alternatives (such as Azure CLI or PowerShell for Windows, nor Bash for Linux). There are no explicit PowerShell-heavy examples, Windows tools, or missing Linux examples, but the lack of Linux CLI instructions may disadvantage Linux users.
Recommendations
- Add instructions for obtaining the Automation Account ID using Azure CLI (cross-platform) and Bash commands for Linux users.
- Where UI steps are described, provide equivalent command-line alternatives for both Windows (PowerShell) and Linux (Bash/Azure CLI).
- Explicitly mention that all DNS records and configuration steps apply equally to both Windows and Linux Hybrid Runbook Workers, unless there are platform-specific caveats.
- Ensure troubleshooting and next steps documentation includes links or notes relevant to Linux environments, not just Windows.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/feature-management-overview.md
...azure-app-configuration/feature-management-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page lists .NET and ASP.NET Core libraries first in all tables and sections, which are traditionally associated with Windows development. No explicit Windows-only tools or PowerShell examples are present, and Linux is not mentioned at all. However, the ordering and focus on .NET/ASP.NET Core may subtly prioritize Windows-centric frameworks over cross-platform or Linux-first technologies.
Recommendations
- Explicitly mention the cross-platform nature of .NET Core and ASP.NET Core, and clarify that these libraries are supported on Linux and macOS as well as Windows.
- Rotate or randomize the order of frameworks in tables, or group them by language family rather than by traditional Windows-first frameworks.
- Add a note or section highlighting Linux compatibility and any Linux-specific considerations for each library.
- Where possible, provide examples or references for running the libraries on Linux (e.g., using .NET on Ubuntu, Java on CentOS, etc.).
- Ensure that documentation does not implicitly suggest Windows is the default or primary platform by always listing Windows-associated frameworks first.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/how-to-targeting-filter-python.md
...re-app-configuration/how-to-targeting-filter-python.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows and macOS/Linux instructions for setting up a Python virtual environment and setting environment variables. However, in both cases, the Windows instructions are presented first, followed by macOS/Linux. There are no Linux-specific examples or tools missing, and parity is maintained in the commands provided. No exclusive use of Windows tools or PowerShell is present, but the order of presentation consistently favors Windows.
Recommendations
- Alternate the order of platform instructions (e.g., show Linux/macOS first in some sections) to avoid implicit prioritization of Windows.
- Consider grouping platform-specific instructions under clear headings, so users can quickly find their OS without perceiving bias.
- Explicitly mention that all platforms are equally supported, and ensure that Linux/macOS users feel their workflows are first-class.
- Where possible, provide combined or platform-agnostic commands (e.g., using `python -m venv venv` and then describing activation for each OS in a table or side-by-side format).
Azure Cache For Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/quickstart-create-redis.md
...icles/azure-cache-for-redis/quickstart-create-redis.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page only demonstrates how to create an Azure Cache for Redis instance using the Azure portal, without providing any command-line examples. There are no explicit Windows or Linux command-line instructions, but the absence of CLI (Azure CLI, Bash, or PowerShell) examples means Linux users do not see parity with Windows users who might expect PowerShell or portal instructions.
Recommendations
- Add Azure CLI examples for creating a Redis instance, which can be run on both Linux and Windows.
- If providing PowerShell examples, ensure Bash equivalents are also included.
- Explicitly mention that the Azure portal instructions are platform-agnostic, or provide links to platform-specific instructions.
- Include a section or links for automating Redis instance creation via CLI for Linux users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-javascript.md
.../azure-app-configuration/howto-telemetry-javascript.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions in the order: Windows CMD, PowerShell, then macOS/Linux. This prioritizes Windows tools and patterns before Linux equivalents, which may suggest a subtle Windows-first bias. However, all platforms are ultimately covered with appropriate examples.
Recommendations
- Present environment variable setup instructions for all platforms in parallel (e.g., a table or side-by-side code blocks) rather than listing Windows first.
- Rotate the order of platform instructions or start with the platform most relevant to the target audience.
- Explicitly state that the instructions apply equally to Windows, macOS, and Linux to reinforce cross-platform parity.
- Where possible, use platform-agnostic language and tools in introductory explanations before diving into platform-specific commands.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-targetingfilter-aspnet-core.md
...app-configuration/howto-targetingfilter-aspnet-core.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only cross-platform .NET CLI commands and code samples, but does not include any platform-specific instructions or examples. However, it omits any explicit mention of Linux or macOS environments, and does not address platform-specific considerations (such as file paths, environment variables, or shell differences). There are no Windows-only tools or PowerShell commands, but the lack of explicit Linux/macOS parity or troubleshooting guidance may disadvantage non-Windows users.
Recommendations
- Explicitly state that all dotnet CLI commands work on Windows, Linux, and macOS.
- Add notes or examples for common Linux/macOS shell environments (e.g., bash/zsh), especially for commands involving file paths or environment variables.
- Mention where files (such as user secrets) are stored on Linux/macOS, as paths differ from Windows.
- Include troubleshooting tips for Linux/macOS users, such as permissions or .NET SDK installation guidance.
- If screenshots or UI references are shown, provide Linux/macOS equivalents where relevant.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-dotnet-core-app.md
.../azure-app-configuration/quickstart-dotnet-core-app.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally presents Windows command-line instructions (cmd and PowerShell) before Linux/macOS equivalents when setting environment variables. However, all major steps include Linux/macOS commands, and the .NET CLI is emphasized as cross-platform. There are no missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present Linux/macOS commands before or alongside Windows commands to avoid implicit prioritization of Windows.
- Explicitly state that all steps are cross-platform at the beginning of relevant sections.
- Where possible, use generic or platform-agnostic instructions first, then provide platform-specific notes.
- Ensure screenshots and terminal output examples are not exclusively from Windows environments.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md
...icles/azure-app-configuration/quickstart-go-web-app.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (Command Prompt and PowerShell) before macOS/Linux, but does include equivalent Linux/macOS commands. There are no exclusive Windows tools or missing Linux examples, and the Go application instructions are cross-platform.
Recommendations
- Present macOS/Linux instructions before or alongside Windows instructions to avoid implicit prioritization.
- Consider using tabbed or parallel layouts for OS-specific instructions to reinforce parity.
- Explicitly state that all Go commands and code samples are cross-platform.
- Where possible, use OS-agnostic language (e.g., 'your terminal') before listing OS-specific commands.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0003.md
...tions/errors-diagnostics/diagnostic-events/azfd0003.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or commands, but it also omits any troubleshooting steps or examples for both Windows and Linux. This lack of parity is a subtle bias, as users on Linux (or any OS) are not given guidance or examples relevant to their environment.
Recommendations
- Add explicit troubleshooting steps or examples for both Windows (e.g., using PowerShell or Azure CLI on Windows) and Linux (e.g., using Bash or Azure CLI on Linux).
- Include sample commands for checking or updating the AzureWebJobsStorage connection string on both platforms.
- Mention platform-agnostic tools (such as Azure CLI or Azure Portal) and clarify that these can be used on any OS.
- If providing scripts or commands, ensure both Windows and Linux variants are shown side by side.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0011.md
...tions/errors-diagnostics/diagnostic-events/azfd0011.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it references 'deployment scripts' and 'application settings' without clarifying how these are set on different platforms. There are no explicit Windows or PowerShell examples, but there is also no mention of Linux, Bash, or cross-platform tooling. This absence may lead to confusion for Linux users who may not know how to set these values outside of the Azure Portal or Windows-centric tools.
Recommendations
- Add explicit examples for setting FUNCTIONS_WORKER_RUNTIME using both Windows (PowerShell, CMD) and Linux (Bash, CLI) environments.
- Clarify how to set application settings via Azure CLI and in deployment scripts for both Windows and Linux.
- Include links or references to platform-specific guides for managing Azure Functions settings.
- Ensure parity in instructions and examples for both Windows and Linux users throughout the documentation.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/flex-consumption-site-updates.md
...icles/azure-functions/flex-consumption-site-updates.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page does not display overt Windows bias in terms of examples, tools, or terminology. However, it lacks explicit Linux-specific examples or references, and does not mention platform-specific deployment or monitoring patterns. All configuration examples use platform-neutral infrastructure-as-code tools (Bicep, ARM templates), and monitoring is described via Application Insights and KQL, which are cross-platform Azure services. No Windows-specific tools (e.g., PowerShell, CMD) or terminology are present, but there is also no mention of Linux command-line tools, shell scripts, or platform-specific deployment nuances.
Recommendations
- Add explicit notes clarifying that the described strategies and configuration steps apply equally to both Windows and Linux-based Azure Functions apps.
- Include Linux-specific deployment and monitoring examples (e.g., using Azure CLI in Bash, or shell scripting for automation).
- Mention any platform-specific differences in behavior, if applicable, such as nuances in instance lifecycle or logging between Windows and Linux hosts.
- Provide sample troubleshooting steps or log access instructions for both Windows and Linux environments.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-documentdb-input.md
...azure-functions/functions-bindings-documentdb-input.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page provides only C# code examples and configuration guidance for Azure Functions using DocumentDB input binding. There are no references to Windows-specific tools or patterns, nor is there explicit mention of Windows or Powershell. However, the documentation lacks any Linux-specific examples, CLI commands, or guidance for non-Windows environments. All examples assume the use of Visual Studio/.NET, which is more common on Windows, and there is no mention of cross-platform development environments or Linux-specific instructions.
Recommendations
- Add examples or guidance for using Azure Functions with DocumentDB input binding in Linux environments, such as using the Azure Functions Core Tools on Linux.
- Include CLI-based setup instructions (e.g., using Azure CLI or Bash scripts) alongside or in place of Visual Studio-centric workflows.
- Mention and provide guidance for cross-platform development tools (e.g., VS Code, JetBrains Rider) and how to configure them for this scenario.
- Clarify that the .NET SDK and Azure Functions tools are available on Linux and macOS, and provide any platform-specific prerequisites or troubleshooting tips.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-web-pubsub-output.md
...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides code examples for C# and JavaScript, but omits complete samples for Python and PowerShell, and explicitly notes that Java support is unavailable. There is no evidence of Windows bias such as PowerShell-heavy examples, Windows-first ordering, or exclusive mention of Windows tools. However, the absence of Linux-specific examples or parity for Python and PowerShell may disadvantage users on Linux platforms.
Recommendations
- Add complete Python and PowerShell code samples, ensuring they work on both Windows and Linux environments.
- Include explicit notes or examples for running Azure Functions and Web PubSub bindings on Linux (e.g., using Azure Functions Core Tools on Linux, Docker, or WSL).
- Ensure troubleshooting and setup instructions are platform-agnostic or provide Linux-specific guidance where relevant.
- If any tooling or configuration differs between Windows and Linux, document both workflows equally.
Azure Large Instances
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-large-instances/quality-checks.md
.../main/articles/azure-large-instances/quality-checks.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation outlines quality checks for Azure Large Instances but does not provide any OS-specific examples, commands, or tools. However, it also does not mention any Windows- or Linux-specific tools, commands, or patterns. The absence of examples or instructions means Linux users are not directly disadvantaged, but there is a lack of parity in that neither platform is addressed explicitly.
Recommendations
- Provide explicit examples for both Windows (e.g., using PowerShell or Windows-native tools) and Linux (e.g., using Bash, SSH, or Linux-native tools) for each quality check.
- List common commands or scripts for verifying network, compute, and storage configurations on both platforms.
- Include sample outputs or troubleshooting steps for both Windows and Linux environments.
- Clarify if any checks are platform-specific and provide guidance for each supported OS.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-performance-metrics-volumes.md
...iles/azure-netapp-files-performance-metrics-volumes.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally maintains cross-platform neutrality, mentioning both Linux and Windows for tools like FIO and VM sizing. However, in the VM sizing section, the link to Windows VM sizes is presented before the Linux equivalent, indicating a subtle 'windows_first' bias. No examples or instructions are exclusively Windows-based, and Linux is not omitted, but Windows is referenced first in at least one key area.
Recommendations
- Present Linux and Windows references in parallel or alternate the order to avoid implicit prioritization.
- Ensure examples and links for both platforms are provided together, or explicitly state parity.
- Consider adding explicit Linux and Windows command examples for installing and running benchmark tools, if not already present.
- Review other documentation pages linked (e.g., 'Performance benchmarks for Linux') to ensure Linux guidance is equally thorough and discoverable.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/includes/kerberos-other-servers.md
.../azure-netapp-files/includes/kerberos-other-servers.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation mentions Kerberos support but only lists Linux/UNIX directory servers (FreeIPA, OpenLDAP, Red Hat Directory Server) as not supported, without providing any examples or guidance for Linux users. There is no mention of Windows equivalents or examples, but the lack of Linux-specific instructions or alternatives suggests a bias toward environments where these servers are not used (potentially Windows-centric).
Recommendations
- Explicitly mention supported directory servers, including both Windows (e.g., Active Directory) and Linux/UNIX options.
- Provide configuration examples for both Windows and Linux environments.
- Clarify Kerberos support status for Windows Active Directory to ensure Linux users understand the limitations and available alternatives.
- Add guidance or links for Linux users on how to proceed if their directory server is unsupported.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/cross-region-replication-manage-disaster-recovery.md
...s/cross-region-replication-manage-disaster-recovery.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally avoids explicit Windows bias in its main instructions, as it references mounting volumes for both Windows and Linux virtual machines. However, in the mounting steps, the phrase 'Mount or unmount a volume for Windows or Linux virtual machines' consistently lists Windows before Linux, which may subtly reinforce a Windows-first perspective. There are no examples, commands, or tools that are exclusive to Windows or PowerShell, and no Linux examples are missing.
Recommendations
- Alternate the order of 'Windows or Linux' and 'Linux or Windows' when referencing both platforms to avoid implicit prioritization.
- Where possible, provide direct links or inline examples for both Windows and Linux mounting procedures, rather than a single shared link.
- Review related linked documentation to ensure Linux instructions are as detailed and prominent as Windows instructions.
- Consider adding a short section or note explicitly affirming parity and support for both Windows and Linux clients.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/performance-linux-direct-io.md
...cles/azure-netapp-files/performance-linux-direct-io.md
Low Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation is focused on Linux best practices, but it briefly mentions the Windows tool DISKSPD as supporting a similar construct to direct I/O, without providing equivalent detail or examples for Windows. No explicit Windows or PowerShell examples are given, and the primary focus remains on Linux tools and commands. However, the mention of DISKSPD (a Windows tool) in a Linux-focused article may introduce slight bias by referencing a Windows utility without similar Linux context.
Recommendations
- Remove or clarify the mention of DISKSPD unless directly relevant to Linux users.
- If cross-platform context is desired, provide equivalent detail for both Linux and Windows tools, or move Windows-specific content to a separate section or article.
- Ensure all examples and tool references are directly applicable to Linux, or clearly indicate when a tool is platform-specific.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-node-get-started-server.md
...brid-connections-http-requests-node-get-started-server.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation instructs users to run 'npm install hyco-https' from a 'Node command prompt', which is a Windows-specific term and may imply Windows as the default environment. No explicit Linux or cross-platform instructions or examples are provided, but the rest of the content is platform-neutral.
Recommendations
- Replace 'Node command prompt' with 'terminal' or 'command line' to use platform-neutral terminology.
- Add a note clarifying that the instructions apply to all platforms (Windows, Linux, macOS).
- Optionally, provide example commands for both Windows and Linux/macOS if there are any platform-specific differences.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter.md
...b/main/articles/azure-resource-manager/bicep/linter.md
Low Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation page mentions Visual Studio Code and the Bicep CLI as the primary tools for using the Bicep linter. While these tools are cross-platform, the page references the linter rule 'use-recent-az-powershell-version', which is specific to Windows and PowerShell environments. No explicit Linux or bash examples, nor mentions of Linux-specific tools or workflows, are provided. The documentation does not show command-line usage examples that clarify compatibility or usage differences between Windows and Linux shells.
Recommendations
- Add explicit examples of using Bicep CLI and linter in Linux environments, such as bash or zsh.
- Clarify that Visual Studio Code and Bicep CLI are cross-platform and provide installation or usage notes for Linux users.
- Include references or examples for Azure CLI usage, which is more common in Linux environments, alongside or instead of PowerShell-specific rules.
- If mentioning PowerShell-specific rules, provide equivalent guidance for bash or other Linux shells where possible.
- Add screenshots or terminal output examples from Linux environments to demonstrate parity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operators-comparison.md
...s/azure-resource-manager/bicep/operators-comparison.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation references 'Azure CLI or Azure PowerShell' for deploying Bicep files, with Azure PowerShell (a Windows-centric tool) mentioned alongside Azure CLI. No explicit Linux-specific tools or shell examples are provided, and the order of mention (CLI first, then PowerShell) is not strongly biased, but the inclusion of PowerShell without mentioning Bash or Linux-native workflows may suggest a mild Windows-first bias. All code examples are in Bicep, which is platform-agnostic.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- If referencing PowerShell, also mention Bash or shell equivalents for Linux users, or clarify that PowerShell Core is available cross-platform.
- Provide example commands for deploying Bicep files using Azure CLI in Bash (Linux/macOS) and PowerShell (Windows), or link to platform-specific deployment guides.
- Ensure that introductory or instructional text does not implicitly prioritize Windows tools or workflows over Linux equivalents.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/outputs.md
.../main/articles/azure-resource-manager/bicep/outputs.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents both Azure PowerShell (commonly used on Windows) and Azure CLI examples for retrieving output values, but the PowerShell example is listed first. No other Windows-specific tools, patterns, or examples are present, and Linux parity is generally maintained elsewhere.
Recommendations
- List Azure CLI examples before Azure PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux and macOS.
- Explicitly mention that both Azure CLI and Azure PowerShell are available on all major platforms, but CLI is often preferred for Linux/macOS users.
- Consider providing Bash or shell scripting examples where relevant, especially for automation scenarios.
- Review other documentation pages for consistent ordering and parity between Windows and Linux tooling.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/resource-declaration.md
...s/azure-resource-manager/bicep/resource-declaration.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for determining supported resource locations, but the PowerShell example is presented first. There are no Linux-specific tools or shell examples (e.g., Bash), but Azure CLI is cross-platform. No exclusive Windows tools or patterns are used, and no examples are missing for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though available cross-platform).
- Where possible, add Bash shell examples for common tasks, especially for scripting scenarios.
- Ensure that any references to tooling or workflows do not assume a Windows environment by default.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/tutorial-get-started-with-custom-providers.md
...roviders/tutorial-get-started-with-custom-providers.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any OS-specific examples or instructions, but it also does not mention or demonstrate Linux tools, shell commands, or patterns. There is a lack of explicit parity for Linux users, as no examples or references are given for Linux environments, even though Azure CLI and REST APIs are cross-platform.
Recommendations
- Add explicit examples using Bash or other Linux shells when demonstrating command-line interactions.
- Mention that Azure CLI and REST API instructions are cross-platform and provide sample commands for both Windows (PowerShell/CMD) and Linux (Bash).
- Where relevant, include notes or tips for Linux users, such as authentication methods, environment setup, or script execution differences.
- Ensure that any referenced scripts or automation steps are shown in both PowerShell and Bash formats.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/includes/app-service-certificates.md
...gement/relocation/includes/app-service-certificates.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or commands, but it also omits any mention of Linux or cross-platform tools for certificate export/import. There is no explicit Windows bias, but the lack of Linux-specific guidance or examples may leave Linux users without clear instructions.
Recommendations
- Add explicit examples for exporting and importing certificates using cross-platform tools such as OpenSSL.
- Include command-line instructions for both Windows (e.g., PowerShell) and Linux (e.g., Bash) environments where relevant.
- Mention common Linux certificate management patterns and tools to ensure parity.
- Clarify that the export/import process can be performed on any supported OS, and link to platform-agnostic guides where possible.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resource-groups-portal.md
...ce-manager/management/manage-resource-groups-portal.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation exclusively provides instructions and screenshots for managing Azure resource groups via the Azure portal, with no mention of command-line tools or scripts. There are no examples for Linux users (e.g., Azure CLI, Bash), nor for Windows users (e.g., PowerShell). However, the absence of Linux-oriented command-line examples (such as Azure CLI) is a notable gap, as these are commonly used on Linux and cross-platform environments.
Recommendations
- Add Azure CLI examples for each major operation (create, list, delete, lock, tag resource groups) alongside the portal instructions. Azure CLI is cross-platform and widely used on Linux.
- If including PowerShell examples, ensure Azure CLI examples are presented first or side-by-side to avoid Windows-first bias.
- Explicitly mention that the Azure portal is platform-agnostic, but provide links or sections for users who prefer command-line tools (especially Linux users).
- Include a section comparing different management methods (Portal, Azure CLI, PowerShell) and link to relevant documentation for each.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resource-groups-python.md
...ce-manager/management/manage-resource-groups-python.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows, Linux, and macOS, but presents the Windows instructions first, followed by Linux and macOS. There is no exclusive use of Windows tools or missing Linux examples; parity is maintained in the examples and CLI usage. However, the ordering of instructions may subtly prioritize Windows users.
Recommendations
- Present environment setup instructions in a neutral or alphabetical order (e.g., Linux, macOS, Windows) to avoid implicit prioritization.
- Explicitly state that all platforms are equally supported at the beginning of the prerequisites section.
- Ensure that editor-specific notes (e.g., Visual Studio restart) are balanced with equivalent notes for popular Linux/macOS editors (e.g., VS Code, PyCharm).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-resources-portal.md
...re-resource-manager/management/tag-resources-portal.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation exclusively covers tagging resources using the Azure portal UI, which is platform-agnostic. However, it does not mention or provide examples for command-line methods (such as Azure CLI, PowerShell, or Bash scripting), which are often important for Linux users. The absence of CLI examples or references may disadvantage Linux users who prefer or require non-GUI workflows.
Recommendations
- Add a 'Command-line alternatives' section with examples using Azure CLI (az tag commands), which are cross-platform and widely used on Linux.
- If mentioning PowerShell, ensure Azure CLI examples are given equal or greater prominence, and provide Bash scripting examples where relevant.
- Reference documentation for both Azure CLI and PowerShell for tagging resources, making it clear that both are supported and linking to their respective guides.
- Clarify that the Azure portal is accessible from any OS, but that automation and scripting can be achieved via CLI tools on Linux, macOS, and Windows.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-resources-python.md
...re-resource-manager/management/tag-resources-python.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows, Linux, and macOS, but lists Windows instructions first and offers more detail for Windows (including both 'setx' and 'set', and a Visual Studio restart note). Linux and macOS instructions are present and correct, but are listed after Windows and are slightly less detailed regarding editor restart requirements.
Recommendations
- Present environment setup instructions in a neutral order (e.g., alphabetical: Linux, macOS, Windows) or group them together to avoid implying priority.
- Ensure parity in detail for all platforms (e.g., mention restarting editors for Linux/macOS as well, not just Windows/Visual Studio).
- If providing editor-specific notes (like Visual Studio), consider including equivalents for common Linux/macOS editors (e.g., VS Code, PyCharm).
- Consider a single cross-platform table or section for environment variable setup, with platform-specific commands clearly labeled but not prioritized.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-resources.md
...les/azure-resource-manager/templates/copy-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions both Azure PowerShell and Azure CLI when discussing version requirements for supporting zero-count copy loops, but lists PowerShell before CLI. There are no explicit Linux or cross-platform shell examples (e.g., Bash), and no mention of Linux-specific tools or patterns. However, the bias is minimal, as both CLI and PowerShell are referenced, and the examples are all in ARM template JSON, which is platform-agnostic.
Recommendations
- List Azure CLI before Azure PowerShell when referencing cross-platform tools, or mention both together as 'Azure CLI or PowerShell' to avoid implying a Windows-first workflow.
- Explicitly state that Azure CLI is available on Linux, macOS, and Windows, reinforcing cross-platform support.
- Where possible, add example deployment commands for both Azure CLI (e.g., 'az deployment group create ...') and PowerShell ('New-AzResourceGroupDeployment ...'), showing parity.
- If referencing shell commands, provide both Bash and PowerShell variants, or clarify that the instructions apply equally to all supported platforms.
- Consider a note or section highlighting cross-platform compatibility for ARM/Bicep deployments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/resource-location.md
.../azure-resource-manager/templates/resource-location.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for retrieving resource locations, but the PowerShell (Windows-centric) example is listed before the Azure CLI example. No explicit Linux or Bash-specific examples are provided, but the CLI example is cross-platform. There is a slight 'windows_first' bias in the ordering of examples.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples across documentation pages, or explicitly state that Azure CLI commands work on all platforms including Linux and macOS.
- Consider providing Bash-specific examples or notes where relevant, especially for tasks that may differ between platforms.
- Add a brief note clarifying that Azure CLI is available and supported on Windows, Linux, and macOS, to reinforce cross-platform parity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-variables.md
...e-manager/templates/template-tutorial-add-variables.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents deployment instructions for both Azure PowerShell and Azure CLI, but the PowerShell (Windows-centric) example is listed first. There are no Linux-specific shell examples (e.g., Bash), but the Azure CLI example is cross-platform. No exclusive Windows tools or patterns are used, and both tools are referenced in prerequisites. However, the ordering may subtly prioritize Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples across tutorials, or present Azure CLI (which is cross-platform) first to avoid perceived Windows prioritization.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Where possible, provide Bash shell examples for common Linux workflows, especially for tasks like setting variables.
- Clarify in the prerequisites that both Azure PowerShell and Azure CLI are available cross-platform, and link to installation guides for all OSes.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/howto-disable-local-auth.md
...ain/articles/azure-signalr/howto-disable-local-auth.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides instructions for disabling local authentication in Azure SignalR Service using the Azure Portal, ARM templates, and Azure Policy, but does not include any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). There is no explicit Windows bias in the form of Windows/Powershell-specific tools or instructions, but the lack of CLI examples means Linux users do not see parity with GUI or template-based instructions.
Recommendations
- Add Azure CLI examples for disabling local authentication, as Azure CLI is cross-platform and widely used on Linux.
- If relevant, provide Bash script snippets for automating the process.
- Ensure that any command-line instructions are presented in a platform-neutral way, or include both PowerShell and Bash/CLI equivalents if scripting is necessary.
- Explicitly mention that the ARM template method can be deployed using Azure CLI or Azure PowerShell, and provide example commands for both.
Azure Signalr
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-reference-data-plane-rest-api.md
...azure-signalr/signalr-reference-data-plane-rest-api.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples, but it also does not include any Windows- or PowerShell-specific instructions, tools, or patterns. However, there is a lack of parity in that no Linux or cross-platform command-line examples (such as curl, bash, or CLI usage) are provided for interacting with the REST API. All sample references are either generic or point to .NET-based repositories, which may implicitly favor Windows environments but are not explicitly Windows-centric.
Recommendations
- Add explicit examples of making REST API calls using cross-platform tools such as curl or httpie.
- Include sample scripts for both Windows (PowerShell) and Linux/macOS (bash) environments to demonstrate authentication and API usage.
- Clarify that the REST API can be accessed from any platform and provide links or code samples for popular Linux tools.
- If referencing .NET samples, also mention alternative SDKs or libraries available for other platforms/languages.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/tutorial-configure-networking.md
...articles/azure-vmware/tutorial-configure-networking.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation exclusively uses the Azure Portal GUI for all instructions and does not provide any CLI-based examples (such as Azure CLI, PowerShell, or Bash scripts). However, there is no explicit Windows bias in the form of PowerShell commands, Windows tools, or Windows-first ordering. The absence of command-line examples, especially Azure CLI or Bash, can disadvantage Linux users or those who prefer automation.
Recommendations
- Add Azure CLI command examples alongside portal instructions for all major steps (creating virtual networks, gateways, and connections).
- Where possible, provide Bash script snippets for common tasks to support Linux users.
- Explicitly mention that all tasks can be performed using Azure CLI on Linux, macOS, or Windows, and link to relevant Azure CLI documentation.
- If PowerShell examples are ever added, ensure Azure CLI equivalents are always present and shown before or alongside PowerShell.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-secure-network-access-control.md
...zure-web-pubsub/howto-secure-network-access-control.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides configuration instructions only via the Azure Portal (GUI) and Bicep templates, with no command-line examples for either Windows (PowerShell, CMD) or Linux (Bash, CLI). However, the absence of Linux-oriented examples (such as Azure CLI commands or Bash scripts) means users on Linux lack parity with Windows users, who might be more familiar with GUI or Bicep workflows.
Recommendations
- Add Azure CLI (az) command examples for each configuration task (public network access, default action, request type rules, IP rules), as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that Bicep templates can be deployed from any OS, but provide instructions for deploying them using Azure CLI (az deployment group create ...) on Linux.
- Where screenshots are shown for the portal, consider including terminal output or CLI command snippets for parity.
- Clarify that all configuration steps can be performed from Linux environments using Azure CLI, and link to relevant CLI documentation.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/socket-io-serverless-protocol.md
...cles/azure-web-pubsub/socket-io-serverless-protocol.md
Low Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation page demonstrates a mild Windows bias by referencing the Azure CLI for obtaining the AccessKey, which is most commonly used and supported on Windows. No Linux-specific tools or shell examples are provided, and there is no mention of Linux command-line alternatives or parity. However, the page does not include PowerShell-specific examples, nor does it prioritize Windows concepts or tools elsewhere. All code samples are either HTTP requests or JavaScript, which are cross-platform.
Recommendations
- Explicitly mention that the Azure CLI is cross-platform and available on Linux and macOS, not just Windows.
- Provide example commands for obtaining the AccessKey using Bash or other Linux shells, if relevant.
- Add a note or section highlighting Linux compatibility and any platform-specific considerations for authentication or tooling.
- If there are any platform-specific differences in using the Azure CLI or other tools, document them for both Windows and Linux users.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-serverless-static-web-app.md
...azure-web-pubsub/tutorial-serverless-static-web-app.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation exclusively uses Azure CLI commands and does not provide any Windows-specific tools or PowerShell examples. However, it does not explicitly address Linux or macOS users, nor does it mention or show shell differences, environment variable syntax differences, or potential platform-specific issues. The CLI commands provided are generally cross-platform, but the documentation assumes a generic shell environment and does not clarify or provide parity guidance for Linux/macOS users.
Recommendations
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, and mention any prerequisites or differences (e.g., how to set environment variables in different shells).
- Provide alternative syntax for setting environment variables (e.g., 'export VAR=value' for bash/zsh on Linux/macOS, versus 'set VAR=value' for Windows CMD, or '$env:VAR="value"' for PowerShell).
- Add a note or section clarifying that all commands are cross-platform and provide links to platform-specific Azure CLI installation guides.
- If any step is known to behave differently on Linux/macOS (such as file paths or authentication flows), call this out explicitly.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql-flex-use-rest-api-create-update-policy.md
...base-postgresql-flex-use-rest-api-create-update-policy.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
Summary
The documentation page exhibits mild Windows bias by referencing the 'default PowerShell object' for PostgreSQL Flexible servers when describing backup scheduling and retention. No Linux-specific tools, shell commands, or cross-platform CLI examples are provided. All examples are REST API and JSON-based, which are platform-neutral, but the only tooling reference is to PowerShell, which is primarily a Windows technology (even though PowerShell Core is cross-platform, it is still most commonly associated with Windows environments).
Recommendations
- Replace or supplement the mention of 'default PowerShell object' with references to Azure CLI, Bash scripts, or other Linux-native tools for managing backup policies.
- Provide example commands for creating backup policies using Azure CLI or curl, which are commonly used on Linux systems.
- Clarify that the REST API and JSON examples are platform-agnostic and can be used from any operating system.
- If mentioning PowerShell, also mention cross-platform alternatives and provide equivalent examples for Linux users.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-policy-supported-skus.md
.../articles/backup/backup-azure-policy-supported-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation lists supported VM SKUs for Azure Backup Policy, and presents all Windows-based SKUs first in a long, detailed section, followed by a much shorter section for Linux distributions. There are many more Windows SKUs listed, with detailed breakdowns, while Linux SKUs are grouped and less granular. No examples, tools, or patterns are mentioned, but the ordering and detail level show a clear Windows-first bias.
Recommendations
- Reorder the table or provide separate tables for Windows and Linux SKUs to give equal prominence.
- Expand the Linux section to include more details, such as specific image SKUs, variants, and supported features.
- Add clarifying notes about Linux support parity, including any limitations or differences compared to Windows.
- If possible, provide links or references to Linux-specific backup documentation or troubleshooting guides.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/disk-backup-troubleshoot.md
.../blob/main/articles/backup/disk-backup-troubleshoot.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any OS-specific examples, commands, or troubleshooting steps. However, it also does not include any Windows- or PowerShell-specific instructions, nor does it reference Windows tools or patterns. The absence of both Windows and Linux examples means Linux users are not disadvantaged compared to Windows users, but there is a lack of parity in that neither is addressed. The documentation could be improved by including cross-platform command-line examples (e.g., Azure CLI, PowerShell) for common troubleshooting actions.
Recommendations
- Add Azure CLI examples for common troubleshooting steps, as Azure CLI is cross-platform and widely used on Linux.
- If relevant, include PowerShell examples, but ensure they are presented alongside Azure CLI or Bash equivalents.
- Explicitly mention that the troubleshooting steps apply to all supported platforms (Windows, Linux, macOS) unless otherwise noted.
- Where permissions or resource group creation is discussed, provide sample commands for both Azure CLI and PowerShell.
- Link to platform-agnostic Azure documentation for resource management tasks.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/account-key-rotation.md
...-docs/blob/main/articles/batch/account-key-rotation.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides instructions for rotating Batch account keys primarily through the Azure portal, without offering any command-line examples. There are no examples using Windows-specific tools (e.g., PowerShell), but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash) or cross-platform automation instructions are provided.
Recommendations
- Add Azure CLI examples for key rotation, which are cross-platform and can be used on both Windows and Linux.
- Include Bash script snippets for automating key rotation, demonstrating how Linux users can perform these tasks.
- If PowerShell examples are added in the future, ensure that equivalent Bash/Azure CLI examples are also provided.
- Explicitly mention that the Azure portal is accessible from any OS, but highlight command-line options for automation and scripting.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-managed-disks.md
...ocs/blob/main/articles/backup/restore-managed-disks.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides instructions for restoring disks to both Windows and Linux VMs, but lists Windows VM instructions before Linux VM instructions. There is no evidence of exclusive use of Windows tools, PowerShell-heavy examples, or missing Linux examples; both platforms are referenced with parity in attach/detach/swap disk instructions via portal links.
Recommendations
- Present instructions for Windows and Linux VMs in parallel or alternate the order to avoid implicit prioritization.
- Explicitly state that the steps apply equally to both Windows and Linux VMs where applicable.
- Ensure that any CLI or script-based examples (referenced in other docs) include both Windows (PowerShell) and Linux (Bash) variants.
- Review linked resources to confirm Linux parity in step-by-step instructions.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-cross-region-restore.md
...lob/main/articles/backup/quick-cross-region-restore.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only Azure Portal (web UI) instructions and does not include any command-line examples. There is no mention of Windows-specific tools or PowerShell, but also no coverage of Linux CLI tools (such as Bash, Azure CLI, or PostgreSQL command-line utilities). This omission may disadvantage Linux users who prefer or require command-line workflows.
Recommendations
- Add Azure CLI examples for enabling Cross Region Restore and restoring PostgreSQL databases, as the Azure CLI is cross-platform and widely used on Linux.
- Include Bash or psql command-line snippets for restoring PostgreSQL databases, where appropriate.
- Explicitly mention that the steps are platform-agnostic if only the portal is supported, or clarify any platform limitations.
- Provide parity by ensuring that any PowerShell or Windows-specific instructions (if added in the future) are matched with equivalent Linux/Bash/CLI instructions.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/threat-detection-overview.md
...blob/main/articles/backup/threat-detection-overview.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation describes threat detection for Azure VM backups with Microsoft Defender for Cloud but does not provide any OS-specific examples or instructions. However, it implicitly assumes a Windows-centric environment by omitting any mention of Linux-specific considerations, tools, or examples, despite Azure VMs commonly running both Windows and Linux. There are no PowerShell or Windows tool references, but the lack of Linux parity in examples or troubleshooting is a subtle form of bias.
Recommendations
- Explicitly state that threat detection supports both Windows and Linux Azure VMs, if applicable.
- Include examples or notes about how threat detection works for Linux VMs, such as any differences in malware detection, configuration, or reporting.
- If there are Linux-specific limitations or requirements (e.g., supported distributions, agent installation), document them clearly.
- Provide troubleshooting steps or status interpretation examples for both Windows and Linux VM scenarios.
- Ensure that related content and tutorials include Linux VM walkthroughs where relevant.
Bastion
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/private-only-deployment.md
.../blob/main/articles/bastion/private-only-deployment.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only Azure Portal (GUI) instructions and does not include any command-line examples. There are no examples using PowerShell, Azure CLI, or any OS-specific tools. However, the absence of Azure CLI (which is cross-platform and commonly used on Linux) examples means Linux users are not fully supported, especially those who prefer or require automation or non-GUI workflows.
Recommendations
- Add Azure CLI examples for all deployment steps, as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are added in the future, ensure Azure CLI equivalents are also provided.
- Explicitly mention that all steps can be performed from any OS via the Azure Portal, but provide command-line alternatives for automation and parity.
- Include a section or links for deploying Bastion using ARM templates or Bicep for advanced, OS-agnostic automation.
Business Process Tracking
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/business-process-tracking/includes/logic-apps-sku-standard.md
...s-process-tracking/includes/logic-apps-sku-standard.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page does not provide any platform-specific examples, but also lacks any mention of Linux or cross-platform considerations. There is no evidence of Windows-specific tools, commands, or examples, but the absence of Linux examples or guidance may indicate a subtle bias by omission.
Recommendations
- Add explicit examples or notes for both Windows and Linux environments where relevant.
- Include cross-platform instructions or highlight platform-agnostic approaches.
- If platform-specific steps are necessary, present Windows and Linux instructions side-by-side.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/private-connectivity.md
...-docs/blob/main/articles/batch/private-connectivity.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only Azure Portal (GUI) instructions for configuring private endpoints with Azure Batch accounts. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts) for either Windows or Linux. However, the absence of any CLI examples means Linux users (who often prefer or require CLI-based automation) are not served. There is also no mention of Linux-specific tools or considerations, nor any explicit Windows bias in the form of PowerShell or Windows tool references.
Recommendations
- Add Azure CLI examples for all major steps (creating private endpoints, configuring DNS zones, migrating DNS zones, etc.), as Azure CLI is cross-platform and widely used on Linux.
- Include Bash script snippets for common automation scenarios.
- If PowerShell examples are added, ensure Azure CLI or Bash equivalents are provided alongside.
- Mention any Linux-specific considerations (e.g., editing /etc/hosts, using dig/nslookup on Linux, DNS resolver configuration).
- Clarify that all steps can be performed from Linux, macOS, or Windows environments using Azure CLI.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/using-the-shell-window.md
...ob/main/articles/cloud-shell/using-the-shell-window.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally maintains cross-platform neutrality, referencing both Bash and PowerShell environments and providing copy/paste shortcuts for Windows, macOS, and Linux. However, in the 'Copy and paste' section, Windows instructions are listed first, which may indicate a subtle 'windows_first' bias. No exclusive use of Windows tools, missing Linux examples, or PowerShell-heavy content was found.
Recommendations
- Alternate the order of platform instructions (e.g., sometimes list Linux or macOS first) to avoid implicit prioritization of Windows.
- Explicitly state that Cloud Shell supports both Bash (Linux) and PowerShell equally in the introduction.
- Where possible, provide parity in examples and screenshots for both Bash and PowerShell environments.
- Ensure that all platform-specific instructions (e.g., keyboard shortcuts) are equally detailed and visible.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/analytics/logs/call-summary-updates-log-schema.md
...epts/analytics/logs/call-summary-updates-log-schema.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page generally avoids explicit platform bias in its instructions and examples. However, there is a subtle Windows-first bias in the sample data: the only explicit OS version shown in the P2P call example is 'Windows 10.0.17763 Arch: x64', and this appears before any other OS examples. Other platforms (Darwin/macOS, Android) only appear later in group call examples. No Linux-specific OS version is shown in any sample data, nor is Linux mentioned in the text or examples. There are no PowerShell-specific instructions or Windows-only tools referenced, but the ordering of OS examples and omission of Linux may give the impression of Windows primacy.
Recommendations
- Add at least one sample call log with a Linux-based 'osVersion' (e.g., 'Linux 5.4.0-104-generic; Arch: x64') to demonstrate Linux support.
- When listing sample data, rotate or randomize the order of OS examples, or explicitly include all major platforms (Windows, macOS, Linux, Android, iOS) in the first set of examples.
- In the 'osVersion' property description, explicitly mention that Linux and other OSes are supported and provide example values.
- Review other documentation pages linked from this one to ensure Linux is represented in instructions and troubleshooting guides.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/call-automation/play-ai-action.md
...on-services/concepts/call-automation/play-ai-action.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples, commands, or tools. However, it references the 'Audio Content Creation tool' for creating WAV files, which is a Microsoft tool that may not be available or easily usable on Linux. There are no explicit instructions or examples for Linux users, nor are alternative Linux-compatible tools mentioned for audio file creation.
Recommendations
- Include examples or recommendations for creating compatible WAV files using common Linux tools (e.g., ffmpeg, sox, Audacity).
- Clarify whether the 'Audio Content Creation tool' is cross-platform or provide Linux alternatives.
- Add a section or note acknowledging how Linux users can prepare audio files for use with Azure Communication Services.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/best-practices-native.md
...on-services/concepts/includes/best-practices-native.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides platform-specific guidance for iOS, Android, and Windows, but does not mention Linux at all. There are no examples, requirements, or instructions for using the Calling Native SDK on Linux platforms, nor is Linux discussed as a supported or unsupported platform. This omission may lead Linux developers to feel excluded or uncertain about SDK compatibility.
Recommendations
- Explicitly state whether Linux is supported or unsupported as a platform for the Calling Native SDK.
- If Linux is supported, add a dedicated section for Linux with minimum requirements, permission configuration, and relevant examples, similar to the iOS, Android, and Windows sections.
- If Linux is not supported, clarify this in the 'Supported platforms' section to avoid ambiguity.
- Where possible, provide parity in examples and troubleshooting steps for Linux users (e.g., how to configure permissions, manage logs, or handle device access on Linux).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/notifications.md
...icles/communication-services/concepts/notifications.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not exhibit explicit Windows bias in terms of command-line examples or tool recommendations. All provided command-line examples use the 'armclient' tool, which is a cross-platform CLI and not specific to Windows or PowerShell. There are no Windows-specific tools, PowerShell scripts, or references to Windows-first patterns. However, there is a lack of explicit Linux/macOS examples or mentions, which may leave Linux users uncertain about platform compatibility or alternative workflows.
Recommendations
- Explicitly state that the 'armclient' tool and Azure portal steps are cross-platform and supported on Windows, Linux, and macOS.
- If there are any platform-specific prerequisites or installation steps for 'armclient', provide links or instructions for all major operating systems.
- Add a note confirming that all command-line instructions are valid on Linux/macOS terminals, or provide alternative commands if any step differs.
- Where screenshots or UI instructions are given, clarify that the Azure portal experience is consistent across platforms and browsers.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/handle-events-with-event-processor.md
.../call-automation/handle-events-with-event-processor.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only C# code examples and does not reference any Windows-specific tools, PowerShell, or Windows-only patterns. However, it lacks any mention of Linux environments, alternative shells, or cross-platform considerations. There are no explicit instructions or examples for Linux users, nor is there guidance on running the code outside of a Windows context.
Recommendations
- Add explicit statements clarifying that the event processor and SDK are cross-platform (if applicable), and can be used on Linux, macOS, and Windows.
- Include Linux-specific instructions or examples, such as running the code on .NET Core in a Linux environment, or deploying the webhook endpoint on a Linux server.
- Mention any platform requirements or differences, if they exist, for hosting the webhook endpoint or running the Azure Communication Services SDK.
- If the code is platform-agnostic, state this clearly to reassure Linux users.
- Provide sample commands for running or deploying the application on Linux (e.g., using dotnet CLI on Ubuntu).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-ai-action-how-to-java.md
...automation/includes/recognize-ai-action-how-to-java.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation demonstrates a mild Windows bias by referencing Windows first in prerequisite links (e.g., resource creation tabs default to 'windows'), but otherwise provides cross-platform Java and Maven instructions that are equally applicable to Linux and macOS. There are no exclusive Windows tools, PowerShell scripts, or missing Linux examples in the main content.
Recommendations
- Ensure that prerequisite links and quickstart guides do not default to 'windows' tabs or provide clear instructions for Linux/macOS users.
- Explicitly mention that all terminal and Maven commands work on Linux, macOS, and Windows.
- Where possible, provide links or notes for Linux/macOS equivalents when referencing platform-specific instructions or UI elements.
- Review tabbed content in linked resources to ensure Linux and macOS parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-js.md
...w-tos/call-automation/includes/play-audio-how-to-js.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation exhibits a mild 'windows_first' bias in the prerequisites section, where links to Azure resource creation include a '?tabs=windows' parameter and reference 'tabs=windows' before any mention of other platforms. However, the rest of the documentation is platform-neutral, focusing on JavaScript and Node.js, which are cross-platform technologies. There are no PowerShell-specific examples, Windows-only tools, or missing Linux equivalents in the main content.
Recommendations
- Update prerequisite links to either default to platform-neutral pages or explicitly provide tabs/links for both Windows and Linux (and macOS) users.
- Ensure that any referenced quickstarts or guides do not default to Windows instructions, or clearly indicate how Linux users can follow along.
- If platform-specific setup is required (e.g., for Node.js installation), provide instructions or links for both Windows and Linux.
- Review all documentation links for platform-specific query parameters and adjust to be inclusive.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/mute-participants-how-to-java.md
...l-automation/includes/mute-participants-how-to-java.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation exhibits a mild 'windows_first' bias by linking to resource creation instructions with a '?tabs=windows' parameter and 'pivots=platform-azp', suggesting Windows as the default or primary platform. However, all code and command-line instructions (Maven, Java, XML) are cross-platform and do not use Windows-specific tools or shell commands. No explicit PowerShell or Windows-only command examples are present, and the instructions are generally applicable to Linux and macOS as well.
Recommendations
- Ensure that links to Azure resource creation guides either default to a neutral or platform-agnostic tab, or explicitly mention and provide Linux/macOS alternatives.
- If platform-specific instructions are necessary, provide Linux/macOS equivalents alongside Windows instructions, or clarify that the steps are cross-platform.
- Audit all quickstart and prerequisite links to avoid defaulting to Windows-specific tabs or pivots.
- Explicitly state in the prerequisites or introduction that the instructions are valid for all major operating systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-python.md
...s/call-automation/includes/play-audio-how-to-python.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation demonstrates a mild Windows bias in the virtual environment activation instructions, where the Windows command is presented first and with more explicit guidance. The prerequisites link also uses a Windows-specific tab by default. However, most of the content is platform-neutral and uses Python code examples that work on both Windows and Linux.
Recommendations
- Present virtual environment activation instructions for Windows and Unix/Linux in parallel, or list Unix/Linux first to balance representation.
- Ensure prerequisite links and quickstarts do not default to Windows tabs or mention Windows before Linux; provide equal visibility for Linux/macOS instructions.
- Explicitly mention that all Python code examples are cross-platform, and note any platform-specific caveats if they exist.
- Where external tools are referenced (e.g., Speech synthesis with Audio Content Creation tool), clarify platform compatibility or provide alternatives if any are Windows-only.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-java.md
...call-automation/includes/play-audio-quickstart-java.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page shows evidence of Windows bias primarily in the prerequisites section, where the link to creating an Azure Communication Services resource uses a Windows-specific tab and query parameter ('tabs=windows'). There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux-specific tools or patterns. However, the rest of the page uses Java and Maven commands, which are cross-platform, and does not provide PowerShell or Windows-only command-line examples.
Recommendations
- Update prerequisite links to use neutral or cross-platform tabs (e.g., avoid '?tabs=windows').
- Explicitly mention that all Maven and Java commands work on Linux, macOS, and Windows.
- Where applicable, provide links or instructions for creating Azure resources using CLI or portal in a way that is platform-agnostic.
- Add a note in the prerequisites clarifying that the steps and tools are supported on Linux, macOS, and Windows.
- Review other linked quickstarts and ensure Linux parity in examples and instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-how-to-python.md
...os/call-automation/includes/recognize-how-to-python.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally provides cross-platform instructions and Python code examples, but there is a minor Windows bias in the 'Prerequisites' and 'Activate your virtual environment' sections. Windows instructions and links are presented before Unix/Linux equivalents, and the resource creation link defaults to a Windows tab. However, Linux activation commands are present, and all code samples are OS-agnostic.
Recommendations
- Present Unix/Linux and Windows instructions side-by-side or in a neutral order, rather than listing Windows first.
- Avoid defaulting resource creation links to Windows tabs; provide a neutral or platform-agnostic default, or clearly indicate both options.
- Where platform-specific commands are required, consider using tabbed content or clear headings for each OS.
- Review all links and references to ensure Linux/macOS users are equally supported and not required to adapt Windows-centric instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-action-quickstart-java.md
...utomation/includes/recognize-action-quickstart-java.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page demonstrates a subtle Windows bias in the prerequisites section, where the link to creating an Azure Communication Services resource uses a Windows-specific tab and pivot by default ('?tabs=windows&pivots=platform-azp'). No explicit Linux or cross-platform instructions are provided, and the documentation does not mention Linux-specific considerations or alternative commands/tools. However, the main quickstart and code samples are platform-neutral (Java/Maven), and do not use Windows-only tools or PowerShell.
Recommendations
- Update prerequisite links to default to a neutral or cross-platform tab/pivot, or explicitly mention Linux/macOS instructions alongside Windows.
- Add a note clarifying that the Java/Maven commands work on Linux, macOS, and Windows, and provide any OS-specific setup tips if relevant.
- Ensure all referenced quickstart/resource creation guides include Linux/macOS steps and screenshots, not just Windows.
- Review other linked documentation for similar Windows-first pivots and update to ensure parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-how-to-js.md
...ow-tos/call-automation/includes/recognize-how-to-js.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page exhibits a mild 'windows_first' bias. In the prerequisites, the link to creating an Azure Communication Services resource includes a 'tabs=windows' parameter, and the only platform-specific mention is for Windows. There are no explicit Linux or macOS instructions or examples, but the rest of the guide uses cross-platform JavaScript/Node.js commands and code samples.
Recommendations
- Update prerequisite links to either be platform-neutral or provide tabs for Windows, Linux, and macOS, ensuring Linux users are equally supported.
- Explicitly mention that the instructions and commands (npm, node) work on Linux and macOS as well as Windows.
- If there are any platform-specific steps (e.g., environment variables, file paths), provide Linux/macOS equivalents alongside Windows.
- Review all quickstart and resource links to ensure they do not default to Windows instructions when Linux options are available.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-android.md
...osed-captions/closed-captions-teams-interop-android.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation shows a subtle Windows bias in the prerequisites section, where resource creation links use the 'windows' tab by default and the URL contains '?tabs=windows'. However, the main technical content is platform-neutral Java code, and there are no explicit Windows-only tools, PowerShell examples, or missing Linux equivalents.
Recommendations
- Update prerequisite links to use platform-neutral or user-detecting tabs, or provide explicit Linux/macOS options alongside Windows.
- Ensure that quickstart and resource creation documentation referenced from this page includes Linux and macOS instructions equally and does not default to Windows.
- Consider adding a note clarifying that the SDK and features are cross-platform, and provide links to Linux/macOS setup guides if available.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-ios.md
...s/closed-captions/closed-captions-teams-interop-ios.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows first in the resource creation link (with '?tabs=windows' in the URL), and by not mentioning or providing parity for Linux or macOS in the prerequisites or resource creation steps. However, all code samples are platform-neutral (Swift/iOS), and there are no explicit Windows-only tools or PowerShell examples.
Recommendations
- Update prerequisite links to either be platform-neutral or provide explicit tabs/sections for Linux and macOS, not just Windows.
- In the resource creation step, mention or link to instructions for Linux and macOS users, ensuring all platforms are equally represented.
- Review all quickstart and reference links to ensure they do not default to Windows and provide parity for Linux/macOS.
- Add a note clarifying that the instructions and features are available cross-platform where applicable, or specify any platform limitations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/includes/chat-az-cli.md
...tion-services/quickstarts/chat/includes/chat-az-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally provides parity between Windows, macOS, and Linux for environment variable setup, with clear tabs for each OS. However, there is a notable Windows-first bias: Windows instructions and links are consistently presented before Linux/macOS equivalents. For example, the Azure CLI installation link points to the Windows-specific page, and in environment variable setup, Windows is always listed first.
Recommendations
- Present OS options in a neutral or rotating order (e.g., Linux, macOS, Windows) rather than always listing Windows first.
- In the prerequisites, provide a general Azure CLI installation link or links for all major OSes, not just Windows.
- Ensure that all examples and instructions are equally detailed for Linux and macOS, and consider highlighting cross-platform commands where possible.
- Where possible, use language that does not assume Windows as the default environment.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-net.md
...ts/identity/includes/access-tokens/access-token-net.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page shows mild Windows bias by listing Windows command-line environments (cmd, PowerShell) before Bash when instructing users to run .NET CLI commands. However, all actual commands shown are cross-platform and there are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples. The instructions and code samples are generally OS-agnostic.
Recommendations
- List Bash (or 'terminal') before Windows environments (cmd, PowerShell) when mentioning command-line usage to avoid implying Windows primacy.
- Explicitly state that all CLI commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider including a short note or section confirming Linux/macOS compatibility for the steps, especially for environment variable usage and .NET SDK installation.
- If any platform-specific issues exist (e.g., environment variable syntax differences), provide examples for both Windows and Linux/macOS.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-net.md
...ity/includes/active-directory/service-principal-net.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page exhibits a mild 'windows_first' bias by listing Windows terminal options (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. All other instructions and code samples are platform-agnostic, relying on .NET Core/SDK and not using Windows-specific tools or patterns. There are no PowerShell-specific commands, nor are there missing Linux examples, but the ordering subtly prioritizes Windows environments.
Recommendations
- When mentioning terminal options, list Bash (or 'Bash or other Unix shells') before or alongside Command Prompt and PowerShell to avoid implying Windows is the default or preferred environment.
- Explicitly state that all commands work cross-platform (Windows, Linux, macOS) to reinforce parity.
- Where possible, provide example output or troubleshooting notes for both Windows and Linux terminals, especially if there are known differences.
- Consider linking to .NET cross-platform documentation or prerequisites for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-call-web.md
...uickstarts/rooms/includes/rooms-quickstart-call-web.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page demonstrates a subtle Windows bias by mentioning the Microsoft Installer (MSI) as the method to install Node.js, which is a Windows-specific installer, without referencing Linux/macOS installation methods. No explicit PowerShell or Windows-only commands are present, and most instructions use cross-platform tools (npm, npx, webpack). However, the installation prerequisite could confuse or exclude Linux/macOS users.
Recommendations
- Mention cross-platform installation options for Node.js, such as using package managers like apt (Linux), brew (macOS), or direct downloads for all platforms.
- Provide links or brief instructions for installing Node.js on Linux and macOS alongside the MSI reference.
- Clarify that all command-line instructions (npm, npx, mkdir, cd) are valid for Windows, Linux, and macOS terminals.
- Avoid referencing platform-specific installers unless alternatives are also provided.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-java.md
...es/quickstarts/rooms/includes/rooms-quickstart-java.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation exhibits a minor 'windows_first' bias in the section instructing users to open a console window, where 'cmd' and 'PowerShell' (Windows shells) are mentioned before 'Bash' (common on Linux/macOS). All other instructions and code samples are cross-platform (Java/Maven), and there are no Windows-specific tools, commands, or exclusive PowerShell examples. No Linux-specific instructions or examples are missing, but the ordering subtly prioritizes Windows environments.
Recommendations
- When listing console environments, use a neutral or alphabetical order (e.g., 'Bash, cmd, or PowerShell') or explicitly state that any terminal (cmd, PowerShell, Bash, Terminal, etc.) can be used.
- Where possible, clarify that all commands are cross-platform and work on Windows, Linux, and macOS.
- If there are any platform-specific steps (e.g., setting environment variables, installing Maven), provide both Windows and Linux/macOS instructions or links.
- Consider adding a note at the start of the 'Set up' section confirming that the instructions are valid for all major operating systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/phone-numbers-az-cli.md
...quickstarts/telephony/includes/phone-numbers-az-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation shows a mild Windows bias by presenting the Windows installation link for Azure CLI first and listing the Windows environment variable instructions before macOS and Linux. However, command-line examples use Azure CLI, which is cross-platform, and Linux/macOS instructions are present.
Recommendations
- Provide a platform-neutral Azure CLI installation link or mention all platforms equally in the prerequisites.
- Rotate or randomize the order of OS tabs (Windows, macOS, Linux) for environment variable setup, or default to a platform-neutral view.
- Explicitly state that all CLI commands work on Windows, macOS, and Linux to reinforce cross-platform parity.
- Where possible, use language that does not imply Windows is the default or primary platform.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-resource-id.md
...ces/quickstarts/voice-video-calling/get-resource-id.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only a screenshot-based method for finding the Azure Resource ID, without any command-line examples. It does not mention or provide instructions for Linux users (e.g., using Azure CLI), nor does it provide PowerShell or Windows-specific instructions, but the absence of Linux/CLI examples may disadvantage non-Windows users.
Recommendations
- Add Azure CLI command-line instructions for finding the Resource ID, which work cross-platform (Windows, Linux, macOS).
- If providing PowerShell examples, ensure equivalent Azure CLI examples are also included.
- Clarify that the Resource ID can be obtained via the Azure Portal (as shown) or via command-line tools, and provide both methods.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/closed-captions/closed-captions-javascript.md
...includes/closed-captions/closed-captions-javascript.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation shows a mild Windows bias in the prerequisites section, where the link to creating an Azure Communication Services resource includes a 'tabs=windows' parameter and the URL suggests a Windows-first or Windows-only quickstart. There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux tools or environments. However, the main content is JavaScript code, which is inherently cross-platform.
Recommendations
- Ensure that prerequisite links and quickstarts include Linux (and macOS) tabs or instructions, not just Windows.
- Remove or generalize the 'tabs=windows' parameter in documentation links, or add equivalent Linux/macOS tabs.
- Explicitly state that the instructions and code samples are cross-platform and can be used on Linux, macOS, and Windows.
- Where platform-specific setup is required (e.g., for SDK installation or environment setup), provide Linux-specific guidance alongside Windows instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/calling-widget/calling-widget-js-tutorial.md
...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation demonstrates a mild 'windows_first' bias by presenting Windows command prompt instructions before macOS equivalents. However, it does provide both Windows and macOS/Linux commands for project setup, and all other instructions (Node, VS Code, running the app) use cross-platform commands. There are no PowerShell-specific examples, exclusive Windows tools, or missing Linux examples.
Recommendations
- Present macOS/Linux commands before or alongside Windows commands to avoid implying Windows is the primary platform.
- Explicitly mention Linux in command examples (e.g., 'For macOS and Linux, use this command:').
- Where possible, use language such as 'terminal' instead of 'command prompt' to be more platform-neutral.
- Ensure that all instructions and troubleshooting steps are validated on Linux, and add Linux-specific notes if any differences exist.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/voice-video-calling/diagnostic-options-tag.md
...utorials/voice-video-calling/diagnostic-options-tag.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page primarily presents telemetry examples and user agent strings where the Windows platform is mentioned first and exclusively (e.g., 'Mozilla/5.0 (Windows NT 10.0; Win64; x64)'). There are no explicit Linux or cross-platform examples, and the only OS context shown is Windows. However, there are no Windows-specific tools, PowerShell commands, or instructions that would further increase the bias.
Recommendations
- Include user agent string examples from Linux and macOS clients to demonstrate cross-platform support.
- Explicitly mention that the SDK and telemetry tagging work on all supported platforms, not just Windows.
- If platform-specific behaviors exist, document them for Linux and macOS as well.
- Add a note or section clarifying that the instructions and examples are applicable regardless of the operating system.
Confidential Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/confidential-computing/confidential-computing-enclaves.md
...fidential-computing/confidential-computing-enclaves.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not mention or highlight any Windows-specific tools, commands, or patterns. However, it lacks explicit examples or guidance for Linux users, which may leave Linux developers uncertain about platform compatibility or required steps.
Recommendations
- Add explicit statements clarifying that SGX development is supported on both Windows and Linux platforms.
- Include links or references to Linux-specific SGX development tools (e.g., Intel SGX SDK for Linux) alongside any Windows equivalents.
- Provide example workflows or commands for both Windows (e.g., Visual Studio, PowerShell) and Linux (e.g., GCC, Bash) environments in the 'Developing for enclaves' section.
- Mention any platform-specific requirements or differences in the development and deployment process for SGX enclaves.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/functions-unified-platform.md
.../articles/container-apps/functions-unified-platform.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples, commands, or tooling references. However, it also does not mention or demonstrate parity for Linux environments, nor does it clarify whether the guidance is cross-platform. The absence of any OS-specific instructions or examples (Windows or Linux) means Linux users may be left uncertain about platform compatibility or required steps.
Recommendations
- Explicitly state that Azure Functions on Azure Container Apps supports both Windows and Linux containers, if applicable.
- Add example workflows or deployment steps for both Windows and Linux environments, including any differences in Dockerfiles, shell commands, or configuration.
- If any platform-specific limitations or requirements exist, document them clearly.
- Include sample commands for both PowerShell (Windows) and Bash (Linux/macOS) where relevant.
- Provide links to platform-specific quickstarts or guides for both Windows and Linux users.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/secure-deployment.md
...blob/main/articles/container-apps/secure-deployment.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page does not provide any OS-specific examples, commands, or tooling references (such as PowerShell, Windows CLI, or Linux shell commands). However, it also does not provide any Linux-specific examples, nor does it mention cross-platform command-line usage or considerations. The guidance is entirely Azure portal- and service-focused, omitting any mention of local development, deployment, or operational tasks that might differ between Windows and Linux environments. This results in a lack of Linux parity in practical, hands-on examples.
Recommendations
- Add cross-platform command-line examples (e.g., Azure CLI commands) for common security tasks, and clarify that these commands work on both Windows and Linux.
- Where relevant, include sample scripts or configuration snippets for both PowerShell (Windows) and Bash (Linux/macOS) to demonstrate parity.
- Explicitly mention that Azure Container Apps supports both Linux and Windows containers, and note any security considerations unique to each platform.
- Provide links to platform-specific guidance (e.g., securing Linux containers, using Linux-based development environments) where appropriate.
- If any operational tasks (such as log collection, secrets management, or network troubleshooting) differ between Windows and Linux, call out those differences and provide examples for both.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/automate/get-usage-details-legacy-customer.md
...-billing/automate/get-usage-details-legacy-customer.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only raw HTTP API request examples and does not include any platform-specific command-line examples. However, it also does not provide any examples of how to use these APIs from common environments (such as PowerShell, Windows Command Prompt, Bash, or curl), which can be a missed opportunity for parity. There is no explicit Windows bias, but the absence of Linux (or cross-platform) command-line examples means Linux users may not have clear guidance.
Recommendations
- Add example commands using cross-platform tools such as curl or HTTPie to demonstrate how to call the API from Linux, macOS, or Windows.
- If including PowerShell examples, ensure equivalent Bash/curl examples are also provided.
- Explicitly mention that the API can be accessed from any platform and provide sample scripts for both Windows and Linux environments.
- Consider adding a section on authenticating and making requests using Azure CLI, which is cross-platform.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/cost-management-error-codes.md
...anagement-billing/costs/cost-management-error-codes.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page provides troubleshooting guidance for Azure Cost Management errors but does not include any platform-specific examples, commands, or references. However, where tooling is mentioned (such as Power BI), only Windows-centric tools are referenced, and there are no examples or guidance for Linux users or alternative open-source tools. No PowerShell, Windows command-line, or Windows-specific patterns are present, but the lack of Linux parity in tooling references constitutes a subtle bias.
Recommendations
- Where Power BI is referenced, mention alternative data analysis tools available on Linux (e.g., Jupyter Notebook, pandas, Grafana) and provide example workflows for Linux users.
- If API usage is discussed, include example API calls using curl or other Linux-native tools, not just portal or Power BI workflows.
- Explicitly state that the troubleshooting steps apply equally to users on Linux, macOS, and Windows, and clarify any platform-specific differences if they exist.
- Provide links to documentation for Linux-compatible Azure management tools (e.g., Azure CLI) and include example commands where relevant.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/configure-autoscaling.md
...in/articles/cyclecloud/how-to/configure-autoscaling.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide explicit Windows or PowerShell examples, nor does it mention Windows-specific tools or patterns. However, it also does not provide any Linux-specific examples or command-line instructions, which may leave Linux users without clear guidance, especially for CLI-based configuration. The documentation is GUI-focused and omits parity for Linux command-line workflows.
Recommendations
- Add Linux command-line examples for configuring autoscaling, such as using shell scripts or CLI commands.
- Mention and provide examples for configuring autoscaling via Linux tools or configuration files, if supported.
- Clarify whether the GUI instructions apply equally to both Windows and Linux environments, or specify any differences.
- Include references to Linux documentation or resources for users who prefer non-GUI workflows.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/disable-autoscaling.md
...main/articles/cyclecloud/how-to/disable-autoscaling.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page does not provide any examples or instructions for either Windows or Linux platforms. However, the absence of Linux-specific guidance or examples, especially given the context of cluster management (which is commonly performed on Linux), suggests a potential bias if only Windows instructions are later provided or implied.
Recommendations
- Ensure that all instructions and examples include both Windows (PowerShell, CMD) and Linux (bash, shell) equivalents.
- Explicitly mention any platform-specific differences in the autoscaling enable/disable process.
- If tools or commands are Windows-specific, provide Linux alternatives or note their absence.
- Add sample commands for disabling/enabling autoscaling using Linux shell commands if applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/airflow-get-ip-airflow-cluster.md
...rticles/data-factory/airflow-get-ip-airflow-cluster.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides instructions and screenshots for retrieving the IP address of a Workflow Orchestration Manager cluster, but does not include any command-line examples or instructions specific to Linux or macOS environments. There are no references to Linux tools, shell commands, or cross-platform CLI usage; all examples are either UI-based or use REST API calls shown in screenshots, which may implicitly assume a Windows-centric workflow (e.g., using Azure Portal or tools commonly accessed from Windows environments).
Recommendations
- Add explicit command-line examples using curl or wget for REST API calls, demonstrating how to retrieve the access token and cluster IP address from Linux/macOS terminals.
- Include sample scripts or commands for both PowerShell (Windows) and Bash (Linux/macOS) to show parity.
- Reference cross-platform tools such as Azure CLI or az rest commands, and provide examples for their usage.
- Clarify that the steps can be performed from any operating system, and provide guidance for users on Linux/macOS where applicable.