183
Pages Scanned
19
Pages Flagged
183
Changed Pages
10.4%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-09 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 183
Files Completed: 183
Problematic Pages
19 issues found
App Service
Tutorial: ASP.NET app with Azure SQL Database
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The tutorial is heavily oriented toward Windows users, specifically those using Visual Studio on Windows. All instructions, screenshots, and tooling references are for Visual Studio (Windows), with no mention of Linux/macOS alternatives. PowerShell and Package Manager Console commands are used without cross-platform equivalents. There are no examples or guidance for Linux/macOS users, such as using VS Code, CLI tools, or cross-platform deployment workflows.
Recommendations
- Add instructions for Linux/macOS users, including how to use VS Code or the Azure CLI for app publishing and database setup.
- Provide cross-platform examples for package installation and database migration (e.g., dotnet CLI, EF Core migrations).
- Include guidance for connecting to Azure SQL Database from non-Windows environments, such as using sqlcmd on Linux/macOS or Azure Data Studio.
- Mention alternative tools and workflows for app deployment and log streaming that work on Linux/macOS.
- Clearly indicate which steps are Windows-only and provide links or references to Linux/macOS equivalents where possible.
Create Pull Request
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides step-by-step instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, all CLI-based examples are exclusively in Azure PowerShell, with no mention of Azure CLI or Bash equivalents. PowerShell is presented as the only scripting option, and instructions for installing Azure PowerShell reference Windows-centric guidance. There are no Linux/macOS-specific examples or notes, and PowerShell is shown before ARM templates, reinforcing Windows-first patterns.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash shell scripting examples where appropriate, or clarify that PowerShell commands can be run on Linux/macOS with PowerShell Core.
- Mention that Azure PowerShell is available on Linux/macOS, and provide links to installation instructions for those platforms.
- Consider presenting Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly state platform compatibility for each tool and example.
API Management
Defend API Management Against DDoS Attacks
...rticles/api-management/protect-with-ddos-protection.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation references enabling DDoS IP Protection via a linked page that uses PowerShell for configuration, which is traditionally Windows-centric. There are no explicit Linux/macOS CLI or Azure CLI examples on this page. The Azure portal steps are platform-neutral, but the only programmatic example referenced is PowerShell.
Recommendations
- Add Azure CLI examples for enabling DDoS IP Protection, as Azure CLI is cross-platform and works on Linux/macOS.
- Explicitly mention that PowerShell can be used on Linux/macOS, or provide Bash equivalents.
- Ensure that referenced pages (such as manage-ddos-protection-powershell-ip.md) include Azure CLI and REST API instructions alongside PowerShell.
API Management
Add a Custom CA Certificate - API Management | Microsoft Docs
...api-management/api-management-howto-ca-certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation primarily describes uploading CA certificates via the Azure portal, which is platform-neutral. However, the only command-line example provided is the Windows PowerShell command (`New-AzApiManagementSystemCertificate`). There is no mention of Linux/macOS equivalents (such as Azure CLI or REST API usage), nor are Linux tools or workflows referenced. This creates friction for non-Windows users who prefer or require command-line automation.
Recommendations
- Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform.
- Mention REST API options for certificate management, with example requests.
- Clarify that PowerShell is Windows-centric and provide alternatives for Linux/macOS users.
- Consider linking to documentation on using certificates with Linux tools (e.g., OpenSSL) for certificate preparation.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias: Windows examples and certificate store access patterns are presented first and in greater detail, with C# and Java code samples for Windows, while Linux examples are less prominent and mostly limited to file-based access. There are no direct code examples for Linux in languages other than C#, and users of Node.js, PHP, Python, or Java on Linux are referred to external documentation. Windows-specific tools and patterns (certificate store, thumbprint usage) are emphasized throughout.
Recommendations
- Add code examples for Linux environments in popular languages such as Node.js, Python, Java, and PHP, showing how to load certificates from the provided file paths.
- Present Linux and Windows examples in parallel or with equal prominence, especially in sections describing certificate access.
- Clarify at the beginning that both Windows and Linux are supported, and provide a summary table of differences.
- Reduce reliance on Windows-specific terminology and tools (e.g., certificate store, thumbprints) when describing cross-platform approaches.
- Link to or provide sample scripts for common Linux certificate management tasks.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for RBAC assignments, but PowerShell is given equal prominence and referenced in multiple places. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, while Linux alternatives (OpenSSL) are referenced but not explained in detail. Windows tooling is presented first or equally, and some export instructions link to Windows-specific guides. Linux/macOS users may need to infer steps or consult external documentation for parity.
Recommendations
- Provide explicit Linux/macOS instructions for certificate export (e.g., OpenSSL usage, file paths, and troubleshooting).
- Include more detailed OpenSSL command examples, especially for common scenarios and error handling.
- Add links to Linux/macOS certificate management guides, or summarize key steps inline.
- When mentioning Windows tools (IIS, Certreq.exe), also mention Linux/macOS equivalents or clarify when Windows-only steps are required.
- Ensure Azure CLI examples are shown before or alongside PowerShell, and clarify cross-platform support.
Low 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 shown immediately after Bash for every step, indicating a Windows-first approach. The PowerShell formatting is prominent, which may suggest a bias toward Windows users. However, Linux (Bash) examples are present and complete, so Linux/macOS users can follow the instructions without missing information.
Recommendations
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)') to reduce visual bias and improve clarity.
- Ensure Bash examples are presented first or equally, especially since Azure CLI is cross-platform.
- Add a brief note clarifying that Bash examples are for Linux/macOS and PowerShell for Windows, to guide users.
- Review for any subtle differences in command syntax or environment variables that may affect Linux/macOS users.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell (Windows) examples for Azure CLI commands. However, in each case, the Bash example is shown first, followed by the PowerShell version. There are no exclusive Windows tools or patterns, and Linux/macOS users are fully supported.
Recommendations
- No major changes needed, as both Bash and PowerShell examples are provided.
- Consider clarifying in the tab headers or code comments which examples are for Bash (Linux/macOS) and which are for PowerShell (Windows) to further reduce ambiguity.
- Ensure that the Bash examples are always presented first if following a Linux-first approach, or provide clear tabs for each platform.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template. However, PowerShell is a Windows-centric tool and is presented alongside Azure CLI, which is cross-platform. There is minor bias in listing PowerShell as a primary method, but Linux/macOS users can use Azure CLI without issue. No Windows-only tools or patterns are mentioned, and the instructions are generally platform-neutral.
Recommendations
- Explicitly note that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell, or clarify that both methods are equivalent.
- Add a brief note that Azure PowerShell is available on Linux/macOS via PowerShell Core, but Azure CLI is often simpler for non-Windows environments.
- Ensure that any references to uploading files in Azure Cloud Shell are clear for both Bash and PowerShell environments.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is most commonly used on Windows) and its dedicated example introduces a mild Windows bias. Additionally, PowerShell is listed alongside CLI in the prerequisites and workflow steps, and the PowerShell example is given equal prominence to CLI, which may subtly prioritize Windows tools. However, all critical tasks can be completed using Azure CLI, which works on Linux and macOS, and no steps are Windows-only.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (if true), or note any Windows-specific limitations.
- Consider adding Bash or shell script examples for Azure CLI to reinforce Linux parity.
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
- If PowerShell is not required for Linux/macOS users, note that CLI is sufficient for all tasks.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral, but there is minor evidence of Windows bias. Specifically, the 'Related content' section references 'Connect virtual networks from different deployment models using PowerShell', which is a Windows-centric tool, and it appears before any mention of Linux or cross-platform alternatives. No Linux-specific examples or CLI guidance are provided, and PowerShell is mentioned without reference to Azure CLI or Bash equivalents.
Recommendations
- Add links to equivalent Azure CLI documentation for connecting virtual networks, ensuring Linux/macOS users have clear guidance.
- When referencing PowerShell, also mention Azure CLI or Bash alternatives, or clarify if PowerShell Core (cross-platform) is supported.
- Review related content and examples to ensure Linux/macOS parity, such as including links to Bash or CLI-based tutorials.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low 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 receives equal prominence. There is a slight bias in the inclusion of PowerShell-specific requirements and examples, which are more relevant to Windows users, while Linux/macOS users primarily use Azure CLI. However, Linux parity is generally maintained, as CLI instructions are present and not secondary.
Recommendations
- Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider listing Azure CLI instructions first in each section to reduce Windows-first perception.
- Add a brief note clarifying that Azure PowerShell is primarily for Windows, while Azure CLI works on all platforms.
- Ensure that prerequisite sections for Azure CLI and PowerShell are equally detailed and accessible.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation primarily uses Azure Portal and Azure CLI examples, but when mentioning programmatic options for disabling regional gateways, Azure PowerShell is referenced alongside REST API and Azure CLI. Azure PowerShell is mentioned before Linux-native tools, and no Bash or Linux-specific scripting examples are provided. However, the Azure CLI is used for the main command-line examples, which is cross-platform.
Recommendations
- When listing programmatic options, mention Azure CLI before Azure PowerShell, as CLI is cross-platform.
- Provide Bash shell script examples for disabling/enabling regional gateways, especially for Linux/macOS users.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
- If referencing PowerShell, clarify that Azure PowerShell is available on Linux/macOS, or provide equivalent Bash examples.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides extensive PowerShell examples for backup and restore operations, with PowerShell shown first in each section. While Azure CLI and REST API examples are also provided, there is a notable emphasis on PowerShell usage, which is most commonly associated with Windows environments. The PowerShell examples use Windows-style variable assignment and scripting, and the prerequisites highlight Azure PowerShell installation before mentioning CLI or REST alternatives. However, Linux/macOS users can use Azure CLI and REST API methods, which are documented in parity.
Recommendations
- Consider presenting Azure CLI examples before PowerShell, or at least alternating their order to avoid implicit Windows-first bias.
- Explicitly mention that Azure CLI and REST API methods are fully cross-platform and suitable for Linux/macOS users.
- Add a note clarifying that PowerShell Core is available on Linux/macOS, and provide any relevant installation guidance if PowerShell usage is intended for those platforms.
- Ensure that all critical operations have CLI and REST API examples, and highlight their parity with PowerShell.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but the PowerShell example is given equal prominence and detail. The prerequisites list both Azure CLI and Azure PowerShell, but does not mention Bash or other Linux-native tools. The PowerShell example is presented after the CLI example, but the overall structure and content are neutral. There are no Windows-only tools or patterns mentioned, and the Azure CLI example is cross-platform. However, there is a mild bias in listing PowerShell as a primary tool alongside CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding Bash shell script examples for Azure CLI usage.
- Explicitly state that PowerShell is optional and primarily for Windows users.
- Mention that Azure CLI can be used on all platforms, while PowerShell is most common on Windows.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks, but PowerShell is featured equally alongside CLI. PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. However, Azure CLI examples are present and shown first in each section, ensuring Linux parity. No Windows-only tools or patterns are mentioned, and all instructions are cross-platform except for PowerShell.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- Consider adding a note for Linux/macOS users recommending Azure CLI as the preferred tool.
- Optionally, include Bash shell script examples for common tasks to further support Linux users.
- Ensure that all prerequisites and instructions for Azure CLI are clear and accessible for Linux/macOS environments.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is focused on gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (such as Test-NetConnection in PowerShell) are provided only for Windows, with no Linux/macOS equivalents. The use of Windows tools and commands is presented first and exclusively, and Linux users are not given guidance for comparable tasks. This creates friction for Linux users who may need to troubleshoot or understand related concepts, even though the feature itself is Windows-only.
Recommendations
- Clarify early and prominently that all operational and troubleshooting steps are Windows-specific due to the feature limitation.
- Where troubleshooting steps are relevant to general networking (e.g., testing connectivity from a VM), provide Linux/macOS equivalents (such as 'nc', 'telnet', or 'curl' for TCP connectivity tests).
- Add a note in troubleshooting sections that Linux users should use their platform's tools, and provide example commands.
- Ensure that any generic networking advice is platform-neutral or includes both Windows and Linux/macOS examples.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance using zone pivots, but Windows-specific examples, tools, and terminology (such as PowerShell, Windows Server base images, and IIS/ASP.NET) are often presented first or in greater detail. PowerShell commands are included alongside Bash/Azure CLI, and Windows-specific tooling (like Kudu and references to C:\home) appear throughout. Linux equivalents are present but sometimes less detailed or appear after Windows instructions.
Recommendations
- Ensure Linux-specific examples and explanations are as detailed and prominent as Windows ones.
- Where possible, present Linux and Windows instructions side-by-side, rather than Windows-first.
- Expand Linux troubleshooting and diagnostic sections to match Windows depth (e.g., Kudu, SSH, logs).
- Review for any Windows terminology or tooling that could be replaced with cross-platform alternatives.
- Clarify persistent storage paths for Linux (avoid referencing C:\home in Linux pivots).
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_path_bias
Summary
The documentation is generally cross-platform and uses Azure CLI as the primary scripting example, which is available on all major OSes. However, there are several instances where Windows conventions, paths, and tools are mentioned first or exclusively, such as using Windows-style environment variables (%HOME%), Windows directory paths (D:\home\site\wwwroot), and references to Kudu DebugConsole and FTP uploads without explicit Linux/macOS equivalents. There are also minor references to Windows-specific features (e.g., MySQL in-app for Windows), but these are called out as such. Linux paths and conventions are mentioned, but often after Windows, and sometimes only in explanatory tables.
Recommendations
- When referencing file paths, provide both Windows and Linux/macOS equivalents (e.g., D:\home\site\wwwroot and /home/site/wwwroot).
- When mentioning environment variables like %HOME%, also mention $HOME for Linux/macOS.
- In sections about uploading files (e.g., _backup.filter), suggest cross-platform tools (such as SCP, SFTP, or Azure CLI az webapp create-remote-connection) alongside FTP and Kudu DebugConsole.
- When showing examples or screenshots, alternate between Windows and Linux views, or clarify that the instructions apply to both.
- Explicitly state that the Azure CLI commands work on all platforms, and provide troubleshooting tips for common Linux/macOS issues if applicable.