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 1801-1825 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily by presenting .NET/ASP.NET (Windows-centric) code samples first and in greater detail, while not providing any explicit Linux-specific configuration or troubleshooting guidance. There are no examples or instructions for Linux command-line tools (such as Bash, OpenSSL, or curl) for certificate handling, nor is there any mention of Linux-specific behaviors or caveats. The focus on the X-ARR-ClientCert header and .NET-centric validation patterns further reinforces a Windows-oriented approach, even though App Service supports Linux hosting.
Recommendations
- Add Linux-specific command-line examples (e.g., using Bash, OpenSSL, or curl) for uploading, validating, or troubleshooting client certificates.
- Include guidance or notes on differences in certificate handling between Windows and Linux App Service plans, if any.
- Provide parity in code samples by including examples for popular Linux-first frameworks (e.g., Nginx, Apache, or Kestrel on Linux) and how to access/validate client certificates in those environments.
- Explicitly mention that the provided instructions and code samples are cross-platform where applicable, or clarify any platform-specific limitations.
- Consider reordering or balancing the presentation of code samples so that Windows and Linux (or cross-platform) approaches are given equal prominence.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is generally cross-platform and avoids OS-specific instructions, but there is a subtle Windows bias in the troubleshooting section. Specifically, when advising users to clear the DNS cache, only the Windows command (`ipconfig /flushdns`) is provided, with no equivalent instructions for Linux or macOS users. No PowerShell-specific or Windows-only tools are otherwise mentioned, and the rest of the content is platform-neutral.
Recommendations
- When providing troubleshooting steps such as clearing the DNS cache, include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- Explicitly state that the instructions apply to all platforms, or provide platform-specific tabs or notes where OS-specific actions are required.
- Review other sections for subtle OS-specific terminology or screenshots, ensuring parity for Linux/macOS users where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page generally avoids platform-specific instructions, but in the troubleshooting section, it provides a Windows-specific command ('ipconfig /flushdns') for clearing the DNS cache without mentioning the equivalent command for Linux or macOS. No Linux or cross-platform alternatives are provided, and the Windows command is presented as the only example.
Recommendations
- When mentioning platform-specific commands (such as clearing DNS cache), provide equivalent instructions for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo /etc/init.d/nscd restart') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- Use language that is inclusive of all major platforms, such as 'On Windows, use ...; on Linux, use ...; on macOS, use ...'.
- Review the documentation for any other subtle Windows-first assumptions and ensure parity by including Linux/macOS equivalents wherever relevant.
- Consider adding a short section or callout box for common troubleshooting steps across different operating systems.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section, it specifically mentions the Windows command 'ipconfig /flushdns' for clearing DNS cache, without providing an equivalent command for Linux or macOS users. No Linux or cross-platform alternatives are mentioned, and no Linux command-line examples are given.
Recommendations
- When suggesting command-line tools (such as for clearing DNS cache), provide equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- Explicitly mention that the instructions apply to all platforms, or provide platform-specific notes where relevant.
- Review other troubleshooting or command-line steps to ensure parity between Windows, Linux, and macOS.
- Consider adding a short section or callout box for cross-platform DNS cache clearing instructions.
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 compatible with .NET and Azure App Service, but it does not provide explicit instructions or examples for Linux users. The use of GitHub Codespaces and Azure Developer CLI (azd) is cross-platform, but there are no Linux-specific terminal commands, deployment notes, or troubleshooting tips. The documentation also references 'Open in Browser' and Swagger UI navigation in a way that may be more familiar to Windows users. There are no references to Windows-only tools, but the lack of explicit Linux parity is a subtle form of bias.
Recommendations
- Explicitly state that all commands and steps work on Linux, macOS, and Windows, and mention any OS-specific prerequisites if needed.
- Provide example terminal commands for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) when relevant, especially for deployment, file navigation, or environment variable management.
- Include troubleshooting tips for common Linux issues (e.g., permissions, case sensitivity, .NET SDK installation).
- Clarify that GitHub Codespaces and Azure Developer CLI are cross-platform, and provide links to installation guides for Linux users.
- If referencing UI actions like 'Open in Browser', note how to do this from a Linux terminal (e.g., using xdg-open or open commands).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Azure portal steps and DNS concepts. However, in the troubleshooting section, only a Windows-specific command ('ipconfig /flushdns') is provided for clearing the DNS cache, with no mention of equivalent commands for Linux or macOS. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing troubleshooting steps, include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder') alongside the Windows 'ipconfig /flushdns' command.
- Wherever OS-specific instructions are necessary, present them in a cross-platform format (e.g., using tabs or lists for Windows, Linux, and macOS).
- Review other sections for any subtle platform assumptions and ensure parity in examples and instructions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides a troubleshooting step for clearing the DNS cache that only references the Windows-specific ipconfig /flushdns command, without mentioning the equivalent commands for Linux or macOS. No Linux or cross-platform command-line examples are given, and the only OS-specific tool mentioned is for Windows.
Recommendations
- When providing troubleshooting steps involving command-line tools, include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`) alongside the Windows example.
- Wherever possible, use cross-platform language or provide parallel instructions for all major operating systems.
- Review the documentation for other implicit Windows-first assumptions and ensure parity in guidance for Linux and macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily uses platform-agnostic instructions but contains a subtle Windows bias in the troubleshooting section, where only the Windows command (ipconfig /flushdns) is provided for clearing the DNS cache. No equivalent Linux or macOS commands are mentioned. There are no PowerShell-heavy sections or exclusive references to Windows tools, but the absence of cross-platform examples in this context may disadvantage Linux/macOS users.
Recommendations
- When suggesting clearing the DNS cache, include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo service nscd restart') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- Review all troubleshooting steps and ensure platform parity by providing instructions for Windows, Linux, and macOS where applicable.
- Consider adding a short note or table summarizing common DNS cache flush commands for all major operating systems.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-app-service-certificate.md
...s/app-service/configure-ssl-app-service-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for exporting App Service certificates, but the PowerShell example is given its own dedicated section, and a specific FAQ addresses PowerShell usage. There are no Linux-specific tools or shell examples (e.g., bash, OpenSSL), and the CLI instructions, while cross-platform, are not explicitly labeled as Linux-friendly. The overall structure and examples may give the impression of a Windows-first or PowerShell-preferred workflow.
Recommendations
- Add explicit Linux/macOS shell (bash) examples for certificate export, including using OpenSSL to handle .pfx files.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Include troubleshooting or FAQs for Linux users, such as handling .pfx files or installing certificates on Linux-based systems.
- When presenting multiple command-line options, consider listing Azure CLI (cross-platform) before PowerShell to avoid a Windows-first impression.
- Mention common Linux tools (e.g., keytool, OpenSSL) where relevant, especially in sections about certificate export and installation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a 'windows_first' bias by providing detailed ASP.NET Core and ASP.NET Web Forms (Windows-centric) code samples before other platforms. There are no explicit Linux command-line or configuration examples (e.g., for Apache/Nginx, OpenSSL, or Linux shell), and the focus is on .NET/Windows patterns. While Node.js, Java, and Python samples are included, there is no guidance for Linux-specific TLS mutual authentication setup or validation outside the Azure App Service context.
Recommendations
- Add Linux-native command-line examples (e.g., using OpenSSL, curl, or wget) to demonstrate client certificate creation, validation, and testing.
- Include guidance or references for configuring mutual TLS in common Linux web servers (e.g., Nginx, Apache) when running on App Service for Linux.
- Provide parity in code samples by including examples for popular Linux-first frameworks (e.g., FastAPI, Go, Ruby on Rails) and shell scripting.
- Clarify that the .NET examples are cross-platform, or provide explicit instructions for running them on Linux if applicable.
- Ensure that any tool or UI references (such as Azure CLI) are shown with both Windows and Linux shell syntax where differences exist.
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 compatible with .NET and Azure App Service, but it does not explicitly mention or provide examples for Linux-based development environments or deployment scenarios. The instructions reference GitHub Codespaces (which is Linux-based) and the Azure Developer CLI (which is cross-platform), but there are no explicit Linux shell commands, nor is there any mention of Linux-specific considerations. All code and deployment steps are shown in a way that is neutral but implicitly assumes familiarity with Windows/.NET workflows. There are no PowerShell-specific commands, but the lack of Linux/Bash-specific examples or troubleshooting tips may disadvantage Linux users.
Recommendations
- Explicitly mention that the tutorial works on both Windows and Linux environments, and clarify any OS-specific prerequisites.
- Provide Bash shell equivalents for any terminal commands, especially for deployment and running the app.
- Include notes or troubleshooting tips for common Linux development environments (e.g., WSL, Ubuntu, Docker containers).
- If any steps differ for Linux (such as file paths, environment variable syntax, or permissions), call these out in side notes or callouts.
- Add a section or appendix with Linux-specific setup instructions for .NET and Azure CLI if not already covered elsewhere.
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 .NET and Azure App Service, which are cross-platform, but it implicitly favors Windows-centric workflows. It references GitHub Codespaces (which is Linux-based) but does not provide any explicit Linux or macOS terminal commands, troubleshooting, or deployment guidance. There are no examples or notes for Linux users regarding environment setup, file paths, or alternative tools. The use of Azure Developer CLI (azd) and dotnet CLI is cross-platform, but the lack of explicit Linux guidance or parity checks may leave Linux users with unanswered questions.
Recommendations
- Explicitly state that all CLI commands (dotnet, azd) work on Linux, macOS, and Windows, and provide any necessary prerequisites for Linux (e.g., installing .NET SDK, azd).
- Add a section or notes for Linux/macOS users, including common troubleshooting tips (e.g., file permissions, case sensitivity, environment variables).
- If referencing 'Open in Browser' or similar UI actions, clarify how to do this from a Linux terminal or Codespaces environment.
- Where file paths are mentioned, use forward slashes or note that paths are the same on all platforms.
- If there are any platform-specific differences (e.g., environment variable syntax, deployment steps), call them out explicitly.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-zip.md
...zure-docs/blob/main/articles/app-service/deploy-zip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias, primarily by referencing Windows paths and tools first, and by providing more detailed instructions for Windows-specific features (such as the Kudu UI, which is not available for Linux). Windows paths are often mentioned before Linux equivalents, and the Kudu UI workflow is only supported on Windows, with Linux users directed to alternative methods. However, most command-line examples (Azure CLI, cURL) are cross-platform, and Linux paths are included where relevant.
Recommendations
- When mentioning default deployment paths, list Linux and Windows paths together or mention Linux first if the majority of users are on Linux.
- Clarify the availability of features (such as the Kudu UI) for both Windows and Linux early in the relevant sections, and provide direct Linux alternatives in the same flow rather than as afterthoughts.
- Where a feature is Windows-only (e.g., Kudu UI), provide a step-by-step Linux alternative (such as using the ZIP deploy API or FTP) in parallel, not just as a note.
- Ensure that all examples and instructions are explicitly cross-platform where possible, and avoid assuming the user is on Windows unless the feature is truly exclusive.
- Consider adding a summary table or section at the top that clearly outlines which deployment methods are available for Windows and Linux App Service plans.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-openid-connect.md
...github-actions/deploy-github-actions-openid-connect.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides deployment examples for multiple platforms and languages. However, for the ASP.NET (classic) tab, the example exclusively uses a Windows runner (runs-on: windows-latest) and Windows-specific tools (NuGet, MSBuild with Windows path syntax), without offering a Linux-based alternative. In contrast, all other language tabs (including ASP.NET Core) use Ubuntu runners and cross-platform tooling. The ASP.NET example is also presented before the Java, Node.js, and Python examples, reinforcing a 'windows_first' bias for .NET technologies.
Recommendations
- Provide a Linux-based example for ASP.NET (classic) using Mono or .NET Core-compatible tooling if possible, or clarify that Windows is required and explain why.
- If Windows is required for ASP.NET (classic), explicitly state this in the documentation to avoid confusion.
- Consider reordering or grouping examples so that Windows-specific instructions do not appear to be the default or primary approach.
- Where possible, mention cross-platform alternatives to Windows tools (e.g., dotnet CLI instead of MSBuild/NuGet) or explain the platform limitations.
- Ensure parity in detail and clarity across all language/platform tabs, so Linux users do not feel secondary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-azure-portal-1.md
...ncludes/quickstart-python/deploy-zip-azure-portal-1.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions using GUI navigation in the Azure portal, which is platform-neutral in appearance, but does not mention or provide examples for command-line alternatives. This omission can disadvantage Linux users who may prefer or require CLI-based workflows (e.g., Azure CLI, Bash scripting), especially since Windows users are often more accustomed to GUI-based instructions.
Recommendations
- Add equivalent instructions using the Azure CLI (az webapp config appsettings set ...) with Bash examples.
- Explicitly mention that the steps can be performed via CLI or PowerShell, and link to relevant documentation for both.
- Ensure that future documentation includes both GUI and command-line instructions to serve users on all platforms equally.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-2.md
...tart-python/create-app-service-visual-studio-code-2.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions that are platform-neutral in wording but implicitly assumes a graphical user interface (GUI) workflow typical of Windows environments. There are no explicit Linux or command-line alternatives mentioned, and the steps may not be as clear for Linux users who might prefer or require CLI-based instructions.
Recommendations
- Add explicit instructions or notes for Linux users, such as how to perform the same actions using the Azure CLI.
- Include screenshots or examples from both Windows and Linux environments if the GUI differs.
- Clarify whether the steps are identical across platforms, and if not, provide platform-specific guidance.
- Mention any prerequisites or differences in setup for Linux users (e.g., installation of VS Code and Azure Tools on Linux).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-file.md
...-service/includes/quickstart-python/deploy-zip-file.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows instructions (using 7-Zip) before macOS/Linux (using the zip utility) in the section on creating a ZIP file, and specifically recommends a third-party Windows tool (7-Zip) rather than built-in options. However, the rest of the documentation is largely cross-platform, with Azure CLI and cURL examples that work on all OSes.
Recommendations
- Present macOS/Linux and Windows instructions in parallel tabs or alternate the order to avoid always listing Windows first.
- For Windows, mention built-in zip support (e.g., via File Explorer's 'Send to > Compressed (zipped) folder') before recommending third-party tools like 7-Zip.
- Ensure all screenshots and examples have Linux/macOS equivalents where possible.
- Explicitly state that Azure CLI and cURL commands are cross-platform, and provide any OS-specific notes if needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-visual-studio-code-1.md
.../quickstart-python/stream-logs-visual-studio-code-1.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation only describes enabling streaming logs via the Azure Tools for VS Code extension, which is a GUI tool commonly used on Windows. There are no instructions or examples for enabling streaming logs using command-line tools or methods commonly used on Linux systems.
Recommendations
- Add instructions for enabling streaming logs using the Azure CLI, which is cross-platform and commonly used on Linux.
- Provide examples for enabling streaming logs via the Azure Portal, which is platform-agnostic.
- Explicitly mention that the VS Code extension is available on all platforms, if relevant, or provide alternative steps for Linux users who may not use VS Code.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-service-principal.md
...hub-actions/deploy-github-actions-service-principal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides deployment examples for multiple platforms. However, the ASP.NET (not Core) example is Windows-specific: it uses 'runs-on: windows-latest', relies on Windows-only tools (NuGet, MSBuild), and uses Windows path syntax. This is the only example that is Windows-exclusive; all other stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) use 'runs-on: ubuntu-latest' and cross-platform tooling. The ASP.NET section appears first among .NET examples, potentially reinforcing a Windows-first impression for .NET users.
Recommendations
- Add a Linux-based example for ASP.NET (if possible, e.g., using Mono or .NET Core for legacy apps), or clarify that ASP.NET (not Core) is Windows-only and explain why.
- Reorder sections so that cross-platform or Linux-first examples (such as ASP.NET Core) appear before Windows-only examples.
- Explicitly state in the ASP.NET section that it is Windows-only, and provide guidance for users who want to target Linux.
- Where Windows-specific tools are used (NuGet, MSBuild), mention Linux alternatives or note their absence.
- Ensure parity in detail and clarity between Windows and Linux examples across all stacks.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/build-settings-azure-portal-1.md
...al-nodejs-mongodb-app/build-settings-azure-portal-1.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation uses UI navigation instructions that are tailored to the Azure portal, which is platform-agnostic, but it does not provide any command-line examples. There are no Linux-specific instructions, CLI commands, or references to cross-platform tools. The absence of CLI or Linux examples can disadvantage users who prefer or require non-GUI, scriptable, or Linux-based workflows.
Recommendations
- Add Azure CLI examples for creating or updating application settings, which work across Windows, Linux, and macOS.
- Include PowerShell and Bash script examples for automation.
- Explicitly mention that the Azure portal is accessible from any OS, and provide parity between GUI and CLI instructions.
- Consider linking to documentation that covers both Windows and Linux workflows for managing app settings.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-stream-diagnostic-logs-1.md
...php-mysql-app/azure-portal-stream-diagnostic-logs-1.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides instructions that reference the 'File System' logging option, which is primarily associated with Windows-based App Service plans. There is no mention of Linux-based App Service plans or their equivalent logging configuration, leading to a lack of parity for Linux users.
Recommendations
- Include instructions for configuring application logging on Linux-based App Service plans.
- Clarify whether the 'File System' option is available or behaves differently on Linux versus Windows.
- Provide alternative logging options or tools for Linux users, such as using Azure Blob Storage or Application Insights.
- Add a note or table comparing logging features and configuration steps between Windows and Linux App Service environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-custom-container.md
...in/articles/app-service/quickstart-custom-container.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists Windows-related pivots (Visual Studio, PowerShell, CLI, Azure Portal) before Linux equivalents, and includes a dedicated PowerShell section (a Windows-centric tool) without an equivalent for Linux shells. This ordering and tooling emphasis may signal a Windows-first bias and a heavier focus on Windows-native tools.
Recommendations
- Alternate the order of Windows and Linux pivots or group them together to avoid the perception of prioritizing Windows.
- Add Linux shell (e.g., Bash) or cross-platform CLI examples where PowerShell is used, or provide a Linux shell equivalent pivot.
- Ensure that Linux tools and workflows are given equal prominence and detail as Windows tools.
- Consider a neutral, platform-agnostic introduction before splitting into OS-specific instructions.
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 PowerShell and Azure CLI examples for scripting tasks, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI (which is cross-platform and more common on Linux/macOS). There are no Linux shell-specific examples or explicit mention of Linux environments, and PowerShell is given equal or greater prominence than Azure CLI, which may signal a Windows-first bias.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., bash) where appropriate.
- Add a short section or note for Linux/macOS users, clarifying that all Azure CLI steps are fully supported and providing any OS-specific tips if needed.
- Consider including bash script examples or references for common Linux workflows, especially for tasks like environment variable assignment.
- Reduce reliance on PowerShell-specific instructions or clarify that PowerShell Core is available cross-platform if its use is required.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-connect-msi-azure-database/code-sql-mi.md
...des/tutorial-connect-msi-azure-database/code-sql-mi.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation consistently references Microsoft SQL Server and its client libraries (e.g., Microsoft.Data.SqlClient, mssql-jdbc, ODBC Driver 18 for SQL Server), which are Windows-centric or Microsoft-specific. The Python example assumes the presence of 'ODBC Driver 18 for SQL Server', which is not always available or straightforward to install on Linux. There are no explicit Linux-specific instructions, troubleshooting, or alternative driver suggestions. No PowerShell or cmd.exe examples are present, but the documentation implicitly assumes a Windows/Microsoft ecosystem.
Recommendations
- Add explicit instructions for installing ODBC Driver 18 for SQL Server on Linux and macOS, or mention compatible open-source alternatives (e.g., FreeTDS).
- Include troubleshooting notes for common Linux issues (e.g., driver installation, environment variable differences).
- Provide example connection strings or code snippets that work on Linux, including any required driver or authentication configuration differences.
- Clarify cross-platform compatibility of all client libraries and tools mentioned.
- Where possible, mention or link to documentation for non-Windows 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 page shows a subtle Windows bias, primarily by referencing Windows first in quickstart links and not providing explicit Linux-specific instructions or examples for environment setup, deployment, or tooling. While the content is mostly cross-platform (Python/Flask), the quickstart and setup links default to Windows tabs, and there are no Linux shell or deployment examples, nor any mention of Linux-specific considerations.
Recommendations
- Ensure that quickstart and setup links default to neutral or Linux tabs, or provide both Windows and Linux options equally.
- Add explicit Linux (bash) command-line examples for environment variable setup, deployment, and local development.
- Mention Linux-specific tools or patterns (e.g., systemd for service management, Linux file paths) where appropriate.
- Clarify that all steps are cross-platform, and call out any differences for Linux users.
- Include screenshots or portal instructions that are not Windows-centric.