3257
Pages Scanned
50
Pages Flagged
3257
Changed Pages
1.5%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-01-09 00:00:08
Finished At: 2026-01-09 17:00:18
Status: cancelled
Target Repo: Azure
Current Phase: discovery
Files Queued: 13826
Files Completed: 3257
Problematic Pages
50 issues found
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/access-tokens.md
...ob/main/articles/active-directory-b2c/access-tokens.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by recommending Microsoft PowerShell as the example HTTP client for testing the token request, without mentioning any Linux or cross-platform alternatives (such as curl or httpie). No Linux-specific or cross-platform command-line examples are provided, and the only tool explicitly referenced is PowerShell, which is traditionally associated with Windows environments. This may lead Linux users to feel unsupported or unsure about how to perform the same actions on their platform.
Recommendations
- Include examples using cross-platform tools such as curl or httpie for making HTTP requests.
- Explicitly mention that PowerShell is available on Linux and macOS, or provide alternative Linux-native commands.
- Add a section or note listing common tools for both Windows and Linux users to test HTTP requests (e.g., curl, wget, httpie, PowerShell).
- Ensure that examples and tool recommendations are presented in a platform-neutral order, or provide parallel examples for both Windows and Linux.
Create Pull Request
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/force-password-reset.md
.../articles/active-directory-b2c/force-password-reset.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for configuring password expiry duration, referencing Windows-centric tools (Azure portal, PowerShell), and omitting equivalent Linux/macOS CLI or scripting examples. No mention is made of using cross-platform tools like Azure CLI or Bash scripts, and PowerShell is presented as the sole automation method.
Recommendations
- Add equivalent examples using Azure CLI (az) commands, which are cross-platform, for tasks such as updating password expiry settings.
- Explicitly mention that PowerShell examples can be run on macOS and Linux using PowerShell Core, or provide Bash/cURL examples for Microsoft Graph API calls.
- Include instructions for using the Azure portal from non-Windows operating systems, or clarify that the portal is web-based and OS-agnostic.
- Wherever PowerShell is used, provide alternative command-line examples (e.g., using cURL or HTTPie) for REST API operations.
- Review the order of tool presentation to avoid always listing Windows/PowerShell first; consider starting with cross-platform or REST-based solutions.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/id-token-hint.md
...ob/main/articles/active-directory-b2c/id-token-hint.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a clear Windows bias. All command-line examples for generating cryptographic keys and certificates use PowerShell, a Windows-specific tool. The guide for creating a self-signed certificate only provides a PowerShell example and explicitly references the Windows environment. There are no equivalent Linux or cross-platform command-line examples (e.g., using OpenSSL or Bash). The documentation does not mention or link to Linux tools or workflows, and Windows tools are presented as the default and only option.
Recommendations
- Provide equivalent Linux/macOS examples for generating symmetric keys (e.g., using OpenSSL or /dev/urandom in Bash).
- Add instructions for creating self-signed certificates on Linux/macOS using OpenSSL.
- When referencing platform-specific tools (like PowerShell), clarify that the instructions are for Windows and provide alternatives for other platforms.
- Consider using cross-platform tools or scripts where possible, or at least link to relevant Linux documentation.
- Reorder or parallelize sections so that Linux and Windows instructions are given equal prominence, rather than Windows-first.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/client-credentials-grant-flow.md
.../active-directory-b2c/client-credentials-grant-flow.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page exhibits Windows bias in several ways. The only explicit command-line example for generating a GUID uses PowerShell ('new-guid'), a Windows-specific tool, and mentions it before suggesting an online generator. The scripting example for obtaining an access token is given first in PowerShell, with a cURL (Linux/macOS-friendly) example following. There are no Linux shell or cross-platform alternatives for the GUID generation or other administrative tasks. Windows terminology and tools are referenced without Linux equivalents.
Recommendations
- Provide Linux and macOS equivalents for all command-line examples, such as using 'uuidgen' for GUID generation.
- When listing multiple platform options, alternate or randomize the order, or present them side-by-side rather than always listing Windows/PowerShell first.
- Explicitly mention cross-platform tools (e.g., cURL, HTTPie, uuidgen) and provide examples for each.
- Avoid referencing Windows-specific tools (like PowerShell) without also including Linux/macOS alternatives.
- Add a section or callout for Linux/macOS users, ensuring parity in instructions and tooling.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tenant-management-directory-quota.md
...ive-directory-b2c/tenant-management-directory-quota.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides only a PowerShell script for interacting with the Microsoft Graph API to monitor directory quota, with no equivalent examples for Linux or cross-platform tools (e.g., Bash, curl, Python). The exclusive use of PowerShell and Windows-centric command patterns demonstrates a Windows bias, making it less accessible for Linux or macOS administrators.
Recommendations
- Provide equivalent examples using Bash with curl or HTTPie, which are commonly available on Linux and macOS.
- Include a cross-platform example using Python and the requests library, which works on all major operating systems.
- Clearly indicate that PowerShell Core (pwsh) is available on Linux/macOS if PowerShell is to be used, and provide installation guidance.
- Reorder or parallelize examples so that Linux/macOS options are presented alongside or before Windows/PowerShell examples.
- Explicitly state that the API can be accessed from any platform, not just Windows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-ca-certificates.md
...api-management/api-management-howto-ca-certificates.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by providing a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI, Bash, or Linux-native instructions. The use of PowerShell and lack of Linux-specific or cross-platform examples may disadvantage users on non-Windows systems.
Recommendations
- Add equivalent Azure CLI commands for uploading CA certificates, with syntax examples for Bash and Linux environments.
- Explicitly mention cross-platform options and clarify that certificate upload can be performed from any OS using Azure CLI or REST API.
- Provide sample workflows for Linux and macOS users, including certificate file handling and upload steps.
- Reorder examples so that cross-platform or OS-neutral methods (e.g., Azure CLI, REST API) are presented before or alongside PowerShell.
- Include notes or links to documentation on installing and using Azure CLI on Linux/macOS.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/configure-managed-identity-kv-secret-user.md
.../includes/configure-managed-identity-kv-secret-user.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are labeled as 'Formatted for PowerShell' and are always presented immediately after the Bash examples. However, the PowerShell examples use Windows-specific syntax (e.g., backticks for line continuation, $variable assignment), and there is no explicit mention of Linux or macOS environments. The documentation does not clarify which example is for which OS, and the PowerShell examples may be confusing for non-Windows users. There is also a lack of explicit Linux/macOS context or troubleshooting, and the ordering of examples (Bash first, then PowerShell) could be interpreted as a mild 'windows_first' bias, especially since PowerShell is a Windows-native shell.
Recommendations
- Clearly label Bash examples as 'Linux/macOS (Bash)' and PowerShell examples as 'Windows (PowerShell)' to avoid confusion.
- Provide a brief note explaining which shell/environment each example is intended for.
- Consider including troubleshooting notes or environment setup instructions for both Linux/macOS and Windows users.
- If possible, provide parity in example depth and clarity for both platforms, and avoid assuming PowerShell is the default for Windows users.
- Ensure that Linux/macOS users are not required to adapt PowerShell-specific syntax.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-notification-workflow.md
...in/articles/api-center/set-up-notification-workflow.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a strong bias toward Windows and Microsoft-centric tools and workflows. All examples and instructions are built around the Azure Portal, Logic Apps, and Microsoft Teams, with no mention of Linux-compatible alternatives or cross-platform notification tools. There are no CLI, Bash, or non-Microsoft notification examples, and the only automation platforms referenced are Logic Apps and Power Automate, both of which are primarily accessed via the Azure Portal (a web GUI) and are closely tied to the Microsoft ecosystem. The notification workflow is exclusively demonstrated using Microsoft Teams, with no mention of alternatives like Slack or email, which are commonly used in Linux environments. The documentation also consistently references the Azure Portal UI, which, while web-based, is presented in a way that assumes familiarity with Microsoft patterns and does not provide parity for users who prefer or require command-line or Linux-native tools.
Recommendations
- Provide equivalent examples using Azure CLI and/or Azure PowerShell, and ensure CLI examples are given equal prominence.
- Include instructions for setting up similar workflows using cross-platform tools such as Bash scripts, curl, or automation via GitHub Actions or other CI/CD tools that are popular in Linux environments.
- Offer notification workflow examples that use email, Slack, or other cross-platform messaging services in addition to Microsoft Teams.
- Explicitly mention that Logic Apps and Power Automate can be triggered and managed via CLI or REST API, and provide links or examples.
- Add a section or callout for Linux users, highlighting any differences or additional steps needed for non-Windows environments.
- Avoid assuming the use of the Azure Portal for all steps; provide alternatives for users who prefer command-line or infrastructure-as-code approaches (e.g., ARM/Bicep, Terraform).
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell examples and instructions, referencing Azure PowerShell cmdlets and tools first, and providing more detailed PowerShell usage scenarios. While Azure CLI and REST API examples are included, PowerShell is consistently presented before CLI (which is more cross-platform and Linux-friendly), and there are no explicit Bash scripting or Linux shell examples beyond the CLI. There is also no mention of Linux-specific considerations or parity in the prerequisites or troubleshooting sections.
Recommendations
- Present Azure CLI (Bash) examples before or alongside PowerShell examples to ensure Linux users are equally supported.
- Expand Bash/Linux shell scripting examples, including variable handling and error checking, to match the detail level of PowerShell sections.
- Explicitly state that all CLI examples are cross-platform and tested on Linux, macOS, and Windows.
- Add troubleshooting tips or notes for Linux users, such as common issues with authentication or permissions.
- Where PowerShell-specific cmdlets are mentioned, provide equivalent Azure CLI commands and reference the official CLI documentation.
- Avoid using 'PowerShell' as the default or primary automation tool in introductory or summary sections; instead, refer to both PowerShell and CLI equally.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-basic-authentication.md
...pi-management/developer-portal-basic-authentication.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively mentioning the Azure PowerShell cmdlet (New-AzApiManagementUser) as the CLI tool for adding users, with no mention of Linux-friendly alternatives such as Azure CLI or REST API. No Linux-specific or cross-platform command-line examples are provided, and the only non-portal automation example is PowerShell, which is most commonly used on Windows.
Recommendations
- Include Azure CLI examples for adding users to the developer portal, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention REST API methods for user management, providing sample requests and responses.
- Clarify that PowerShell is available cross-platform, but also provide parity with CLI and REST instructions.
- Ensure that automation and scripting examples are not limited to Windows-centric tools, and present Linux-friendly options alongside or before Windows-specific ones.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-faq.md
...b/main/articles/api-management/developer-portal-faq.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for role assignment and management tasks, and by referencing a Windows batch script (.bat) for cleanup operations. There are no equivalent examples or instructions for Linux users (e.g., Bash scripts, Azure CLI), nor are cross-platform alternatives mentioned. This may hinder Linux users or those working in non-Windows environments from following the guidance without additional research.
Recommendations
- Provide equivalent Azure CLI or Bash script examples alongside PowerShell scripts for role assignment and management tasks.
- Include instructions for running cleanup operations using shell scripts (.sh) or Azure CLI, not just Windows batch files.
- Explicitly state cross-platform compatibility for all scripts and tools, or provide guidance for Linux/macOS users where differences exist.
- Where possible, mention both Windows and Linux tools/patterns together, or in parallel sections, to ensure parity.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-soap-api.md
...s/blob/main/articles/api-management/import-soap-api.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is given equal prominence to CLI, and PowerShell is a Windows-centric tool. The prerequisites section lists Azure PowerShell immediately after Azure CLI, and the PowerShell example is detailed and uses Windows-specific cmdlets. There are no Linux shell (bash) or cross-platform scripting examples, nor is there mention of Linux-specific tools or patterns. The documentation assumes familiarity with PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add bash/sh shell script examples using Azure CLI to demonstrate Linux-native workflows.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Mention that PowerShell Core is available on Linux and macOS, but provide explicit bash examples for parity.
- Where possible, use generic CLI commands in examples before introducing platform-specific tools like PowerShell.
- Add notes or links for Linux users on installing and using Azure CLI and PowerShell Core on their systems.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-injection-resources.md
.../api-management/virtual-network-injection-resources.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell in the 'Related content' section for connecting virtual networks, without mentioning equivalent Linux/CLI/Bash examples. There are no explicit Linux or cross-platform command-line examples, and the only automation example provided is for PowerShell, which is Windows-centric. Additionally, where portal actions are described, there is no mention of Azure CLI or cross-platform alternatives.
Recommendations
- Add Azure CLI (cross-platform) examples alongside or before PowerShell references, especially in 'Related content' and any automation guidance.
- When referring to automation or scripting, provide both PowerShell and Bash/CLI equivalents to ensure Linux parity.
- Mention the Azure portal, Azure CLI, and PowerShell equally when describing configuration steps, or provide links to all relevant platform-specific guides.
- Review all linked articles (such as VPN and VNet connection guides) to ensure they include Linux/CLI options, and update this page to reference them.
- Explicitly state that all operations can be performed from Windows, Linux, or macOS using Azure CLI, and provide examples or links where appropriate.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/quickstart-arm-template.md
...ain/articles/api-management/quickstart-arm-template.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page primarily demonstrates deployment using the Azure Portal, with only brief mentions of Azure PowerShell, Azure CLI, and REST API as alternatives. There are no explicit examples or step-by-step instructions for deploying via Azure CLI (which is cross-platform and preferred on Linux) or Bash scripting. The only command-line tool mentioned by name in the main flow is Azure PowerShell, a Windows-centric tool, and it is listed before Azure CLI. There are no Linux-specific instructions or screenshots.
Recommendations
- Add explicit, step-by-step examples for deploying the ARM template using Azure CLI (az deployment group create ...) and Bash, including command snippets.
- When listing alternative deployment methods, mention Azure CLI before Azure PowerShell to reflect cross-platform parity.
- Include screenshots or terminal output examples from Linux environments where appropriate.
- Clarify that all deployment methods (Azure Portal, Azure CLI, PowerShell, REST API) are supported on all platforms, and provide links to Linux-specific setup guides for Azure CLI.
- Consider adding a section or callout box specifically for Linux/macOS users, highlighting the recommended tools and any differences.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/self-hosted-gateway-enable-azure-ad.md
.../api-management/self-hosted-gateway-enable-azure-ad.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by consistently referencing Azure Portal and PowerShell/CLI tools before or instead of Linux-native alternatives. Role assignment and app registration steps are linked primarily to Azure Portal (a web UI often associated with Windows workflows) and PowerShell/CLI, with no explicit Linux shell or cross-platform command-line examples. There are no Linux-specific instructions for tasks like role assignment or app registration, and the documentation does not mention or prioritize Linux-native tools or workflows.
Recommendations
- Provide explicit Linux shell (bash) examples for Azure CLI commands, especially for role assignments and app registration.
- When referencing Azure Portal, also link to or describe equivalent steps using Azure CLI in bash, making it clear these can be run on Linux/macOS.
- Where PowerShell is mentioned, ensure Azure CLI (bash) alternatives are presented first or equally.
- Clarify that all command-line steps can be performed on Linux, and provide sample commands where appropriate.
- Add a section or callout for Linux users, summarizing the parity of steps and tools available.
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
missing_linux_example
windows_tools
Summary
The documentation provides a PowerShell script as the only automated method for identifying impacted Traffic Manager profiles, with no equivalent Bash, Azure CLI, or Linux-native example. All step-by-step instructions for resource identification are Windows/PowerShell-centric, and there is no mention of cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux or macOS administrators.
Recommendations
- Provide equivalent Azure CLI or Bash scripts for identifying impacted Traffic Manager profiles, ensuring Linux and macOS users have a supported method.
- When referencing scripts or tools, mention both PowerShell and CLI/Bash options, or explicitly state platform compatibility.
- Include examples or guidance for running the detection and mitigation steps on Linux-based systems.
- Consider adding a table or section summarizing available tools/scripts for both Windows (PowerShell) and Linux/macOS (Bash/CLI), with links to each.
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_tools
missing_linux_example
windows_first
Summary
The documentation focuses exclusively on discovering ASP.NET web apps hosted on IIS within VMware environments, referencing only Windows-based tools and patterns. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps hosted on Linux. The content and related links reinforce a Windows-first perspective.
Recommendations
- Include guidance and examples for discovering .NET web apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
- Mention whether Azure Migrate supports Linux-based .NET app discovery, and if not, clarify this limitation.
- Add parity in documentation by providing Linux-specific instructions, tools, and troubleshooting steps.
- List Linux environments and discovery capabilities alongside Windows/IIS to ensure cross-platform inclusivity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-undelete.md
...blob/main/articles/app-service/app-service-undelete.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong bias towards Windows environments by exclusively providing PowerShell-based examples and instructions for restoring deleted Azure App Service apps. There are no examples or guidance for users of Linux or macOS, such as using Azure CLI, Bash, or REST API. The only non-PowerShell method mentioned is the Azure portal, but all automation and scripting is PowerShell-centric. This may alienate or hinder users who primarily use Linux or cross-platform tools.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include REST API examples or references for advanced users who may wish to automate app restoration without PowerShell.
- When listing command-line options, present Azure CLI and PowerShell examples side-by-side, or at least mention both, to avoid the perception of Windows-first bias.
- Explicitly state that PowerShell examples can be run cross-platform using Azure PowerShell Core, or provide Bash scripting alternatives where possible.
- Review and update the documentation to ensure that Linux and macOS users have clear, supported pathways for performing all documented tasks.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-dotnet-sqldatabase.md
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily biased toward Windows and Visual Studio users. All instructions and screenshots are based on Visual Studio for Windows, with no mention of Linux or cross-platform development tools. Steps for publishing, configuring, and managing the app and database rely on Visual Studio GUI and Windows-specific tools (e.g., SQL Server Object Explorer, Package Manager Console, PowerShell). There are no examples or instructions for Linux users or those using cross-platform tools like VS Code, Azure CLI, or the Azure Portal directly.
Recommendations
- Add parallel instructions for Linux and macOS users, including how to perform each step using cross-platform tools such as VS Code, Azure CLI, and the Azure Portal.
- Provide command-line examples (e.g., using Azure CLI, dotnet CLI, or Bash) for app deployment, database creation, and configuration, in addition to Visual Studio GUI steps.
- Include screenshots and workflow descriptions for non-Windows environments.
- Mention and link to Linux-compatible tools and workflows early in the tutorial, not just as an afterthought.
- Clarify which steps are Windows-specific and provide alternatives for other platforms where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-customize-sign-in-out.md
...vice/configure-authentication-customize-sign-in-out.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation contains a Windows bias in the 'Authorize or deny users' section, where server-level authorization is described exclusively for Windows apps using IIS and web.config, without providing equivalent Linux guidance. The Kudu console and web.config editing are presented as the main approach, with no mention of Linux alternatives or parity. Other sections use cross-platform Azure CLI examples and avoid OS-specific instructions.
Recommendations
- Add a section describing how to implement server-level authorization for Linux-based App Service apps, such as using middleware in popular frameworks (e.g., Node.js, Python, .NET Core) or configuring authorization in the application code.
- Explicitly state that server-level authorization via web.config is not available on Linux, and provide links or examples for common Linux-based approaches.
- Ensure that for every Windows/IIS-specific example, an equivalent Linux/app-level example is provided, or at least referenced.
- Review the order of presentation to avoid 'Windows first' biasâconsider presenting cross-platform or Linux approaches alongside Windows ones.
- Mention any built-in features or best practices for authorization on Linux App Service (e.g., using .htaccess for PHP, or app-level authorization for other stacks).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/app-service-app-service-environment-geo-distributed-scale.md
...-service-app-service-environment-geo-distributed-scale.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for configuring Traffic Manager and App Service Environments. There are no equivalent examples using Azure CLI, Bash scripts, or ARM templates, which are commonly used on Linux and cross-platform environments. The only automation tooling mentioned is PowerShell, and the narrative assumes its use without referencing alternatives. This may hinder accessibility for Linux or macOS users and those who prefer cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown, ensuring Linux and macOS users can follow along without needing PowerShell.
- Mention and link to ARM/Bicep template documentation for users who prefer declarative infrastructure-as-code approaches.
- When introducing automation tooling, mention Azure CLI and ARM templates alongside PowerShell, rather than only referencing PowerShell.
- Include screenshots or terminal output from Bash or cross-platform shells where relevant.
- Review the language to avoid assuming PowerShell as the default tool; use more inclusive phrasing such as 'using Azure PowerShell or Azure CLI...'
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
missing_linux_example
windows_tools
Summary
The documentation presents Windows examples and tools (cmd, bat, exe, PowerShell) in detail and lists them first, while Linux sections are less detailed, only mentioning .sh scripts and providing fewer examples. Windows-specific tools and file types are emphasized, and Linux equivalents (e.g., .sh, .py, .js) are not given the same breadth or specificity.
Recommendations
- Provide Linux examples with the same level of detail as Windows, including supported file types for Bash, Python, Node.js, and Java.
- List Linux and Windows sections in parallel structure, ensuring neither is prioritized in order or detail.
- Explicitly mention Linux tools and runtimes (e.g., bash, python, node, java) and their supported file types, similar to how Windows tools are listed.
- Include examples for Linux containers that match the variety shown for Windows containers (e.g., .py, .jar, .war).
- Consider a summary table comparing supported file types across both platforms for clarity and parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-basic-auth-disable.md
...n/articles/app-service/configure-basic-auth-disable.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. It references and prioritizes Windows-centric tools and workflows such as Web Deploy (a Windows-only tool), Visual Studio, and FTP, which are more commonly used in Windows environments. The fallback and troubleshooting sections mention Windows agents specifically and provide more detail for Windows scenarios. There is a lack of explicit Linux or cross-platform examples, and no mention of Linux-native deployment tools or command-line patterns outside of the Azure CLI. Powershell is implied via references to the Azure portal and Windows agents, but not directly shown. Linux deployment agents and workflows are not covered in detail, and there are no Linux-specific troubleshooting steps or parity checks.
Recommendations
- Add explicit Linux examples and troubleshooting steps, especially for deployment agents and self-hosted runners.
- Mention Linux-native tools and workflows (e.g., SCP, SFTP, rsync, or Linux-based CI/CD runners) where relevant.
- Clarify which deployment methods and tools are cross-platform and which are Windows-only.
- Provide parity in troubleshooting guidance for Linux agents (e.g., what to do if authentication fails on a Linux agent).
- Include Bash or shell script examples for common tasks, not just Azure CLI.
- When referencing Visual Studio or Web Deploy, also mention cross-platform alternatives (e.g., VS Code, Git, or other CI/CD tools).
- Review and balance the order of presentation so that Windows and Linux options are given equal prominence.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-custom-container.md
...ain/articles/app-service/configure-custom-container.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific instructions, tools, and examples (such as PowerShell and Windows paths) are often presented first or exclusively, with Linux equivalents sometimes missing or less detailed. Some sections, especially those about persistent storage, memory, and CPU configuration, provide more context and examples for Windows users, while Linux instructions are less prominent or absent. PowerShell commands are frequently included alongside Bash, but not always with parity in Linux-specific guidance. Windows tools and patterns (e.g., Kudu, IIS, .NET Framework) are referenced more extensively.
Recommendations
- Ensure all configuration examples (e.g., for persistent storage, memory, CPU, environment variables) provide both Bash (Linux) and PowerShell (Windows) commands with equal prominence.
- When introducing concepts or features, avoid presenting Windows-specific details first; instead, use neutral or parallel explanations for both platforms.
- Expand Linux-specific sections to match the depth and clarity of Windows sections, including troubleshooting, logs access, and advanced configuration.
- Where Windows tools (e.g., Kudu, IIS) are mentioned, provide Linux alternatives or clarify their applicability to Linux containers.
- Review for sections where only Windows parent images, paths, or frameworks are discussed, and add corresponding Linux examples (e.g., base images, file paths, frameworks).
- Audit for any missing Linux examples, especially in advanced scenarios (e.g., custom entrypoints, SSH, persistent storage), and add them where needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjobs-supported-platforms.md
...includes/webjobs-create/webjobs-supported-platforms.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation lists Windows hosting options before Linux and prioritizes Windows file/script types (.exe, .cmd, .bat) and PowerShell scripts (.ps1) ahead of Bash (.sh) and other cross-platform scripting languages. This ordering and emphasis suggest a Windows-centric perspective, with Windows tools and patterns mentioned first and in more detail.
Recommendations
- List Linux hosting options and script types before or alongside Windows equivalents to avoid implicit prioritization.
- Provide equal detail and examples for Linux tools (e.g., Bash, shell scripts) and mention them as prominently as Windows tools.
- Include explicit examples for both Windows and Linux platforms to demonstrate parity.
- Avoid grouping Windows-specific file types together at the top of lists; interleave with Linux equivalents.
- Add notes or sections highlighting Linux-specific considerations, best practices, or troubleshooting tips.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-diagnostics.md
...application-gateway/application-gateway-diagnostics.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 enabling diagnostic logging, with no equivalent Azure CLI, Bash, or Linux-native instructions. It references Windows-centric tools (PowerShell, Excel, Visual Studio, C#) for log manipulation and analysis, and does not mention or prioritize Linux-friendly alternatives. The absence of cross-platform command-line examples and reliance on Windows tools may hinder accessibility for Linux users.
Recommendations
- Add Azure CLI examples alongside PowerShell for enabling and configuring diagnostic logging, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash or shell script snippets for common tasks, such as downloading and processing logs.
- Mention and provide examples for Linux-native tools (e.g., jq, awk, sed) for parsing and analyzing JSON log files.
- Reference cross-platform editors and data visualization tools (e.g., VS Code, LibreOffice Calc, or open-source log viewers) instead of or in addition to Excel and Visual Studio.
- Ensure that all code and tool references are either cross-platform or have Linux equivalents clearly documented.
- Consider reordering sections so that cross-platform or Linux-friendly methods are presented before or alongside Windows/PowerShell approaches.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md
...les/application-gateway/application-gateway-ilb-arm.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native workflows. Windows/PowerShell tools are referenced exclusively and repeatedly, and there are no Linux or cross-platform alternatives provided. The documentation assumes the user is working in a Windows/PowerShell environment from the outset.
Recommendations
- Add equivalent Azure CLI (az) command examples for each PowerShell step, with clear instructions for running them on Linux, macOS, and Windows.
- Include a section at the beginning outlining both PowerShell and CLI options, and recommend the CLI for cross-platform scenarios.
- Reference Bash and shell scripting alternatives where appropriate, especially for automation.
- Avoid language such as 'switch PowerShell mode' or 'Using Windows PowerShell' unless also providing guidance for CLI users.
- Ensure all code samples are available in both PowerShell and CLI formats, and alternate their order or present them side-by-side.
- Explicitly mention that Azure CLI is supported on Linux, macOS, and Windows, and link to installation instructions.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-websocket.md
...s/application-gateway/application-gateway-websocket.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by referencing Azure PowerShell and linking to a 'quick-create-powershell.md' page as the next step, without mentioning or providing equivalent Azure CLI or Linux shell examples. The only tooling mentioned for creating listeners is Azure PowerShell and the portal, with no reference to cross-platform or Linux-native tools. There are no examples or instructions for Linux users, nor is Azure CLI (which is cross-platform) mentioned.
Recommendations
- Include Azure CLI examples alongside or before PowerShell examples to ensure Linux and macOS users are supported.
- Mention that both Azure PowerShell and Azure CLI can be used to configure Application Gateway, and provide links to both sets of documentation.
- Update the 'Next steps' section to reference both PowerShell and Azure CLI quick-create guides.
- Explicitly state that configuration can be performed from any OS, and provide guidance for Linux users where relevant.
- Add sample commands or scripts for Linux environments, such as bash shell or Azure CLI, especially in sections describing listener creation or gateway setup.
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_tools
missing_linux_example
windows_first
Summary
The documentation exhibits a Windows bias by requiring PowerShell for the migration script, only providing PowerShell commands for scripting and base64 decoding, and not offering equivalent Bash/Linux shell examples. The script-based migration is only supported via a PowerShell script, and Linux alternatives are not mentioned. Additionally, PowerShell is listed as a prerequisite before Azure CLI, and Windows tooling is assumed throughout.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell commands, especially for base64 decoding and script execution.
- Offer a Bash or cross-platform version of the migration script, or document how to run the PowerShell script on Linux (e.g., with pwsh).
- List prerequisites in a cross-platform neutral order, and clarify that Azure CLI and Docker are cross-platform.
- Explicitly mention support for Linux/macOS environments, and provide guidance for users on those platforms.
- Where only PowerShell is available, note this limitation and suggest alternatives or workarounds for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/networking-features.md
.../blob/main/articles/app-service/networking-features.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias primarily in the Hybrid Connections section, where only Windows Server is mentioned as a supported platform for the Hybrid Connection Manager, with no mention of Linux support or alternatives. Additionally, the gateway-required virtual network integration feature is explicitly limited to App Service Windows plans, with no Linux equivalent or workaround discussed. There are no Linux-specific examples, tools, or instructions provided, and Windows tools/patterns are referenced before any cross-platform or Linux options.
Recommendations
- Explicitly state whether Hybrid Connection Manager is available for Linux, and if not, provide alternative solutions or workarounds for Linux users.
- Include Linux-specific instructions, examples, or notes wherever Windows-only features are mentioned, or clarify platform limitations.
- Where features are Windows-only (e.g., gateway-required VNet integration), offer guidance for Linux users on equivalent networking patterns or recommend supported alternatives.
- Add parity in documentation by providing examples, screenshots, and step-by-step guides for both Windows and Linux environments where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-private-endpoint.md
...main/articles/app-service/overview-private-endpoint.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows and PowerShell examples and tools before Linux equivalents, and by omitting explicit Linux-focused instructions or examples. The related content section lists Azure PowerShell before ARM templates and Terraform, and there are no Bash or Linux CLI-specific examples. The text also refers to Windows and Linux apps together but does not provide parity in examples or troubleshooting for Linux environments.
Recommendations
- Add explicit Linux/Bash CLI examples alongside or before PowerShell examples, especially in sections referencing Azure CLI.
- Ensure that Linux tools and workflows (such as Bash scripting, Linux DNS tools, etc.) are mentioned and demonstrated where relevant.
- In the 'Related content' section, list Azure CLI and ARM template examples before PowerShell, or group them without preference.
- Include troubleshooting notes or examples specific to Linux environments (e.g., modifying /etc/hosts, using dig/nslookup on Linux).
- Clarify any platform-specific differences in setup or behavior for Windows vs. Linux apps, and provide guidance for both.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-create-probe-portal.md
...ion-gateway/application-gateway-create-probe-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page provides instructions for creating a custom probe in Azure Application Gateway primarily through the Azure Portal and PowerShell. The navigation selector lists 'Azure Resource Manager PowerShell' and 'Azure Classic PowerShell' as alternatives, with no mention of Azure CLI (which is cross-platform and Linux-friendly), Bash, or Linux-specific tools. All command-line examples and references are PowerShell-centric, and there are no Linux/Unix shell or Azure CLI equivalents provided. This structure prioritizes Windows tools and patterns, making it less accessible for Linux users.
Recommendations
- Add Azure CLI examples for all operations currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash or shell script snippets where relevant, especially for automation scenarios.
- Mention Azure CLI as an alternative in the selector at the top, alongside PowerShell.
- Ensure that any references to command-line tools or automation scripts are balanced between Windows (PowerShell) and Linux (Bash/Azure CLI).
- Explicitly state that the Azure Portal is accessible from any OS, but provide parity in command-line instructions.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-externally-managed-scheduled-autoscaling.md
...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively provides PowerShell-based examples for creating and managing Azure Automation runbooks, which is a Windows-centric tool. There are no Bash, Azure CLI, or Python examples, nor is there mention of using Linux-based automation options. The workflow and tooling described (PowerShell runbooks, Az module) are more familiar to Windows users, and no Linux-first or cross-platform alternatives are presented.
Recommendations
- Provide equivalent examples using Azure CLI and/or Python runbooks, which are more familiar to Linux users.
- Explicitly mention that Azure Automation supports Python and Bash runbooks, and link to relevant documentation.
- Add a section or note highlighting cross-platform options and when to use each (PowerShell, Python, Bash, etc.).
- Ensure that Linux-friendly tools and patterns are described with parity to Windows/PowerShell approaches.
- Consider reordering or parallelizing examples so that Windows and Linux approaches are presented together.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-key-vault-common-errors.md
...gateway/application-gateway-key-vault-common-errors.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by providing only PowerShell command examples for certificate management and updates, without offering equivalent Azure CLI or Bash examples. The use of PowerShell as the sole scripting tool assumes a Windows environment. Additionally, when mentioning programmatic alternatives to the portal, 'ARM template, CLI, or PowerShell' are listed, but only PowerShell examples are shown. There are no Linux-specific instructions or screenshots, and the portal navigation assumes a GUI typical of Windows users.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell scripts, especially for certificate upload/update and Key Vault operations.
- Where programmatic options are mentioned (ARM template, CLI, PowerShell), provide examples for both CLI and PowerShell.
- Explicitly state that the Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
- Include screenshots or instructions for using the Azure portal from non-Windows environments (e.g., browser-agnostic language).
- Review the order of tool mentions to avoid always listing Windows tools first; alternate or group by platform.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-infrastructure.md
...es/application-gateway/configuration-infrastructure.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell cmdlets for restarting the Application Gateway, without providing equivalent Azure CLI (cross-platform) or Bash examples. There are no explicit Linux or Bash examples, and the only command-line instructions are PowerShell-specific. This could hinder Linux or macOS users who may prefer or require CLI/Bash instructions.
Recommendations
- For every PowerShell example or reference, provide an equivalent Azure CLI (az) command, ideally with Bash syntax.
- When referencing command-line operations (e.g., restarting the Application Gateway), include both PowerShell and CLI/Bash instructions, or link to cross-platform documentation.
- Avoid assuming PowerShell as the default tool; mention both PowerShell and CLI equally, or lead with CLI/Bash for improved Linux parity.
- Add a note clarifying that all operations can be performed via Azure CLI on any platform, and provide links to relevant CLI documentation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-listeners.md
...rticles/application-gateway/configuration-listeners.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides a PowerShell-only example for enabling HTTP/2 support, with no equivalent example for Linux users (e.g., Azure CLI, Bash, or ARM templates). The only code snippet uses Azure PowerShell, which is primarily a Windows tool, and there are no references to cross-platform alternatives. This may hinder Linux or macOS users who do not use PowerShell.
Recommendations
- Add equivalent Azure CLI examples for all configuration steps currently shown only with PowerShell.
- Explicitly mention that Azure CLI and ARM templates can be used for listener configuration, and provide links or examples.
- Ensure that code snippets are provided for both PowerShell and CLI (Bash) where applicable.
- Review the documentation for other areas where only Windows-centric tools or workflows are described, and add Linux/macOS-friendly alternatives.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-twilio.md
...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by only referencing .NET applications and configuration via web.config, which are primarily Windows-centric technologies. There are no examples or guidance for deploying the sample app on Linux, nor are alternative Linux hosting or configuration instructions provided. The certificate creation and hosting instructions link to Azure App Service guidance, which is platform-neutral, but the lack of explicit Linux instructions or parity in examples is notable.
Recommendations
- Provide equivalent instructions for deploying the demo app on Linux environments (e.g., using Kestrel, Nginx, or Apache).
- Include examples for configuring the application using environment variables or appsettings.json, which are more common in cross-platform .NET Core apps.
- Add guidance for certificate creation and management on Linux (e.g., using OpenSSL).
- Clarify that the sample app can be hosted on both Windows and Linux platforms, and provide links or steps for both.
- Where possible, use .NET Core/.NET 6+ terminology and examples, which are cross-platform, rather than .NET Framework/web.config (Windows-centric).
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/import-api-management-apis.md
...main/articles/api-center/import-api-management-apis.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell shells, but consistently lists PowerShell examples immediately after Bash, and explicitly formats commands for PowerShell. Notes repeatedly mention PowerShell as a supported environment, and variable syntax differences are called out. There is no mention of Linux-specific tools, nor are Linux distributions or shells (other than Bash) discussed. Windows/PowerShell is given equal or slightly more prominence than Linux/Bash, suggesting a subtle Windows bias.
Recommendations
- Explicitly state that all CLI commands work equally well on Linux, macOS, and Windows, and mention supported shells (e.g., Bash, Zsh, Fish) on Linux.
- Provide examples for additional Linux shells (e.g., Zsh) if syntax differs, or clarify that Bash examples apply to most Linux shells.
- List Bash/Linux examples before PowerShell, or alternate the order to avoid implicit prioritization.
- Add a note about running Azure CLI in native Linux environments (e.g., Ubuntu, CentOS) and on macOS.
- Reference installation instructions for Azure CLI on Linux and macOS alongside Windows.
- Avoid unnecessary emphasis on PowerShell unless there is a specific Windows-only scenario.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/configure-managed-identity-apim-reader.md
...ter/includes/configure-managed-identity-apim-reader.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are given immediately after Bash in every case, and the PowerShell formatting is explicitly called out. There is no mention of Linux-specific tools, nor are Linux workflows prioritized or explained in detail. The portal instructions are platform-neutral, but the CLI section leans toward Windows parity by always including PowerShell and not, for example, Zsh or other Linux shell variants.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly in a note at the start of the CLI section.
- Consider providing examples for other popular Linux shells (e.g., Zsh) if syntax differs, or explicitly state that Bash commands work for most Linux/macOS environments.
- Ensure that Bash examples appear first and are clearly marked as the default for cross-platform usage.
- Add a short section or note on how to run Azure CLI commands on Linux/macOS, including installation and environment setup if relevant.
- Avoid labeling PowerShell examples as 'Formatted for PowerShell' without a corresponding 'Formatted for Bash' label, to avoid implying PowerShell is the primary or default shell.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-bicep.md
...ob/main/articles/api-center/set-up-api-center-bicep.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell is mentioned alongside CLI throughout, and there is no mention of Bash or Linux-specific shell environments. The prerequisites and tooling sections reference Azure PowerShell requirements, which are Windows-centric, and the overall structure tends to present PowerShell as a primary option, which may implicitly prioritize Windows users.
Recommendations
- Explicitly mention Bash or Linux shell environments in the prerequisites and deployment sections.
- Add Bash-specific instructions or notes where relevant, especially for file handling and environment setup.
- Ensure that Azure CLI examples are clearly marked as cross-platform and, where possible, provide additional context for Linux/macOS users (e.g., file paths, uploading files in Cloud Shell).
- Avoid positioning PowerShell as the default or primary method; instead, clarify that both CLI and PowerShell are supported equally across platforms.
- Include troubleshooting tips or links for common Linux/macOS issues (e.g., file permissions, path formats) when working with Bicep and Azure CLI.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-container-apps.md
...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell (Windows) examples are always presented immediately after Bash, and sometimes the syntax comments and code are more detailed for PowerShell. There are no Linux-specific tools or patterns mentioned, and the Azure portal (web UI) is referenced throughout, which is platform-agnostic. However, the documentation does not provide any Linux-specific troubleshooting, nor does it mention Linux-native shells beyond Bash, and the structure implicitly prioritizes Windows parity by always including PowerShell examples.
Recommendations
- Ensure that Bash examples are always presented first, as is currently done, but consider including a note that Bash examples are suitable for Linux and macOS users.
- Add explicit statements clarifying that all Azure CLI commands work identically on Linux, macOS, and Windows (with Bash or PowerShell).
- Where PowerShell-specific syntax is explained, provide equivalent explanations for Bash (e.g., variable assignment, line continuation).
- Consider including troubleshooting tips or common issues for Linux environments, such as permissions or shell differences.
- If possible, add examples or notes for other popular Linux shells (e.g., zsh, fish) or clarify that Bash examples are compatible with these.
- Review for any subtle language that assumes a Windows-first audience and adjust to be more platform-neutral.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-function-app-as-api.md
.../articles/api-management/import-function-app-as-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes using the Azure Portal GUI for all operations and does not provide any command-line examples. While it does not explicitly mention Windows tools like PowerShell or CMD, the only alternative tool referenced is Visual Studio Code (which is cross-platform but often associated with Windows). There are no examples using Azure CLI, Bash, or other Linux-native tools, nor is there any mention of Linux-specific workflows. The documentation assumes use of the Azure Portal, which is platform-agnostic but often perceived as Windows-centric due to its integration with other Microsoft tools.
Recommendations
- Add Azure CLI examples for importing a Function App as an API, including relevant commands for Linux/macOS users.
- Include Bash shell command examples where applicable, especially for tasks like retrieving keys or configuring API Management.
- Explicitly mention that all steps can be performed from any OS via the Azure Portal, and highlight any cross-platform tools.
- If Visual Studio Code is referenced, clarify its cross-platform nature and provide instructions for Linux/macOS installation and usage.
- Consider adding a section or callout for Linux users, summarizing parity and any differences in workflow.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/set-backend-service-policy.md
.../articles/api-management/set-backend-service-policy.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references PowerShell as a management tool for backend entities but does not mention Linux-native tools (such as Azure CLI or Bash scripting) or provide Linux-specific examples. All management tooling references are either Windows-centric or generic, with no explicit Linux parity. No Linux-specific examples or command-line instructions are provided.
Recommendations
- Add references and links to Azure CLI documentation and examples for managing backend entities, alongside or before PowerShell.
- Explicitly mention that backend entities can be managed using cross-platform tools such as Azure CLI and REST API, not just PowerShell.
- Provide example commands for both PowerShell and Azure CLI (or Bash) when describing management operations.
- Ensure that any scripts or automation examples are available in both PowerShell and Bash/Azure CLI formats.
- Review and update the documentation to avoid implying that PowerShell is the primary or only supported tool for management tasks.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-app-service-as-api.md
...n/articles/api-management/import-app-service-as-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric development patterns (ASP.NET Core, Visual Studio Code) and omitting Linux-specific examples or tooling. All examples and tutorials assume a Windows-based workflow, with no mention of Linux alternatives for creating, publishing, or managing Azure web apps and APIs.
Recommendations
- Add Linux-specific examples for creating and publishing web APIs, such as using Python (Flask, FastAPI), Node.js, or Java.
- Include instructions for deploying web apps to Azure App Service from Linux environments, e.g., using Azure CLI, GitHub Actions, or Docker.
- Reference Linux-friendly editors and tools (e.g., VS Code on Linux, JetBrains IDEs, command-line workflows) alongside Visual Studio Code.
- Explicitly mention cross-platform compatibility and provide parity in screenshots and step-by-step guides for both Windows and Linux users.
- Highlight any differences or considerations when using Azure portal and API Management from Linux systems.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-container-app-with-oas.md
...ticles/api-management/import-container-app-with-oas.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal UI and not providing any command-line examples. There are no CLI (az), PowerShell, or Bash examples, nor is there mention of Linux-specific workflows. All instructions are centered around the Azure portal, which is platform-agnostic but often associated with Windows-first workflows. There are no explicit Linux or cross-platform command-line instructions, nor are alternative tools (such as cURL, Bash scripts, or az CLI) mentioned.
Recommendations
- Add examples using the Azure CLI (az) for importing and testing APIs, which are cross-platform and widely used on Linux.
- Include Bash/cURL command examples for testing the imported API, in addition to the Azure portal UI.
- Explicitly mention that all steps can be performed from any OS via the Azure portal, and highlight any platform-specific considerations if they exist.
- Provide PowerShell and Bash script equivalents for common tasks, ensuring parity between Windows and Linux users.
- Where screenshots are used, ensure they do not show Windows-specific UI elements (such as Windows file paths or PowerShell prompts).
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/protect-with-ddos-protection.md
...rticles/api-management/protect-with-ddos-protection.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references enabling DDoS IP Protection via a link to a Powershell-based guide, but does not mention or provide equivalent Linux/CLI examples. The instructions for enabling DDoS Protection focus on the Azure Portal UI, which is platform-agnostic, but the only programmatic example referenced is Windows/Powershell-specific. No Bash, Azure CLI, or Linux-native instructions are provided.
Recommendations
- Add Azure CLI examples for enabling DDoS Protection on a public IP address and virtual network, ensuring Linux users have parity.
- Explicitly mention that both Powershell and Azure CLI can be used, and provide links to both sets of instructions.
- Where possible, include Bash script snippets or instructions for Linux environments alongside Powershell examples.
- Review related linked documentation to ensure Linux/CLI instructions are present and referenced equally.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-mcp.md
...n/articles/app-service/configure-authentication-mcp.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates a mild Windows bias by referencing Microsoft Entra ID and Visual Studio Code (with GitHub Copilot) as primary examples, both of which are strongly associated with Windows development environments. There is also a focus on App Service Authentication, which is more commonly used in Windows-centric Azure workflows. No explicit Linux or cross-platform command-line examples (e.g., Bash, curl) are provided, and no mention is made of Linux-specific tools or patterns. However, there are no direct PowerShell examples or exclusive Windows command-line instructions.
Recommendations
- Include Linux-centric examples, such as using Bash or curl to interact with authentication endpoints.
- Mention Linux-friendly identity providers or tools (e.g., Keycloak, Auth0) alongside Microsoft Entra ID.
- Add explicit notes or sections for configuring MCP server authorization in Linux-based App Service environments.
- Provide parity in client registration and consent flows for Linux users, possibly referencing CLI tools available on Linux.
- Ensure that examples and scenarios are not exclusively tied to Visual Studio Code or other Windows-preferred tools.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a detailed PowerShell example first for granting Microsoft Graph permissions, which is a Windows-centric tool. Although an Azure CLI example is also included, PowerShell is presented before CLI, and there are no explicit Linux shell (bash) or cross-platform scripting examples. The instructions reference Visual Studio for publishing, which is primarily a Windows tool, and do not mention Linux development environments or alternatives.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux users.
- Include bash shell script examples for Linux users where applicable.
- Mention Linux-compatible development tools (such as VS Code or command-line deployment) alongside Visual Studio.
- Clarify that all steps can be performed on Linux, macOS, or Windows, and note any platform-specific differences.
- Add notes or links to Linux-specific documentation for enabling managed identity and assigning permissions.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/self-hosted-gateway-overview.md
...rticles/api-management/self-hosted-gateway-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page exhibits a mild 'windows_first' bias by listing 'PowerShell' as a primary configuration tool in the management plane description, before mentioning other technologies. However, the rest of the documentation is platform-neutral, with a strong emphasis on Linux-based deployment (Docker, Kubernetes) and no exclusive use of Windows tools or examples. There are no PowerShell-heavy sections, missing Linux examples, or exclusive references to Windows tools.
Recommendations
- When listing configuration tools for the management plane, mention cross-platform tools (such as Azure CLI or REST API) before or alongside PowerShell to avoid implying Windows is the default or preferred environment.
- Provide explicit examples or references for Linux/macOS users where command-line interaction is discussed, ensuring parity with any PowerShell or Windows-specific mentions.
- If PowerShell is mentioned, clarify that it is available cross-platform, or provide alternative commands for Bash/Azure CLI where appropriate.
- Continue emphasizing Linux-based deployment and containerization, as this aligns with cross-platform best practices.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-facebook.md
...-service/configure-authentication-provider-facebook.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides only portal-based configuration steps and does not include any command-line examples. There are no explicit Windows-specific tools or commands (such as PowerShell), but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash) or cross-platform automation examples are provided. This omission can disadvantage Linux users or those who prefer automation over portal UI.
Recommendations
- Add Azure CLI examples for configuring Facebook authentication, which are cross-platform and suitable for both Windows and Linux users.
- Include Bash script snippets for automating the setup process.
- Explicitly mention that the portal steps are platform-agnostic, but provide links or references to CLI-based alternatives for users who prefer command-line interfaces.
- Ensure future documentation includes both portal and CLI/scripted approaches to accommodate a wider range of developer preferences and environments.