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 1826-1850 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-up.md
...docs/blob/main/articles/app-service/manage-scale-up.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking to Windows-specific App Service pricing details and omitting any mention of Linux-specific scaling workflows, tools, or differences. There are no examples or guidance tailored for Linux-based App Service plans, nor are Linux-specific considerations or links provided.
Recommendations
- Include explicit guidance or notes for scaling Linux-based App Service plans, highlighting any differences or considerations.
- Provide links to both Windows and Linux App Service pricing details and feature matrices.
- Add examples or screenshots that show the experience for Linux-based App Service plans, if different.
- Clarify in the documentation when instructions apply equally to both Windows and Linux, or call out platform-specific steps where relevant.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not explicitly mention or provide examples for Linux or cross-platform environments. All command-line instructions use Azure Developer CLI (azd), which is cross-platform, but there is no mention of Linux-specific considerations, nor are there any screenshots or guidance for Linux users. The use of .NET Blazor and App Service is not inherently Windows-specific, but the absence of Linux parity guidance or explicit cross-platform notes may leave Linux users underserved.
Recommendations
- Explicitly state that all CLI commands (azd, Azure CLI) work on Linux, macOS, and Windows, and provide any prerequisites or installation links for Linux users.
- Include a note or section confirming that the sample app and deployment steps are fully supported on Linux and macOS, not just Windows.
- Add Linux/macOS-specific troubleshooting tips or environment setup notes if there are any known differences (e.g., file permissions, path formats, shell differences).
- If screenshots are shown, consider including at least one from a Linux desktop or terminal to reinforce cross-platform support.
- Mention that Codespaces is a cloud-based, OS-agnostic environment, but also provide instructions for running the sample locally on Linux.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/terraform-secure-backend-frontend.md
...p-service/scripts/terraform-secure-backend-frontend.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only Windows-based examples for the App Service plan and web apps (using azurerm_service_plan with os_type set to 'Windows' and azurerm_windows_web_app resources). There are no Linux equivalents or guidance for deploying Linux web apps, which may lead users to believe that only Windows is supported or recommended for this scenario.
Recommendations
- Include parallel examples using azurerm_linux_web_app and an App Service plan with os_type set to 'Linux'.
- Add a section or note clarifying that the same architecture is supported for Linux web apps, with links to relevant documentation.
- Provide guidance or code snippets for both Windows and Linux scenarios, or use variables to allow easy switching between OS types.
- Ensure that any OS-specific configuration (such as app settings or site_config) is explained for both Windows and Linux web apps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-azure-portal-2.md
...-nodejs-mongodb-app/deploy-local-git-azure-portal-2.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions that are generic but implicitly assume a GUI workflow typical of Windows environments, without mentioning or providing examples for Linux command-line alternatives or workflows. There is no reference to Linux tools or CLI-based deployment methods, which may be more familiar to Linux users.
Recommendations
- Include equivalent instructions for Linux users, such as how to perform the same actions using the Azure CLI or other command-line tools.
- Explicitly mention that the steps apply to both Windows and Linux environments, or provide separate sections/examples for each.
- Add screenshots or examples from Linux desktops or terminal sessions to ensure parity.
- Reference Linux-friendly deployment patterns, such as using Git from the terminal, alongside GUI instructions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/configure-startup-azure-portal-2.md
.../quickstart-python/configure-startup-azure-portal-2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions that are tailored to a graphical user interface (GUI) commonly associated with Windows environments, without mentioning equivalent steps for Linux users or command-line alternatives. There is no reference to Linux tools or terminal-based workflows.
Recommendations
- Include instructions for restarting the web app using the command line (e.g., Azure CLI, Bash) for Linux users.
- Explicitly mention if the steps apply to both Windows and Linux, or provide separate sections for each platform.
- Add screenshots or descriptions for Linux environments if the GUI differs, or clarify that the web portal is platform-agnostic.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/remove-resource-group-visual-studio-code-2.md
...t-python/remove-resource-group-visual-studio-code-2.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation describes using a right-click context menu to delete a resource group, which is a pattern typical of Windows GUI applications. There is no mention of equivalent actions for Linux users, such as command-line instructions or alternative interfaces.
Recommendations
- Include instructions for deleting a resource group using the command line (e.g., Azure CLI or Bash), which is platform-agnostic and accessible to Linux users.
- If a GUI is required, clarify whether the instructions apply to cross-platform tools (such as VS Code) or are specific to Windows-only tools.
- Provide Linux-specific or neutral examples alongside Windows GUI instructions to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-azure-portal-1.md
...cludes/quickstart-python/stream-logs-azure-portal-1.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes use of the Azure portal's GUI, which is more commonly associated with Windows workflows. There are no examples or instructions for enabling streaming logs using command-line tools like Azure CLI or PowerShell, nor is there any mention of Linux-specific approaches or parity.
Recommendations
- Add instructions for enabling streaming logs using Azure CLI, which is cross-platform and commonly used on Linux.
- Include PowerShell examples if relevant, but ensure they are presented alongside CLI/bash examples.
- Explicitly mention that the steps apply to both Windows and Linux App Service plans, or clarify any differences.
- Provide guidance for users who prefer command-line or automated approaches, not just portal-based workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-local-git-azure-portal-3.md
...thon-postgresql-app/deploy-local-git-azure-portal-3.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation references copying the 'Git Clone Uri' for later use but does not provide any platform-specific instructions or examples. There is an implicit bias as there are no Linux/macOS-specific instructions or examples, and the lack of cross-platform guidance may lead users to assume a Windows-centric workflow.
Recommendations
- Add explicit instructions or examples for setting up a Git remote on both Windows (e.g., using PowerShell or Command Prompt) and Linux/macOS (e.g., using Bash).
- Include screenshots or command snippets for both platforms to ensure parity.
- Clarify that the instructions apply to all platforms, or provide separate sections for Windows and Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-get-connection-string-3.md
...-php-mysql-app/azure-portal-get-connection-string-3.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation instructs users to copy a connection string and paste it into a text file, implicitly assuming the use of a GUI and a text editor, which are more common in Windows environments. There are no examples or instructions for Linux users (e.g., using terminal commands or Linux-native editors), and no mention of cross-platform alternatives.
Recommendations
- Provide explicit instructions for both Windows and Linux users, such as how to copy and save the connection string using terminal commands (e.g., echo or cat) on Linux.
- Mention cross-platform text editors (e.g., VS Code, nano, vim) instead of generically referring to a 'text file'.
- Include screenshots or command-line examples for both Windows and Linux environments to ensure parity.
- Avoid assuming a GUI workflow; offer CLI alternatives where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-create.md
...-docs/blob/main/articles/app-service/webjobs-create.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation does not provide any explicit examples or guidance for Linux users. All references to uploading executables or scripts are generic, but the sample file names (e.g., ConsoleApp.zip, ConsoleApp1.zip) and terminology (e.g., 'executable') are strongly associated with Windows development. There is no mention of Linux shell scripts, Python, or other cross-platform script types, nor are there examples or notes about running WebJobs authored on Linux or using Linux tools.
Recommendations
- Include explicit examples for Linux users, such as uploading a .sh (shell script) or Python script, alongside .exe or .bat examples.
- List supported file types with both Windows and Linux script formats (e.g., .exe, .bat, .cmd, .ps1, .sh, .py).
- Provide sample file names and walkthroughs that use Linux-friendly naming and formats (e.g., myscript.sh, myjob.py).
- Add notes or sections clarifying any differences or considerations when deploying WebJobs from Linux environments.
- Ensure screenshots and instructions are not Windows-centric, or provide parallel Linux examples where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-java.md
...docs/blob/main/articles/app-service/quickstart-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page uses zone pivots to separate instructions for different Java stacks. However, for 'java-javase' and 'java-jboss', only Windows-based quickstart includes are referenced, while only 'java-tomcat' uses a Linux-based quickstart. This results in missing Linux examples for Java SE and JBoss, and Windows instructions are prioritized for these stacks.
Recommendations
- Provide equivalent Linux quickstart instructions for Java SE and JBoss stacks, not just Tomcat.
- Ensure that for each Java stack (Tomcat, Java SE, JBoss), both Windows and Linux deployment examples are available and equally discoverable.
- Review the included markdown files to confirm that Linux instructions are present and up-to-date for all supported Java stacks.
- Consider restructuring the pivots or documentation flow so that Linux and Windows parity is clear and users can easily find instructions for their preferred OS.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/terraform-backup.md
.../main/articles/app-service/scripts/terraform-backup.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively focuses on creating a Windows web app, with no mention of Linux web apps or examples for Linux. All references, resource names, and verification steps are specific to Windows, and there is no guidance or parity for users interested in Linux-based web apps.
Recommendations
- Add a parallel section or quickstart for creating an Azure Linux web app with a backup using Terraform.
- Where possible, generalize instructions and highlight differences between Windows and Linux web apps.
- Provide verification steps and CLI commands for both Windows and Linux web apps.
- Include notes or links to Linux-specific documentation for users who may want to deploy on Linux instead of Windows.
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 contains a minor Windows bias in the troubleshooting section, where only the Windows-specific command ('ipconfig /flushdns') is provided for clearing the DNS cache. There are no equivalent Linux or macOS commands mentioned. No other Windows-specific tools, PowerShell scripts, or patterns are present, and the rest of the documentation is platform-neutral.
Recommendations
- Add equivalent Linux and macOS commands for clearing DNS cache in the troubleshooting section (e.g., 'sudo systemd-resolve --flush-caches' for Linux, 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder' for macOS).
- When providing OS-specific troubleshooting steps, list all major platforms (Windows, Linux, macOS) or link to a cross-platform guide.
- Review any included automation/script sections to ensure parity or note if scripts are cross-platform.
- Continue to avoid Windows-centric terminology or tools unless alternatives are also provided.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-user-identities.md
...pp-service/configure-authentication-user-identities.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides a detailed C#/.NET example for decoding claims, with no equivalent code samples for Linux-oriented languages or scripting environments (e.g., Python, Node.js, Bash). Framework-specific alternatives are listed, but the most detailed guidance and code are for .NET, which is most commonly associated with Windows. There are no Linux/Unix shell or tool examples, and the order of presentation favors Windows-centric technologies.
Recommendations
- Add example code for decoding the X-MS-CLIENT-PRINCIPAL header in popular Linux-first languages such as Python and Node.js.
- Include a Bash or curl command-line example for decoding the header, demonstrating how Linux users can inspect claims.
- Balance the framework-specific alternatives section by providing more detail and code samples for non-Windows stacks (e.g., Java, PHP, Python, Node.js).
- Explicitly mention that all examples are cross-platform unless otherwise stated, and clarify any OS-specific behaviors.
- Consider reordering the framework-specific alternatives to avoid always listing Windows/.NET first.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-key-vault-references.md
...ticles/app-service/app-service-key-vault-references.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuration tasks, but consistently lists the Azure PowerShell examples after the Azure CLI examples. While Azure CLI is cross-platform, the inclusion and prominence of PowerShell (which is historically associated with Windows, though now cross-platform) may still signal a Windows-centric approach. There are no examples or explicit mentions of Linux shell scripting or Linux-specific tools, and troubleshooting guidance is oriented around the Azure portal UI, which is platform-agnostic but may be more familiar to Windows users.
Recommendations
- Explicitly mention that Azure CLI commands are cross-platform and suitable for both Windows and Linux users.
- Where PowerShell examples are provided, consider also providing equivalent Bash shell script examples for Linux users, especially for scripting scenarios.
- Add a note clarifying that all configuration steps can be performed on Linux, macOS, and Windows, and highlight any platform-specific caveats if they exist.
- Include troubleshooting steps that reference command-line tools available on Linux (e.g., using curl or jq for API calls) in addition to Azure portal instructions.
- If referencing PowerShell, clarify that PowerShell Core is available on Linux and macOS, or provide Bash alternatives where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/configure-startup-azure-portal-2.md
.../quickstart-python/configure-startup-azure-portal-2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions using a graphical interface that is typical of Windows environments, without mentioning or providing alternatives for Linux users or command-line methods. There are no examples or guidance for restarting the web app via Linux tools or CLI.
Recommendations
- Include instructions for restarting the web app using the Azure CLI, which is cross-platform.
- Provide examples for both GUI (portal) and command-line methods, clearly labeling each.
- Explicitly mention that the instructions apply to the Azure Portal, which is platform-agnostic, or clarify if the steps are specific to Windows environments.
- Add Linux-specific or general CLI instructions to ensure parity for users on all platforms.
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 are tailored to the Azure App Service interface, which is primarily oriented around Windows-based workflows. There is no mention of Linux-specific options or considerations, nor are there any examples or notes for users deploying on Linux-based App Service environments.
Recommendations
- Add a section or note specifying whether the instructions apply to both Windows and Linux App Service plans.
- If there are differences for Linux-based App Service (such as logging configuration or file system access), provide parallel instructions or links to Linux-specific documentation.
- Include examples or screenshots for both Windows and Linux environments, if the UI or options differ.
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, with most using Ubuntu runners and Linux-native tooling. However, the ASP.NET (not Core) example is Windows-specific, using 'windows-latest' runners and Windows-only tools such as NuGet and MSBuild. This is the only example that is Windows-specific, and it appears before the Java, Node.js, and Python examples, which use Linux runners. There is no Linux/Mono alternative provided for ASP.NET, and Windows tools are required for that workflow.
Recommendations
- Add a Linux/Mono-based example for ASP.NET if feasible, or clarify that classic ASP.NET requires Windows runners due to tooling constraints.
- Explicitly state in the ASP.NET section why a Windows runner is required, to help users understand the platform limitation.
- Consider reordering the sections so that Linux-first or cross-platform frameworks (e.g., .NET Core, Java, Node.js, Python) appear before Windows-only frameworks, to avoid the impression of Windows preference.
- Where possible, mention Linux equivalents or alternatives for Windows tools, or provide guidance for users on non-Windows platforms.
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 command-line export instructions for Azure CLI and Azure PowerShell, with PowerShell given its own section and a dedicated FAQ entry. There are no explicit Linux-specific examples or mentions of Linux tools (such as OpenSSL), and the order of examples places Azure CLI before PowerShell, but both are included. The FAQ references PowerShell specifically, and there are no Linux troubleshooting notes or parity checks. The documentation assumes familiarity with Azure CLI and PowerShell, which are both cross-platform but often more familiar to Windows users, and does not mention Linux-native certificate management patterns.
Recommendations
- Add explicit Linux-native examples, such as using OpenSSL to handle .pfx files after export.
- Include troubleshooting notes for Linux users (e.g., file permissions, installing Azure CLI on Linux).
- In the FAQ, include references to both PowerShell and CLI, and add Linux-specific troubleshooting tips.
- Clarify that Azure CLI and PowerShell are cross-platform, and provide links to installation instructions for Linux.
- Consider providing a 'Linux' tab or section for certificate export and management, showing common Linux workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-key-vault-references.md
...ticles/app-service/app-service-key-vault-references.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuration steps, but consistently lists PowerShell examples after CLI and does not provide any Linux shell-specific (e.g., Bash) examples or mention Linux-native tools. The use of PowerShell is prominent, and there is no explicit parity for Linux shell scripting or guidance for Linux users beyond the CLI. There is also a lack of explicit mention of Linux-specific considerations outside of a brief note regarding outbound networking for Linux apps.
Recommendations
- Provide explicit Bash shell examples alongside Azure CLI and PowerShell, especially for scripting scenarios.
- Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- When presenting command-line examples, alternate the order (e.g., sometimes show Bash/CLI first, sometimes PowerShell) or group them together to avoid a perceived Windows-first bias.
- Include notes or sections that address any Linux-specific behaviors or troubleshooting steps, especially for common scenarios like file system mounting or networking.
- Where PowerShell is used for advanced scripting (e.g., using Invoke-AzRestMethod), provide equivalent Bash/cURL examples if possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-visual-studio-code-2.md
.../quickstart-python/stream-logs-visual-studio-code-2.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation references the VS Code Output window, which is a cross-platform tool, but does not mention or provide examples for accessing logs via terminal or command-line tools commonly used on Linux. There is no mention of Linux-specific workflows or alternatives, and the guidance assumes the use of a graphical interface, which may not be preferred or available on all Linux systems.
Recommendations
- Include instructions or examples for viewing logs using terminal-based tools (e.g., tail, less, cat) for Linux users.
- Clarify that the VS Code Output window is available on all platforms, or provide alternative methods for users who may not use VS Code.
- Add a section or note addressing how to access logs outside of VS Code, particularly for users working in headless or server environments common on Linux.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnetcore-sqldb-app/deploy-from-local-git-azure-portal-2.md
...core-sqldb-app/deploy-from-local-git-azure-portal-2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation uses UI navigation instructions that are generic but implicitly assume a Windows-style interface (e.g., 'menu on the left', 'top menu bar'), and does not provide any Linux-specific guidance or terminal-based alternatives. There are no examples or instructions for performing these actions via CLI, which is more common in Linux environments.
Recommendations
- Add equivalent instructions for performing these actions using the Azure CLI or other cross-platform tools.
- Explicitly mention that the UI steps apply to all platforms, or clarify any platform-specific differences.
- Provide screenshots or examples from both Windows and Linux environments if the UI differs.
- Include a note or section for Linux users, especially if there are known differences or preferred workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell is featured equally or more prominently in advanced scenarios and code samples. In multi-source rules and Azure Front Door restriction examples, only PowerShell is shown, with no equivalent Bash or Linux-native scripting. While Azure CLI (cross-platform) is present, PowerShell is often shown first or exclusively in some advanced sections, which may signal a Windows-centric approach. There are no explicit references to Windows-only tools, but the lack of Bash or Linux shell examples in advanced scenarios and the prominence of PowerShell may disadvantage Linux users.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI (bash/shell) example, especially in advanced scenarios such as multi-source rules and Azure Front Door restrictions.
- In tabbed code sections, alternate the order of Azure CLI and PowerShell examples, or default to Azure CLI first, as it is cross-platform.
- Add explicit Bash/shell script examples where scripting is shown, not just Azure CLI one-liners, to demonstrate Linux-native automation.
- Review all advanced scenario sections to ensure Linux users are not required to translate PowerShell logic themselves.
- Consider adding a short note at the start clarifying that all features are available equally on Linux and Windows, and that both Azure CLI and PowerShell are supported.
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
Windows Tools
Missing Linux Example
Summary
The documentation references the Azure Tools for VS Code extension, which is commonly used in Windows environments, and does not provide alternative instructions or examples for Linux users or command-line approaches. There is no mention of Linux-specific tools or methods.
Recommendations
- Include instructions for enabling streaming logs using the Azure CLI, which is cross-platform.
- Mention how to access streaming logs from the Azure Portal, which is OS-agnostic.
- Clarify that the VS Code extension is available on Linux and macOS, or provide alternative tools if not.
- Add explicit Linux/macOS command-line examples to ensure 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 page demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) before mentioning the Linux equivalent, and by providing more detailed guidance for Windows paths. Linux-specific instructions are only briefly mentioned and lack example commands or context. No Linux shell or tooling examples are provided, and the Linux path format is only described in a note, not in the main instructional flow.
Recommendations
- Present Linux and Windows paths together in all relevant steps, not just in notes. For example, specify both 'C:\home\site\wwwroot\auth.json' (Windows) and '/home/site/wwwroot/auth.json' (Linux) when describing file locations.
- Include explicit Linux examples and commands (e.g., using bash or Linux file paths) alongside Windows examples.
- Avoid assuming the reader is on Windows by default; structure instructions to address both platforms equally.
- Where platform differences exist (such as relative vs. absolute paths), provide clear, parallel examples for both Windows and Linux.
- Consider adding a table or section summarizing platform-specific differences for quick reference.