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 1651-1675 of 2121 flagged pages
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 focuses exclusively on assessing ASP.NET web apps, which are traditionally Windows-centric, and does not mention Linux-based .NET web apps or provide Linux-specific assessment guidance or examples. All referenced tools and linked resources implicitly target Windows environments, with no mention of Linux compatibility or alternatives.
Recommendations
- Explicitly mention whether the assessment process and tools support both Windows and Linux-based .NET web apps.
- Include examples or guidance for assessing .NET web apps hosted on Linux, if supported.
- Reference Linux-compatible tools or provide parity in instructions for Linux environments.
- Clarify any limitations or differences in assessment for Linux-hosted .NET apps versus Windows-hosted ones.
Create Pull Request
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 providing a concrete example path only for Windows in the main instructions. The Linux path is only mentioned later in a note, and no Linux-specific example or command is provided. There are no Linux shell or tooling examples, and the documentation assumes familiarity with Windows file paths.
Recommendations
- Present both Windows and Linux file paths together in all relevant instructions and examples, e.g., 'C:\home\site\wwwroot\auth.json' (Windows) and '/home/site/wwwroot/auth.json' (Linux).
- Include explicit Linux examples or commands where file paths or environment specifics are discussed.
- Avoid assuming Windows as the default by rephrasing instructions to be platform-neutral, or by listing Linux first in some cases.
- Where platform differences exist (such as path formats), provide clear, parallel examples for both Windows and Linux.
- Consider adding a table or section summarizing key differences between Windows and Linux deployments for this feature.
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
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation page demonstrates a Linux-first bias in the sections related to Java key store and certificate management. Detailed instructions, file paths, and troubleshooting steps are provided only for Linux-based App Service environments, with no equivalent coverage for Windows-based environments. There are no PowerShell or Windows tool examples, and Windows-specific patterns are not mentioned, which may leave Windows users without sufficient guidance.
Recommendations
- Add a section detailing how Java key stores and certificates are managed on Windows-based App Service environments, including default file locations and any differences in behavior.
- Provide examples of how to interact with the Java key store on Windows, such as using Command Prompt or PowerShell, and specify any relevant differences in environment variables or file paths.
- Include troubleshooting steps and manual certificate loading instructions for Windows, similar to the Linux guidance.
- Ensure parity in documentation by explicitly stating when a feature or behavior is Linux-only, and provide alternatives or workarounds for Windows users where possible.
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
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on configuring GitHub authentication via the Azure Portal UI, which is a platform-agnostic web interface. However, it omits any command-line instructions or automation examples. There is an implicit bias in that, for Azure documentation, CLI or scripting examples (such as Azure CLI, PowerShell, or Bash) are often provided, but here, no such examples are given. This can disadvantage Linux users who prefer or require CLI-based workflows, especially since Azure documentation often defaults to PowerShell or Windows tools when examples are given.
Recommendations
- Add Azure CLI examples for configuring GitHub authentication, including commands to set up identity providers and manage secrets.
- Include Bash shell examples for Linux users, especially for automation scenarios.
- If PowerShell examples are added in the future, ensure that equivalent Bash/Azure CLI examples are provided and presented with equal prominence.
- Explicitly mention that all steps can be performed from any OS via the Azure Portal, but highlight CLI options for users who prefer non-GUI workflows.
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 Azure App Service, which are cross-platform, but all terminal instructions and deployment steps are shown using .NET CLI and Azure Developer CLI without explicit mention of Linux or Mac environments. There are no examples or notes for Linux-specific workflows, such as using a local Linux terminal, package managers, or alternative editors. The documentation also references Visual Studio Code features (like 'Open in Browser') that may behave differently on Windows versus Linux/Mac, but does not clarify or provide alternatives.
Recommendations
- Explicitly state that all CLI commands work on Linux, Mac, and Windows, and provide any necessary prerequisites for Linux (e.g., installing .NET SDK, Azure CLI).
- Include notes or examples for running the sample app and deploying from a local Linux or Mac terminal, not just from Codespaces.
- Clarify how to open the app in a browser from the terminal on Linux/Mac (e.g., using 'xdg-open' or 'open' commands) in addition to the Codespaces/VS Code UI.
- Mention any differences in environment variables or file paths that may affect Linux users.
- If referencing Azure App Service, note that it runs on both Windows and Linux, and clarify any differences in deployment or runtime behavior.
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. In the prerequisites and quickstart links, 'windows' is listed as a tab before Linux, and there are no explicit Linux or cross-platform command-line examples. The instructions for environment variable setup and deployment reference the Azure portal and App Service, which are platform-agnostic, but there are no examples or guidance for Linux-specific workflows or tools (e.g., bash scripts, Linux file paths, or Linux deployment methods). The only shell command shown is 'pip install', which is cross-platform, but there is no mention of Linux-specific nuances or alternative approaches.
Recommendations
- Ensure that all quickstart and sample links include Linux tabs or examples, and mention them alongside or before Windows.
- Add explicit Linux command-line examples where relevant, such as using bash to set environment variables or deploy the app.
- Include Linux file path examples and clarify any differences in file handling or permissions.
- Reference Linux deployment methods (e.g., using Azure CLI on Linux, deploying from a Linux workstation) in addition to portal-based instructions.
- If mentioning Visual Studio or Windows-specific tools, also mention VS Code and cross-platform alternatives.
- Review all code and instructions to ensure they are tested and work identically on Linux environments.
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 Linux environments, Linux-based .NET apps, or provide any Linux-specific guidance or examples. All referenced materials and terminology implicitly assume a Windows/ASP.NET context, and there is no discussion of Linux tools or assessment nuances for Linux-hosted .NET applications.
Recommendations
- Explicitly mention that .NET web apps can run on both Windows and Linux, and clarify if the assessment process covers both platforms.
- Include examples or notes for assessing .NET Core/ASP.NET Core apps running on Linux servers.
- Reference Linux-compatible tools or scripts for discovery and assessment, if available.
- Add guidance or links for users migrating from Linux environments, highlighting any differences in assessment or migration steps.
- Ensure parity in documentation by providing Linux-specific considerations, such as file system differences, environment variables, and deployment patterns.
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
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation page demonstrates a Linux-first bias in the sections related to Java key store and certificate management. It provides detailed instructions and examples specifically for Linux-based App Service environments, including file paths, environment variables, and SSH usage, while omitting equivalent instructions or references for Windows-based App Service environments. There are no PowerShell or Windows tool examples, and Windows-specific patterns are not mentioned.
Recommendations
- Add parallel instructions for managing Java key stores and certificates on Windows-based App Service, including file paths (e.g., where certificates are stored on Windows), environment variable usage, and any differences in process.
- Provide examples of how to interact with the Java key store using Windows tools (such as Command Prompt or PowerShell), and document how to access the keytool utility on Windows App Service.
- Clarify in each section whether the instructions apply to both Linux and Windows, or provide separate tabs/pivots for each OS.
- Ensure that references to SSH and Linux file paths are complemented with equivalent instructions for Windows Remote Desktop or Kudu Console where appropriate.
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 subtle Windows bias by referencing Windows first in the quickstart links and not providing explicit Linux or cross-platform command-line examples. While the main content is OS-agnostic (Python/Flask), the quickstart and setup instructions default to Windows tabs, and there are no explicit Linux or bash shell examples for environment variable setup or deployment. There is also a reliance on Azure Portal UI steps, which may not be as accessible or preferred for Linux users who often use CLI tools.
Recommendations
- Ensure that quickstart and setup links default to cross-platform or Linux-first tabs, or provide parallel instructions for both Windows and Linux.
- Include explicit bash/Linux shell examples for setting environment variables and running the application, not just references to the Azure Portal.
- Wherever possible, provide Azure CLI commands for configuration and deployment steps, in addition to or instead of portal UI instructions.
- Review all code snippets and instructions to ensure they are platform-neutral or provide alternatives for both Windows and Linux environments.
- Clarify in the prerequisites and setup sections that the instructions are applicable to both Windows and Linux, and link to relevant Linux documentation where available.
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 a development environment based on GitHub Codespaces and .NET, but does not provide any Linux-specific instructions or examples. All terminal commands and deployment steps are generic, but there is no mention of Linux shell usage, nor are there any references to Linux-specific tools or patterns. The workflow implicitly assumes familiarity with Windows-centric .NET development patterns, and there is no guidance for users developing or deploying from a native Linux environment.
Recommendations
- Explicitly mention that the tutorial works on both Windows and Linux environments, and provide any necessary differences (such as file paths or environment variable handling).
- Include Linux shell command equivalents where appropriate, especially for common tasks like running the app, installing dependencies, or deploying.
- Add a note about how to run the sample locally on Linux (e.g., using Bash, setting environment variables, or using Docker).
- If using Codespaces, clarify that it is a Linux-based environment and provide troubleshooting tips for users running locally on Linux.
- Where file paths or commands might differ between Windows and Linux, provide both versions or use cross-platform conventions.
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, implicitly assuming a Windows environment by referencing ASP.NET (which is historically Windows-centric) and providing no mention of Linux-based .NET apps, Linux tools, or cross-platform assessment workflows. All referenced tools and tutorials are tailored to Windows-centric migration scenarios, with no guidance for Linux users.
Recommendations
- Include explicit guidance and examples for assessing .NET web apps hosted on Linux, such as those running on .NET Core or ASP.NET Core on Linux servers.
- Mention and link to any cross-platform or Linux-compatible assessment tools, if available.
- Add a section or note clarifying support for Linux-based .NET apps and how the assessment process may differ.
- Ensure referenced tutorials and best practices cover both Windows and Linux scenarios, or clearly indicate platform applicability.
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
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively describing configuration steps through the Azure portal UI, which is most commonly accessed and depicted in a Windows environment. There are no CLI, PowerShell, or Linux shell examples, nor are there references to cross-platform command-line tools or automation approaches. This omission may disadvantage Linux users or those preferring non-GUI workflows.
Recommendations
- Add equivalent instructions using Azure CLI (az) commands for configuring GitHub authentication, which are cross-platform and suitable for Linux users.
- Include examples for updating application settings and identity providers using command-line tools (e.g., Bash scripts, Azure CLI) alongside portal-based instructions.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide parity for users who prefer or require CLI-based configuration.
- Where secrets or settings are updated, show both portal and CLI-based approaches to ensure inclusivity for Linux and automation-focused 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, implicitly targeting Windows-based workloads (since classic ASP.NET is a Windows technology). There are no examples, tools, or guidance for assessing .NET web apps running on Linux, nor is there mention of Linux-specific considerations or tools. All referenced materials and linked tutorials appear to assume a Windows environment.
Recommendations
- Explicitly mention whether the assessment process supports both Windows and Linux-based .NET web apps, or clarify any limitations.
- Include examples or notes for assessing .NET Core/ASP.NET Core apps running on Linux, if supported.
- Reference Linux-compatible tools or command-line instructions (e.g., Bash, CLI) alongside any Windows/Powershell guidance.
- Add a section addressing common Linux-specific migration or assessment concerns (such as file system differences, case sensitivity, or service dependencies).
- Ensure that linked tutorials and best practices cover both Windows and Linux scenarios where applicable.
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 Windows bias by referencing the Windows file path (C:\home\site\wwwroot) first and providing more detail for Windows path handling. Linux is only mentioned in a note, with no Linux-specific example or step-by-step guidance. There are no Linux shell or tool references, and the configuration instructions and examples are Windows-centric.
Recommendations
- Provide explicit Linux examples alongside Windows ones, such as using /home/site/wwwroot for file paths.
- Include step-by-step instructions for Linux environments, not just notes about differences.
- Mention Linux deployment tools or patterns where relevant, such as using SCP, SFTP, or Linux-based CI/CD pipelines.
- Ensure parity in detail and clarity for both Windows and Linux users throughout the documentation.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally presents platform-neutral guidance, but there is evidence of Windows bias in the ordering and depth of examples. Key security configuration sections (authentication, Key Vault references, TLS/SSL) do not distinguish between Windows and Linux, and do not provide Linux-specific command-line examples or highlight Linux-specific tools until the 'Java key store in Linux' section, which appears last. There are no PowerShell or Windows command-line examples, but Linux-specific instructions (such as using SSH and keytool) are only mentioned in the Linux section, and not in the main authentication or Key Vault sections. The documentation refers to Azure portal configuration throughout, which is platform-neutral, but does not provide parity for Linux CLI workflows or troubleshooting until later.
Recommendations
- Add Linux-specific examples and command-line instructions (such as using SSH, keytool, or Azure CLI) in all relevant sections, not just the key store section.
- Ensure that Linux workflows (such as configuring authentication, Key Vault references, and TLS/SSL) are described alongside or before Windows/portal workflows.
- Explicitly mention any platform differences or limitations in each section, so Linux users know what applies to them.
- Provide troubleshooting steps and examples for both Windows and Linux environments in all major configuration areas.
- Consider adding a table or pivoted content at the top of each section to clarify platform-specific steps.
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 Windows bias by referencing Windows in the quickstart links and example tabs (e.g., 'flask, windows, azure-cli, vscode-deploy, ...'), and by not providing explicit Linux or cross-platform deployment instructions. There are no Linux-specific examples, and Windows appears first in the context of setup and tooling. The documentation does not mention Linux tools or patterns, nor does it provide parity in example commands or environment setup for Linux users.
Recommendations
- Ensure that quickstart and setup instructions include explicit Linux and macOS tabs/examples alongside Windows, especially for environment setup and deployment.
- Provide Linux-specific deployment instructions (e.g., using Bash, systemd, or Linux-native Azure CLI usage) in addition to or before Windows instructions.
- Avoid referencing Windows first in tab lists or examples; use neutral or alphabetical ordering, or highlight cross-platform approaches.
- Include troubleshooting or environment variable setup examples for Linux (e.g., exporting variables in Bash, using .env files in Linux environments).
- Reference Linux tools (such as Bash, nano/vim for editing files, or Linux package managers) where appropriate, and ensure parity with Windows tooling.
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
Windows First
Missing Linux Example
Summary
The documentation assumes a Windows-centric development environment by referencing Azure App Service, ASP.NET Core, and NuGet packages, and by providing instructions that implicitly target Windows users (e.g., use of GitHub Codespaces, dotnet CLI, and Azure Developer CLI without mentioning Linux-specific alternatives or considerations). There are no examples or instructions for Linux environments, such as using Linux-native tools, package managers, or deployment patterns. The tutorial does not mention how to run or deploy the sample app on Linux, nor does it address potential differences in configuration, permissions, or troubleshooting for Linux users.
Recommendations
- Add explicit instructions for running and deploying the sample app on Linux environments, including common Linux distributions.
- Provide Linux-specific examples for installing .NET SDK, running dotnet CLI commands, and deploying to Azure App Service from Linux terminals.
- Mention any differences in environment variables, file paths, or permissions that Linux users might encounter.
- Include troubleshooting tips for Linux users, such as resolving common issues with .NET on Linux or configuring HTTPS.
- Reference Linux-native editors (e.g., VS Code on Linux) and terminal usage, not just GitHub Codespaces.
- Clarify that Azure App Service supports both Windows and Linux hosting, and link to documentation for Linux-based App Service plans.
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, implicitly targeting Windows-based workloads without mentioning Linux-based .NET web apps or providing Linux-specific guidance. All linked resources and terminology (e.g., ASP.NET, App Service migration) are traditionally associated with Windows environments, and there is no discussion of Linux tools, commands, or assessment nuances for Linux-hosted .NET apps.
Recommendations
- Include explicit references to both Windows and Linux-hosted .NET web apps in the assessment process.
- Provide examples or links for assessing .NET Core/ASP.NET Core apps running on Linux, including any differences in assessment steps or tooling.
- Mention any Linux-compatible tools or scripts for assessment, or clarify if the process is identical across platforms.
- Add a section or note on platform-specific considerations (e.g., file system, dependencies, environment variables) when assessing apps for migration.
- Ensure that documentation and linked resources address both Windows and Linux scenarios equally.
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 Windows Cli Example
Summary
The documentation presents Windows container SSH access first, but only describes browser-based SSH for Windows, while Linux containers receive detailed Azure CLI and SSH client instructions. There are no PowerShell or Windows CLI examples for Windows containers, and the Linux section is much more comprehensive in terms of tooling and usage patterns.
Recommendations
- Provide equivalent CLI or PowerShell instructions for opening SSH sessions to Windows containers, if supported.
- Clarify why Azure CLI SSH is not supported for Windows containers and suggest any alternative approaches.
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence.
- If Windows containers only support browser SSH, explicitly state this limitation and offer guidance for advanced scenarios or troubleshooting.
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 exhibits a 'windows_first' bias by referencing the Windows deployment path (C:\home\site\wwwroot) first and only providing a Linux-specific path as a note later. There are no Linux-specific examples or step-by-step instructions, and the guidance for Linux is limited to a note about absolute paths, without parity in example or detail.
Recommendations
- Provide Linux-specific examples alongside Windows examples, such as using /home/site/wwwroot/auth.json as the default path in the main instructions.
- When mentioning file paths, always present both Windows and Linux formats together (e.g., C:\home\site\wwwroot\auth.json for Windows, /home/site/wwwroot/auth.json for Linux).
- Include a dedicated section or callout for Linux users, outlining any platform-specific considerations or steps.
- Ensure that all configuration steps and references are equally detailed for both Windows and Linux environments.
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 a development environment based on GitHub Codespaces and .NET, but does not provide any explicit Windows-only commands or tools. However, it lacks explicit Linux or cross-platform terminal instructions, and does not mention Linux-specific deployment or testing steps. The use of 'Open in Browser' and reliance on Azure App Service (which is cross-platform) is neutral, but the absence of Linux CLI or shell examples, and the lack of mention of Linux development environments, results in a subtle Windows or general non-Linux bias.
Recommendations
- Explicitly mention that all commands (e.g., 'dotnet run', 'azd up') work on Linux, macOS, and Windows, and provide any necessary shell syntax differences if applicable.
- Include examples of running the sample app and deploying from a Linux terminal (e.g., bash), or clarify that the instructions are cross-platform.
- If using Codespaces, note that it is a Linux-based environment, and provide guidance for users developing locally on Linux or macOS.
- Add troubleshooting notes for common Linux-specific issues (e.g., permissions, case sensitivity, environment variables).
- Where GUI actions are described (e.g., 'Open in Browser'), provide CLI alternatives (e.g., using 'xdg-open' on Linux or 'open' on macOS).
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 the prerequisites and quickstart links, 'windows' is explicitly listed as a tab or context before Linux, and there are no explicit Linux or cross-platform shell examples for environment variable setup, deployment, or local development. All environment variable instructions reference the Azure portal GUI, with no CLI or Linux shell alternatives. There are no PowerShell-specific commands, but the absence of Linux/Bash examples and the ordering of 'windows' first in quickstart links indicate a subtle bias.
Recommendations
- Provide explicit Linux/Bash shell examples for setting environment variables, running the app, and deploying to Azure App Service.
- Ensure that quickstart and sample links either default to cross-platform or include both Windows and Linux tabs equally, with Linux not always listed after Windows.
- Include Azure CLI commands for common tasks (e.g., setting app settings, deploying) alongside portal instructions.
- Clarify that all Python and Flask instructions are cross-platform, and add notes or callouts for any OS-specific steps.
- Where possible, use neutral language and ordering (e.g., 'Windows or Linux') in lists and instructions.
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 for migration to Azure App Service, but it does not mention Linux-based .NET hosting scenarios or provide Linux-specific assessment guidance or examples. The linked resources and terminology (e.g., ASP.NET, which has historically been Windows-centric) reinforce a Windows-first perspective, and there is no mention of Linux tools, patterns, or parity.
Recommendations
- Include examples and guidance for assessing .NET web apps hosted on Linux, such as those running on .NET Core or ASP.NET Core on Linux servers.
- Mention and link to Linux-compatible assessment tools or scripts, if available.
- Clarify whether the assessment process and recommendations apply equally to Linux-hosted .NET apps, and highlight any differences.
- Add Linux-specific best practices or considerations for migration readiness and blocker identification.
- Ensure that terminology and linked resources reflect both Windows and Linux hosting 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
Missing Linux Example
Windows First
Summary
The documentation provides detailed, step-by-step SSH access instructions and CLI examples exclusively for Linux containers, while Windows containers are only mentioned in general terms without equivalent technical detail or command-line examples. Additionally, the Windows section appears before the Linux section, which may reinforce a 'windows_first' bias.
Recommendations
- Add equivalent technical details and step-by-step instructions for SSH access to Windows containers, including any available command-line or PowerShell methods, or explicitly state if such options are not supported.
- If SSH via CLI is not supported for Windows containers, clarify this limitation early and provide alternative troubleshooting or remote access options for Windows users.
- Consider presenting Linux and Windows instructions in parallel or side-by-side to avoid the impression of prioritizing one platform over the other.
- Ensure that both Linux and Windows sections include comparable levels of detail, including example commands, screenshots, and troubleshooting tips.
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 Azure App Service, which are cross-platform, but all terminal and deployment instructions are generic and do not mention or show any Linux-specific commands, shell environments, or deployment patterns. There are no explicit Windows-only tools, but the lack of Linux-specific guidance (such as bash commands, Linux package management, or alternative editors) and the absence of any mention of running locally on Linux or WSL, may make Linux users feel less directly supported. The documentation also refers to 'Open in Browser' and other UI actions that may be more familiar to Windows/VS Code users.
Recommendations
- Add explicit instructions or notes for running the sample app and deploying from a local Linux or WSL environment, not just Codespaces.
- Include bash/zsh shell command examples alongside dotnet CLI commands, and clarify that all commands work on Linux, macOS, and Windows.
- Mention Linux package management for .NET SDK installation (e.g., apt, yum) in prerequisites if not already covered elsewhere.
- Clarify that 'Open in Browser' and other UI actions can be performed in any OS, and provide alternative instructions for users working in a purely terminal environment.
- Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.