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 901-925 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/overview.md
...blob/main/articles/app-service/environment/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. Windows is consistently mentioned before Linux in lists of supported workloads and pricing details. Pricing and SKU tables often refer to Windows-specific plans and limitations (e.g., 'Windows container plans don't support memory-intensive SKUs'), while Linux-specific details are less prominent or absent. There are no Linux-specific examples, tools, or guidance, and the documentation does not provide parity in discussing Linux-specific considerations or features.
Recommendations
- Alternate the order of Windows and Linux in lists and tables to avoid implying priority.
- Include Linux-specific examples, guidance, or notes where relevant (e.g., mention any Linux container limitations or features).
- Where Windows-specific limitations are called out, also note any Linux-specific constraints or advantages.
- Add sections or notes highlighting Linux deployment patterns, troubleshooting, or best practices for App Service Environment.
- Ensure parity in documentation by providing equivalent detail for both Windows and Linux workloads, including references to Linux tools or command-line usage where appropriate.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate.md
...main/articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, and Windows-specific tools (IIS, Certreq.exe) are mentioned for certificate export, while Linux equivalents are not. In automation and FAQ sections, PowerShell is listed before CLI, and Windows container limitations are called out, but Linux-specific guidance is minimal or absent.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI or bash example, and present both side by side.
- When mentioning Windows tools like IIS or Certreq.exe for certificate export, also mention Linux/Unix alternatives (e.g., OpenSSL, certutil) and provide corresponding instructions or links.
- In automation and FAQ sections, present Azure CLI and PowerShell options in parallel, or alternate their order to avoid always listing Windows tools first.
- Explicitly call out any differences or limitations for Linux-based App Service plans, and provide Linux-specific troubleshooting or best practices where relevant.
- Ensure screenshots and UI walkthroughs are not Windows-centric and clarify if steps differ for Linux-hosted apps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-managed-certificate-changes-july-2025.md
...e/app-service-managed-certificate-changes-july-2025.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias primarily in the section addressing Azure Traffic Manager endpoints, where only a PowerShell script is provided for identifying non-Azure endpoints. There are no equivalent Bash, Azure CLI, or cross-platform scripting examples for Linux/macOS users. The instructions for running the script explicitly reference PowerShell, and there is no mention of how to achieve the same outcome on non-Windows platforms. Throughout the rest of the document, examples are generally platform-neutral (using REST API and Azure CLI), but the exclusive reliance on PowerShell for a key scenario introduces a significant Windows-centric bias.
Recommendations
- Provide an equivalent Azure CLI or Bash script for identifying non-Azure Traffic Manager endpoints, or at least describe how Linux/macOS users can perform the same check.
- When referencing scripts or tooling, always include cross-platform alternatives or explicitly state if a solution is Windows-only.
- Instruct users on how to run PowerShell scripts on non-Windows platforms (e.g., via PowerShell Core on Linux/macOS), if no alternative exists.
- Review all example commands and scripts to ensure parity between Windows and Linux users, especially for common administrative tasks.
- Consider including a table or section summarizing all available methods (PowerShell, CLI, REST API) for each scenario, indicating platform compatibility.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-discover-net.md
...cles/app-service/app-service-migration-discover-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on discovering ASP.NET web apps hosted on IIS web servers within VMware environments, which are Windows-centric technologies. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps running on Linux. All discovery capabilities and tooling referenced (Azure Migrate appliance, IIS) are Windows-specific, and Linux scenarios are omitted.
Recommendations
- Include information on discovering .NET web apps hosted on Linux servers, such as those running on Apache, Nginx, or Kestrel.
- Provide examples and guidance for using Azure Migrate or other tools to discover Linux-hosted .NET applications.
- Mention Linux environments explicitly in the overview and capabilities sections, clarifying whether and how they are supported.
- If Linux discovery is not currently supported, clearly state this limitation and provide links to relevant feature requests or roadmaps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-encrypt-at-rest-using-cmk.md
...les/app-service/configure-encrypt-at-rest-using-cmk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows evidence of Windows bias primarily through the exclusive mention and linking of Azure Storage Explorer with a Windows-specific tab for generating SAS tokens, without providing equivalent Linux or cross-platform alternatives. There are no Linux-specific instructions or examples for uploading files or generating SAS tokens, and the only tool mentioned for these tasks is Storage Explorer, which is often associated with Windows workflows. All command-line examples use Azure CLI, which is cross-platform, but GUI instructions and links are Windows-centric.
Recommendations
- Include instructions and examples for uploading files and generating SAS tokens using cross-platform command-line tools such as Azure CLI or azcopy, not just Azure Storage Explorer.
- When referencing Azure Storage Explorer, clarify its cross-platform availability and provide Linux/macOS-specific instructions or screenshots where applicable.
- Avoid linking directly to Windows-specific tabs or instructions; instead, provide parallel steps for Linux and macOS users.
- Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnet-framework.md
...les/app-service/configure-language-dotnet-framework.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and management patterns for ASP.NET apps. All runtime version discovery and file system examples use Windows paths and tools (CMD, PowerShell, Kudu), with no mention of Linux equivalents. There are no examples or instructions for configuring or troubleshooting ASP.NET apps running on Linux App Service plans, nor are Linux-specific tools or file paths referenced.
Recommendations
- Add parallel instructions and examples for ASP.NET apps running on Linux App Service plans, including how to check and set runtime versions, and where to find relevant files.
- Include Linux shell (bash) commands and file paths alongside Windows CMD/PowerShell examples, especially for tasks like listing installed runtimes or accessing logs.
- Mention and link to Linux-specific management tools or interfaces (e.g., SSH, Kudu for Linux, or App Service SSH console) where appropriate.
- Clearly indicate which instructions are Windows-specific and provide equivalent guidance for Linux environments.
- Ensure that references to deployment tools (such as Visual Studio) are balanced with cross-platform alternatives (such as Azure CLI, GitHub Actions, or VS Code).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md
...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows with iisnode. All configuration, troubleshooting, and examples are tailored to Windows, referencing Windows-specific tools (IIS, iisnode, web.config, named pipes, Win32 error codes, Kudu CMD/PowerShell). There are no examples or guidance for Linux-based Azure App Service or cross-platform scenarios. Linux equivalents (e.g., process management, logging, debugging, configuration) are not mentioned or linked.
Recommendations
- Add a parallel section or separate guide for Node.js on Azure App Service for Linux, covering best practices, troubleshooting, and configuration.
- Include Linux-specific examples for common tasks (e.g., process management with PM2, logging locations, configuration files like .env or ecosystem.config.js).
- Reference Linux tools and patterns (e.g., systemd, Linux file paths, Bash shell, SSH access) alongside Windows tools.
- When describing troubleshooting steps (e.g., checking logs, debugging, profiling), provide both Windows and Linux command-line instructions.
- Avoid assuming iisnode/web.config as the only deployment model; mention alternatives like Nginx/Apache reverse proxy setups for Linux.
- Link to official Azure documentation for Node.js on App Service for Linux where available.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate-in-code.md
...icles/app-service/configure-ssl-certificate-in-code.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias: Windows-specific instructions and code samples (C#, Java using Windows-MY store) are presented before Linux equivalents, and in greater detail. Windows tools and concepts (certificate store, user profile, Windows-specific environment variables) are emphasized, while Linux instructions are less detailed and often deferred or generic (e.g., 'see the documentation for the respective language or web platform' for non-.NET languages). There is a lack of parity in language coverage and depth for Linux, especially for non-.NET stacks.
Recommendations
- Provide Linux examples alongside Windows examples in all sections, not just in the container section.
- Include code samples for loading certificates in popular languages (Node.js, Python, Java, PHP) on Linux, not just C#.
- Avoid referring users to 'see the documentation for the respective language' for Linux scenarios—offer at least one concrete example per major language.
- Present Windows and Linux instructions in parallel or in clearly separated, equally detailed sections/tabs.
- Clarify when instructions are Windows-specific and offer Linux alternatives immediately, rather than as afterthoughts.
- Balance the use of Windows tools (certificate store, user profile) with Linux-native patterns (file-based certificates, environment variables).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-run-package.md
...s/blob/main/articles/app-service/deploy-run-package.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias by referencing Windows-style paths (e.g., D:\home\site\wwwroot) before Linux equivalents, and by providing detailed operational instructions and examples that are specific to Windows environments. Linux paths are mentioned only parenthetically, and there are no Linux-specific examples or instructions for common deployment scenarios. Additionally, Windows-centric tools and patterns (such as directory structures and path formats) are described in detail, while Linux equivalents are not elaborated.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows examples, including explicit Linux path formats (e.g., /home/site/wwwroot) in all relevant sections.
- When describing directory structures or operational steps, present both Windows and Linux paths equally, rather than mentioning Linux as an aside.
- Include troubleshooting tips and deployment nuances that are specific to Linux environments.
- If there are differences in behavior or requirements between Windows and Linux App Service environments, clearly document them.
- Where possible, use cross-platform tools and commands, or provide platform-specific alternatives (e.g., Bash scripts for Linux, PowerShell for Windows).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/monitor-app-service.md
.../blob/main/articles/app-service/monitor-app-service.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. It references PowerShell as a means to query Azure activity logs, and mentions Visual Studio integration for Application Insights, both of which are primarily Windows-centric tools. There are no explicit Linux or cross-platform command-line examples (such as Bash or Azure CLI), and the order of tool mentions (PowerShell before CLI) suggests a Windows-first approach. No Linux-specific monitoring or troubleshooting patterns are discussed, and there are no examples or references to Linux-native tools or workflows.
Recommendations
- Provide explicit examples using Azure CLI (az) commands alongside or before PowerShell for querying logs and managing monitoring features.
- Mention and demonstrate integration with cross-platform editors and tools (e.g., VS Code, JetBrains Rider) in addition to Visual Studio.
- Include Linux-specific troubleshooting and log access patterns, such as using SSH, tailing logs, or using Linux-native tools.
- Ensure that all monitoring and diagnostic workflows are described in a platform-neutral way, or with parity between Windows and Linux approaches.
- Add examples or links for Linux App Service environments, including how to access logs, set up Application Insights, and monitor metrics from a Linux perspective.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md
...ent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows (such as Visual Studio and right-click actions), omitting explicit Linux or cross-platform instructions for key steps like file creation, package installation, and deployment. CLI alternatives are only linked, not shown inline, and Linux-specific guidance is missing throughout.
Recommendations
- Provide explicit Linux and cross-platform instructions for creating files (e.g., using 'touch' and editing with nano/vim/code) alongside Visual Studio/Windows steps.
- Include .NET CLI commands for project/file creation and NuGet package installation directly in the documentation, not just as links.
- Show how to manage environment variables and app settings using both Azure Portal (GUI) and Azure CLI/PowerShell, with examples for Linux shells.
- Mention and demonstrate code editing using popular cross-platform editors (e.g., VS Code) in addition to Visual Studio.
- Ensure that all steps, especially deployment and configuration, have Linux/macOS equivalents or are clearly marked as cross-platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-backup.md
...e-docs/blob/main/articles/app-service/manage-backup.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used exclusively or before Linux equivalents; file upload instructions and examples reference Windows-style paths; the Kudu DebugConsole and FTP instructions are described in a Windows-centric manner; and PowerShell is mentioned as a scripting option alongside Azure CLI, but no Linux shell or Bash scripting examples are provided. Linux paths and conventions are only mentioned in passing, and there are no explicit Linux command-line or file system examples.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, including Linux file paths (e.g., /home/site/wwwroot) and environment variables.
- When referencing file uploads or directory locations, include both Windows and Linux paths, or clarify the differences for each OS.
- Include Bash or shell scripting examples in addition to PowerShell, and mention Linux-native tools where appropriate.
- Ensure that screenshots and walkthroughs are not exclusively from Windows environments; add Linux-based screenshots or notes.
- Where Kudu DebugConsole or FTP is referenced, clarify how Linux users can access or use these tools, including command-line alternatives.
- In tables and lists, present Windows and Linux information in parallel, rather than Windows-first or Windows-only.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-sidecar-multi-container-apps.md
...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by requiring PowerShell for both the migration script and for decoding base64 strings, providing only PowerShell script examples, and not offering Linux shell or Bash alternatives. The migration script is a PowerShell (.ps1) script, and there are no Bash or shell script equivalents or instructions for Linux/macOS users. The prerequisites and step-by-step instructions assume a Windows environment, potentially excluding or confusing Linux users.
Recommendations
- Provide equivalent Bash or shell script examples for all PowerShell commands, especially for decoding base64 and running migration scripts.
- Offer a Bash version of the migration script or document how to use the script on Linux/macOS (e.g., via PowerShell Core or alternative tooling).
- List prerequisites in a cross-platform manner, mentioning both PowerShell and Bash/shell as options.
- When referencing scripts, provide both .ps1 (PowerShell) and .sh (Bash) versions, or clarify cross-platform compatibility.
- Ensure that all command-line examples (such as for decoding base64) include both Windows (PowerShell) and Linux/macOS (Bash) syntax.
- Explicitly state platform compatibility for all tools and scripts, and provide guidance for users on non-Windows systems.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/operating-system-functionality.md
...articles/app-service/operating-system-functionality.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page is heavily focused on Windows-based App Service apps, with terminology, environment variables, and examples that are specific to Windows (e.g., %SystemDrive%, %ResourceDrive%, IIS, ASP.NET, COM components, registry access, and Windows event logs). Linux is only mentioned briefly in a note, with no equivalent details or examples for Linux-based App Service environments. There are no Linux-specific environment variables, file system paths, or diagnostic/logging mechanisms discussed. Windows tools and patterns (such as PowerShell, IIS, and the Windows registry) are mentioned exclusively, and there are no Linux command-line or shell examples.
Recommendations
- Add parallel sections or notes for Linux-based App Service apps, describing their file system layout, environment variables (e.g., $HOME, /tmp), and storage persistence.
- Provide Linux-specific examples for file access, such as using $HOME/site or /home/site, and clarify differences in temporary storage and persistence.
- Discuss diagnostic and logging mechanisms available in Linux containers (e.g., syslog, stdout/stderr, Azure Monitor integration) and how they differ from Windows.
- Mention Linux-specific process and code execution capabilities (e.g., bash, sh, shell scripts) alongside PowerShell and Windows command shell.
- Clarify the absence of Windows-specific features (like registry and event logs) in Linux environments, and describe any Linux equivalents or alternatives.
- Ensure that Linux tools and patterns are given equal prominence and are not relegated to footnotes or brief mentions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-security.md
...cs/blob/main/articles/app-service/overview-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Static IP restrictions' section, where features and configuration options are described specifically for 'App Service on Windows' (such as web.config and dynamic IP security), with no mention of Linux equivalents or guidance for Linux-based App Service. There are no Linux-specific examples or parity notes, and Windows terminology and tools (like web.config) are referenced without alternatives.
Recommendations
- For every Windows-specific feature or configuration (e.g., web.config, dynamic IP security), explicitly state whether there is a Linux equivalent or if the feature is unavailable on Linux App Service.
- Add Linux-specific examples or configuration guidance where possible, or provide links to relevant Linux documentation.
- When listing features or instructions, avoid leading with Windows-only options unless Linux is not supported; otherwise, present both platforms equally or clarify differences.
- Include a comparison table or section outlining feature parity and differences between App Service on Windows and Linux, especially for security-related features.
- If a feature is not available on Linux, recommend best practices or workarounds for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-per-app.md
...blob/main/articles/app-service/manage-scale-per-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations, with no equivalent examples for Linux shells (such as Bash or Azure CLI). The use of PowerShell-specific cmdlets (e.g., New-AzAppServicePlan, Set-AzAppServicePlan) and the absence of cross-platform or Linux-native tooling (like Azure CLI) may disadvantage users on Linux or macOS. The documentation also introduces PowerShell before any mention of ARM templates, reinforcing a Windows-first approach.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell command-line instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell examples are for Windows users and provide Bash/Azure CLI alternatives for Linux/macOS users.
- Consider reordering sections so that cross-platform tools (like Azure CLI or ARM templates) are presented before or alongside PowerShell.
- Where possible, provide guidance on how to accomplish the same tasks using REST API calls or SDKs, which are platform-agnostic.
- Review and update documentation metadata (such as ms.custom) to reflect support for cross-platform tools, not just Azure PowerShell.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-vnet-integration.md
...main/articles/app-service/overview-vnet-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation displays a mild Windows bias. Windows-specific features (such as Windows Containers and Windows Server Active Directory) are mentioned explicitly, with detailed calculations and limitations, while Linux equivalents are not discussed in similar depth. There is a lack of Linux-specific examples or guidance, except for a brief mention of Linux continuous deployment network dependencies. Windows tools and patterns (e.g., Kudu console, Windows Containers) are referenced without providing Linux alternatives or parity in explanation.
Recommendations
- Provide equivalent Linux container guidance, including subnet/IP calculations and limitations for Linux-based App Service plans.
- Include Linux-specific examples and scenarios, such as how environment variables or networking features are surfaced in Linux environments (e.g., via SSH or Kudu for Linux).
- When referencing Windows-specific features (e.g., Windows Containers, Active Directory), also mention Linux alternatives or explicitly state if not supported.
- Ensure that any tooling or portal instructions (such as Kudu console) clarify whether they apply to both Windows and Linux, or provide Linux-specific instructions where needed.
- Balance the order of presentation so that Linux and Windows are given equal prominence, or clarify when a feature or limitation is OS-specific.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-webjobs.md
...ocs/blob/main/articles/app-service/overview-webjobs.md
High Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by prioritizing Visual Studio and Windows App Service deployment in both the deployment options and next steps. There are no explicit Linux or cross-platform deployment examples, and Visual Studio (a Windows-centric tool) is highlighted before mentioning more platform-agnostic methods. The page also lacks Linux-specific guidance or parity in tooling references.
Recommendations
- Add explicit examples and guidance for deploying WebJobs from Linux/macOS environments using Azure CLI, zip deployment, or other cross-platform tools.
- Balance the deployment section by mentioning Visual Studio and cross-platform methods (e.g., VS Code, CLI, GitHub Actions) together, or list platform-agnostic options first.
- Include references to Linux-compatible development and deployment workflows in the 'Next steps' section, such as using VS Code, Azure CLI, or GitHub Actions.
- Clarify that WebJobs can be developed and deployed from any OS, and provide links to relevant Linux/macOS documentation where available.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-diagnostics.md
...blob/main/articles/app-service/overview-diagnostics.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by frequently specifying features as 'Windows apps only' (e.g., proactive CPU monitoring, proactive auto-healing, Navigator) and providing more detailed descriptions and tool availability for Windows than for Linux. Linux support is mentioned but often as an afterthought, with fewer details and no Linux-specific troubleshooting examples or tool walkthroughs. There are no Linux command-line or shell examples, and the documentation does not provide parity in tool descriptions or usage scenarios for Linux-based App Service apps.
Recommendations
- Provide Linux-specific troubleshooting examples and walkthroughs, including screenshots and step-by-step instructions.
- Ensure that all diagnostic tools and features are clearly marked for both Windows and Linux, with equivalent detail for each platform.
- Add Linux shell/command-line examples where relevant, not just references to Windows or portal-based workflows.
- Where features are Windows-only, explicitly state if and when Linux support is planned, and suggest alternative approaches for Linux users.
- Reorder sections or provide parallel subsections for Windows and Linux to avoid the perception of Windows as the default or primary platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-local-cache.md
...blob/main/articles/app-service/overview-local-cache.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias by referencing Windows file paths (e.g., D:\home), Windows-specific deployment patterns, and tools (such as Kudu/SCM) without providing equivalent Linux examples or clarifying Linux path differences. The only mention of Linux is in the context of unsupported scenarios, and there are no Linux-specific instructions or examples for enabling or managing local cache. Additionally, the documentation refers to Windows containers and provides links for them, but does not offer parity for Linux containers beyond stating their lack of support.
Recommendations
- Include Linux-specific examples and file path references (e.g., /home/site) alongside Windows examples.
- Clarify differences in local cache behavior and configuration between Windows and Linux App Service plans.
- Provide instructions or notes for Linux users, even if the feature is unsupported, to guide them to alternatives (such as App Cache) with clear steps.
- Ensure that all tools and site extension recommendations (like Azure Web Apps Disk Usage) are available or have alternatives for Linux environments, or explicitly state their availability.
- When mentioning unsupported scenarios, provide links or references to Linux-specific documentation or workarounds.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/monitor-instances-health-check.md
...articles/app-service/monitor-instances-health-check.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing features and tooling (such as Process Explorer and diagnostic information collection) that are only available for Windows applications, without mentioning Linux equivalents or clarifying Linux limitations in detail. Several advanced monitoring and diagnostic features are described as Windows-only, and there are no Linux-specific examples or guidance for parity. Additionally, the note about the 'x-ms-auth-internal-token' header being Windows-only is buried, and there are no Linux-specific troubleshooting or configuration examples.
Recommendations
- Explicitly state feature parity or limitations for Linux throughout the documentation, not just in notes.
- Provide Linux-specific guidance or alternatives for features like process monitoring and diagnostic information collection.
- Include Linux examples or clarify when a feature is Windows-only, ideally at the start of each relevant section.
- If a feature is unavailable on Linux, suggest alternative approaches or tools (such as using SSH, Azure Monitor, or Linux-native diagnostic tools).
- Ensure that all code and configuration examples are tested and applicable on both Windows and Linux, or provide separate examples as needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-managed-identity.md
...main/articles/app-service/overview-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive Azure PowerShell examples and references, with some CLI parity but no explicit Linux shell (bash) or cross-platform scripting examples. PowerShell is presented as a primary automation tool, and certain instructions (such as for user-assigned identities in Functions) are only available in PowerShell. There is no mention of Linux-specific tools, nor are bash or shell script examples provided. The CLI examples are present but sometimes marked as 'azurepowershell-interactive', which may confuse Linux users. The documentation implicitly assumes familiarity with PowerShell and Windows-centric tooling.
Recommendations
- Add explicit bash/shell script examples for all CLI operations, ensuring parity with PowerShell instructions.
- Clarify that Azure CLI commands are cross-platform and provide Linux/macOS terminal usage notes where appropriate.
- Avoid labeling CLI examples as 'azurepowershell-interactive' when they are not PowerShell-specific.
- Where PowerShell is the only supported method (e.g., for Functions user-assigned identity assignment), explicitly state the lack of Linux-native support and provide workarounds or roadmap information.
- Include references to Linux-native tools or scripting environments where possible.
- Ensure that CLI and ARM template examples are presented before or alongside PowerShell examples to avoid a 'windows_first' impression.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/samples-resource-manager-templates.md
...cles/app-service/samples-resource-manager-templates.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Examples
Uneven Linux Examples
Summary
The documentation provides both Linux and Windows examples for basic App Service deployments, but Windows examples are often listed before Linux ones and there are more Windows-specific templates (e.g., Windows container, Windows with MySQL/PostgreSQL) than Linux equivalents. Some resource integrations (like database connections) are split into separate Linux and Windows sections, but the general 'App with connected resources' section defaults to Windows. There are no explicit PowerShell or Windows tool biases, but the ordering and coverage favor Windows scenarios.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, alternating their order or grouping them together.
- Add Linux equivalents for all Windows-specific templates, such as Linux container app templates and Linux app with Azure SQL Database.
- Combine 'App with connected resources' into a unified section with both Linux and Windows examples side by side.
- Clearly label which templates are for Linux and which are for Windows in all sections.
- Review for parity in advanced scenarios (e.g., deployment slots, VNet integration, App Service Environment) to ensure Linux is equally represented.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. While Azure CLI examples (which are cross-platform) are provided, PowerShell examples are also given equal prominence, and in some sections, PowerShell is the only non-CLI scripting example. There is no mention of Linux-specific tools or shell environments (e.g., bash, curl, grep) except for a single 'curl' command for IPv6 testing. The documentation refers to the Azure Cloud Shell, which can be used from any OS, but does not clarify that PowerShell commands are Windows-centric. Outbound IPv6 support is noted as 'Windows apps only' without further Linux guidance. No Linux-specific troubleshooting or command-line examples (e.g., using dig instead of nslookup, or bash scripting) are present.
Recommendations
- For every PowerShell example, provide an equivalent bash or Linux shell example where possible, especially for scripting or automation tasks.
- Clarify in the documentation that PowerShell commands are primarily for Windows users, and suggest alternatives for Linux/macOS users.
- Where 'nslookup' is suggested, mention 'dig' as an alternative for Linux users.
- For outbound IPv6 support, explicitly state the current limitations for Linux apps and provide guidance or workarounds for Linux users.
- Include more Linux-native command-line examples (e.g., using curl, jq, grep) for querying and parsing Azure CLI output.
- When referencing the Azure Cloud Shell, note that both Bash and PowerShell environments are available, and provide examples for both.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/template-deploy-private-endpoint.md
...pp-service/scripts/template-deploy-private-endpoint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell example (Remove-AzResourceGroup) for cleaning up resources, with no equivalent command for Linux users (such as Azure CLI or Bash). This suggests a bias towards Windows tooling and omits guidance for users on other platforms.
Recommendations
- Include Azure CLI examples (e.g., 'az group delete --name <your resource group name>') alongside PowerShell commands for resource group deletion.
- When referencing command-line operations, provide both PowerShell and Bash/Azure CLI syntax to ensure cross-platform accessibility.
- Clarify that the Azure Portal and Azure CLI are cross-platform options, and provide links or instructions for each where relevant.