183
Pages Scanned
20
Pages Flagged
183
Changed Pages
10.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-08 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 183
Files Completed: 183
Problematic Pages
20 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 heavily centers on Visual Studio for Windows, with all instructions, screenshots, and workflow steps referencing Windows-specific tools and UI. PowerShell and Package Manager Console examples are given, but no Linux/macOS equivalents or CLI alternatives are provided. The publishing workflow assumes Visual Studio on Windows, and Azure App Service (Windows) is selected by default, with no mention of Linux App Service or cross-platform development tools. There are no instructions for Linux/macOS users, nor any guidance for using .NET CLI, Azure CLI, or VS Code.
Recommendations
- Add parallel instructions for Linux/macOS users, including how to use .NET CLI, Azure CLI, and VS Code for app creation, publishing, and database connection.
- Include examples for publishing to Azure App Service (Linux) and clarify when Windows-specific steps are required.
- Provide cross-platform alternatives for PowerShell commands, such as Bash or Azure CLI equivalents.
- Mention and link to documentation for using Visual Studio Code and other cross-platform IDEs.
- Add notes or sections indicating which steps are Windows-only and how Linux/macOS users can achieve similar outcomes.
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
missing_linux_example
windows_tools
Summary
The documentation provides detailed instructions and code samples for Azure portal, Azure PowerShell, and ARM templates, but omits equivalent examples for Azure CLI (which is cross-platform and commonly used on Linux/macOS). PowerShell is featured heavily for scripting and automation, with explicit installation instructions and sample code, while no mention is made of Azure CLI or Bash scripting. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer CLI tools native to their platforms.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks (creating, updating, and removing managed identities).
- Mention Azure CLI as a supported tool for managing API Management instances and managed identities.
- Provide Bash scripting examples where appropriate, or clarify that PowerShell scripts can be run cross-platform if true.
- Reorder sections so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside PowerShell.
- Explicitly state that all operations can be performed via Azure CLI, not just 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 provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI or Bash examples. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not the default shell on Linux/macOS. The rest of the instructions are portal-based and platform-agnostic.
Recommendations
- Add Azure CLI example(s) for uploading a CA certificate, or clarify if this operation is not supported via Azure CLI.
- If PowerShell is the only supported CLI, explicitly state this and provide guidance for Linux/macOS users on installing and using PowerShell Core.
- Consider including Bash or REST API examples for certificate upload to improve parity.
- Mention cross-platform alternatives before or alongside Windows/PowerShell commands.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides three main workflows: Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, PowerShell is presented as a first-class option, and its example is given equal prominence to CLI. There is no explicit mention of Linux/macOS compatibility for PowerShell, nor are there any Linux/macOS-specific instructions or troubleshooting tips. The CLI example is generic and cross-platform, but the PowerShell section may confuse Linux/macOS users, as Azure PowerShell is less commonly used outside Windows. No Linux-specific tools or shell examples (e.g., Bash) are provided.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but may require additional setup on Linux/macOS.
- Add a Bash shell example for Azure CLI to demonstrate Linux/macOS usage.
- Explicitly mention that the Azure CLI example works on Linux/macOS and Windows.
- Consider adding troubleshooting notes for Linux/macOS users, such as file path conventions or authentication differences.
- If PowerShell is not recommended for Linux/macOS, state this clearly.
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-specific instructions and code samples (especially for C# and Java) are presented first and in greater detail, with Linux examples either missing, less detailed, or deferred to external language documentation. Windows certificate store access is explained thoroughly, while Linux approaches are less emphasized. Some sections provide only Windows code, or refer Linux users to 'see the documentation for the respective language.'
Recommendations
- Provide parallel Linux code examples (e.g., for Java, Node.js, Python, PHP) for loading certificates, not just C#.
- Present Linux and Windows instructions/examples side-by-side or in tabs throughout, not just in container sections.
- Expand on Linux-specific certificate handling (e.g., permissions, file formats, environment variables) where relevant.
- Avoid referring Linux users to external documentation for basic tasks that are explained in detail for Windows.
- Where possible, use cross-platform code samples (e.g., .NET Core) and clarify any OS-specific differences.
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 PowerShell-based guide, which is typically Windows-centric. There are no explicit Linux/macOS CLI examples or mentions of Azure CLI or other cross-platform tools. The guidance for enabling DDoS Protection on a public IP address points users to a PowerShell-focused workflow, potentially creating friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for enabling DDoS IP Protection, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell commands can be run on Linux/macOS using PowerShell Core, or provide Bash equivalents.
- Where possible, provide step-by-step instructions for both Azure Portal and Azure CLI workflows.
- Clarify tool requirements and alternatives for non-Windows users.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Medium 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 be a Windows-only feature. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command) are given only for Windows, with no Linux/macOS equivalents. Windows tools and patterns (PowerShell, netstat -aon) are mentioned exclusively or before any cross-platform alternatives. Linux users are told the feature is unsupported, but troubleshooting guidance is Windows-centric, creating friction for users managing hybrid environments.
Recommendations
- Clarify early and prominently that gateway-required virtual network integration is Windows-only, and that Linux apps are not supported.
- Where troubleshooting steps are given (e.g., Test-NetConnection, netstat -aon), provide equivalent Linux/macOS commands (e.g., nc, netcat, lsof, ss, curl) for users managing hybrid environments or diagnosing issues from non-Windows hosts.
- Add links or references to regional virtual network integration documentation for Linux users, as recommended throughout the page.
- Explicitly state that all examples and tools are Windows-specific due to feature limitations, to avoid confusion.
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 provides Azure CLI and Azure PowerShell examples for disabling routing to a regional gateway, but it mentions the PowerShell cmdlet before the CLI command and does not provide Linux/macOS-specific guidance or examples. The overall workflow is portal-centric and cross-platform, but command-line instructions slightly favor Windows/PowerShell users.
Recommendations
- List Azure CLI commands before PowerShell cmdlets, as Azure CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure CLI works on Linux/macOS and provide any relevant shell usage tips.
- Add bash/zsh shell example snippets where appropriate, especially for scripting or automation.
- Clarify that all portal instructions are platform-agnostic.
- Consider mentioning that PowerShell Core is available on Linux/macOS if referencing PowerShell.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are given alongside Bash for every step, and in some cases, PowerShell syntax is shown first or is labeled as 'Formatted for PowerShell', which may imply a Windows-centric approach. There is no explicit Linux bias, but the inclusion of PowerShell examples throughout may create a perception of Windows preference.
Recommendations
- Clearly label Bash and PowerShell examples, and ensure Bash (Linux/macOS) examples are shown first, as Bash is the default shell for Azure CLI and most cross-platform users.
- Consider providing only Bash examples unless there is a specific need for PowerShell, or move PowerShell examples to a separate tab or section to avoid clutter and bias.
- Explicitly mention that Bash examples are suitable for Linux/macOS and Windows (with WSL or Git Bash), and PowerShell is for Windows users.
- Ensure variable naming and command syntax is consistent and correct for each shell (e.g., $scope vs. $apimID).
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 without explicit mention of Linux/macOS alternatives. Azure CLI is cross-platform, but the documentation does not highlight this or provide Bash-specific guidance. The PowerShell example may create friction for Linux/macOS users, especially since PowerShell is less commonly used outside Windows.
Recommendations
- Clarify that Azure CLI is cross-platform and works natively on Linux/macOS.
- Consider providing Bash shell examples or explicitly noting that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells.
- Mention that PowerShell Core is available on Linux/macOS if referencing PowerShell, or link to installation instructions for non-Windows platforms.
- If possible, prioritize Azure CLI examples or present them before PowerShell, since CLI is more universal.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are consistently shown immediately after Bash, and are labeled as 'Formatted for PowerShell', which may imply a Windows-centric approach. There is no explicit mention of Linux/macOS, nor are Bash examples labeled as 'Linux/macOS'. The portal instructions are platform-neutral, but the CLI section subtly prioritizes Windows by including PowerShell variants for every command.
Recommendations
- Label Bash examples as 'Linux/macOS' and PowerShell as 'Windows' to clarify platform applicability.
- Consider using tabbed code blocks for Bash (Linux/macOS) and PowerShell (Windows) to visually separate and equally prioritize both platforms.
- Add a brief note explaining that Bash examples are for Linux/macOS terminals and PowerShell examples are for Windows.
- Ensure parity in instructions and avoid implying that PowerShell is the default or preferred shell for Azure CLI usage.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files. While both tools are cross-platform, Azure PowerShell is more commonly associated with Windows environments. However, the CLI example is given first, and both are presented equally. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks using Azure CLI. No Linux-specific examples or notes are missing, but minor bias exists in the inclusion of PowerShell, which may be unnecessary for Linux users.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider adding a note that Azure PowerShell is also available on Linux/macOS, or indicate which tool is preferred for each platform.
- Optionally, provide Bash shell scripting examples for common automation scenarios.
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, Azure PowerShell is primarily used on Windows and its example is given equal prominence. The PowerShell example is detailed and included alongside CLI, but there are no Linux/macOS-specific shell examples (e.g., Bash) or notes about cross-platform usage. Additionally, the PowerShell section appears after the CLI, but both are presented as primary options.
Recommendations
- Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
- Add explicit notes or examples for Bash or other Linux-native shells if relevant.
- Mention that Azure PowerShell can be used on Linux/macOS, but CLI is generally preferred for cross-platform scenarios.
- Consider including a brief comparison table or guidance for users on different platforms to help them choose the best tool.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, resource review, and cleanup steps. Azure CLI is cross-platform and appears first in each example section, while PowerShell (which is Windows-centric, though available on Linux/macOS) is provided as an alternative. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using Azure CLI. There is a minor bias in that PowerShell is included throughout, but CLI is always shown first, minimizing friction.
Recommendations
- Consider clarifying that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Optionally, add a note that PowerShell examples are provided for users who prefer PowerShell, but Azure CLI is the default for cross-platform scenarios.
- Ensure that any referenced prerequisites for PowerShell mention its availability on Linux/macOS, if relevant.
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 detailed PowerShell examples for backup and restore operations, with PowerShell examples presented before Azure CLI and REST API examples. While Azure CLI (bash) and REST API instructions are included, the prominence and order of PowerShell content may create friction for Linux/macOS users, especially since PowerShell is traditionally associated with Windows environments.
Recommendations
- Present Azure CLI (bash) examples before or alongside PowerShell examples to signal equal support for Linux/macOS users.
- Explicitly mention that Azure PowerShell is cross-platform and provide guidance for installing and using PowerShell on Linux/macOS.
- Expand CLI examples to cover managed identity scenarios, matching the detail provided in PowerShell sections.
- Add a note clarifying that all operations can be performed from Linux/macOS using Azure CLI or PowerShell Core.
- Ensure parity in variable setup and context for CLI and REST examples, matching the completeness of PowerShell instructions.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides links for creating an AKS cluster using Azure CLI, Azure PowerShell, and Azure Portal, with PowerShell mentioned before Portal. However, all deployment and verification steps use kubectl commands, which are cross-platform and standard for Kubernetes. No Windows-specific tools or patterns are prioritized, and Linux/macOS users can follow all steps without friction.
Recommendations
- Consider listing Azure CLI before PowerShell in the prerequisites, as Azure CLI is more commonly used on Linux/macOS.
- Explicitly mention that kubectl commands work on Windows, Linux, and macOS to reassure non-Windows users.
- If possible, provide brief notes or links about installing kubectl on different platforms.
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_first
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and requirements for API Management virtual network injection. However, in the 'Related content' section, a link to 'Connect virtual networks from different deployment models using PowerShell' is included, which presents Windows/PowerShell tooling before any Linux or cross-platform alternatives. No Linux-specific examples or CLI equivalents are mentioned alongside this reference.
Recommendations
- Add links or references to Azure CLI or Bash-based guides for connecting virtual networks, ensuring Linux/macOS users have parity.
- When referencing PowerShell-based documentation, also mention cross-platform alternatives (e.g., Azure CLI) where available.
- Review related content sections to ensure Windows tools are not presented as the default or only option.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is structured to cover both Windows and Linux containers, with clear pivots for each. However, there are several sections where Windows-specific information, examples, and tools (such as PowerShell) are presented first or in greater detail. PowerShell examples are consistently provided alongside Bash/Azure CLI, and Windows parent images and tools are discussed before Linux equivalents. Some Windows-specific features (like IIS, .NET Framework, and machine key injection) are covered in dedicated pivots, but Linux parity is generally maintained. Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- Where possible, alternate the order of Windows and Linux pivots or present Linux examples first in some sections.
- Ensure that Linux-specific parent image recommendations and cached images are listed with equal prominence as Windows images.
- For generic configuration tasks (environment variables, persistent storage, etc.), clarify Linux-specific paths and behaviors before or alongside Windows details.
- Consider providing Bash/Azure CLI examples before PowerShell, or at least in parallel, to avoid implicit Windows-first bias.
- Review pivoted content for completeness and parity, ensuring Linux pivots are as detailed as Windows pivots.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC permissions, but PowerShell is presented as a first-class option throughout. References to Windows tools (IIS, Certreq.exe) for certificate export are given, and the FAQ links to both Azure CLI and PowerShell scripts, but PowerShell is mentioned first. The certificate export section mentions OpenSSL for Linux/macOS, but also references Windows-specific tools and links to Windows documentation. Overall, Windows tools and patterns are mentioned alongside Linux equivalents, but Windows options are often presented first or more prominently.
Recommendations
- Ensure Linux/macOS tools (OpenSSL, Azure CLI) are mentioned before or alongside Windows tools in all relevant sections.
- Provide explicit Linux/macOS instructions and links for certificate export and management, not just OpenSSL commands.
- In automation sections and FAQs, list Azure CLI examples before PowerShell, or clarify parity between the two.
- Where Windows-specific tools are referenced (IIS, Certreq.exe), add equivalent Linux/macOS guidance or clarify when Windows-only steps are required.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
minor_windows_pathing
Summary
The documentation is generally cross-platform, with Azure Portal and Azure CLI instructions (CLI being cross-platform). However, there are several instances where Windows conventions, tools, or paths are mentioned first or exclusively, and PowerShell is referenced alongside CLI for automation. Linux equivalents are present but sometimes secondary. There are minor references to Windows paths and tools (e.g., D:\home, %HOME%, Kudu DebugConsole, FTP) without always clarifying Linux alternatives. PowerShell is mentioned as an automation option, but no Bash or shell script samples are provided. Overall, Linux/macOS users can complete all tasks, but some friction exists due to Windows-first conventions.
Recommendations
- When referencing file paths (e.g., %HOME%, D:\home), also mention Linux equivalents (e.g., /home/site/wwwroot).
- When describing how to upload files (e.g., via FTP or Kudu DebugConsole), clarify that these tools are available for both Windows and Linux App Service plans, and mention SFTP or SCP as alternatives.
- When listing automation options, provide Bash/shell script examples or explicitly state that Azure CLI commands work on all platforms.
- If referencing PowerShell, also reference Bash or shell scripting for parity.
- In tables or lists where both Windows and Linux are supported, avoid listing Windows first unless there is a technical reason.