App Service
432
Total Pages
240
Linux-Friendly Pages
192
Pages with Bias
44.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2121 issues found
Showing 1576-1600 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-azure-database.md
...les/app-service/tutorial-connect-msi-azure-database.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains good cross-platform parity, primarily using Azure CLI for setup and configuration, which is cross-platform. However, there is a subtle Windows bias in the dev environment setup section: Visual Studio for Windows is presented first and in more detail, while Visual Studio for Mac is noted as lacking integration. PowerShell is also mentioned as an option for authentication, but Linux-specific shells or tools (e.g., Bash, zsh) are not mentioned. There are no explicit Linux examples or screenshots, and the documentation does not highlight Linux-native development environments or workflows.
Recommendations
- Present cross-platform options in parallel or in a non-Windows-first order (e.g., group Visual Studio, VS Code, CLI, and PowerShell together, or rotate the order).
- Include explicit Linux development environment instructions (e.g., using Bash/zsh, common Linux IDEs, or editors like JetBrains Rider or Eclipse).
- Add a note or section confirming that all CLI commands work identically on Linux, macOS, and Windows, and provide example terminal commands for Linux/macOS users.
- Where PowerShell is mentioned, also mention Bash/zsh as alternatives for Linux/macOS users.
- Include screenshots or terminal output from Linux/macOS environments to reinforce parity.
- Highlight any platform-specific caveats, if any exist, for Linux/macOS users.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section, only a Windows-specific command (`ipconfig /flushdns`) is provided for clearing the DNS cache, with no mention of Linux or macOS equivalents. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing troubleshooting steps that involve OS-level commands (such as clearing DNS cache), include equivalent instructions 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`).
- Explicitly state that the command given is for Windows, and offer parity for other major platforms.
- Review future documentation for similar platform-specific troubleshooting tips and ensure cross-platform coverage.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-assess-net.md
...ticles/app-service/app-service-migration-assess-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses on assessing .NET web apps for migration to Azure App Service but does not mention Linux-based .NET hosting, Linux tools, or provide any Linux-specific guidance or examples. The implicit assumption is that the reader is working in a Windows environment, which is common for legacy ASP.NET apps, but modern .NET Core/ASP.NET Core apps are often hosted on Linux. There is no discussion of Linux assessment tools, patterns, or considerations.
Recommendations
- Explicitly mention that both Windows and Linux hosting are supported on Azure App Service, and clarify which assessment steps apply to each.
- Include examples or notes for assessing .NET Core/ASP.NET Core apps running on Linux, including any differences in migration blockers or readiness checks.
- Reference Linux-native tools or commands (such as Bash scripts or Linux CLI) where appropriate, alongside any Windows/Powershell examples.
- Add a section or links addressing Linux-specific migration considerations, such as file system differences, case sensitivity, and environment variable handling.
- Ensure parity in documentation by providing Linux and Windows assessment workflows side-by-side where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-assess-net.md
...ticles/app-service/app-service-migration-assess-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses on assessing .NET web apps for migration to Azure App Service but does not mention or provide examples for Linux-based .NET web apps. The references and linked resources implicitly assume a Windows/IIS/ASP.NET context, with no explicit mention of Linux hosting scenarios or tools relevant to Linux environments.
Recommendations
- Include explicit references to assessing .NET web apps hosted on Linux (e.g., ASP.NET Core on Kestrel/Nginx/Apache).
- Provide examples or guidance for both Windows (IIS) and Linux (Kestrel, Nginx, Apache) hosting environments.
- Mention any differences or additional considerations when assessing Linux-hosted .NET apps for Azure App Service migration.
- Add links to documentation or tools relevant for Linux-based .NET app assessment and migration.
- Ensure parity in terminology and examples so that Linux users feel equally supported.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell examples are often presented first or given special emphasis (e.g., in advanced scenarios). There is a notable presence of PowerShell-specific code blocks outside of the tabbed CLI/PowerShell sections, and no mention of Linux-native tools or shell scripting (e.g., Bash). While Azure CLI is cross-platform, the documentation does not explicitly provide Bash or Linux shell examples, and PowerShell is sometimes highlighted as the default scripting interface.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples, especially in advanced scenarios.
- Where PowerShell examples are given outside of tabbed sections, provide equivalent Bash/Azure CLI examples.
- Clarify that Azure CLI commands can be run natively on Linux/macOS and in Bash, not just in Cloud Shell.
- Avoid implying that PowerShell is the default or preferred scripting environment for all users.
- Consider including Bash script snippets for common scenarios to improve accessibility for Linux users.
- Review screenshots and UI instructions to ensure they are not Windows-centric, though this page appears neutral in that regard.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-assess-net.md
...ticles/app-service/app-service-migration-assess-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on assessing ASP.NET web apps, which are traditionally Windows-centric, and does not mention Linux-based .NET web apps or provide guidance/examples for assessing .NET apps hosted on Linux. All referenced tools and tutorials are oriented towards Windows environments, with no mention of Linux assessment tools or cross-platform considerations.
Recommendations
- Explicitly mention support for assessing .NET web apps running on Linux, if applicable.
- Include examples or references for assessing .NET Core/ASP.NET Core apps hosted on Linux environments.
- List Linux-compatible tools or command-line instructions alongside Windows tools.
- Clarify whether the assessment process and recommendations differ for Linux-hosted .NET apps, and provide relevant guidance.
- Ensure that referenced tutorials and best practices include Linux scenarios where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for managing access restrictions, but PowerShell examples are given equal or greater prominence, especially in advanced scenarios and code samples. PowerShell is a Windows-centric tool, and its heavy usage may disadvantage Linux users. There are no explicit Linux shell (bash) or scripting examples outside of Azure CLI, and PowerShell is sometimes presented before or alongside CLI, which can be perceived as a Windows-first approach.
Recommendations
- Ensure that Azure CLI (which is cross-platform) examples are always presented before PowerShell examples, especially in code blocks and advanced scenarios.
- Where possible, add bash shell script examples for common tasks, especially for advanced scenarios currently only shown in PowerShell.
- Clarify in the documentation that both Azure CLI and PowerShell are available in Azure Cloud Shell and are cross-platform, but highlight that Azure CLI is often more familiar to Linux users.
- Audit for any PowerShell-only advanced examples (such as multi-source rules) and provide equivalent Azure CLI or bash examples.
- Explicitly mention that all features are available regardless of the OS used for management, and avoid implying that PowerShell is the default or preferred tool.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally presents Windows-related tools and examples before Linux equivalents. For example, in the 'Premium V3 availability' section, the Windows SKU availability command is shown before the Linux one. In the automation section, Azure PowerShell is given a dedicated section with a full example, which is a Windows-centric tool, while the Azure CLI example (cross-platform) is also present. There are no explicit Linux shell or scripting examples, and the PowerShell example may not be directly usable on Linux systems.
Recommendations
- Present Linux and Windows examples in parallel or in alternating order to avoid always listing Windows first.
- Provide Bash or shell script examples alongside PowerShell, especially for automation tasks.
- Clarify when a tool or command is cross-platform (e.g., Azure CLI) and when it is Windows-specific (e.g., Azure PowerShell).
- Include notes or links for Linux users on how to perform equivalent actions, especially for steps that reference Windows tools or UI patterns.
- Ensure screenshots and UI instructions are not biased toward Windows-only environments.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page presents Windows containers first and provides more detail and ease-of-use for Windows (no modifications required, browser SSH supported), while the Linux section is more complex and requires additional configuration. There is a lack of parity in example depth: Windows containers have no CLI or command-line SSH examples, while Linux containers have detailed CLI and SSH command examples. However, there are no PowerShell or Windows command-line examples for Windows containers, and the Linux section is more comprehensive.
Recommendations
- Present Linux and Windows container instructions in parallel, rather than always listing Windows first.
- Provide equivalent command-line SSH access instructions for Windows containers, or explicitly state if such access is not possible and why.
- Clarify the differences in SSH support between Windows and Linux containers in a comparative table.
- Add PowerShell or Windows command-line examples for Windows containers if possible, or explain the limitations.
- Ensure both Linux and Windows sections have similar depth and structure in their examples and troubleshooting tips.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias in its quickstart and sample app references. The primary quickstart link for creating the sample Flask app includes 'windows' as a tab in its URL, and there is no explicit mention or example of Linux-specific commands, deployment steps, or environment setup. While the main instructions are generally cross-platform (using Python, Flask, and environment variables), the absence of Linux-specific guidance or parity in example references may disadvantage Linux users.
Recommendations
- Ensure that quickstart/sample app links and references include both Windows and Linux tabs or provide a neutral, platform-agnostic link.
- Explicitly mention that all commands (e.g., pip install, python app.py) work on both Windows and Linux, or provide Linux-specific command examples where appropriate (such as using python3 instead of python if needed).
- Add a section or callout for Linux/macOS users, especially for environment variable setup, local development, and deployment steps.
- Where Azure portal instructions are given, clarify that the steps are the same regardless of the OS used for development.
- Review all referenced documentation to ensure Linux parity and update links or instructions as needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for managing access restrictions, but PowerShell examples are often presented first and are more detailed in some advanced scenarios. There is a notable emphasis on PowerShell, which is traditionally associated with Windows environments, even though Azure CLI is cross-platform. No Linux-specific tools or shell scripting examples are provided, and there is no mention of Linux command-line environments or considerations, despite the documentation stating support for Linux apps and containers.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Add explicit Bash/shell script examples for common scenarios, especially for advanced use cases currently only shown in PowerShell.
- Include notes or tips for Linux users, such as how to use Azure CLI in native Linux shells or integrate with other Linux tools.
- Clarify that PowerShell Core is available cross-platform, but highlight that Azure CLI is the default for Linux environments.
- Where possible, provide parity in example complexity and coverage between Azure CLI and PowerShell sections.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-file-based.md
...les/app-service/configure-authentication-file-based.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 Windows file path (C:\home\site\wwwroot) as the default example for where to place the configuration file, and only later noting the Linux equivalent in a note. There are no Linux-specific examples or screenshots, and the Linux path is only mentioned as a constraint rather than as a primary example. No Linux command-line or deployment examples are provided.
Recommendations
- Present both Windows and Linux file paths side-by-side in the main instructions, not just in a note.
- Include explicit Linux examples (e.g., using /home/site/wwwroot/auth.json) in step-by-step instructions and code snippets.
- If referencing deployment locations or commands, provide both Windows and Linux variants.
- Consider adding a table or section that summarizes differences and best practices for both platforms.
- Add Linux-specific troubleshooting or tips where relevant, to ensure parity and clarity for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-assess-net.md
...ticles/app-service/app-service-migration-assess-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on assessing ASP.NET web apps, which are traditionally associated with Windows environments. There is no mention of Linux-based .NET web apps, nor are there examples or guidance for assessing .NET apps running on Linux. All referenced tools and tutorials implicitly assume a Windows context, and there is no parity for Linux users.
Recommendations
- Include explicit guidance and examples for assessing .NET web apps running on Linux, such as ASP.NET Core apps deployed on Linux servers.
- Mention and link to any tools or scripts that support Linux environments, or clarify if the assessment process is Windows-only.
- Add a section comparing assessment steps or considerations for both Windows and Linux .NET web apps.
- Ensure referenced tutorials and best practices include Linux scenarios where applicable.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page presents Windows container SSH access first and describes it as requiring no special configuration, while Linux containers are described as needing extra steps. The Windows section lacks any CLI or command-line examples (since they're not supported), but the Linux section provides detailed CLI instructions and examples. There are no PowerShell or Windows command-line examples, but the ordering and framing may give the impression that Windows is simpler or preferred. There is also a lack of parity in the level of detail: Linux users get step-by-step CLI instructions, while Windows users are told only that browser SSH is supported.
Recommendations
- Present Linux and Windows instructions in parallel, with equal detail and prominence.
- Clarify up front that SSH via CLI is only supported for Linux containers, and explain why this is the case.
- If possible, provide equivalent command-line or automation options for Windows containers, or explicitly state their absence and suggest alternatives.
- Avoid language that frames one platform as simpler or requiring less effort unless this is a technical limitation, and explain the reasons for any differences.
- Consider adding a summary comparison table of SSH access methods for both Linux and Windows containers.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by referencing Windows first in quickstart links and not providing explicit Linux-specific instructions or examples for environment setup, deployment, or tooling. While the content is generally cross-platform (Python/Flask), it assumes Azure portal or Windows-centric workflows and omits Linux command-line or deployment examples.
Recommendations
- Ensure that all quickstart and setup links include both Windows and Linux tabs or examples, or default to neutral (cross-platform) instructions.
- Explicitly mention and provide Linux/macOS equivalents for any environment setup, deployment, or configuration steps (e.g., using Bash, Linux file paths, or Linux-specific Azure CLI usage).
- If referencing the Azure portal or Visual Studio, also mention VS Code and command-line deployment options for Linux users.
- Add a section or callouts for common Linux development environments and how to adapt environment variable setup, file permissions, and local testing.
- Review all code snippets and instructions to ensure they are not implicitly Windows-specific (e.g., file paths, command syntax).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation assumes the use of GitHub Codespaces and .NET, which are cross-platform, but all terminal instructions and deployment steps are generic and do not mention or provide examples for Linux environments, local development, or non-Windows shells. There is an implicit bias toward Windows/Visual Studio workflows (e.g., 'Open in Browser'), and no explicit mention of Linux-specific considerations or alternative tooling. The instructions do not address running or deploying the app outside of Azure App Service, which is often more common in Linux environments.
Recommendations
- Provide explicit instructions for running the sample locally on Linux (e.g., Ubuntu), including prerequisites such as installing the .NET SDK and any required dependencies.
- Include terminal commands that are shell-agnostic or provide both PowerShell/Command Prompt and Bash equivalents where relevant.
- Mention and demonstrate how to use the sample with local development environments on Linux and macOS, not just Codespaces or Azure.
- Clarify that all steps can be performed on Linux and macOS, and note any differences (such as file paths or environment variable syntax).
- If referencing 'Open in Browser', provide alternatives for Linux users (e.g., using xdg-open or open commands).
- Add a note about deploying to Azure App Service for Linux, and mention that App Service supports both Windows and Linux hosting.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for managing access restrictions, but PowerShell examples are often presented first and are more detailed in advanced scenarios. There are no explicit Linux shell (bash) or platform-specific examples outside of Azure CLI, and PowerShell is emphasized, which is more familiar to Windows users. No Windows-only tools are mentioned, but the prominence and order of PowerShell content may signal a subtle Windows bias.
Recommendations
- Ensure that Azure CLI examples are always presented before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Where advanced scenarios are demonstrated with PowerShell, provide equivalent Azure CLI examples (e.g., for multi-source rules and HTTP header filtering).
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and clarify when PowerShell is required versus when Azure CLI suffices.
- Consider adding bash shell script examples for common tasks, especially where scripting is discussed.
- Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid showing only Windows browser UI if possible).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-assess-net.md
...ticles/app-service/app-service-migration-assess-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on assessing ASP.NET web apps, implicitly assuming a Windows environment. There are no examples, tools, or guidance specific to Linux-based .NET web apps. The linked resources and terminology (ASP.NET, App Service) are historically Windows-centric, and there is no mention of Linux assessment workflows or parity.
Recommendations
- Include explicit guidance or examples for assessing .NET web apps running on Linux (e.g., ASP.NET Core on Linux).
- Mention any differences or additional considerations for Linux-hosted .NET apps in the assessment process.
- Provide links to Linux-specific documentation or tools, if available.
- Clarify whether the assessment process supports both Windows and Linux workloads, and highlight any platform-specific limitations.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-file-based.md
...les/app-service/configure-authentication-file-based.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 Windows deployment path (C:\home\site\wwwroot) before mentioning the Linux equivalent, and by only providing a Windows example for the config file path. The Linux path is mentioned only in a note, and there are no Linux-specific examples or screenshots. There are no PowerShell-specific commands or Windows-only tools, but the documentation implicitly assumes Windows as the default platform.
Recommendations
- Provide both Windows and Linux file path examples side by side when referencing deployment directories (e.g., 'C:\home\site\wwwroot' for Windows and '/home/site/wwwroot' for Linux).
- Instruct users on how to locate or deploy the configuration file on both Windows and Linux environments.
- Include a Linux-specific example for the 'platform.configFilePath' setting in the main instructions, not just in a note.
- Add a table or section explicitly comparing Windows and Linux behaviors for file-based configuration.
- Ensure that all platform-specific differences are clearly documented and that neither platform is treated as the implicit default.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-github.md
...pp-service/configure-authentication-provider-github.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation assumes configuration is performed exclusively through the Azure Portal GUI, which is a web-based tool accessible from any OS, but does not provide any command-line examples. There are no CLI (Azure CLI, Bash, or PowerShell) instructions, but the absence of Linux-specific (or cross-platform) command-line examples may disadvantage users who prefer or require automation or terminal-based workflows, which are especially common on Linux. There is also no mention of Linux-native tools or patterns.
Recommendations
- Add Azure CLI examples for configuring GitHub authentication, including commands to set up identity providers and manage secrets.
- Include Bash shell command examples for Linux users, especially for scripting or automation.
- Explicitly mention that all steps can be performed from any OS via the Azure Portal, but provide parity by showing how to accomplish the same tasks using cross-platform tools.
- If PowerShell examples are added in the future, ensure Bash/Azure CLI equivalents are provided alongside.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation lists Windows hosting options and file/script types before Linux equivalents, and Windows-specific tools and scripts (.exe, .cmd, .bat, .ps1) are mentioned before Bash scripts and cross-platform scripting languages. This ordering and emphasis subtly prioritize Windows environments and tooling.
Recommendations
- Alternate the order of Windows and Linux hosting options, or list them together to avoid prioritization.
- List Bash scripts (.sh) and cross-platform scripting languages before or alongside Windows-specific scripts to demonstrate equal support.
- Explicitly mention Linux tools or patterns (e.g., cron jobs, shell environments) where relevant.
- Add examples or notes highlighting parity and any differences in behavior or support between Windows and Linux environments.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page presents Windows containers first and provides more detail for Linux containers, but omits equivalent SSH/CLI instructions for Windows containers. The Linux section includes step-by-step CLI commands and example outputs, while the Windows section only mentions browser-based SSH and explicitly states that Azure CLI SSH sessions are not supported for Windows containers. There are no PowerShell or Windows-native SSH client examples, nor guidance for advanced Windows container access.
Recommendations
- Provide parity in example depth: If browser-based SSH is the only supported method for Windows containers, explicitly state this and explain the technical reasons. If there are alternative methods (e.g., PowerShell remoting, Windows SSH client), provide step-by-step instructions and examples as done for Linux.
- Include Windows-native command-line examples: If possible, show how to use Windows tools (e.g., PowerShell, Windows SSH client) to connect to Windows containers, or clarify their limitations.
- Balance section order: Consider alternating or combining Linux and Windows instructions for each scenario, or clearly indicate why one platform has more options.
- Clarify feature parity: Add a comparison table summarizing which SSH access methods are available for Linux vs. Windows containers, so users can quickly see the differences.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows first in the quickstart links and tabs, and by not providing explicit Linux-specific examples or instructions. While the content is generally cross-platform (using Python, Flask, and Azure CLI), there is a lack of parity in highlighting or demonstrating Linux workflows, especially in the setup and deployment sections.
Recommendations
- Ensure that all quickstart and setup links include both Windows and Linux tabs/examples, and that Linux is given equal prominence.
- Explicitly mention and provide Linux-specific instructions or screenshots where platform differences exist (e.g., environment variable setup, file paths, deployment commands).
- Where possible, use neutral, cross-platform language and tools (such as Azure CLI and VS Code) and avoid defaulting to Windows-first terminology or ordering.
- Add a section or callout for common Linux deployment scenarios, such as using Bash scripts, systemd for service management, or Linux-specific troubleshooting tips.
- Review and update all referenced links to ensure Linux users are not redirected to Windows-centric instructions by default.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation assumes the use of GitHub Codespaces (a Linux-based environment) but does not provide any explicit Linux or cross-platform command-line examples or troubleshooting. While it avoids overt Windows-specific tools, it implicitly assumes a .NET development workflow that is most familiar to Windows users and does not mention Linux-specific considerations, such as running .NET apps locally on Linux, using Linux package managers, or alternative editors/terminals. The deployment and development instructions (e.g., 'dotnet run', 'azd up') are cross-platform, but there is no explicit guidance for Linux or macOS users, nor any mention of PowerShell or Windows-only tools. The documentation also refers to opening the app in a browser and navigating to URLs, which is generic but could be clarified for different OS environments.
Recommendations
- Explicitly state that the tutorial is cross-platform and works on Windows, Linux, and macOS.
- Add a note or section with Linux/macOS-specific instructions for running the app locally, such as using the terminal, installing .NET SDK on Linux, and opening URLs from the command line.
- Provide troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variables).
- Mention that all CLI commands (dotnet, azd) are cross-platform and provide links to installation instructions for each OS.
- If referencing editors or terminals, mention alternatives (e.g., VS Code, GNOME Terminal, Terminal.app) and not just Windows tools.
- Include screenshots or terminal output from Linux/macOS environments where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-python.md
...service/tutorial-ai-integrate-azure-ai-agent-python.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates subtle Windows bias by referencing Azure App Service (which is traditionally associated with Windows hosting), mentioning NuGet packages (a Windows/.NET package manager) in the security section, and using terminology like 'App Service app' throughout. However, the code examples, setup, and deployment instructions are Linux-friendly (bash commands, Python, GitHub Codespaces), and there are no explicit PowerShell or Windows command-line instructions. Still, Windows-centric tools and patterns are mentioned before or instead of their Linux equivalents.
Recommendations
- Replace or supplement references to 'NuGet packages' with 'Python packages' or 'pip packages' in the security section, since the tutorial is Python-based.
- Clarify that Azure App Service supports both Linux and Windows, and ensure examples and terminology are inclusive of both platforms.
- If mentioning package management or dependency updates, provide Python (pip/requirements.txt) guidance before or alongside any .NET/NuGet references.
- Review security best practices to ensure all recommendations are relevant to Python/Linux environments, not just Windows/.NET.
- Avoid Windows-centric terminology unless the tutorial is specifically for Windows users; otherwise, provide cross-platform context.