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 1851-1875 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-1.md
...tart-python/create-app-service-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 without clarifying platform compatibility or providing Linux-specific guidance. It implicitly assumes a Windows environment by referencing VS Code extensions commonly associated with Windows workflows, and does not mention Linux installation or usage.
Recommendations
- Explicitly state that the Azure Tools for VS Code extension is available on all platforms, including Linux.
- Provide instructions or screenshots for installing and accessing the Azure Tools extension on Linux.
- Mention any platform-specific considerations or differences in the user interface for Linux users.
Create Pull Request
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# example for decoding user claims, which is specific to .NET (commonly associated with Windows environments), and offers only brief mentions of PHP and Java without code samples. There are no Linux/Unix shell or cross-platform code examples (e.g., Python, Node.js), nor are there instructions for accessing headers in a Linux-native way. The focus on .NET and lack of parity in examples for other platforms indicates a Windows/.NET-first bias.
Recommendations
- Add code examples for popular Linux-friendly languages such as Python (Flask/Django), Node.js (Express), and Bash to demonstrate how to access and decode the X-MS-CLIENT-PRINCIPAL header.
- Provide step-by-step instructions or code snippets for accessing request headers in Linux-native environments, such as Apache or Nginx configurations.
- Ensure that framework-specific alternatives include equal detail and code samples for non-Windows platforms, not just .NET.
- Reorder or balance the presentation so that Windows/.NET examples are not always first, or group examples by language without implied priority.
- Explicitly mention that the process is cross-platform and provide links or references to Linux/Unix-specific documentation where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-apm.md
...in/articles/app-service/configure-language-java-apm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally provides parity between Linux and Windows examples, but there are subtle signs of Windows bias. In some sections, Windows-specific tools (like the Kudu console) are mentioned for Windows, while Linux uses SSH, and in the Application Insights section, the Windows example includes an extra setting (XDT_MicrosoftApplicationInsights_Java=1) not explained for Linux. Additionally, in the Azure CLI section for Application Insights, the instructions for setting app settings show the Linux tab before Windows, but the overall structure and some notes (like retrieving locations) do not clarify OS differences. The documentation does not provide PowerShell-specific examples or exclusively Windows tools, but the mention of Kudu (a Windows-centric tool) and the extra Windows-specific setting indicate a mild Windows bias.
Recommendations
- Provide equivalent explanations for OS-specific settings, such as clarifying the purpose of 'XDT_MicrosoftApplicationInsights_Java=1' for Windows and whether a Linux equivalent is needed.
- Where a Windows-specific tool (like Kudu) is mentioned, suggest a Linux equivalent or clarify if SSH is the recommended approach.
- Ensure that any extra steps or settings for one OS are clearly explained and, if not needed on the other OS, state so explicitly.
- Continue to present Linux and Windows instructions side-by-side, and avoid assuming familiarity with Windows tools or patterns.
- If possible, provide parity in tooling recommendations (e.g., mention cross-platform tools where available).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-security.md
...ticles/app-service/configure-language-java-security.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation page demonstrates a Linux-first bias in the section on Java key store usage, providing detailed instructions and examples specifically for Linux environments, while omitting equivalent instructions or examples for Windows-based App Service environments. There are no PowerShell or Windows tool references, but Linux paths, commands, and behaviors are described exclusively.
Recommendations
- Add a section describing how Java key stores and certificate management work on Windows-based App Service, including default locations, behaviors, and any differences from Linux.
- Provide Windows-specific examples for initializing and loading the Java key store, including file paths and environment variables relevant to Windows.
- Mention how to interact with the Java Key Tool on Windows App Service (e.g., via Kudu console or other supported methods), and reference the appropriate documentation.
- Ensure parity in troubleshooting and manual certificate management instructions for both Linux and Windows environments.
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 tools. 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 cross-platform tools such as the Azure CLI.
- Provide examples for both GUI (Windows) and command-line (Linux/macOS) workflows.
- Clarify which tool or interface is being referenced (e.g., Azure Portal, Visual Studio, etc.), and mention alternatives accessible from Linux.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-configure-credentials.md
...n/articles/app-service/deploy-configure-credentials.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides command-line examples using Azure CLI and Azure PowerShell, but does not include any explicit Linux- or macOS-specific shell examples (e.g., Bash, zsh). While Azure CLI is cross-platform, there are no examples showing usage in a Linux shell environment, and PowerShell is mentioned as an alternative but is traditionally associated with Windows. Additionally, the documentation does not mention or demonstrate Linux-native tools (such as curl, scp, or sftp) for interacting with FTP/S or Git endpoints, nor does it provide Linux-specific guidance for credential usage. The only Linux-specific note is a brief mention of Bash variable interpolation, but no example is provided.
Recommendations
- Add explicit Bash or Linux shell examples for all command-line operations, especially for credential management and Git/FTP/S usage.
- Include examples using Linux-native tools (e.g., curl, sftp, scp) for interacting with deployment endpoints.
- When listing command-line options, present Azure CLI (cross-platform) and Bash/Linux shell examples before or alongside PowerShell.
- Provide guidance or troubleshooting tips specific to Linux environments, such as file permission issues or credential storage.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample terminal outputs from a Linux shell.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation-terraform.md
...articles/app-service/environment/creation-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is present and detailed, which may indicate a slight Windows bias. However, the Azure CLI tab is listed first, and all Terraform commands are platform-agnostic. There are no Linux-specific examples or explicit mentions of Linux tools, but the CLI examples are compatible with Linux/macOS. There are no exclusive Windows tools or patterns, but the inclusion of PowerShell as a primary verification method can be seen as a Windows-centric approach.
Recommendations
- Add explicit mention that Azure CLI commands work on Linux, macOS, and Windows, to reassure non-Windows users.
- Consider including a Bash shell example or tab, especially for common verification steps, to demonstrate parity with Linux environments.
- Clarify that PowerShell is optional and that all steps can be completed using the cross-platform Azure CLI.
- If possible, provide troubleshooting or environment setup notes for Linux/macOS users, especially for file creation and environment variable handling.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-connect-msi-azure-database/code-sql-mi.md
...des/tutorial-connect-msi-azure-database/code-sql-mi.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation assumes the presence of Windows-specific tools (such as 'ODBC Driver 18 for SQL Server') and does not mention Linux compatibility or alternatives. There are no explicit Linux-specific instructions or troubleshooting notes, and the documentation does not clarify cross-platform support for the drivers or environment variables.
Recommendations
- Explicitly state whether the required drivers (e.g., ODBC Driver 18 for SQL Server) are available on Linux and provide installation instructions for Linux distributions.
- Include notes or troubleshooting tips for common Linux issues (such as driver installation, environment variable configuration, or authentication differences).
- Where possible, provide both Windows and Linux installation commands for dependencies.
- Clarify that the code samples are cross-platform (if they are), or specify any platform-specific requirements.
- Mention any Linux-specific tools or patterns that may be relevant for connecting to Azure SQL Database.
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 refers to setting up a Git remote but does not provide any platform-specific instructions or examples. There is an implicit bias as it omits Linux/macOS command-line examples or guidance, which are often necessary for cross-platform parity. The phrasing and lack of explicit Linux instructions may lead users to assume a Windows-centric workflow.
Recommendations
- Add explicit Linux/macOS command-line examples for setting up a Git remote (e.g., using 'git remote add origin <Git Clone Uri>').
- Include both Windows (Command Prompt/PowerShell) and Linux/macOS (bash) command examples side by side where relevant.
- Clarify that the instructions apply to all platforms, or specify any platform-specific steps if needed.
- Ensure future documentation consistently provides parity between Windows and Linux/macOS workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-intelligent-apps-dotnet-to-azure-sql.md
...service/deploy-intelligent-apps-dotnet-to-azure-sql.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation implicitly assumes a Windows development environment by referencing Windows-centric UI actions (e.g., 'Right click', 'click Save'), and does not provide any explicit Linux or cross-platform command-line alternatives for common tasks such as file creation, editing, or package management. There are no PowerShell-specific commands, but the absence of Linux/CLI examples and the use of GUI instructions suggest a Windows-first bias.
Recommendations
- For every step that uses a GUI action (e.g., 'Right click', 'click Save'), provide equivalent command-line instructions suitable for Linux/macOS users (e.g., using 'touch' or 'nano' to create/edit files).
- Explicitly mention that the steps can be performed on Linux/macOS and provide any necessary differences (such as file paths or command syntax).
- If referencing Azure Data Studio or SQL editors, clarify their cross-platform availability and provide installation or usage notes for Linux/macOS.
- Include terminal-based package installation commands (e.g., 'dotnet add package ...') alongside or instead of GUI-based instructions.
- Review all instructions for assumptions about file system navigation or UI elements that may not exist on Linux/macOS, and provide alternatives.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-security.md
...ticles/app-service/configure-language-java-security.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation page demonstrates a Linux-first bias, especially in the sections on Java key store management, where only Linux paths, tools, and instructions are provided. There are no equivalent instructions or examples for Windows-based App Service environments, such as Windows file paths, certificate store handling, or PowerShell/Windows command-line usage. This may leave Windows users without clear guidance for similar tasks.
Recommendations
- Add equivalent instructions for Windows-based App Service environments, including how certificates are loaded into the Java key store on Windows.
- Provide Windows file paths (e.g., %JAVA_HOME%\lib\security\cacerts) and explain any differences in certificate handling between Linux and Windows.
- Include examples of using Windows command-line or PowerShell to interact with the Java key store, such as using keytool on Windows.
- Clarify in each section whether the instructions apply to both Linux and Windows, or specify the differences.
- Ensure parity in troubleshooting and debugging steps for both platforms, such as how to open a remote terminal on Windows App Service.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-linux-open-ssh-session.md
...ticles/app-service/configure-linux-open-ssh-session.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides detailed, step-by-step SSH access instructions and CLI examples exclusively for Linux containers, while Windows containers are only mentioned briefly and lack any equivalent command-line or PowerShell examples. The Windows section is presented first, but it only describes browser-based SSH access and notes that CLI-based SSH is not supported for Windows containers. There are no PowerShell or Windows-native SSH instructions, and the Linux section is much more comprehensive.
Recommendations
- Provide parity in documentation by including equivalent instructions or explicit statements for Windows containers, even if only to clarify limitations (e.g., 'SSH via CLI/PowerShell is not supported for Windows containers').
- If possible, add PowerShell or Windows-native SSH client instructions for Windows containers, or explain why such access is not available.
- Consider presenting Linux and Windows instructions in parallel or with equal prominence, rather than always listing Windows first.
- Explicitly state the differences in SSH support between Linux and Windows containers at the top of the page for clarity.
- If browser-based SSH is the only supported method for Windows containers, provide a detailed walkthrough and screenshots for that scenario, similar to the Linux CLI example.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md
...ain/articles/app-service/app-service-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page generally avoids overt Windows bias, but there are subtle indications. The mention of configuring auto-healing via web.config and references to iisnode settings for Node.js apps are Windows/IIS-specific concepts. While there is a brief mention of running Node.js apps on Linux with PM2, there are no equivalent Linux-native examples for configuring auto-healing or process management outside of Node.js. The documentation does not provide Linux-specific guidance for features like auto-healing or configuration files, and the primary configuration example (web.config) is Windows-centric.
Recommendations
- Provide Linux-native examples for configuring auto-healing, such as using app settings or startup scripts, instead of only referencing web.config.
- When mentioning iisnode or web.config, clarify that these are Windows/IIS-specific and provide equivalent guidance for Linux-based App Service environments (e.g., using PM2, environment variables, or other process managers).
- Include explicit Linux configuration file examples (such as appsettings.json, environment variables, or startup scripts) alongside Windows examples.
- Review all troubleshooting and best practice sections to ensure Linux and Windows parity in examples and tool recommendations.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for managing access restrictions, but PowerShell examples are featured prominently, including in advanced scenarios and inline code blocks. In several places, PowerShell is presented before or alongside Azure CLI, and some advanced examples (such as multi-source rules and Azure Front Door restrictions) are only shown in PowerShell. There are no explicit Linux shell or Bash-specific examples outside of Azure CLI, and the documentation assumes familiarity with PowerShell cmdlets, which are more common in Windows environments.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI (bash-friendly) example, especially in advanced scenarios such as multi-source rules and Azure Front Door restrictions.
- When presenting code tabs, consider listing Azure CLI first or at least alternating the order to avoid implicit prioritization of PowerShell.
- Where possible, provide Bash shell script snippets for common tasks, especially for advanced scenarios currently only shown in PowerShell.
- Clarify in the introduction that all programmatic examples are cross-platform when using Azure CLI, and explicitly mention that PowerShell examples are primarily for Windows users.
- Audit all advanced scenario sections to ensure Linux users have parity in example coverage and guidance.
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 key configuration steps, but consistently lists Azure PowerShell examples after Azure CLI, which is a mild form of 'windows_first' bias. Additionally, the PowerShell examples are given equal prominence to CLI, which can be seen as 'powershell_heavy' since PowerShell is primarily a Windows-centric tool, though it is now cross-platform. There are no Linux-specific shell (bash) examples, nor are Linux-native tools or patterns (such as environment variable export commands or bash scripting) mentioned, but Azure CLI is cross-platform and generally preferred on Linux, so this is not a strong bias. No Windows-only tools or patterns are referenced, and the documentation does mention a Linux-specific configuration caveat, indicating some awareness of Linux scenarios.
Recommendations
- Add explicit bash shell examples for all Azure CLI commands to demonstrate Linux parity and usability.
- Clarify in the introduction that both Azure CLI and PowerShell examples are provided, and that Azure CLI is recommended for Linux/macOS users.
- Where PowerShell is used, note that it is available cross-platform, but provide bash alternatives for Linux users.
- Include troubleshooting steps or notes specific to Linux environments where relevant, such as file permissions or environment variable handling.
- Consider adding a section or callout summarizing differences or additional steps for Linux vs. Windows deployments, if any.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a 'windows_first' bias by providing detailed ASP.NET Core and ASP.NET Web Forms (Windows-centric) code samples before other platforms, and by referencing Windows-specific request properties (e.g., HttpRequest.ClientCertificate) without equivalent Linux or cross-platform details. There is also a 'missing_linux_example' bias: the documentation does not show how to access the client certificate directly in a Linux-native environment (e.g., using NGINX/Apache on Linux), nor does it mention Linux command-line tools (such as OpenSSL) or Linux-specific configuration patterns for mutual TLS. All code samples assume the Azure App Service's forwarding of the certificate via the X-ARR-ClientCert header, which is platform-agnostic, but the narrative and ordering favor Windows/.NET scenarios.
Recommendations
- Add explicit examples or notes for configuring and validating client certificates in Linux-native environments, such as using NGINX or Apache as a reverse proxy in front of App Service (Linux), including relevant configuration snippets.
- Include Linux command-line examples (e.g., using OpenSSL) for generating, inspecting, and testing client certificates, alongside or before any Windows-centric tools.
- Reorder or balance the code sample sections so that Linux-friendly stacks (Node.js, Python, Java) are presented before or alongside Windows/.NET examples, or clarify that the order is not indicative of platform preference.
- Where Windows-specific properties or patterns are mentioned (e.g., HttpRequest.ClientCertificate), provide equivalent guidance for Linux or cross-platform frameworks, or clarify their applicability.
- Add a section or note about how mutual TLS works in App Service (Linux) and any differences in behavior or configuration compared to App Service (Windows), if applicable.
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 references the Windows file path (C:\home\site\wwwroot) first and provides a detailed explanation for Windows path conventions, while the Linux equivalent is only mentioned later and lacks example parity. There are no Linux-specific examples or screenshots, and the primary example uses a Windows-style path.
Recommendations
- Present both Windows and Linux file paths/examples together, or start with Linux if usage is equally common.
- Include explicit Linux file path examples (e.g., '/home/site/wwwroot/auth.json') alongside Windows examples in all relevant steps.
- Clarify any platform-specific behaviors or limitations in a side-by-side or tabbed format to ensure parity.
- Add a table or section summarizing differences between Windows and Linux deployments for this feature.
- Avoid assuming Windows as the default; use neutral language or alternate which platform is mentioned first.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-custom-container.md
...in/articles/app-service/quickstart-custom-container.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists Windows-related pivots and examples (Visual Studio, PowerShell, CLI) before their Linux counterparts, and includes a dedicated PowerShell section for Windows without an equivalent for Linux. This ordering and tooling focus may suggest a Windows-first perspective and a heavier emphasis on Windows-native tools.
Recommendations
- Alternate the order of Windows and Linux pivots to avoid always listing Windows first.
- Ensure Linux-specific tools (such as Bash or Linux CLI) are equally represented and not grouped after Windows tools.
- Provide parity for PowerShell examples by including Bash or shell script examples for Linux.
- Clearly label and balance the documentation so that Linux users can easily find relevant instructions without feeling secondary.
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, only the Windows-specific command ('ipconfig /flushdns') is provided for clearing the DNS cache, with no equivalent Linux or macOS instructions. No other platform-specific tools or examples are present, and the rest of the guide is platform-neutral.
Recommendations
- Add equivalent DNS cache flush instructions for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder') alongside the Windows example.
- When mentioning OS-specific troubleshooting steps, always provide parity for major platforms (Windows, Linux, macOS) or link to official documentation for each.
- Consider a short note or table summarizing common DNS cache flush commands for different operating systems.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-continuous-deployment.md
...n/articles/app-service/deploy-continuous-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing 'Windows apps' specifically in the External Git section, without mentioning Linux or cross-platform scenarios. There are no explicit Linux-specific instructions, examples, or references, and no mention of Linux tools or shell commands. The documentation assumes a generic approach but, where it diverges, it does so in favor of Windows (e.g., 'For Windows apps, you can select External Git...'). There are no PowerShell-heavy examples or Windows-specific tools, but the lack of Linux parity in examples and terminology is notable.
Recommendations
- Replace 'For Windows apps' with 'For Windows and Linux apps' or clarify if External Git is supported for both.
- Add explicit instructions or notes for Linux users, including any differences in setup or troubleshooting.
- Include Linux shell command examples (e.g., git CLI usage on Linux) where relevant, especially in the Local Git section.
- Ensure that any references to platform-specific features or limitations are balanced and clearly documented for both Windows and Linux.
- Consider adding a table or section summarizing platform-specific considerations for continuous deployment to Azure App Service.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-apple.md
...app-service/configure-authentication-provider-apple.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides only a C# code example for generating the client secret JWT, which relies on Microsoft.IdentityModel.Tokens and CngKey (Windows-specific cryptography APIs). There are no examples or guidance for Linux users or for using cross-platform tools (such as OpenSSL, Python, or Node.js). This may make it difficult for developers working on non-Windows platforms to follow the instructions.
Recommendations
- Add examples for generating and signing the JWT client secret using cross-platform tools such as OpenSSL, Python (e.g., PyJWT), or Node.js (e.g., jsonwebtoken).
- Mention and provide code snippets for Linux/macOS environments, ensuring that users on those platforms can easily follow the steps.
- Avoid relying solely on Windows-specific libraries (e.g., CngKey, ECDsaCng) in code samples; if C# is used, show alternatives that work on .NET Core/.NET 5+ on Linux.
- Explicitly state that the process can be completed on any OS, and link to or reference platform-agnostic JWT generation resources.
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
Windows First
Missing Linux Example
Summary
The documentation provides detailed C#/.NET examples and framework-specific notes for Windows-centric technologies (ASP.NET, .NET Core), while offering only brief mentions for PHP and Java. There are no explicit Linux or cross-platform shell (e.g., Bash) examples, and the primary code sample is in C#. This may make it less accessible for developers working on Linux or with non-Windows stacks.
Recommendations
- Add code examples for popular Linux-first languages and frameworks (e.g., Python/Flask, Node.js/Express) showing how to decode and use the X-MS-CLIENT-PRINCIPAL header.
- Include shell (Bash) or cross-platform command-line examples for decoding the Base64-encoded header, demonstrating how to inspect claims outside of a .NET context.
- Expand the 'Framework-specific alternatives' section to include guidance for Linux-centric frameworks and runtimes (e.g., Python WSGI, Node.js, Ruby on Rails).
- Ensure that examples and explanations are presented in a cross-platform manner, not assuming .NET or Windows as the default environment.
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 bias by referencing App Service pricing details specifically for Windows (via the link https://azure.microsoft.com/pricing/details/app-service/windows/) and not mentioning Linux-specific App Service plans or features. There are no command-line examples (such as PowerShell or Bash), but the absence of Linux-specific guidance or parity in pricing/feature discussion is notable.
Recommendations
- Include links and information about App Service Linux pricing tiers and features alongside or before Windows equivalents.
- Explicitly mention if instructions or features apply to both Windows and Linux App Service plans, or clarify any differences.
- Provide examples or notes for scaling up Linux-based App Service apps if there are any platform-specific considerations.
- Ensure that related documentation (such as scaling databases) references both Windows and Linux compatible services where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-gateway-based-vnet-integration.md
.../app-service/migrate-gateway-based-vnet-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples presented alongside or immediately after CLI examples. While the content is generally cross-platform, there is a subtle Windows bias: PowerShell is a Windows-centric tool (though available on Linux, it is less commonly used there), and there are no explicit Linux shell (e.g., Bash) or native Linux tool examples. The documentation does not mention or demonstrate Linux-specific patterns or tools, and PowerShell is given equal prominence to CLI, which is more universally cross-platform.
Recommendations
- Clarify that Azure CLI examples are cross-platform and can be run in Bash or other Linux shells.
- Consider providing Bash script examples or explicitly noting that Azure CLI commands are intended for Linux/macOS users as well.
- If PowerShell is included, clarify its availability on Linux and provide installation guidance or links for non-Windows users.
- Avoid implying that PowerShell is the default or primary automation tool for all users; instead, emphasize Azure CLI for cross-platform parity.
- Where appropriate, add notes or examples for Linux-native environments, such as using Bash scripting for automation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/networking-features.md
.../blob/main/articles/app-service/networking-features.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in the 'Hybrid Connections' section, where it specifies that the required relay agent (Hybrid Connection Manager) must be installed on a Windows Server 2012 or newer host. There is no mention of Linux support or alternatives for this agent, nor are there Linux-specific instructions or examples. The rest of the documentation is generally platform-neutral, but the omission of Linux guidance in this key networking feature is a notable gap.
Recommendations
- Explicitly state whether Hybrid Connection Manager is available for Linux, and if so, provide installation and usage instructions for Linux environments.
- If Hybrid Connection Manager is Windows-only, clarify this limitation and suggest alternative approaches for Linux-based deployments.
- Wherever platform-specific requirements exist, provide equivalent guidance or workarounds for Linux users to ensure parity.
- Review other networking features for any implicit Windows assumptions and add Linux-specific notes or examples where appropriate.