214
Pages Scanned
20
Pages Flagged
214
Changed Pages
9.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-03 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 214
Files Completed: 214
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
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The tutorial is heavily oriented toward Windows users, with all instructions and screenshots based on Visual Studio for Windows. PowerShell and Package Manager Console examples are used exclusively, and there are no instructions or examples for Linux/macOS users (e.g., using VS Code, CLI tools, or cross-platform deployment methods). Windows-specific tools and UI patterns are referenced throughout, creating friction for non-Windows users.
Recommendations
- Add parallel instructions for Linux/macOS users, including how to use VS Code or the .NET CLI for project creation, publishing, and database management.
- Provide examples using Azure CLI and cross-platform tools instead of only PowerShell/Visual Studio Package Manager Console.
- Include screenshots and steps for VS Code or CLI-based workflows.
- Mention that Visual Studio for Windows is required for this workflow, and suggest alternatives for Linux/macOS users.
- Clarify which steps are Windows-only and which can be performed on other platforms.
Create Pull Request
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides detailed instructions for enabling diagnostic logging via PowerShell but omits equivalent CLI or Bash examples for Linux/macOS users. The only programmatic example is a PowerShell cmdlet, and references to log conversion tools are .NET/C#-centric. There is no mention of Azure CLI or Bash scripting for enabling diagnostics, nor are Linux-native tools referenced for log analysis or conversion.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash scripting examples for common log management tasks.
- Mention or link to log conversion tools that are platform-agnostic or provide Python-based alternatives.
- Ensure that references to visualization tools (e.g., Excel, Power BI) are balanced with Linux-friendly options (e.g., Grafana, Kibana).
- When referencing PowerShell, clarify that Azure CLI is also available and provide links or examples.
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 page primarily describes uploading CA certificates via the Azure portal, which is platform-agnostic. However, the only command-line example provided is the PowerShell `New-AzApiManagementSystemCertificate` command, with no mention of Azure CLI or REST API equivalents. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add Azure CLI examples for uploading CA certificates, if supported.
- Mention REST API methods for certificate management where applicable.
- Clarify whether PowerShell is required or if alternatives exist for non-Windows users.
- Provide links or brief instructions for using cross-platform tools.
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 PowerShell, but omits equivalent Azure CLI examples, which are cross-platform and preferred by many Linux/macOS users. The PowerShell installation instructions and usage are prominent, and no Linux-specific guidance or parity is offered. The ARM template and portal instructions are platform-neutral, but the scripting section is Windows/PowerShell-centric.
Recommendations
- Add Azure CLI examples alongside PowerShell for all scripting sections, including creation and management of managed identities.
- Mention that Azure CLI is cross-platform and provide installation links for Linux/macOS users.
- Where PowerShell is referenced, clarify its cross-platform availability, but prioritize CLI for Linux parity.
- Ensure that all code samples and instructions are available for both PowerShell and CLI users.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section specifies that the relay agent (Hybrid Connection Manager) must be installed on a Windows Server 2012 or newer host, with no mention of Linux support or alternatives. This creates friction for Linux users who may wish to use Hybrid Connections. No PowerShell or Windows-first examples are present, but the omission of Linux guidance for Hybrid Connection Manager is a notable gap.
Recommendations
- Clarify whether Hybrid Connection Manager supports Linux hosts, and if so, provide installation and usage instructions for Linux.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest Linux-compatible alternatives for outbound connectivity.
- Review other sections for tool-specific guidance and ensure parity for Linux/macOS users where possible.
- Add a note or table summarizing platform support for each networking feature, especially where Windows-only tools are required.
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 approaches (such as using the Windows certificate store and C#/.NET examples) are presented first and in greater detail, with full code samples for both C# and Java on Windows. Linux guidance is present but less comprehensive: Linux-specific code examples are only provided for C#, and for other languages (Node.js, PHP, Python, Java), Linux users are told to consult external documentation. There is also a reliance on Windows concepts (certificate store, thumbprints) and tools, with Linux equivalents mentioned later or less prominently.
Recommendations
- Provide Linux-specific code samples for popular languages (Node.js, Python, Java, PHP), not just C#.
- Present Windows and Linux approaches in parallel sections or tabs, rather than Windows-first.
- Expand explanations of Linux certificate handling, including how to use environment variables and file paths in various languages.
- Clarify any differences in certificate formats or handling between Windows and Linux.
- Where possible, avoid assuming familiarity with Windows certificate stores or tools when discussing cross-platform scenarios.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is a noticeable Windows bias: Windows-specific tools (such as Kudu, MSDeploy, Web Deploy) are mentioned first and in more detail, and Windows-related environment variables and paths (e.g., D:\home, %HOME%) are often shown before or instead of Linux equivalents. Several sections (e.g., Build Automation, Logging, Caching) default to Windows terminology and examples, with Linux information sometimes appearing as an afterthought or in separate tabs. Some settings are described only for Windows, even when Linux equivalents exist.
Recommendations
- Ensure Linux and macOS examples and paths are shown alongside Windows examples, not just as secondary notes.
- Where Windows tools (e.g., Kudu, MSDeploy) are discussed, provide equivalent Linux tooling or clarify Linux alternatives (e.g., Oryx, ZIP deploy).
- Use platform-neutral terminology where possible, or clearly indicate when a setting is Windows-only.
- For each environment variable, specify applicability (Windows, Linux, or both) in the main table, not just in descriptions.
- Add Linux/macOS-specific troubleshooting and configuration guidance where relevant.
- Review ordering of sections and examples to avoid always presenting Windows first.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Application Gateway health monitoring provides configuration examples and references primarily using Azure PowerShell cmdlets (e.g., New-AzApplicationGatewayProbeHealthResponseMatch), without equivalent Azure CLI or ARM template examples. The 'MinServers' property is noted as only configurable via PowerShell, Azure CLI, or ARM templates, but only PowerShell is demonstrated. Additionally, PowerShell is mentioned first and exclusively in example sections, which may create friction for Linux/macOS users who prefer Azure CLI or other cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for probe matching and custom probe configuration.
- Provide ARM template snippets for relevant configuration tasks.
- When listing supported tools, mention Azure CLI and ARM templates before or alongside PowerShell.
- Clarify that all configuration tasks can be performed on Linux/macOS using Azure CLI or ARM templates.
- Consider including a table or section comparing PowerShell, Azure CLI, and ARM template approaches for common probe configuration scenarios.
Application Gateway
Configure an internal load balancer (ILB) endpoint
...configure-application-gateway-with-private-frontend-ip.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation page primarily provides instructions for configuring an internal load balancer endpoint using Azure Application Gateway via the Azure portal. When creating backend VMs, only Windows Server is used as the example image, and IIS (a Windows web server) is installed. The Cloud Shell instructions exclusively use PowerShell and Windows-specific commands for IIS installation, with no mention of Linux VM options, Linux web servers (such as Apache or Nginx), or Bash alternatives. This creates friction for Linux/macOS users who may wish to use Linux VMs or different web servers.
Recommendations
- Provide parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu) and installing a Linux web server (such as Apache or Nginx).
- Include Bash/CLI examples in Cloud Shell for Linux VM configuration and web server installation.
- Mention that backend pools can use Linux VMs and provide guidance for Linux users.
- Where PowerShell is used, offer Bash equivalents or clarify that both shells are supported in Cloud Shell.
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides command examples for Azure portal, Azure CLI, and Azure PowerShell in all relevant sections. However, PowerShell examples are always present and shown alongside CLI, which may subtly prioritize Windows users. The ordering of examples (portal, CLI, then PowerShell) is consistent, but PowerShell is included even though it is primarily a Windows tool, while no Linux/macOS-specific shell examples (e.g., Bash, zsh) are given. There is no evidence of Windows-only tools or patterns, and Linux parity is generally maintained, but the presence and prominence of PowerShell may create minor friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, not just Windows.
- Consider adding Bash/zsh script examples where appropriate, or explicitly state that Azure CLI commands are suitable for Linux/macOS users.
- If PowerShell is included, note its availability on non-Windows platforms to avoid implicit Windows bias.
- Ensure that CLI examples are equally prominent and that Linux/macOS users are not left uncertain about tool compatibility.
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 each step, and some variable assignment patterns (e.g., $scope=$apimID.substring(1)) are PowerShell-specific. There is no explicit Linux/macOS bias, but the inclusion of PowerShell examples and variable assignment patterns may create friction for Linux users. However, Bash examples are present for all steps.
Recommendations
- Clearly label Bash and PowerShell examples to avoid confusion.
- Ensure Bash examples are shown first for cross-platform parity.
- Add a note clarifying which examples are for Linux/macOS (Bash) and which are for Windows (PowerShell).
- Consider providing a brief explanation of the differences in variable assignment and string manipulation between Bash and PowerShell.
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 the prerequisites section tracks Azure PowerShell. The PowerShell example is given equal prominence to CLI, and there is no explicit mention of Linux/macOS-specific considerations (such as file path differences or shell compatibility). However, Azure CLI is cross-platform and shown first in deployment steps, mitigating most bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add a note indicating Azure PowerShell is primarily used on Windows, and CLI is recommended for Linux/macOS.
- Explicitly mention file path conventions for Linux/macOS (e.g., ./main.bicep vs .\main.bicep).
- Consider including a Bash example for deploying Bicep files, or referencing Cloud Shell as a cross-platform solution.
- Ensure prerequisites for Azure CLI are as prominent as PowerShell, and avoid tracking PowerShell unless necessary.
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 'Formatted for PowerShell', which may indicate a slight Windows bias. There are no missing Linux examples, but the presence of PowerShell-specific formatting and variable assignment patterns may create friction for Linux/macOS users. No Windows-only tools or patterns are mentioned, and the Azure CLI is cross-platform.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly with explicit labels.
- Consider showing Bash examples first, as Bash is the default shell on most Linux/macOS systems.
- Provide a brief note explaining the differences in shell syntax for users unfamiliar with PowerShell.
- Ensure parity in explanations and avoid implying PowerShell is the default or preferred shell.
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 concepts and requirements. However, in the 'Related content' section, a PowerShell-based example for connecting virtual networks is listed before any Linux or CLI equivalent, which may subtly prioritize Windows tools. No explicit PowerShell commands or Windows-specific tooling are used in the main guidance, and Linux/macOS users can complete all tasks described.
Recommendations
- In the 'Related content' section, add or prioritize links to Azure CLI or ARM template-based guides for connecting virtual networks, ensuring Linux/macOS parity.
- Where PowerShell is referenced, clarify that Azure CLI and portal options are available and provide links to those alternatives.
- Review other cross-links to ensure Linux/macOS users are equally supported in all referenced guides.
App Service
Authentication and Authorization
...s/app-service/overview-authentication-authorization.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides platform architecture details for both Windows (IIS module) and Linux/containers (Ambassador pattern), but the Windows section is presented first and slightly more detailed. All command-line examples use cross-platform Azure CLI (az), and no Windows-specific tools or PowerShell are mentioned. No critical features are described as Windows-only, and Linux/container parity is generally maintained.
Recommendations
- Consider presenting Linux/container architecture details before or alongside Windows to avoid implicit Windows-first bias.
- Explicitly state that all Azure CLI examples are cross-platform and work on Linux/macOS as well as Windows.
- If possible, add clarifying notes about any minor differences in configuration or troubleshooting on Linux/container platforms.
- Ensure parity in troubleshooting/logging guidance for Linux/container environments, if any platform-specific differences exist.
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 mentions Windows/PowerShell as an option for creating an AKS cluster before Linux alternatives, but all deployment and operational examples use cross-platform tools (kubectl, YAML). No Windows-specific tools or patterns are prioritized in the main workflow, and Linux users can follow all steps without friction.
Recommendations
- List Linux (Azure CLI) and Windows (PowerShell) options together or with Azure CLI first, as it is cross-platform.
- Clarify that all kubectl commands and YAML files are platform-agnostic and can be run from any OS.
- Add a brief note that the workflow is fully compatible with Linux/macOS terminals.
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 to the CLI. The inclusion of PowerShell as a main workflow, and its detailed example, may create friction for Linux/macOS users, especially since native shell (bash/zsh) examples are not provided. The order of examples (portal, CLI, PowerShell) does not overtly prioritize Windows, but the presence of PowerShell as a core example is a mild bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider adding a bash/zsh shell example for invoking Azure CLI commands, demonstrating Linux/macOS usage.
- Explicitly note PowerShell's platform support, and suggest alternatives for Linux/macOS users if relevant.
- Ensure that CLI instructions are comprehensive and do not assume Windows-specific shell environments.
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, and PowerShell is a Windows-centric tool. The structure presents CLI and PowerShell examples in tabbed format, but PowerShell is included throughout, which may imply Windows as a primary platform. No Linux-specific tools or shell examples (e.g., Bash) are given, and there is no explicit mention of Linux/macOS compatibility or differences.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and are platform-agnostic.
- Consider mentioning Bash or shell environments for Linux/macOS users, or explicitly state that Azure CLI commands can be run in Bash, Zsh, or other shells.
- Add a note about Azure PowerShell being primarily for Windows, and recommend Azure CLI for cross-platform usage.
- If possible, provide example screenshots or terminal prompts from Linux/macOS environments to reinforce parity.
- Ensure that prerequisites for Azure CLI include instructions for Linux/macOS installation, not just Windows.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides cross-platform instructions for managing identities in Azure App Service and Azure Functions, including Azure CLI, PowerShell, ARM templates, and SDKs for .NET, JavaScript, Python, and Java. However, PowerShell examples are prominent and often listed before Azure CLI, and PowerShell is referenced heavily in some sections. Azure CLI (which is cross-platform) is included, but PowerShell (traditionally Windows-centric) is sometimes prioritized, and there are minor instances where PowerShell is used for tasks that could be shown with Bash or other Linux-native tools. There are no outright missing Linux examples, but the ordering and prominence of PowerShell may create friction for Linux/macOS users.
Recommendations
- Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
- Where possible, add Bash shell script examples alongside PowerShell for token retrieval and scripting.
- Clarify that Azure PowerShell is available cross-platform, but highlight Azure CLI as the preferred tool for Linux/macOS users.
- Consider including explicit notes or links for Linux/macOS users regarding installation and usage of Azure CLI and Azure PowerShell.
- Review and balance example ordering so that Windows-specific tools (PowerShell) do not appear before cross-platform tools (CLI/ARM).
App Service
Integrate your app with an Azure virtual network
...main/articles/app-service/overview-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a comprehensive overview of Azure App Service virtual network integration, with most content applicable to both Windows and Linux. However, in the 'Subnet requirements' section, Windows Containers-specific limits and calculations are described before any Linux-specific guidance. There are also more detailed examples for Windows Containers, while Linux container guidance is less prominent and only briefly mentioned in the 'Linux continuous deployment' section.
Recommendations
- Add parity by including Linux container-specific subnet/IP guidance alongside Windows Containers, not only in the Linux continuous deployment section.
- Ensure Linux-specific examples and limits are described with equal detail and visibility as Windows equivalents.
- Where Windows-specific guidance is given, provide a clear Linux counterpart or clarify if not applicable.
- Consider reorganizing sections so Linux and Windows guidance are presented together, rather than Windows first.