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 1626-1650 of 2121 flagged pages
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 demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) and providing a relative path example for Windows before mentioning Linux. The Linux-specific requirement (absolute path) is only mentioned in a note, and no Linux file system example is given in the main steps. There are no Linux command-line or file management examples, and the documentation assumes familiarity with Windows paths and conventions.
Recommendations
- Provide Linux file path examples (e.g., /home/site/wwwroot/auth.json) alongside Windows examples in all relevant steps, not just in notes.
- Explicitly mention both Windows and Linux deployment scenarios in the main instructions, not only in side notes.
- Include Linux command-line examples (e.g., using cp, mv, or editors like nano/vim) for creating and deploying the configuration file.
- Clarify any platform-specific differences in configuration up front, rather than as afterthoughts or notes.
- Ensure parity in guidance for both Windows and Linux users, including screenshots or terminal snippets where appropriate.
Create Pull Request
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 that is platform-agnostic (using GitHub Codespaces and .NET CLI), but it lacks explicit Linux-specific instructions or examples. There is a subtle Windows-first bias in that the .NET ecosystem and Azure App Service are more commonly associated with Windows, and there are no mentions of Linux-specific deployment, troubleshooting, or command-line differences. No PowerShell or Windows-only tools are shown, but the absence of Linux terminal or shell examples (e.g., bash) and lack of mention of Linux App Service plans or differences constitutes a 'missing_linux_example' bias.
Recommendations
- Explicitly mention that all .NET CLI commands work on Linux, macOS, and Windows, and show example terminal prompts for bash/zsh as well as Windows CMD/PowerShell if relevant.
- Include a note or section about deploying to Azure App Service (Linux) and any differences in configuration or troubleshooting.
- If referencing file paths, show both Windows (\) and Linux (/) path formats.
- If using Codespaces, clarify that the environment is Linux-based and that all steps are cross-platform.
- Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, case sensitivity, environment variables).
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 environments. There are no examples or mentions of Linux-based .NET web apps, nor are Linux tools, commands, or assessment patterns referenced. The linked resources and terminology (e.g., ASP.NET, App Service) reinforce a Windows-centric perspective.
Recommendations
- Include explicit guidance or examples for assessing .NET web apps running on Linux (e.g., ASP.NET Core on Linux).
- Mention and link to Linux-compatible tools or command-line instructions for assessment.
- Clarify whether the assessment process and recommendations apply equally to Linux-hosted .NET apps, or note any differences.
- Add references to Linux migration scenarios and best practices where relevant.
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 presents Windows container SSH access first and describes it as requiring no modifications, while Linux custom containers are described as needing extra configuration. The detailed SSH access instructions and examples (CLI commands, SSH session walkthrough) are provided only for Linux containers, with no equivalent CLI or PowerShell instructions for Windows containers. This creates a 'windows_first' bias in structure, but a 'missing_linux_example' bias in the Windows section, as it lacks parity in example depth.
Recommendations
- Provide equivalent, detailed SSH access instructions for Windows containers, including any available CLI or PowerShell commands, or explicitly state if such access is not possible.
- Balance the order of presentation by either combining the Linux and Windows instructions or alternating which platform is presented first.
- If Windows containers do not support CLI-based SSH access, clearly explain the limitation and suggest any available alternatives.
- Ensure both platforms have comparable example depth and clarity, including troubleshooting tips and session output where possible.
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 shows a subtle Windows bias by referencing Windows first in the sample app quickstart link (with 'tabs=flask,windows,azure-cli,...'), and does not provide any explicit Linux-specific instructions or examples for environment setup, deployment, or tooling. While the core instructions are cross-platform (Python, Flask, Azure), there is a lack of parity in highlighting Linux workflows or mentioning Linux-specific considerations.
Recommendations
- Ensure that quickstart and reference links include Linux as a first-class option, or provide parallel Linux and Windows tabs/examples.
- Explicitly mention that all instructions (such as environment variable setup, running pip, etc.) work on both Windows and Linux, or call out any differences.
- Provide Linux-specific deployment guidance or troubleshooting tips, especially for common issues (e.g., file permissions, case sensitivity, using bash/zsh shells).
- If referencing the Azure portal or CLI, clarify that these steps are OS-agnostic, or provide command-line examples for both Windows (PowerShell/cmd) and Linux (bash).
- Consider adding a section or callout for Linux users to ensure they feel equally supported.
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 for migration to Azure App Service, but it does not mention Linux-based .NET web apps or provide any Linux-specific guidance or examples. All references and linked resources implicitly assume a Windows environment, with no mention of Linux tools, patterns, or parity.
Recommendations
- Explicitly mention support for both Windows and Linux-based .NET web apps where applicable.
- Include examples or notes on assessing .NET Core/ASP.NET Core apps running on Linux environments.
- Reference Linux-compatible tools or command-line instructions (e.g., Bash, CLI) alongside any Windows/Powershell examples.
- Clarify any differences in assessment steps or recommendations for Linux-hosted web apps.
- Ensure linked resources and tutorials also address Linux scenarios or provide parity.
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 demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) before mentioning Linux, and only provides a Linux-specific note as an aside. There are no Linux-specific examples or screenshots, and the Linux path is only mentioned in a note, not in the main instructional steps or examples.
Recommendations
- Present both Windows and Linux file paths side-by-side in all relevant steps and examples.
- Include explicit Linux examples (e.g., using /home/site/wwwroot/auth.json) in the main instructions, not just in notes.
- Clarify platform differences early in the document, possibly with a table summarizing path conventions for both Windows and Linux.
- Where possible, provide screenshots or command-line examples for both Windows and Linux environments.
- Review for other implicit Windows assumptions (e.g., directory separators, environment variables) and ensure Linux equivalents are always provided.
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-based .NET hosting, Linux tools, or provide any Linux-specific guidance or examples. All references and linked resources implicitly assume a Windows/IIS/ASP.NET context, with no parity for Linux-based .NET Core or ASP.NET Core apps.
Recommendations
- Explicitly mention that both Windows and Linux-based .NET web apps can be assessed and migrated, if supported.
- Include examples or guidance for assessing .NET Core/ASP.NET Core apps running on Linux (e.g., on Apache, Nginx, or Kestrel).
- Reference Linux-compatible assessment tools or scripts, if available.
- Clarify any differences in assessment or migration steps for Linux-hosted .NET apps.
- Add links to documentation or tutorials specifically covering Linux scenarios.
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 demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) before mentioning Linux, and only provides a Linux-specific note as an aside. There are no Linux-specific examples or screenshots, and the Linux path is only mentioned in a note, not in the main instructions or examples.
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 configuration samples.
- Clarify platform-specific differences early in the document, ideally in a dedicated section or table.
- Where possible, provide parity in screenshots, CLI commands, and file path references for both Windows and Linux environments.
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 references a Python (Flask) app and is generally cross-platform, but there is evidence of Windows bias. The quickstart link in the prerequisites uses the 'windows' tab by default, and there are no explicit Linux or macOS command-line examples or deployment instructions. All environment variable setup and deployment instructions are described in terms of the Azure Portal or App Service, with no mention of Linux-specific workflows (e.g., bash commands, Linux file paths, or systemd services). There are no PowerShell-specific commands, but the absence of Linux-specific examples and the default to Windows in quickstart links indicate a subtle Windows-first approach.
Recommendations
- Ensure that quickstart and sample links default to a neutral or Linux tab, or provide parallel links for both Windows and Linux.
- Add explicit Linux/macOS command-line examples for setting environment variables, running the app, and deploying (e.g., using bash, export commands, systemd, or gunicorn).
- Include Linux-specific notes or troubleshooting tips for common issues (such as file permissions or case sensitivity).
- When referencing the Azure Portal, also mention equivalent CLI commands (az cli) for Linux users.
- Review all code snippets and instructions to ensure they are platform-agnostic or provide both Windows and Linux variants where differences exist.
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 modifications, while Linux custom containers require extra steps and configuration. The Windows section lacks command-line or PowerShell examples, but the Linux section provides detailed CLI instructions and examples. There is a slight 'windows_first' ordering bias and a lack of parity in example depth for Windows (no CLI/PowerShell examples), but the Linux section is actually more detailed. There is no evidence of 'powershell_heavy' or 'windows_tools' bias, and Linux is not omitted, but the ordering and lack of Windows CLI parity are notable.
Recommendations
- Provide equivalent command-line or PowerShell examples for Windows containers, or explicitly state if such access is not supported.
- Clarify in both sections the supported SSH access methods (browser, CLI, etc.) for each OS to avoid confusion.
- Consider presenting Linux and Windows instructions in parallel or with equal prominence, rather than always listing Windows first.
- If CLI access is not available for Windows containers, explain why and offer any available alternatives.
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 usage of GitHub Codespaces and Azure App Service, which are cross-platform, but all terminal instructions and environment references are generic or implicitly Windows/.NET-centric. There are no explicit Linux or macOS command-line examples, nor any mention of Linux-specific tools or deployment patterns. The workflow and code samples are focused on .NET and Azure, which are cross-platform, but the documentation does not acknowledge or provide guidance for Linux users (e.g., local development, deployment, or troubleshooting on Linux).
Recommendations
- Explicitly mention that all terminal commands work on Windows, Linux, and macOS, and clarify any OS-specific differences if they exist.
- Provide example commands for common Linux shells (e.g., bash/zsh) where relevant, especially for deployment or environment variable management.
- Include notes or links for Linux/macOS users on how to run and test .NET apps locally (e.g., using dotnet CLI on Ubuntu/macOS).
- If using Codespaces, clarify that it provides a Linux-based environment, and mention how to replicate the setup locally on Linux.
- Add troubleshooting tips or references for Linux users, such as installing .NET SDK or handling file permissions.
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 implicitly assumes a Windows-centric environment. There are no explicit examples or mentions of Linux-based .NET web apps, nor are Linux-specific tools or considerations discussed. The linked resources and terminology (e.g., ASP.NET, which historically is Windows-focused) further reinforce this bias.
Recommendations
- Include explicit mentions and examples of assessing .NET web apps running on Linux (e.g., ASP.NET Core on Linux).
- Reference Linux-based tools or command-line instructions (such as Bash scripts or Linux-native assessment tools) alongside any Windows or PowerShell examples.
- Clarify in the documentation whether the assessment process and recommendations apply equally to both Windows and Linux-hosted .NET web apps.
- Add links to resources or tutorials specifically addressing Linux-based .NET app assessment and migration.
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 explicit instructions or examples for Linux or non-Windows local development environments. All terminal commands and deployment steps are generic, but there is an implicit bias toward Windows-centric workflows (e.g., Visual Studio Code, Codespaces, Azure CLI) without acknowledging or providing parity for Linux-specific tools, shell environments, or deployment patterns. There are no PowerShell-specific commands, but the absence of Linux-specific terminal or deployment instructions constitutes a subtle Windows-first and missing-Linux-example bias.
Recommendations
- Explicitly mention that the tutorial works on both Windows and Linux, and provide any necessary shell command differences (e.g., path separators, environment variable syntax).
- Include examples or notes for running the sample app and deploying from a local Linux environment (e.g., using Bash, zsh, or Linux-native .NET SDK).
- Add troubleshooting tips or prerequisites for Linux users, such as installing the .NET SDK, Azure CLI, and ensuring compatibility with Linux distributions.
- If using Codespaces, clarify that it provides a Linux-based environment, and note that all commands are cross-platform unless otherwise stated.
- Where relevant, provide alternative instructions for Linux-native editors (e.g., Vim, Emacs, GNOME Terminal) or mention that Visual Studio Code is available on Linux.
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 page focuses exclusively on configuring GitHub authentication via the Azure Portal GUI, which is a web-based interface and not inherently OS-specific. However, it omits any command-line examples or automation steps, such as using Azure CLI, PowerShell, or Bash scripts. There is no mention of Linux tools or workflows, nor are there any CLI-based instructions that would be relevant for Linux users. The absence of Linux-specific or cross-platform command-line examples results in an implicit bias, as many Azure docs often provide PowerShell or Windows-first CLI examples.
Recommendations
- Add Azure CLI examples for configuring GitHub authentication, as the CLI is cross-platform and widely used on Linux.
- Include Bash script snippets where appropriate, especially for automation scenarios.
- If PowerShell examples are added, ensure 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, and provide links to CLI documentation for users who prefer command-line workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-aad.md
...s/app-service/configure-authentication-provider-aad.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 not providing any command-line examples (such as Azure CLI, PowerShell, or Bash). There are no platform-specific instructions, but the absence of Linux-oriented or cross-platform command-line examples means Linux users are underserved. All steps are described in terms of portal navigation, which is platform-agnostic but implicitly assumes a GUI workflow common to Windows environments. No Linux tools, shell commands, or deployment patterns are mentioned.
Recommendations
- Add Azure CLI examples for all major configuration steps (e.g., app registration, authentication provider setup, managed identity assignment), as the CLI is cross-platform and widely used on Linux.
- Where PowerShell is relevant, provide Bash or shell script equivalents.
- Include explicit notes or sections for Linux/macOS users, especially for tasks like managing secrets, environment variables, or automating setup.
- Reference cross-platform tools (e.g., az CLI) before or alongside any GUI-based instructions.
- If portal navigation is the only method, clarify that the steps are platform-agnostic and provide links to CLI or REST API documentation for automation and scripting use cases.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation shows mild Windows bias by referencing Azure Storage Explorer with a direct link to the Windows tab for generating SAS tokens, and by mentioning Storage Explorer as the primary tool for file uploads and SAS generation. There are no explicit Linux or cross-platform alternatives suggested for these steps, and the only tool-specific instructions are Windows-centric.
Recommendations
- Include explicit instructions or links for using Azure Storage Explorer on Linux and macOS, or clarify that the tool is cross-platform.
- Provide alternative command-line examples (e.g., using Azure CLI or AzCopy) for uploading files and generating SAS tokens, which work on all platforms.
- Avoid linking directly to the Windows-specific tab in documentation; instead, link to a neutral or cross-platform section.
- Mention that all Azure CLI commands shown are cross-platform, and highlight any platform-specific considerations if they exist.
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 environments. There are no examples, tools, or instructions provided for assessing .NET web apps running on Linux. All referenced resources and terminology (such as ASP.NET) are traditionally associated with Windows, and there is no mention of Linux-based .NET Core or cross-platform scenarios.
Recommendations
- Include explicit guidance and examples for assessing .NET web apps running on Linux, such as .NET Core or ASP.NET Core apps.
- Reference tools and workflows that are cross-platform or provide Linux-specific alternatives where applicable.
- Clarify in the introduction whether the assessment process applies to both Windows and Linux-hosted .NET web apps, and update terminology to reflect cross-platform support.
- Add links to documentation or tutorials for assessing Linux-based .NET web apps, if available.
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 references a Python quickstart link that includes 'windows' as a tab and does not provide explicit Linux or cross-platform command-line examples for key setup and deployment steps. There are no explicit Linux shell or bash commands shown for environment variable setup or deployment, and the only mention of command-line usage is via pip (which is cross-platform). The documentation assumes use of the Azure Portal or Visual Studio for deployment and environment variable management, which are more commonly associated with Windows workflows. There is no mention of Linux-specific tools or deployment patterns.
Recommendations
- Provide explicit Linux/bash command-line examples for setting environment variables, running the app, and deploying to Azure App Service.
- Ensure that quickstart and sample links default to or include Linux/bash tabs, not just Windows.
- Include instructions for using cross-platform tools (such as Azure CLI in bash) for all setup and deployment steps.
- Mention and demonstrate Linux-friendly editors (such as VS Code in WSL or on Linux) and deployment workflows.
- Clarify that all steps can be performed on Linux, macOS, or Windows, and provide parity in instructions and screenshots where relevant.
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 information before Linux, but only provides detailed, step-by-step SSH instructions and CLI examples for Linux containers. There are no equivalent command-line or tooling examples for Windows containers, and the documentation notes that SSH via Azure CLI is not supported for Windows containers, with no alternative methods or troubleshooting guidance provided.
Recommendations
- Provide parity in example depth: If Windows containers do not support Azure CLI SSH access, explicitly state this and suggest any available alternatives (such as RDP, PowerShell Remoting, or other remote management tools) or clarify the roadmap for feature parity.
- Include troubleshooting and configuration details for Windows containers similar to the Linux section, or clearly state the limitations and expected user experience.
- If browser-based SSH is the only supported method for Windows containers, provide a detailed walkthrough and screenshots, matching the depth of the Linux CLI section.
- Consider reordering or balancing the presentation so that Linux and Windows instructions are equally prominent, or use side-by-side tabbed content to avoid the perception of a 'windows_first' bias.
- If possible, provide links to additional resources for Windows container management to help users achieve similar administrative goals as those shown for Linux.
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 (which is Linux-based), but all terminal instructions are generic and do not mention Windows-specific tools or PowerShell. However, there is an implicit Windows/.NET bias in that the entire tutorial is centered around ASP.NET Core, NuGet, and .NET CLI, with no mention of Linux-specific workflows, alternative editors, or deployment methods outside of Azure App Service. There are no explicit Linux command-line examples, nor are there any references to Linux package managers or shell environments. The documentation also assumes the use of Azure Developer CLI (azd) and dotnet CLI, which are cross-platform, but does not provide parity examples for Linux users or mention any Linux-specific considerations.
Recommendations
- Explicitly mention that all CLI commands work on both Windows and Linux, and provide any necessary shell-specific notes (e.g., path separators, environment variable syntax).
- Include a note or section for Linux users, highlighting any differences in setup, deployment, or troubleshooting.
- Provide alternative instructions for running the sample app locally on Linux (e.g., using Bash, systemd, or Docker), not just in Codespaces or Azure.
- If referencing editors or tools, mention cross-platform options (e.g., Visual Studio Code, JetBrains Rider) and not just Visual Studio (Windows).
- Clarify that Azure App Service supports both Windows and Linux hosting, and provide links to documentation for both.
- Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, case sensitivity, dependency installation).
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 modifications, while Linux custom containers require extra steps. The Windows section lacks command-line or PowerShell examples, but the Linux section provides detailed Azure CLI and SSH command-line instructions. There are no equivalent CLI or PowerShell instructions for Windows containers, and the Linux section is more comprehensive in terms of actionable steps. However, the initial placement of Windows content and the lack of parity in example depth may suggest a subtle 'windows_first' and 'missing_linux_example' bias (in reverse: missing Windows CLI example).
Recommendations
- Provide equivalent command-line (e.g., PowerShell or Azure CLI) instructions for opening SSH sessions to Windows containers, if supported.
- Ensure that both Windows and Linux sections have similar levels of detail and actionable examples.
- If SSH via CLI is not supported for Windows containers, explicitly state this and offer alternative remote management options for Windows containers.
- Consider presenting Linux and Windows instructions in parallel or with equal prominence, rather than always listing Windows first.
- Clarify any feature gaps between Windows and Linux containers to set user expectations.
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, but implicitly assumes a Windows environment by referencing only ASP.NET (traditionally Windows/IIS-based) and omitting any mention of Linux-hosted .NET web apps, Linux tools, or cross-platform assessment methods. There are no examples or guidance for users running .NET apps on Linux, nor are Linux-specific tools or patterns mentioned.
Recommendations
- Explicitly mention support for assessing .NET web apps hosted on Linux, including .NET Core/ASP.NET Core apps.
- Provide examples or references for assessment processes on Linux environments, such as using Bash scripts or Linux-native tools.
- Clarify whether the assessment tools and recommendations apply equally to Linux-hosted .NET apps, and if not, provide guidance or links for Linux users.
- Include parity in documentation for both Windows and Linux scenarios, ensuring that Linux users are not excluded from the assessment workflow.
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 location for the configuration file, and only later mentioning the Linux equivalent. There are no explicit Linux command-line or file system examples, and Linux-specific instructions are minimal and only provided as a note. No Linux shell commands or patterns are shown, and the documentation assumes familiarity with Windows paths and conventions.
Recommendations
- Present both Windows and Linux file paths together when describing file locations (e.g., 'C:\home\site\wwwroot\auth.json' for Windows and '/home/site/wwwroot/auth.json' for Linux).
- Include explicit Linux examples and instructions alongside Windows ones, such as how to create or deploy the configuration file on Linux-based App Service environments.
- Avoid assuming Windows as the default platform; use neutral language or parallel examples.
- Add a table or section summarizing platform-specific differences (e.g., path formats, deployment nuances) for clarity.
- Where relevant, provide Linux shell command examples (e.g., using cp, mv, or echo) in addition to any Windows/Powershell commands.
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 workflows are presented generically without explicit mention of Windows or Linux. However, there is an implicit Windows/.NET bias due to the exclusive focus on ASP.NET Core, NuGet, and .NET CLI tools, with no mention of Linux-specific development environments, shell commands, or alternative (non-Windows) deployment patterns. There are no PowerShell-specific commands, but the lack of Linux/Unix shell examples or explicit Linux parity is notable.
Recommendations
- Explicitly mention that all .NET CLI commands work on Linux, macOS, and Windows, and clarify that the tutorial is platform-agnostic.
- Add a note or section describing how to run the sample app and commands in a local Linux or macOS environment (e.g., using bash/zsh instead of just 'codespace terminal').
- Provide alternative instructions for deploying from a local Linux shell (e.g., using Azure CLI in bash) in addition to Codespaces.
- If referencing file paths, use forward slashes or clarify path conventions for both Windows and Linux.
- Include a brief section or callout for Linux users, confirming that all tools and steps are supported cross-platform and linking to .NET installation instructions for Linux.