213
Pages Scanned
25
Pages Flagged
213
Changed Pages
11.7%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-05 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 213
Files Completed: 213
Problematic Pages
25 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, specifically those using Visual Studio on Windows. All examples, screenshots, and instructions reference Windows tools and workflows (Visual Studio, Package Manager Console, SQL Server Object Explorer), with no mention of Linux/macOS equivalents or cross-platform tooling. PowerShell and Windows-specific commands are used, and the publishing workflow is tied to Visual Studio's Windows UI. There are no instructions for Linux/macOS users, nor alternatives for cross-platform development environments.
Recommendations
- Add instructions for using Visual Studio Code or CLI tools (such as Azure CLI, dotnet CLI) for publishing and managing ASP.NET apps and Azure SQL Database.
- Provide examples for Linux/macOS users, including how to run and debug the sample project using dotnet CLI and VS Code.
- Include cross-platform alternatives for database management (e.g., Azure Data Studio, sqlcmd on Linux/macOS, or Azure Portal).
- Clarify which steps are Windows-only and offer parity guidance for Linux/macOS users where possible.
- Reorder examples to avoid always presenting Windows/Visual Studio first, or explicitly note Windows-specific sections.
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_first
Summary
The documentation provides detailed instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, it exclusively offers PowerShell-based CLI examples for scripting, with no equivalent Azure CLI (az) or Bash examples. PowerShell is primarily associated with Windows, although it is cross-platform, but Azure CLI is more commonly used on Linux/macOS. The PowerShell instructions are presented before any mention of ARM templates, and there is no guidance for Linux/macOS users or explicit mention of cross-platform alternatives.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all scripting tasks, including creating resource groups, managed identities, and API Management instances.
- Explicitly mention that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
- Consider presenting Azure CLI and PowerShell examples side-by-side or in tabs, rather than PowerShell-only.
- Include notes or links for Linux/macOS users about installing and using Azure CLI.
- Review and update any references to Windows-centric tools or patterns to ensure Linux/macOS parity.
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/Linux commands. 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, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention if PowerShell is required and provide guidance for Linux/macOS users on how to install/use PowerShell if no alternative exists.
- Consider including Bash or REST API examples for certificate management to ensure parity for non-Windows users.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell section is Windows-centric and lacks mention of cross-platform PowerShell Core usage on Linux/macOS. The PowerShell example is given equal prominence to CLI, but there are no explicit Linux/macOS shell examples (e.g., Bash). Additionally, there is no guidance for Linux users regarding PowerShell installation or usage, and the portal instructions do not mention platform differences.
Recommendations
- Clarify that Azure CLI is cross-platform and works on Linux/macOS.
- Explicitly state that Azure PowerShell can be used on Linux/macOS via PowerShell Core, and provide installation links or notes.
- Consider adding Bash shell examples for Azure CLI usage to reinforce Linux parity.
- Mention any platform-specific differences in the Azure portal experience, if applicable.
- Add a short section or note for Linux/macOS users outlining recommended tools and any prerequisites.
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. The primary, detailed code examples for loading certificates are given for Windows (C# and Java using the Windows certificate store), with Linux-specific guidance and examples appearing later and being less comprehensive. Non-Windows languages (Node.js, PHP, Python, Java) are referenced only by suggesting users consult external documentation, with no direct examples provided. Windows-specific tools and patterns (certificate store, environment variables, and app settings) are explained in detail, while Linux equivalents are less emphasized or lack parity in example depth.
Recommendations
- Provide direct, in-page code examples for loading certificates in popular languages (Node.js, Python, Java, PHP) for both Windows and Linux environments.
- Ensure Linux examples are as detailed as Windows ones, including file paths, environment variables, and error handling.
- Present Windows and Linux guidance in parallel or with equal prominence, rather than leading with Windows.
- Clarify any platform-specific limitations or differences up front, and link to language- or OS-specific best practices where appropriate.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and does not focus on Windows-specific features. However, the 'Hybrid Connections' section exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. This creates friction for Linux users who may wish to use Hybrid Connections but are not provided guidance or examples.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux users.
- Review other sections for tool-specific instructions and ensure parity for Linux/macOS where possible.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page provides examples and instructions for both Windows and Linux users in most sections, but there are notable Windows biases. Windows directory paths (%HOME%, D:\home\site\wwwroot) and tools (Kudu DebugConsole, FTP) are mentioned first or exclusively in several places. PowerShell is referenced alongside Azure CLI for scripting, but Linux shell examples are not provided. The instructions for creating the _backup.filter file use Windows-style paths and refer to Windows-specific folders. However, Linux parity is generally maintained for core backup/restore tasks, and Azure CLI is cross-platform.
Recommendations
- Provide Linux/macOS equivalents for directory paths (e.g., /home/site/wwwroot instead of D:\home\site\wwwroot).
- Include Linux shell scripting examples alongside PowerShell in the 'Automate with scripts' section.
- Clarify that tools like Kudu DebugConsole and FTP are available for both Windows and Linux App Service apps, and provide Linux-specific instructions where relevant.
- Show Linux directory structure and path examples in the partial backup section.
- Ensure that references to environment variables (e.g., %HOME%) include Linux equivalents ($HOME).
App Service
Tutorial for event-driven background processing with the WebJobs SDK
...b/main/articles/app-service/webjobs-sdk-get-started.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The tutorial is heavily oriented toward Windows users, specifically those using Visual Studio 2022. All instructions, screenshots, and examples reference Windows tools and workflows (e.g., Visual Studio menus, Package Manager Console, PowerShell commands). There are no examples or guidance for Linux/macOS users, such as using .NET CLI, VS Code, or alternative package management methods. This creates friction for non-Windows users, though the underlying .NET 8/WebJobs SDK is cross-platform.
Recommendations
- Add instructions for creating and managing the project using .NET CLI (dotnet new, dotnet add package, etc.), which works on Linux/macOS.
- Include examples for installing NuGet packages via CLI, not just via Visual Studio Package Manager Console.
- Provide guidance for running and debugging the project using VS Code or other cross-platform editors.
- Mention any platform-specific limitations (if any) and clarify that WebJobs SDK projects can be developed and run on Linux/macOS.
- Add screenshots or descriptions for Azure Portal steps that are not OS-specific.
- Explicitly note that Visual Studio is optional and provide parity steps for Linux/macOS users.
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 provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux scenarios. However, there is a notable Windows bias: Windows-specific tools (such as Kudu, Web Deploy/MSDeploy, IIS, and Windows paths) are mentioned first or exclusively in several sections, and Windows-centric terminology and examples (e.g., `%HOME%`, `D:\home`, `.dll` extensions, Windows-specific build automation) appear before or more frequently than Linux equivalents. Linux-specific details are often present but secondary, and some settings are described primarily in Windows terms with Linux notes added later. The build automation section is split into Windows (Kudu) and Linux (Oryx) tabs, but the Windows tab is presented first. Some environment variables and features are described only for Windows, with Linux coverage less prominent.
Recommendations
- Ensure Linux examples and terminology are presented alongside Windows examples, not after or as an afterthought.
- When describing environment variables, provide both Windows and Linux path examples (e.g., `D:\home` and `/home`).
- In build automation sections, consider presenting Linux (Oryx) and Windows (Kudu) equally, or default to the user's platform if possible.
- Where Windows tools (e.g., Web Deploy/MSDeploy, IIS, .dll) are mentioned, clarify Linux alternatives or note if not applicable.
- Review language-specific settings to ensure Linux-specific variables and behaviors are described with equal detail and clarity.
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 largely platform-neutral, focusing on Azure networking concepts. However, there is a minor bias in the 'Related content' section, which links to a PowerShell-based guide for connecting virtual networks. This may imply Windows-first tooling, as PowerShell is traditionally associated with Windows, even though it is now cross-platform. No Linux-specific CLI examples or references are provided, and the PowerShell guide is mentioned before any Azure CLI or ARM template alternatives.
Recommendations
- Add links to equivalent Azure CLI documentation for connecting virtual networks, ensuring Linux/macOS users have clear guidance.
- Where PowerShell is referenced, clarify that Azure CLI or ARM templates can also be used, and provide links or examples.
- In the 'Related content' section, balance PowerShell links with Azure CLI alternatives, or note that PowerShell is available cross-platform.
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, and the PowerShell formatting is explicitly called out as 'Formatted for PowerShell', which may indicate a slight bias toward Windows users. Additionally, the PowerShell examples are not strictly necessary since Azure CLI works identically on all platforms, but their inclusion may help Windows users. The Bash examples are present and shown first, so Linux parity is mostly maintained.
Recommendations
- Clarify that Azure CLI commands work cross-platform and that Bash examples are suitable for Linux/macOS users.
- Consider grouping Bash and PowerShell examples under clear headings (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)') to make parity explicit.
- Ensure variable naming and command syntax is consistent and correct between Bash and PowerShell examples.
- Add a note that PowerShell examples are for Windows users, while Bash is for Linux/macOS.
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 for examples, but briefly mentions Azure PowerShell (set-azapimanagement) as a tool for disabling regional gateways. The PowerShell reference appears alongside CLI and REST API options, but no Linux-specific or macOS-specific guidance or examples are provided. The ordering sometimes places PowerShell before CLI, and there are no explicit Linux/macOS parity notes. However, the CLI examples are platform-agnostic and are shown in full, so Linux/macOS users can complete all tasks.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- When mentioning Azure PowerShell, note its Windows-centric nature and suggest Azure CLI as the preferred cross-platform tool.
- Consider providing example scripts or command-line snippets for Linux/macOS environments where relevant, such as bash or zsh.
- Explicitly state that all portal and CLI steps are platform-independent unless otherwise noted.
API Center
Perform API Linting and Analysis
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both bash and PowerShell examples for Azure CLI commands, but PowerShell syntax is often shown immediately after bash, and Visual Studio Code is referenced as the primary editor. Output paths and screenshots use Windows-style paths and environments (e.g., C:\Users\<user>), and instructions reference Windows keyboard shortcuts. However, Linux/macOS equivalents are generally present, and the Azure CLI and Azure Developer CLI are cross-platform tools.
Recommendations
- Show bash and PowerShell examples side-by-side, or alternate which comes first.
- Include explicit notes that all CLI commands work on Linux/macOS and Windows.
- Add screenshots or output examples from Linux/macOS environments, or clarify that output paths may differ.
- Mention that Visual Studio Code is available on Linux/macOS, and provide alternative editor options if relevant.
- Use generic file paths in examples, or note differences between OSes.
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 for every step, and in each case, the PowerShell version is shown immediately after the Bash version, indicating a Windows-first approach. There is no explicit mention of Linux/macOS, but Bash is used, which is cross-platform. The presence of PowerShell throughout may create friction for Linux/macOS users, but all necessary Bash examples are present.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and Windows (with WSL or Git Bash).
- Consider labeling Bash examples as 'Linux/macOS' and PowerShell as 'Windows', to make parity clearer.
- If possible, provide a brief note about running Azure CLI on Linux/macOS and Windows, including links to installation guides.
- Ensure Bash examples are not presented as secondary to PowerShell; consider alternating order or making Bash the default.
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 the Bicep file, but PowerShell is mentioned alongside CLI throughout and is given equal prominence. There is a slight bias in that PowerShell is included as a primary option, which is more relevant to Windows users, while Linux/macOS users typically use Azure CLI. However, CLI examples are present and shown first, so Linux users are not blocked.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- Explicitly state that Azure CLI works on Linux/macOS and is recommended for those platforms.
- Consider adding a note or section for Linux/macOS users, highlighting the CLI workflow and any relevant differences.
- Ensure that any referenced prerequisites or setup guides for Azure CLI include Linux/macOS instructions.
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 shown first in each example section. Azure CLI and REST API examples are also included, supporting cross-platform usage. However, the prominence and detail of PowerShell examples, as well as their placement before CLI/Bash examples, indicate a mild Windows bias. All CLI examples use Bash syntax, ensuring Linux/macOS parity, and REST API instructions are platform-neutral.
Recommendations
- Consider presenting Azure CLI (Bash) examples before PowerShell, or side-by-side, to avoid implying Windows as the default platform.
- Expand Azure CLI examples to include managed identity scenarios, matching the detail provided for PowerShell.
- Explicitly note that Azure CLI and REST API methods are fully supported on Linux/macOS, and highlight their parity.
- Where possible, provide links to additional Linux/macOS-specific guidance or troubleshooting.
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 steps, but PowerShell is featured equally alongside CLI, which is primarily used on Windows. There is no explicit mention of Linux/macOS-specific tools or patterns, and the CLI examples are cross-platform. However, PowerShell is presented as a first-class option, which may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- Add brief notes indicating that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
- Consider including Bash shell examples or highlighting CLI usage in Bash for Linux/macOS users.
- If possible, reorder examples to show Azure CLI first, or explicitly state platform applicability for each tool.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions using pivot sections, but in several shared sections, Windows/PowerShell examples are consistently presented before Linux/Bash equivalents. PowerShell commands are included alongside Bash for most configuration steps, and some advanced configuration and troubleshooting (e.g., customizing container memory, CPU, health ping, and diagnostic log access) are described in more detail for Windows containers. Windows-specific tools and patterns (e.g., C:\home, System.ConfigurationManager, IIS, .NET Framework) are referenced more prominently, and some sections (like customizing ASP.NET machine key injection) are Windows-only. However, Linux parity is generally maintained through dedicated pivot sections and Linux-specific instructions.
Recommendations
- When providing both Bash and PowerShell examples, alternate the order or clearly label both as equal options to avoid implicit prioritization.
- Ensure that advanced configuration and troubleshooting sections for Linux containers are as detailed as those for Windows containers, especially for topics like diagnostic log access, resource limits, and health checks.
- Where possible, provide Linux-native tool references (e.g., mention /home before C:\home in shared sections) and avoid defaulting to Windows terminology in cross-platform sections.
- Review pivoted content to ensure Linux and Windows sections are equally comprehensive and up-to-date.
- Consider adding a summary table at the top outlining which features/commands apply to Windows, Linux, or both, to help users quickly find relevant 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 (a Windows-centric tool) listed before the Azure Portal. However, all deployment and operational examples use cross-platform tools (kubectl, YAML), and no Windows-specific commands or tools are prioritized or exclusively used. There are no missing Linux/macOS examples, and no Windows-only tools are referenced in the main deployment flow.
Recommendations
- List Azure CLI (cross-platform) before Azure PowerShell in the prerequisites to emphasize Linux/macOS parity.
- Explicitly mention that all kubectl commands and YAML deployments are cross-platform and can be run from Linux, macOS, or Windows terminals.
- Consider adding a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
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 example commands for Azure portal, Azure CLI, and Azure PowerShell in all procedural sections. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its examples are given equal prominence alongside CLI. The ordering of examples consistently places Azure PowerShell after CLI, but before any mention of Linux-specific tooling. There are no Linux-specific shell examples (e.g., Bash), and the documentation does not reference Linux tools or patterns. However, the CLI examples are sufficient for Linux/macOS users, and the documentation does not require Windows-only tools for any critical steps.
Recommendations
- Explicitly state that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform automation tool.
- Consider adding Bash shell script examples or clarifying that CLI commands are suitable for Linux/macOS users.
- If PowerShell is included, note that PowerShell Core is available cross-platform, but CLI is generally preferred for Linux users.
- Review ordering of examples to ensure CLI (cross-platform) is shown before PowerShell, and clarify tool suitability for each OS.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service plans, covering both Windows and Linux options. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (such as PowerShell, RDP, IIS customization, .NET Framework) are discussed first and in detail, with explicit mention that this feature is Windows-only. While this is accurate and appropriate for the feature, the overall page does not provide Linux-specific examples or parity for similar advanced hosting scenarios, and Windows terminology appears before Linux in some places.
Recommendations
- Add Linux-specific advanced hosting options or clarify their absence, especially for scenarios like OS customization, private networking, and legacy component support.
- When listing operating systems or features, alternate the order or explicitly state Linux capabilities where relevant.
- Provide links or references to Linux hosting documentation for users seeking similar functionality.
- Ensure parity in examples and explanations for scaling, pricing, and feature availability between Windows and Linux where applicable.
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
missing_linux_example
Summary
The documentation generally aims for cross-platform parity, but there are subtle Windows biases. In the 'Export the merged private certificate to .pfx' section, explicit instructions are provided for both OpenSSL (Linux/macOS) and Windows tools (IIS, Certreq.exe). However, the Windows export path is referenced with a link to a Windows Server 2008-era guide, and no equivalent Linux/macOS GUI or alternative is mentioned. In the FAQ and automation sections, both Azure CLI (cross-platform) and Azure PowerShell (primarily Windows, but available cross-platform) are referenced, but PowerShell is mentioned second. The only significant bias is that Windows tools are referenced for certificate export without Linux GUI alternatives, and the documentation does not clarify that all steps are equally supported on Linux/macOS. There are no PowerShell-heavy or Windows-only sections, but minor friction exists for Linux/macOS users.
Recommendations
- Add explicit notes confirming that all certificate management steps (including .pfx export and upload) are fully supported on Linux/macOS.
- Provide a Linux/macOS GUI alternative (such as using GNOME Certificates or Keychain Access) for exporting .pfx files, or clarify that OpenSSL is the recommended tool for non-Windows users.
- Update the Windows export link to a more current version if possible, and consider adding a Linux/macOS-focused quickstart for certificate export.
- Where Windows tools are mentioned (IIS, Certreq.exe), add a parallel note or link for Linux/macOS users to avoid the impression of Windows-first support.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, ARM templates, and portal instructions for most tasks. However, PowerShell examples are prominent and often shown alongside or before CLI examples, and PowerShell is referenced in several places (including a dedicated 'PowerShell' tab for token retrieval). Azure PowerShell is a cross-platform tool, but its historical association with Windows and the presence of a dedicated PowerShell tab (in addition to Azure CLI) may create a perception of Windows bias. The CLI examples are present and correct, but PowerShell is sometimes prioritized or referenced first. There are no outright missing Linux examples, and no exclusive mention of Windows-only tools.
Recommendations
- Ensure Azure CLI examples are always presented before or alongside PowerShell examples, as CLI is more commonly used on Linux/macOS.
- Clarify that Azure PowerShell is cross-platform and not Windows-only, to avoid confusion.
- Consider adding Bash shell script examples for token retrieval, especially in the 'Connect to Azure services in app code' section, to further improve Linux parity.
- Review tab ordering and ensure CLI is not deprioritized compared to PowerShell.
- Explicitly mention that all instructions (except PowerShell tab) are applicable to Linux/macOS unless otherwise noted.
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 is largely platform-neutral, focusing on Azure App Service virtual network integration. However, there is a section ('Windows Containers specific limits') where Windows container-specific guidance and calculations are presented before any Linux-specific information. Linux container guidance is only mentioned briefly in the 'Linux continuous deployment' subsection, which is much shorter and less detailed. There are no PowerShell-only examples, Windows tools, or missing Linux examples for core tasks, but Windows-specific guidance appears first and is more detailed.
Recommendations
- Add a comparable section for Linux containers, including subnet sizing, IP address requirements, and networking unit calculations, to match the detail provided for Windows containers.
- Ensure Linux-specific guidance is as prominent and detailed as Windows guidance, especially in sections about container limits and networking.
- Consider presenting Linux and Windows container guidance side-by-side or in parallel subsections for parity.
- Expand the 'Linux continuous deployment' section to include more details, such as subnet/IP requirements, limitations, and troubleshooting tips.
App Service
Tutorial: Access Azure databases with managed identity
...les/app-service/tutorial-connect-msi-azure-database.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally provides cross-platform guidance, using Azure CLI and mentioning development environments for Windows, macOS, and Linux. However, there is a minor Windows-first bias in the 'Set up your dev environment' section, where Visual Studio for Windows is described first and in more detail, while Visual Studio for Mac and Linux users are directed to use Azure CLI. PowerShell is also mentioned as an option, but not prioritized. All critical tasks can be completed on Linux/macOS, but the ordering and emphasis slightly favor Windows.
Recommendations
- Reorder the 'Set up your dev environment' tabs so that cross-platform tools (Azure CLI, Visual Studio Code) are listed before Windows-specific tools (Visual Studio for Windows, PowerShell).
- Explicitly mention Linux as a supported development environment in the prerequisites and dev environment setup.
- Provide parity in instructions and detail for macOS/Linux users, especially for Visual Studio Code and Azure CLI.
- Where possible, avoid language that implies Visual Studio for Windows is the default or primary workflow.
- Ensure all code and CLI examples are clearly marked as cross-platform, and clarify any Windows-only steps.