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 1601-1625 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-auth-aad.md
...cs/blob/main/articles/app-service/tutorial-auth-aad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Minor Missing Linux Example
Summary
The documentation provides both Windows and Linux pivots for most steps, but the Windows instructions and examples are consistently presented before the Linux ones. In a few places, directory names and runtime versions differ slightly between pivots, but both platforms are generally covered. However, the 'platform-windows' pivot appears first, and some minor details (like directory names) are more explicit in the Windows section. There are no exclusive Windows tools (like PowerShell) or commands, and the Azure CLI is used throughout, which is cross-platform. The FAQ and troubleshooting sections are platform-neutral.
Recommendations
- Alternate the order of platform pivots so that Linux is sometimes presented first, or present both pivots in parallel/tabs to avoid implicit prioritization.
- Ensure that directory names and runtime versions are consistent and clearly explained for both platforms.
- Explicitly state that all Azure CLI commands work identically on Windows, Linux, and macOS, to reinforce parity.
- Consider adding a brief note at the top acknowledging cross-platform support and that instructions are available for both Windows and Linux.
- Review for any subtle differences in instructions or terminology that may unintentionally favor Windows, and harmonize where possible.
Create Pull Request
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 provides both Azure CLI and Azure PowerShell examples for automating Premium V3 tier configuration, but it lists PowerShell as a primary automation option and includes a dedicated PowerShell section. The CLI examples are cross-platform, but there is a subtle Windows-first bias in the ordering and inclusion of PowerShell, which is primarily used on Windows. The documentation does not mention Linux-specific tools (e.g., bash scripts) or provide explicit Linux shell examples beyond Azure CLI. The portal instructions are platform-neutral, but the automation section could better highlight Linux parity.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend it as the primary cross-platform automation tool.
- Add bash script examples for Linux users, demonstrating how to automate with shell scripting.
- Clarify that PowerShell is available on Linux and macOS, but is more commonly used on Windows.
- Reorder automation sections to present Azure CLI before PowerShell, emphasizing cross-platform compatibility.
- Mention Linux-native tools or workflows where relevant, such as using bash or integrating with Linux CI/CD pipelines.
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 for assessing .NET web apps running on Linux, nor is there mention of Linux-specific considerations or tools. The linked resources and terminology (ASP.NET, App Service) reinforce a Windows-centric perspective, potentially excluding users running .NET Core or ASP.NET Core apps on Linux.
Recommendations
- Include explicit guidance and examples for assessing .NET web apps running on Linux, such as .NET Core or ASP.NET Core apps.
- Mention and link to Linux-compatible tools or assessment workflows, if available.
- Clarify whether the assessment process applies equally to Linux-hosted .NET apps, and note any differences or additional steps required.
- Balance terminology by referencing both Windows and Linux hosting scenarios where applicable.
- Add a section or note addressing Linux users, including any prerequisites or limitations.
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 only for Linux containers, while Windows containers are mentioned only briefly and lack equivalent technical guidance. The Windows section is presented first, but does not offer parity in terms of actionable steps or troubleshooting, potentially leaving Windows users underserved and Linux users as the primary audience.
Recommendations
- Add step-by-step instructions for opening SSH sessions to Windows containers, including any available CLI, PowerShell, or RDP alternatives, or clearly state if such options are unavailable.
- If SSH via CLI is not supported for Windows containers, explicitly mention this and suggest any supported remote management alternatives.
- Balance the order of presentation by either alternating Linux and Windows sections or providing equivalent depth for both platforms.
- Include troubleshooting tips and example outputs for Windows containers, similar to those provided for Linux.
- Where features are not available for Windows, provide clear guidance and links to feature requests or roadmap information.
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: in the prerequisite links and quickstart references, the 'windows' tab is listed first, and there are no explicit Linux-specific instructions or examples for environment variable setup, deployment, or local development. While the content is mostly cross-platform, it assumes familiarity with the Azure portal and does not provide parity for Linux command-line or deployment workflows.
Recommendations
- Ensure that all quickstart and prerequisite links include both Windows and Linux tabs, and consider listing Linux first or equally.
- Add explicit Linux (bash) command-line examples for setting environment variables and deploying to Azure App Service.
- Include instructions for using Linux-native tools (e.g., export for environment variables, bash scripts) alongside or before Windows/portal-based instructions.
- Clarify that all steps are cross-platform and, where differences exist (such as file paths or command syntax), provide both Windows and Linux variants.
- If referencing the Azure portal, note any differences in experience for Linux-hosted App Service plans.
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 frequently presented first and are more prominent in advanced scenarios. There are no explicit Linux shell or Bash-specific examples, and PowerShell is a Windows-centric tool, which may disadvantage Linux users. However, the Azure CLI is cross-platform and included, mitigating some bias. There are no references to Windows-only tools outside of PowerShell, and the documentation does mention Linux App Service workloads, but practical Linux command-line usage is not highlighted.
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.
- Explicitly mention that Azure CLI commands can be run from Bash or other Linux shells, and provide example command lines in Bash syntax where appropriate.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for Linux/macOS environments.
- Where possible, provide Bash script snippets or usage patterns for Linux users, especially in advanced or automation scenarios.
- Review screenshots and UI references to ensure they are not Windows-centric (e.g., avoid showing only Windows browser/desktop UI if possible).
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 exhibits a mild Windows bias by referencing the Windows deployment path (C:\home\site\wwwroot) first and providing a relative path example (auth.json) that is only valid on Windows. The Linux-specific requirement for absolute paths is mentioned only in a note, and no Linux-specific example is given in the main steps. There are no Linux command-line or tooling examples, and the documentation does not provide parity in illustrating Linux deployment patterns.
Recommendations
- Provide both Windows and Linux path examples in the main instructions, not just in a note.
- When giving a sample path, include both a Windows (e.g., C:\home\site\wwwroot\auth.json) and a Linux (/home/site/wwwroot/auth.json) version.
- Explicitly state the differences in path handling for both platforms in the main step-by-step instructions, not only in a note.
- If referencing deployment directories, clarify how these map to both Windows and Linux App Service environments.
- Consider including a Linux-focused example or section, especially for common deployment scenarios.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnet-storage-managed-identity/introduction.md
...torial-dotnet-storage-managed-identity/introduction.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples, but consistently lists PowerShell (a Windows-centric tool) before CLI in all code sections. There are no explicit Linux or Bash-specific examples, and PowerShell is given prominence, which may suggest a Windows-first approach. However, the inclusion of Azure CLI examples does provide cross-platform parity, as CLI is available on Linux, macOS, and Windows.
Recommendations
- Alternate the order of PowerShell and Azure CLI tabs or present Azure CLI first, as it is cross-platform and widely used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider adding Bash-specific notes or examples where relevant.
- Add a brief section or note highlighting that all steps can be performed from Linux or macOS using Azure CLI, and link to relevant setup guides for non-Windows environments.
- If possible, include screenshots or terminal output from Linux environments to reinforce parity.
- Avoid language that assumes Visual Studio or other Windows-only tools as the default workflow; mention cross-platform alternatives where applicable.
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, which are cross-platform, but it lacks explicit Linux-specific instructions or examples. All terminal commands and deployment steps are shown in a generic way, but there are subtle Windows-first assumptions, such as references to 'Open in Browser' (a Codespaces UI feature, but not a standard Linux terminal operation) and no mention of Linux-specific tools or alternative workflows. There are no PowerShell-specific commands, but the absence of Linux shell (bash) or self-hosted deployment examples may make Linux users feel less directly supported.
Recommendations
- Add explicit Linux shell (bash) command examples where relevant, especially for running and deploying the app outside Codespaces.
- Include instructions for running the sample app locally on Linux (e.g., using bash terminal, systemd, or Docker), not just in Codespaces.
- Mention and provide examples for Linux-native tools (such as curl or wget for testing endpoints) alongside browser-based Swagger UI instructions.
- Clarify that all .NET CLI commands work cross-platform, and provide troubleshooting tips for common Linux-specific issues (e.g., permissions, environment variables).
- If referencing UI actions (like 'Open in Browser'), provide alternative command-line instructions for users working in a pure terminal environment.
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, even though the Linux workflow is more feature-rich and commonly used. The Windows section is brief and lacks parity with the Linux section, which provides detailed CLI-based SSH instructions and examples. There are no equivalent CLI or PowerShell examples for Windows containers, nor is there a discussion of Windows-native SSH tools or workflows.
Recommendations
- Present Linux and Windows instructions in parallel or start with Linux, as it is more commonly used for SSH workflows.
- Provide equivalent command-line (e.g., PowerShell or Windows SSH client) instructions for Windows containers, or clearly state if such functionality is not available.
- If CLI-based SSH access is not supported for Windows containers, explicitly mention this limitation and suggest alternative approaches.
- Include references to Windows-native SSH tools (such as OpenSSH in Windows 10/11, PuTTY, or PowerShell SSH commands) where appropriate.
- Ensure that both Linux and Windows sections have similar depth and structure, including troubleshooting tips, example commands, and expected output.
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 discusses assessing .NET web apps for migration to Azure App Service but implicitly assumes a Windows/ASP.NET context (e.g., references to ASP.NET, which is historically Windows-centric). There are no explicit examples, tools, or instructions for Linux-based .NET web apps or cross-platform scenarios. All referenced materials and terminology focus on traditional Windows environments, with no mention of Linux-compatible assessment tools or workflows.
Recommendations
- Include explicit references and examples for assessing .NET web apps running on Linux (e.g., ASP.NET Core on Linux).
- Mention and link to tools or workflows that support Linux-based .NET applications, such as command-line tools or scripts compatible with Bash.
- Clarify whether the assessment process and recommendations apply equally to Linux-hosted .NET apps, and if not, provide guidance for those scenarios.
- Add a section or note highlighting cross-platform support and any differences in assessment steps or recommendations for 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 application and is generally cross-platform, but there is subtle Windows bias in the way quickstart links and tabs are presented. The quickstart link for creating the sample app includes 'windows' as a tab before 'terminal-bash', and there are no explicit Linux or macOS-specific instructions or examples. All environment variable and deployment instructions are presented in a way that assumes use of the Azure Portal or Visual Studio, with no mention of Linux-native workflows, shell commands, or deployment tools (e.g., Azure CLI from Bash, Linux file paths, or systemd services). There are no PowerShell-specific commands, but the absence of Linux-specific guidance or parity in examples constitutes a 'missing_linux_example' and a 'windows_first' ordering bias.
Recommendations
- Ensure that all quickstart and sample links include Linux and macOS tabs/examples, and that these are presented equally or before Windows where appropriate.
- Add explicit Linux/macOS instructions for environment variable management (e.g., using export in Bash, .env files, or systemd service files).
- Include deployment instructions using Azure CLI from Bash and/or GitHub Actions, not just Azure Portal or Visual Studio.
- When referencing file paths or commands, provide both Windows and Linux/macOS equivalents.
- Review all code snippets and instructions to ensure they are platform-agnostic or provide platform-specific notes where necessary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-name-resolution.md
.../main/articles/app-service/overview-name-resolution.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Summary
The documentation presents some evidence of Windows bias. In the 'Configure name resolution behavior' section, default values for DNS settings are listed with 'Windows default value' before 'Linux default value' in the table, and the note about unsupported features specifically calls out Windows Container apps. However, the documentation does provide Linux values and does not exclusively focus on Windows tools or examples. There are no PowerShell or Windows-only command-line examples; all CLI examples use the cross-platform Azure CLI. There are no missing Linux examples, but Windows is generally mentioned first and more prominently.
Recommendations
- Alternate the order of Windows and Linux in tables or mention Linux first in some cases to avoid always prioritizing Windows.
- Where limitations are called out for Windows, also explicitly state if there are Linux-specific limitations for parity.
- Consider adding a brief section or callout summarizing any Linux-specific behaviors or differences, to balance the Windows-specific notes.
- Ensure that any future examples or troubleshooting steps include both Windows and Linux contexts equally, especially if OS-specific commands or tools are needed.
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 examples/tools relevant to Linux environments. All referenced materials and linked tutorials implicitly assume a Windows context, with no guidance for users running .NET apps on Linux or using Linux-native tools.
Recommendations
- Include explicit mention of assessing .NET web apps hosted on Linux, such as ASP.NET Core apps running on Linux servers.
- Provide examples or references for assessment tools and procedures that are compatible with Linux environments.
- Add guidance or links for users who need to assess .NET apps deployed on Linux, including command-line examples using Bash or Linux-native utilities.
- Clarify whether the assessment process and tools support both Windows and Linux hosting scenarios, and highlight any differences.
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, but PowerShell examples are often given equal or greater prominence, and some advanced scenarios (such as multi-source rules and Azure Front Door restrictions) are illustrated only with PowerShell. There are no explicit Linux shell/bash examples, and PowerShell is traditionally associated with Windows environments, which may disadvantage Linux users. However, the use of Azure CLI (which is cross-platform) mitigates this bias to some extent. There is no mention of Windows-specific tools or patterns outside of PowerShell usage.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI example, especially in advanced scenarios like multi-source rules and Azure Front Door restrictions.
- Where possible, include bash shell script examples for common tasks, to better support Linux-native workflows.
- Clarify that both Azure CLI and PowerShell are available in Azure Cloud Shell, which is cross-platform, to reduce perceived Windows bias.
- Where PowerShell is shown first or exclusively, alternate the order or default to Azure CLI, as it is more universally accessible.
- Explicitly state that all features are available regardless of the underlying OS of the App Service (Windows or Linux), and call out any exceptions if they 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 demonstrates a 'windows_first' bias by describing Windows container SSH access before Linux, despite Linux being the more common SSH use case. Additionally, it lacks parity in example depth: Windows containers are only described in terms of browser SSH (with no CLI or native SSH client instructions), while Linux containers receive detailed CLI and SSH client instructions. There are no PowerShell or Windows-native SSH client examples, but the lack of equivalent CLI/SSH client instructions for Windows containers constitutes a 'missing_linux_example' bias in reverse (i.e., missing Windows parity for CLI/SSH).
Recommendations
- Reorder sections to present Linux and Windows instructions in parallel or start with Linux, as SSH is more commonly associated with Linux.
- Provide equivalent CLI/SSH client instructions for Windows containers, if supported, or clearly state their absence and suggest alternatives.
- If Windows containers support SSH via native Windows tools (e.g., PowerShell, Windows OpenSSH client), include those examples.
- Ensure both Linux and Windows sections have comparable depth and clarity in their instructions, including troubleshooting and example outputs.
- Explicitly mention any platform limitations (e.g., 'SSH via CLI is not supported for Windows containers') early and clearly.
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 the Linux equivalent, and by providing only a Linux path as a note rather than as a first-class example. There are no Linux-specific examples or step-by-step instructions, and the primary example uses a Windows path. Linux users may find it less clear how to apply the instructions to their environment.
Recommendations
- Present both Windows and Linux file paths in all examples, or use platform-agnostic language (e.g., '<project root>/auth.json').
- Include explicit Linux examples alongside Windows ones, especially in step-by-step instructions.
- In the 'Enable file-based configuration' section, show both Windows and Linux paths in the main text, not just in a note.
- Clarify any platform-specific differences (such as path requirements) in a dedicated section or table for quick reference.
- Consider providing a table or code block showing both Windows and Linux configuration file paths side by side.
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 or cross-platform assessment tools. All referenced materials and examples implicitly assume a Windows context, with no guidance or examples for Linux users.
Recommendations
- Explicitly mention support for assessing .NET web apps running on Linux, if applicable.
- Include examples or references for assessing .NET Core or ASP.NET Core apps hosted on Linux.
- Reference or link to Linux-compatible tools and command-line instructions (e.g., Bash, CLI) alongside any Windows/Powershell tools.
- Clarify whether the assessment process or tools differ for Linux-hosted apps and provide guidance accordingly.
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 referencing the Azure portal GUI workflow, which is more commonly used and accessible on Windows environments. There are no command-line examples (such as Azure CLI or PowerShell), nor are there any Linux-specific instructions or considerations. This omission may disadvantage Linux users who prefer or require CLI-based configuration or who do not use the Azure portal's graphical interface.
Recommendations
- Add equivalent instructions using the Azure CLI for all configuration steps, ensuring that Linux and macOS users can follow along without relying on the Azure portal GUI.
- Include examples or notes for configuring authentication via ARM templates or Bicep, which are platform-agnostic.
- If PowerShell examples are added, ensure that Bash or shell equivalents are also provided.
- Explicitly mention that all steps can be performed on any OS, or provide OS-specific guidance where relevant.
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 exhibits a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) and providing a detailed note about path differences, but only gives a concrete example for Windows (relative path) and not for Linux. The Linux path is mentioned only in a note, and there are no Linux-specific examples or commands. No Linux tools or patterns are discussed, and the default pathing and instructions assume familiarity with Windows conventions.
Recommendations
- Provide Linux-specific examples alongside Windows examples, such as using '/home/site/wwwroot/auth.json' in the main instructions, not just in a note.
- When mentioning file paths, always show both Windows and Linux variants together (e.g., 'C:\home\site\wwwroot\auth.json' (Windows) and '/home/site/wwwroot/auth.json' (Linux)).
- Clarify any differences in file deployment or permissions between Windows and Linux App Service environments.
- Include Linux command-line examples (e.g., using bash or Linux-native tools) where relevant.
- Avoid assuming Windows as the default; use neutral language or parallel examples for both platforms.
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 in more favorable terms, stating that no modifications are required for Windows custom containers, while Linux custom containers require extra configuration. The Windows section lacks command-line or PowerShell examples, but the Linux section provides detailed Azure CLI and SSH command instructions. There are no equivalent command-line instructions or troubleshooting steps for Windows containers, and the Linux section is more comprehensive overall.
Recommendations
- Provide parity in example depth: Add command-line or PowerShell instructions for connecting to Windows containers, or explicitly state if such access is not supported.
- Clarify feature differences: Clearly explain any limitations or differences in SSH support between Linux and Windows containers, including why Azure CLI is not supported for Windows.
- Balance order and emphasis: Present Linux and Windows instructions in parallel or clarify why one is presented before the other.
- Add troubleshooting and usage examples for Windows: If possible, include example usage, troubleshooting, and expected output for Windows containers, similar to the Linux section.
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 development environment that is either Windows-based or at least not explicitly Linux-friendly. It references GitHub Codespaces (which is cross-platform) but does not provide any explicit Linux shell commands, nor does it mention Linux-specific tools or workflows. All terminal commands are given in a generic way, but there is no mention of Linux package managers, shell differences, or deployment nuances for Linux users. There are no PowerShell-specific commands, but the lack of Linux-specific guidance or examples (such as using bash, apt, or Linux file paths) indicates a subtle Windows-first bias.
Recommendations
- Explicitly mention that the tutorial works on both Windows and Linux, and clarify any OS-specific prerequisites.
- Provide Linux-specific instructions or notes where relevant (e.g., using bash instead of cmd/PowerShell, Linux file paths, or package installation).
- Include screenshots or terminal output from both Windows and Linux environments to demonstrate parity.
- If using Codespaces, clarify that it is a Linux container by default and note any differences for local Windows or Linux development.
- Mention any OS-specific dependencies or troubleshooting steps that may be needed 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, implicitly targeting Windows environments. There are no examples, tools, or guidance for assessing .NET web apps running on Linux or using cross-platform tools. All referenced materials and terminology (such as ASP.NET) suggest a Windows-centric approach, with no mention of Linux-based .NET Core or cross-platform assessment scenarios.
Recommendations
- Include explicit guidance and examples for assessing .NET web apps running on Linux (e.g., ASP.NET Core on Linux).
- Mention and provide parity for Linux-compatible assessment tools or scripts, if available.
- Clarify whether the assessment process and recommendations apply to both Windows and Linux-hosted .NET apps.
- Add references to documentation or tutorials for Linux-based .NET app migration and assessment.
- Use cross-platform terminology (e.g., '.NET web apps' instead of only 'ASP.NET web apps') where appropriate.
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 demonstrates a Windows/Azure portal bias by exclusively describing configuration steps through the Azure portal UI, which is most familiar to Windows users. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), and no mention of Linux-native workflows or tools. The absence of Linux command-line instructions or parity for headless/server environments is notable.
Recommendations
- Add equivalent instructions using Azure CLI commands, which are cross-platform and commonly used in Linux environments.
- Include examples for configuring authentication via ARM templates or Bicep, which can be used on any platform.
- Explicitly mention that the Azure portal is web-based and platform-agnostic, but provide links or examples for users who prefer command-line or automated approaches.
- Provide sample scripts for updating app settings (such as GITHUB_PROVIDER_AUTHENTICATION_SECRET) using Bash or PowerShell, and clarify that these can be run on both Windows and Linux.
- Ensure that any references to tools or workflows are balanced between Windows and Linux, or are clearly cross-platform.
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 straightforward instructions for Windows (no modifications needed, browser SSH only), while Linux containers require additional configuration and have more detailed, step-by-step CLI instructions. There are no PowerShell or Windows CLI examples, but Linux is treated as the more complex case, and the Windows section lacks parity in terms of CLI-based SSH access examples.
Recommendations
- Present Linux and Windows instructions in parallel or in a neutral order, rather than always listing Windows first.
- Provide equivalent CLI-based SSH access instructions for Windows containers, or explicitly state if such functionality is not available.
- If Windows CLI/PowerShell SSH access is not supported, clarify this limitation and suggest any available alternatives.
- Ensure both Linux and Windows sections have comparable depth and detail in their instructions and troubleshooting steps.
- Consider adding a summary table comparing SSH access methods and requirements for both Linux and Windows containers.