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 1051-1075 of 2121 flagged pages
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
Summary
The documentation page provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are included alongside CLI without clarifying platform parity. There is no explicit mention of Linux-specific tools or shell environments, and PowerShell is a Windows-first tool (though now cross-platform, it is still most familiar to Windows users). The documentation does not provide any Linux shell-specific examples (e.g., bash scripting, jq usage, or curl for REST API), and in the outbound IPv6 section, it notes that outbound IPv6 is only available for Windows apps, with Linux apps limited to IPv4. The overall structure does not prioritize Linux or cross-platform parity in examples or explanations.
Recommendations
- Clearly indicate which commands are cross-platform and which are Windows-specific (e.g., label PowerShell examples as such).
- Provide Linux-native shell examples where possible (e.g., using curl or jq to retrieve properties via the Azure REST API).
- When listing command examples, present Azure CLI (which is cross-platform) before PowerShell, or group them under clear headings for each platform.
- Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide troubleshooting notes for common Linux environments if needed.
- For sections where functionality is Windows-only (such as outbound IPv6), provide a clear roadmap or alternatives for Linux users, or note when parity is expected.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md
...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing installation instructions first for the .NET Core CLI (cross-platform), but then immediately following with instructions for the Visual Studio Package Manager Console, which is Windows-specific and uses PowerShell syntax. There are no explicit Linux or macOS-specific instructions or examples, and the only GUI tool mentioned is Visual Studio, which is primarily a Windows application. No mention is made of Linux-native editors or package managers.
Recommendations
- Explicitly mention that the .NET Core CLI instructions work on Linux and macOS, not just Windows.
- Include examples for installing the NuGet packages using Linux-native package managers or editors (e.g., JetBrains Rider, VS Code).
- Avoid referencing only Windows-specific tools like Visual Studio and the Package Manager Console; if mentioned, provide parity by referencing cross-platform alternatives.
- Add a note clarifying that the PowerShell-based Package Manager Console is only available on Windows, and suggest equivalent steps for Linux users.
- Consider including screenshots or terminal examples from Linux/macOS environments to reinforce cross-platform support.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-performance-degradation.md
...es/app-service/troubleshoot-performance-degradation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as IIS, Procdump, and PowerShell), focusing on .NET/ASP.NET examples, and linking to Windows-centric resources. The Kudu Debug Console section highlights PowerShell and DOS commands, with no mention of Bash or Linux shell support. Diagnostic and profiler instructions are tailored for Windows, and there are no Linux-specific examples or guidance for troubleshooting on Linux-based App Service environments.
Recommendations
- Include Linux-specific troubleshooting steps and examples, such as using Bash in the Kudu console, Linux log file locations, and Linux-compatible diagnostic tools.
- Provide parity in profiler and diagnostic instructions for Linux-based App Service plans (e.g., Application Insights Profiler for Linux, or alternatives).
- Mention Linux equivalents for tools like Procdump (such as gcore or dotnet-dump) and provide links to relevant documentation.
- Balance references to PowerShell with Azure CLI and Bash examples for managing and restarting apps.
- Clarify when instructions or features are Windows-only, and provide alternative steps or notes for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-diagnostic-logs.md
...n/articles/app-service/troubleshoot-diagnostic-logs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by providing more detailed instructions and features for Windows App Service apps, such as web server logging, detailed error messages, and failed request tracing, which are not available or not documented for Linux apps. Linux instructions are present but less detailed, and some features are explicitly marked as Windows-only. Additionally, Windows tools and log formats (e.g., W3C, Log Parser) are mentioned without Linux equivalents.
Recommendations
- Provide equivalent Linux examples and instructions wherever possible, especially for enabling and accessing logs.
- Clearly indicate feature parity or lack thereof between Windows and Linux App Service plans, and suggest alternative approaches for Linux where features are missing.
- Include Linux-native tools or commands for accessing and analyzing logs (e.g., using tail, grep, less, or Azure Storage Explorer on Linux).
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group them under clear subheadings.
- If certain logging features are unavailable on Linux, explicitly state this and provide recommended workarounds or alternatives.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management, but PowerShell is given equal or greater prominence, and is often shown before or alongside CLI. PowerShell is a Windows-centric tool, and its inclusion as a primary example may indicate a bias toward Windows users. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or workflows. The use of PowerShell and references to it as a main automation method may disadvantage Linux-first users, despite Azure CLI being cross-platform.
Recommendations
- Prioritize Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and can be run in native terminals.
- Where PowerShell examples are given, provide equivalent bash shell script examples for Linux users.
- Clarify that Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
- Avoid referring to PowerShell as the default or primary automation tool; instead, present it as an option alongside CLI.
- Add a section or callout for Linux users, highlighting any nuances or best practices for managing access restrictions from Linux environments.
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 First
Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily in the section addressing the identification of Azure Traffic Manager endpoints. It exclusively recommends and provides instructions for a PowerShell script (a Windows-centric tool) to identify non-Azure endpoints, without mentioning or providing alternatives for Linux/macOS users (such as Azure CLI, Bash, or cross-platform scripts). Additionally, the step-by-step instructions for running the script assume a PowerShell environment, and there is no guidance for users on other operating systems. In other sections, while Azure CLI and REST API are referenced, there are no explicit shell or command-line examples, and the only explicit script-based example is Windows/PowerShell.
Recommendations
- Provide equivalent Azure CLI or Bash scripts for identifying Traffic Manager endpoints, or at least mention how Linux/macOS users can achieve the same result.
- When referencing scripts or tools, indicate their platform compatibility and, where possible, offer cross-platform alternatives.
- Include explicit instructions or examples for Linux/macOS users alongside PowerShell/Windows instructions.
- If a PowerShell script is the only available tool, clarify how it can be run on Linux/macOS (e.g., using PowerShell Core), or provide a note about its limitations.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by providing PowerShell automation examples and referencing Azure PowerShell scripts, while Linux-specific automation (such as Bash or shell scripting) is not shown. The 'Automate with scripts' section lists Azure CLI and PowerShell, but the PowerShell example is shown inline, whereas the CLI example is only linked. There are no explicit Linux command-line or scripting examples, and no mention of Linux tools or workflows for certificate management. The only Linux-specific reference is a link to a Node.js configuration guide, which is not prominent.
Recommendations
- Provide explicit Bash or shell script examples for Linux users in the 'Automate with scripts' section, similar to the PowerShell example.
- Ensure Azure CLI examples are shown inline, not just as links, to give Linux users parity with PowerShell users.
- Mention common Linux tools (such as OpenSSL) for certificate management and provide example commands for uploading or converting certificates.
- Balance references to platform-specific guides (e.g., include links to Linux, macOS, and Windows guides for language-specific configuration).
- Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid showing only Windows browser UIs if possible).
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 page demonstrates a Windows bias by providing PowerShell examples alongside Azure CLI, mentioning Windows-specific support (e.g., outbound IPv6), and omitting explicit Linux shell or Bash examples where appropriate. Windows/Powershell commands are presented before or alongside CLI, but there are no Linux-specific instructions or clarifications, and Windows-specific features are highlighted without Linux parity.
Recommendations
- For every PowerShell example, provide an equivalent Bash/Linux shell example, especially for commands that can be run locally (e.g., using curl, dig, or nslookup).
- When listing command-line examples, present Azure CLI (cross-platform) first, and PowerShell second, or clarify that both are supported equally.
- Where features are Windows-only (such as outbound IPv6), clearly state the Linux status and provide alternative guidance or a roadmap for Linux users.
- Include explicit Linux/Bash instructions for common administrative tasks, such as querying properties with jq or using REST APIs directly.
- If referencing tools or environments (like Cloud Shell), clarify that both Bash and PowerShell are available and show examples for both.
- Review all screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid showing only Windows-style file paths or dialogs).
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows (e.g., Visual Studio deployment to Windows App Service) and omitting explicit Linux deployment examples or Linux-specific tooling. References to Visual Studio and Kudu are made without clarifying Linux compatibility or providing equivalent Linux-first guidance. There is no mention of Linux App Service or cross-platform deployment nuances.
Recommendations
- Add explicit examples and guidance for deploying WebJobs to Linux-based App Service plans, including any differences in supported runtimes, file types, or deployment steps.
- Include Linux-friendly deployment workflows, such as using Azure CLI, GitHub Actions, or zip deployment from a Linux environment, and clarify any platform-specific considerations.
- Mention cross-platform editors and tools (e.g., VS Code, command-line tools) alongside Visual Studio, and avoid implying that Visual Studio is the primary or only supported tool.
- Clarify Kudu's availability and feature parity on Linux App Service plans, or provide alternative troubleshooting/monitoring guidance for Linux.
- Ensure that all examples and references are inclusive of both Windows and Linux environments, or clearly indicate when a feature or workflow is Windows-specific.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md
...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for the required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console (PowerShell-based), but it lists the Visual Studio/PowerShell method second. However, there is a subtle bias in that the Package Manager Console is a Windows/Visual Studio-specific tool, and there is no explicit mention of Linux or macOS environments beyond the .NET Core CLI. The documentation does not provide Linux-specific guidance or examples, nor does it mention cross-platform editors or tools outside of Visual Studio.
Recommendations
- Explicitly mention that the .NET Core CLI commands work on Windows, Linux, and macOS, and recommend it as the primary cross-platform installation method.
- Add instructions for installing the packages using other cross-platform editors (e.g., Visual Studio Code) or via editing the project file directly.
- Clarify that the Package Manager Console is specific to Visual Studio on Windows, and suggest alternatives for Linux/macOS users.
- Consider providing a table or section that summarizes installation options for different operating systems and development environments.
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
Summary
The documentation page exhibits a moderate Windows bias. While it provides Azure CLI examples (which are cross-platform), it also includes Azure PowerShell examples without equivalent Bash or Linux-native alternatives. In sections where both CLI and PowerShell are shown, PowerShell is always presented after CLI, but no explicit Linux shell scripting or command-line examples (other than Azure CLI) are given. The only native OS-level command shown is 'nslookup', which is cross-platform. However, in the context of outbound IPv6 support, the documentation explicitly states that outbound IPv6 is only available for Windows apps, with no Linux support, and does not provide Linux-specific guidance or alternatives.
Recommendations
- For every Azure PowerShell example, provide an equivalent Bash/Linux shell example where possible, especially for common administrative tasks.
- Clarify in the outbound IPv6 section whether Linux support is planned or provide a workaround or alternative for Linux users.
- Where Azure CLI is shown, consider explicitly noting its cross-platform nature and, if relevant, provide example outputs from both Windows and Linux terminals.
- If there are any differences in behavior or limitations between Windows and Linux App Service plans (as with outbound IPv6), summarize these in a comparison table for transparency.
- Avoid presenting PowerShell as the only or primary scripting option; ensure parity with Bash or other Linux-native tools where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Script automation examples are provided for Azure CLI and PowerShell, with PowerShell (a Windows-centric tool) being highlighted with inline code, while no explicit Linux shell (e.g., Bash) or cross-platform scripting examples are shown. The automation section lists PowerShell after Azure CLI, but the code sample is only for PowerShell. There are no explicit Linux command-line or OpenSSL certificate management examples, and no mention of Linux-specific tools or workflows. The documentation does reference a Linux Node.js configuration guide, but only in the context of application code, not certificate management or binding.
Recommendations
- Add explicit Bash or shell script examples for certificate binding and management, especially for automation.
- Provide OpenSSL command-line examples for certificate creation and manipulation, as these are common on Linux.
- Ensure that all PowerShell examples are paired with equivalent Azure CLI or Bash examples, and present them side-by-side.
- Reference Linux-native tools and workflows where appropriate, such as using SCP/SFTP for certificate upload.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide installation links for non-Windows platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjob-types.md
...es/app-service/includes/webjobs-create/webjob-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows file types and tools (cmd, bat, exe, PowerShell) first and in greater detail, while Linux support is described more generically and with fewer examples. Windows-specific tools and patterns are mentioned explicitly, whereas Linux examples are minimal and lack parity in detail.
Recommendations
- Provide equally detailed lists of supported file types for Linux, including examples for Bash (*.sh*), Python (*.py*), Node.js (*.js*), Java (*.jar*, *.war*), and other common Linux scripting/programming languages.
- Include Linux-specific tools or patterns where relevant, such as mentioning shell scripts, Python, Perl, or Ruby scripts.
- Ensure that for every Windows example (e.g., PowerShell, cmd), there is a Linux equivalent (e.g., Bash, Python) with comparable detail.
- Avoid listing Windows file types and tools first by default; consider presenting both platforms in parallel or in alphabetical order.
- Clarify that runtimes for Linux file types are also pre-installed or specify any requirements, matching the detail given for Windows.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows (such as Visual Studio deployment to Windows App Service) and omitting explicit Linux deployment or management examples. References to deployment and development are focused on Visual Studio and Windows App Service, with no mention of Linux-specific approaches or parity in tooling. There are no Linux command-line or deployment examples, and the documentation does not clarify cross-platform differences or provide guidance for Linux users.
Recommendations
- Add explicit examples and instructions for deploying and managing WebJobs on Linux-based App Service plans, including command-line (Azure CLI) and cross-platform tooling.
- Mention and demonstrate cross-platform editors and deployment methods (e.g., VS Code, GitHub Actions, Azure CLI) alongside Visual Studio.
- Clarify any differences or limitations between Windows and Linux App Service plans regarding WebJobs support and features.
- Provide Linux shell (bash) examples for common tasks, not just Windows/PowerShell or Visual Studio workflows.
- Ensure that references to Windows-specific tools (e.g., Visual Studio) are balanced with Linux-friendly alternatives and that both are presented equally in documentation and quickstart links.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md
...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Visual Studio and PowerShell-based installation instructions before (and in addition to) cross-platform .NET CLI instructions. There are no explicit Linux or macOS-specific instructions or examples, and the Package Manager Console (PowerShell-based) is highlighted as an alternative to the .NET CLI, which is cross-platform. No Linux-specific tools, terminal commands, or environment considerations are mentioned.
Recommendations
- Explicitly mention that the .NET CLI commands work on Windows, Linux, and macOS, and recommend it as the primary cross-platform method.
- Add Linux/macOS-specific instructions or notes, such as using a terminal or shell to run the .NET CLI commands.
- Avoid presenting Windows/Visual Studio/PowerShell instructions before cross-platform alternatives; consider listing .NET CLI first and PowerShell/Visual Studio as optional for Windows users.
- Include a brief section or note on any platform-specific considerations for Linux/macOS users (e.g., environment variable configuration, shell differences, or prerequisites).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-webjobs.md
...ocs/blob/main/articles/app-service/tutorial-webjobs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windowscode Links
Summary
The documentation demonstrates a mild Windows bias, primarily by referencing Windows-specific concepts and links (such as 'windowscode' in supported file types and CRON expression documentation) across all language pivots. The .NET example, which is often the default or first shown, uses a cross-platform approach (dotnet CLI and bash scripts), but the documentation and links consistently refer to Windows-centric resources. There are no explicit PowerShell examples or exclusive use of Windows tools in the code samples, and most language pivots use bash scripts, suggesting an effort to support Linux scenarios. However, the persistent use of 'windowscode' in documentation links and the lack of explicit Linux/Windows distinctions in file type support or troubleshooting may confuse Linux users or suggest Windows is the primary/assumed environment.
Recommendations
- Update all documentation links (e.g., supported file types, CRON expressions) to either be platform-neutral or provide both Linux and Windows tabs, ensuring Linux users are not directed to 'windowscode' sections by default.
- Clarify in the prerequisites and relevant sections whether the instructions apply to both Windows and Linux App Service plans, and highlight any differences or caveats.
- Where possible, provide explicit Linux and Windows examples or notes if there are platform-specific steps, especially for packaging, file permissions (e.g., making run.sh executable), and troubleshooting.
- Review and update terminology and screenshots to ensure parity and inclusivity for both Windows and Linux users.
- Consider adding a section or note about running WebJobs on Linux, including any limitations, best practices, or differences from Windows hosting.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell automation script but not an equivalent Bash or Linux shell script. The 'Automate with scripts' section lists Azure CLI and PowerShell, but the PowerShell example is shown directly, while the Azure CLI is only linked. There are no explicit Linux or cross-platform shell examples, and the scripting guidance implicitly prioritizes Windows tooling and patterns.
Recommendations
- Provide explicit Bash or Linux shell script examples for automating certificate binding, alongside PowerShell.
- Show Azure CLI commands inline, not just as a link, to give equal visibility to cross-platform tooling.
- Include notes or sections that clarify all steps can be performed from Linux/macOS as well as Windows.
- Where scripting is referenced, ensure both PowerShell and Bash/CLI examples are present and equally prominent.
- Review screenshots and UI references to ensure they are not Windows-specific or, if they are, provide Linux/macOS equivalents where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-storage.md
...cles/app-service/scenario-secure-app-access-storage.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation prioritizes Windows development environments by providing Package Manager Console (PowerShell-based) instructions and referencing Visual Studio (a Windows-centric IDE) before or instead of Linux alternatives. There are no explicit instructions or examples for Linux users, such as using the .NET CLI on Linux, or alternative editors like VS Code. The focus on Windows tools and lack of Linux-specific guidance may hinder parity and accessibility for Linux developers.
Recommendations
- Add explicit Linux instructions for installing the required NuGet packages using the .NET CLI, and clarify that these commands work cross-platform.
- Mention and provide examples for using cross-platform editors like Visual Studio Code, including how to open a terminal and run .NET CLI commands.
- Reorder sections so that cross-platform (CLI-based) instructions appear before Windows/Visual Studio-specific instructions.
- Clearly state which steps are Windows-specific and which are cross-platform, to help Linux and macOS users navigate the tutorial.
- If possible, include screenshots or terminal output from Linux environments to demonstrate parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools and workflows. Package installation instructions are given for the .NET Core CLI (cross-platform) and then for the Visual Studio Package Manager Console, which is Windows-only and uses PowerShell syntax. There are no explicit Linux or macOS-specific instructions, nor is there mention of Linux-native editors or workflows. The documentation assumes Visual Studio and Windows-centric tools as the default development environment.
Recommendations
- Add explicit instructions for Linux and macOS users, such as using VS Code or JetBrains Rider as alternatives to Visual Studio.
- Clarify that the .NET Core CLI commands work on Windows, Linux, and macOS, and consider listing them first.
- Provide terminal commands for installing packages using the .NET CLI as the primary method, and mention Visual Studio/PowerShell as an alternative.
- Include notes about file paths and environment differences (e.g., appsettings.json location, directory separators) between Windows and Linux/macOS.
- Avoid assuming Visual Studio as the default IDE; mention cross-platform editors and workflows.
- Where UI navigation is described (e.g., in Azure portal), clarify that these steps are platform-agnostic.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are given equal prominence and are not explicitly marked as Windows-only, which may confuse Linux/macOS users. There are no explicit Linux shell or Bash alternatives for PowerShell commands, and the documentation does not clarify that Azure PowerShell is primarily a Windows tool. Additionally, outbound IPv6 support is noted as being available only for Windows apps, with no Linux parity or roadmap mentioned.
Recommendations
- Clearly indicate that Azure PowerShell commands are primarily for Windows environments, and recommend Azure CLI for cross-platform use.
- Provide Bash or shell script equivalents for PowerShell commands where possible, or clarify when no equivalent exists.
- In sections where both CLI and PowerShell are shown, present the Azure CLI (cross-platform) example first, and PowerShell second.
- Explicitly state the platform limitations for outbound IPv6 support and, if possible, provide a roadmap or alternatives for Linux users.
- Add a note or table summarizing which tools/commands are cross-platform and which are Windows-specific.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md
...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for the required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console (PowerShell). However, the Package Manager Console (a Windows/Visual Studio-specific tool) is given equal prominence to the cross-platform .NET CLI, and no explicit Linux or non-Windows development environment guidance is offered. There are no Linux-specific instructions or terminal examples, and the Visual Studio workflow is highlighted, which is Windows-centric.
Recommendations
- Clearly indicate that the .NET Core CLI instructions are cross-platform and preferred for Linux/macOS users.
- Add explicit Linux/macOS terminal instructions (e.g., using bash/zsh) for installing packages.
- De-emphasize or move the Visual Studio/Package Manager Console (PowerShell) instructions to a secondary position, or label them as 'Windows/Visual Studio only'.
- Include a note or section on developing and running the sample on Linux (e.g., using VS Code, JetBrains Rider, or the terminal).
- Ensure that all tooling and workflow steps are described in a platform-neutral way unless a step is truly Windows-specific.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell automation examples and mentioning them before Linux/CLI alternatives. The 'Automate with scripts' section lists Azure CLI and PowerShell, but only provides an inline PowerShell code snippet, with no equivalent Bash or Linux shell example. There is no mention of Linux-specific tools or workflows for certificate management, and the documentation does not provide parity for Linux users in automation or command-line instructions.
Recommendations
- Provide Bash or Linux shell script examples alongside PowerShell in the 'Automate with scripts' section.
- Ensure that Azure CLI examples are as prominent and detailed as PowerShell examples, including inline code snippets.
- Mention Linux tools or workflows (such as OpenSSL for certificate handling) where relevant, especially in sections discussing uploading or generating certificates.
- Review the ordering of automation/script sections to avoid always listing Windows/PowerShell first.
- Include links to Linux-specific configuration guides where appropriate, not just in language-specific FAQs.
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. It prioritizes .NET/ASP.NET (Windows-centric) examples, uses Windows-specific terminology (such as 'App Service' and 'X-ARR-ClientCert'), and provides detailed C#/.NET code samples before other languages. There is no explicit mention or example of using Linux-native tools (such as OpenSSL or curl) for certificate handling, nor are there shell or Bash command-line examples. The overall structure and sample order suggest a Windows-first approach, with Linux parity present but not foregrounded.
Recommendations
- Add Linux/Bash command-line examples for enabling client certificates (e.g., using Azure CLI from Bash, not just Cloud Shell).
- Include OpenSSL-based examples for certificate inspection and validation, especially in the 'Access the client certificate' section.
- Provide parity in code sample ordering: alternate or rotate the order of language samples so that Linux-first stacks (Node.js, Python, Java) are not always after .NET.
- Explicitly mention Linux-native tools and patterns where relevant (e.g., using curl with client certificates for testing mutual TLS).
- Clarify that the Azure CLI and Bicep/ARM templates are cross-platform, and provide example shell environments for both Windows and Linux.
- Consider adding a troubleshooting section for common Linux client issues (e.g., curl or wget certificate errors).
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
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI, but no explicit Linux shell or Bash alternatives are given for PowerShell commands. The outbound IP address retrieval section lists Azure PowerShell after Azure CLI, but does not clarify that PowerShell is Windows-centric or provide Linux-native alternatives. Outbound IPv6 support is noted as available only for Windows apps, with no parity for Linux. There is also a lack of Linux-specific troubleshooting or command-line guidance, and no mention of Linux tools (e.g., dig instead of nslookup, or Bash scripting).
Recommendations
- For every PowerShell example, provide an equivalent Bash or Linux-native command (e.g., using Azure CLI in Bash, or REST API with curl).
- Clarify in the documentation when a feature or command is Windows-only, and provide Linux alternatives or workarounds where possible.
- In sections where outbound IPv6 is discussed, explicitly state the lack of Linux support and link to tracking issues or roadmaps for Linux parity.
- Include Linux-native tools in examples (e.g., suggest dig as an alternative to nslookup, or show how to use jq with Azure CLI outputs).
- Add troubleshooting or verification steps that are platform-agnostic or provide both Windows and Linux instructions.
- Review the order of examples to avoid always listing Windows/PowerShell first; alternate or group by platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview.md
.../azure-docs/blob/main/articles/app-service/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation subtly prioritizes Windows by mentioning Windows as the first supported OS in the list ('run them on both Windows and Linux'), and by listing Windows-centric tools (Visual Studio, Azure PowerShell) before or alongside cross-platform or Linux-native alternatives. There are no explicit Linux command-line examples or Linux-specific tools mentioned, and the command-line tooling section lists Azure PowerShell before Azure CLI, which is more cross-platform and Linux-friendly.
Recommendations
- Alternate the order of 'Windows and Linux' mentions to 'Linux and Windows' in some places, or use 'Linux or Windows' to avoid implicit prioritization.
- When listing command-line tools, mention Azure CLI before Azure PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
- Include explicit references to Linux-native tools or workflows (e.g., Bash, shell scripts) where relevant.
- Add examples or links to documentation that demonstrate Linux-based deployment and management workflows.
- Highlight Linux-specific features or benefits where applicable, to balance the focus.