84
Pages Scanned
17
Pages Flagged
84
Changed Pages
20.2%
% Pages Flagged
Scan Information
Started At: 2026-01-16 00:00:11
Finished At: 2026-01-16 00:10:42
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 84
Files Completed: 84
Problematic Pages
18 issues found
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows-specific tools and workflows, especially SignTool and PowerShell, with no equivalent instructions or examples for Linux or macOS users. All setup, installation, and usage instructions are Windows-centric, and there is no mention of cross-platform alternatives or guidance for non-Windows environments.
Recommendations
- Clearly state at the beginning if Artifact Signing with SignTool is Windows-only, and provide guidance for Linux/macOS users if possible.
- If cross-platform signing is supported (e.g., via the SDK, GitHub Actions, or Azure DevOps), add explicit sections or examples for Linux/macOS environments.
- Provide installation and usage instructions for Artifact Signing tools on Linux/macOS, or clarify their absence.
- For GitHub Actions and Azure DevOps, include example workflows that run on Ubuntu/macOS runners, not just Windows.
- If PowerShell is required, mention cross-platform PowerShell (pwsh) support or alternatives.
- If only Windows is supported for certain integrations, make this explicit to set expectations.
Create Pull Request
Communication Services
Automate email resource management
...nication-services/samples/email-resource-management.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides multiple PowerShell-based examples for resource cleanup, with only one Azure CLI example (for deleting the Communication Services resource). The Email Communication Services and Domain resource deletion steps are shown exclusively with PowerShell commands, which are Windows-centric. There are no Linux/macOS CLI equivalents or guidance for these tasks, and PowerShell examples are presented before or instead of cross-platform alternatives.
Recommendations
- Add Azure CLI examples for deleting Email Communication Services and Domain resources, ensuring Linux/macOS users can follow the same steps.
- Clearly indicate which commands are Windows-only and provide cross-platform alternatives where possible.
- Reorder examples to present cross-platform (Azure CLI) commands first, or group them by platform with equal prominence.
- Include notes or links for installing Azure CLI/PowerShell on non-Windows platforms if needed.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
Summary
The documentation mentions PowerShell as a method for publishing changes and updating Data Factory configurations, but does not provide equivalent examples or explicit guidance for Linux/macOS users (e.g., Bash, Azure CLI). This may create friction for non-Windows users who do not use PowerShell.
Recommendations
- Add explicit examples for Linux/macOS users using Azure CLI or Bash scripts for tasks currently described as being performed via PowerShell.
- Clarify which operations can be performed using cross-platform tools and provide links or code samples.
- Where PowerShell is mentioned, note the equivalent Azure CLI or REST API commands if available.
Firewall
Deploy Azure Firewall with Availability Zones
...ticles/firewall/deploy-availability-zone-powershell.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only Azure PowerShell examples for deploying Azure Firewall with Availability Zones. There are no examples using cross-platform tools such as Azure CLI, ARM/Bicep templates, or Terraform. The only scripted deployment method shown is PowerShell, which is most familiar and accessible to Windows users, creating friction for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI examples for deploying Azure Firewall with Availability Zones, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include ARM or Bicep template snippets for infrastructure-as-code deployments, which are platform-agnostic.
- Mention and link to Terraform or other third-party cross-platform deployment options if available.
- Explicitly state that Azure PowerShell can be used on all platforms (via PowerShell Core), but still provide CLI examples for parity.
IoT Hub
Get Started with ADR and Certificate Management in IoT Hub (Preview)
...main/articles/iot-hub/iot-hub-device-registry-setup.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation mentions PowerShell scripts as a deployment method, explicitly noting they are 'Windows only', while the Azure CLI method is presented as cross-platform. The deployment method table lists Azure CLI first, followed by PowerShell, but PowerShell is highlighted as Windows-specific. No Linux/macOS shell script or Bash example is provided as an alternative to PowerShell automation. All command-line examples use Azure CLI, which is cross-platform, but the only script automation option is PowerShell (Windows).
Recommendations
- Provide a Bash or shell script example for Linux/macOS users to automate the IoT Hub, DPS, and ADR setup, paralleling the PowerShell script.
- Explicitly state that Azure CLI is supported on Windows, Linux, and macOS to reassure non-Windows users.
- If script automation is important, offer parity by linking to or including a Linux/macOS shell script.
- Consider renaming the 'script' pivot to clarify platform support (e.g., 'PowerShell (Windows only)' and 'Bash (Linux/macOS)').
Reliability
Reliability in Azure Storage Mover
...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a PowerShell example for associating job definitions to a new agent but does not offer equivalent examples for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API). The only explicit command-line example is PowerShell, which may create friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI or Bash examples alongside the PowerShell example for updating job definitions.
- Explicitly mention that the same operations can be performed using the Azure CLI or REST API, and provide links or code snippets.
- Clarify in the relevant sections that PowerShell is not required and that cross-platform tools are supported.
Sap
Exchange Online Integration for Email-Outbound from SAP ABAP Platform | Microsoft Docs
...oads/exchange-online-integration-sap-email-outbound.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides several configuration steps that require PowerShell and references to the Exchange Online Cloud Shell, with explicit instructions and code snippets for PowerShell usage. There are no equivalent examples or guidance for performing these steps using Linux/macOS tools or CLI alternatives. The reliance on PowerShell and the absence of cross-platform alternatives may create friction for Linux or macOS administrators.
Recommendations
- Where PowerShell is required (e.g., Exchange Online management), clarify if the Cloud Shell is cross-platform and accessible from any OS via browser.
- If possible, provide equivalent examples using Azure CLI, Microsoft Graph API, or REST calls that can be run from Linux/macOS.
- Explicitly state when a step must be performed in PowerShell and if there are no alternatives, and provide guidance for Linux/macOS users (e.g., using Azure Cloud Shell in browser).
- Add notes or links to cross-platform tools or scripts where available.
- For any downloadable scripts, clarify their OS compatibility and provide instructions for running them on Linux/macOS if supported.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation for SMB File Shares in Azure Files demonstrates a moderate Windows bias. Windows terminology, features, and PowerShell examples are frequently presented first or exclusively, especially for client configuration and troubleshooting. Registry and PowerShell instructions are provided only for Windows clients, with no equivalent Linux/macOS guidance for advanced SMB client configuration. While Azure CLI examples are cross-platform, client-side configuration and troubleshooting are Windows-centric, and references to Windows features (e.g., registry keys, Set-SmbClientConfiguration) lack Linux/macOS parity.
Recommendations
- Add equivalent Linux/macOS client configuration and troubleshooting guidance, especially for advanced SMB features (e.g., encryption cipher selection, multichannel support).
- Include Linux/macOS examples for mounting and configuring SMB shares, not just links in 'Next steps'.
- Clarify which SMB features and settings are relevant or supported on Linux/macOS clients, and provide references to appropriate tools (e.g., smb.conf, mount.cifs, smbclient).
- When discussing client-side configuration (e.g., enabling encryption ciphers), provide instructions for Linux/macOS (e.g., how to set ciphers in smb.conf) alongside Windows PowerShell examples.
- Balance the order of examples so that Linux/macOS are not consistently presented after Windows, or only as links.
Sentinel
Manage custom content with repository connections
...cs/blob/main/articles/sentinel/ci-cd-custom-content.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for managing custom content with repository connections in Microsoft Sentinel demonstrates a notable Windows/PowerShell bias. Many conversion and export tasks reference PowerShell scripts as the primary or only method, with Linux/macOS alternatives (such as Bash or Azure CLI) either missing or mentioned secondarily. In several content types (e.g., Analytic rules, Automation rules, Playbooks), only PowerShell scripts are linked for conversion/export, and Linux-friendly approaches are not provided. The workflow customization section also refers to PowerShell deployment scripts without mentioning cross-platform alternatives.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for all tasks currently covered only by PowerShell scripts, especially for conversion and export operations.
- Explicitly state when PowerShell scripts are cross-platform (PowerShell Core), or provide instructions for running them on Linux/macOS.
- Where possible, link to or create Linux/macOS-friendly tools for template conversion and deployment.
- In tables and examples, present Azure CLI or Bash approaches alongside PowerShell, or at least clarify platform compatibility.
- Clarify if any referenced scripts or tools require Windows-only PowerShell, and suggest alternatives for non-Windows users.
Storage
Improve SMB Azure File Share Performance
...cs/blob/main/articles/storage/files/smb-performance.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Windows and Linux guidance for SMB Multichannel and metadata caching, but several sections show Windows bias. Windows tools (robocopy, diskspd.exe, PowerShell) are used for performance verification and examples, with no Linux equivalents provided. PowerShell is the only CLI shown for feature registration, and Windows configuration steps precede Linux instructions. Linux examples are present for mounting, but Linux performance testing and verification steps are missing.
Recommendations
- Add Linux equivalents for performance testing (e.g., fio, dd) and verification commands for SMB Multichannel connections.
- Include Azure CLI or Bash examples for feature registration alongside PowerShell.
- Provide guidance for Linux troubleshooting and configuration verification, similar to the Windows PowerShell steps.
- Balance the order of examples so Linux and Windows instructions are presented with equal prominence.
App Service
Configure Managed Instance on Azure App Service (Preview)
...ain/articles/app-service/configure-managed-instance.md
Low Priority
View Details →
Detected Bias Types
windows_only
powershell_heavy
windows_tools
missing_linux_example
Summary
This documentation is intentionally and explicitly focused on a Windows-only feature: Managed Instance on Azure App Service is a hosting option for Windows web apps that require OS customization. All configuration examples, scripting, and features (such as registry keys, RDP, and PowerShell scripts) are Windows-specific. There are no Linux/macOS equivalents or examples, and the documentation makes clear that only Windows Server 2022 is supported. Linux users cannot use this feature.
Recommendations
- No changes are needed for Linux parity, as this feature is Windows-only by design.
- If a Linux equivalent is developed in the future, provide clear documentation and examples for Linux users.
- Consider adding a prominent note at the top of the page stating that Managed Instance on Azure App Service is only available for Windows workloads, to avoid confusion for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but PowerShell examples are consistently shown immediately after CLI examples, and no explicit Linux/macOS shell examples are given. The CLI examples are cross-platform, but the presence of PowerShell commands (which are Windows-centric, though available cross-platform) may give the impression of Windows prioritization. No Linux-specific tools or workflows are mentioned, but critical tasks are not blocked for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on all platforms (Windows, Linux, macOS) and are the recommended cross-platform approach.
- Consider labeling PowerShell examples as 'Azure PowerShell' and noting that PowerShell Core is available cross-platform, to avoid the impression of Windows-only support.
- Add explicit bash or shell examples where appropriate (e.g., using curl or dig for DNS lookups), especially in sections like 'Find the inbound IP', to improve parity.
- Where both CLI and PowerShell are shown, consider showing CLI first and labeling it as the default/cross-platform method.
Azure App Configuration
How to use Agent Framework in a Python app with Azure App Configuration
...zure-app-configuration/howto-ai-agent-config-python.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (Command Prompt and PowerShell) before mentioning the equivalent macOS/Linux command. The only other Windows-specific reference is a link to Python setup documentation for Windows, but this is contextually appropriate given the section's focus.
Recommendations
- Present environment variable setup instructions for all platforms in parallel (e.g., in a table or side-by-side code blocks), or rotate the order so that Linux/macOS is not always last.
- Optionally, provide a link to Python installation instructions for Linux/macOS alongside the Windows link, or clarify that users should refer to their OS-specific Python installation guides.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for running C# Azure Functions in the isolated worker process. However, there are several instances where Windows tools and patterns are mentioned first or in more detail, and some CLI examples use Windows-centric language. Azure PowerShell is listed as a resource creation method alongside Azure CLI, but Linux shell examples are not always shown with equal prominence. Some instructions (e.g., for checking or setting 32/64-bit process, ReadyToRun, and preview SDK usage) show Windows commands or options first, with Linux as a secondary tab or note.
Recommendations
- Wherever CLI commands are shown, ensure both Windows (PowerShell/CMD) and Linux (Bash) equivalents are provided, or use cross-platform Azure CLI examples by default.
- When listing resource creation or deployment methods, present Azure CLI and Visual Studio Code before Windows-specific tools like Visual Studio or Azure PowerShell.
- In tables or lists, alternate the order of Windows and Linux to avoid always presenting Windows first.
- Add explicit Linux/macOS shell examples for common tasks (e.g., checking process architecture, publishing with dotnet CLI) where only Windows or PowerShell is shown.
- Clarify when a tool or step is Windows-only, and provide Linux/macOS alternatives where possible.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally provides parity for both Windows and Linux users regarding the Premium v4 tier, including explicit notes about feature availability. However, there is a subtle Windows-first bias: in several sections, Windows examples or instructions are presented before Linux equivalents, and Azure PowerShell (primarily used on Windows) is given equal prominence to Azure CLI, despite CLI being more cross-platform. All automation examples are provided for both Azure CLI and PowerShell, but no explicit Bash or Linux shell scripting examples are shown. The overall impact is minor, as Linux users can complete all tasks using the CLI.
Recommendations
- When listing SKU availability commands, present Linux and Windows examples together or alternate their order to avoid a Windows-first impression.
- Consider adding a simple Bash script example for automating app creation, to further support Linux users.
- Clarify in the 'Automate with scripts' section that Azure CLI is fully cross-platform and recommended for Linux/macOS users, while PowerShell is optional.
- Ensure that portal instructions and screenshots are not Windows-centric (e.g., avoid referencing Windows-only UI elements or terminology).
Azure Cache For Redis
Configure active geo-replication for Enterprise Azure Cache for Redis instances
...cache-for-redis/cache-how-to-active-geo-replication.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring active geo-replication, but PowerShell is given equal prominence to CLI, and no explicit Linux/macOS shell examples (e.g., Bash) are shown. The CLI examples are generic and cross-platform, but PowerShell is a Windows-centric tool (despite recent cross-platform support). No Linux-specific tools or workflows are mentioned, and screenshots/instructions focus exclusively on the Azure portal UI, which is platform-agnostic.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and consider showing CLI examples first to emphasize cross-platform support.
- Add explicit Bash shell examples or notes for Linux/macOS users, especially for scripting or automation.
- Mention that PowerShell Core is available on Linux/macOS if PowerShell examples are retained, or clarify the cross-platform nature of CLI vs. PowerShell.
- Ensure that instructions do not imply PowerShell is required for non-Windows users.
Reliability
High Availability (Reliability) in Azure Cosmos DB for NoSQL
...in/articles/reliability/reliability-cosmos-db-nosql.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation references PowerShell as a tool for managing failover and switching write regions, listing it alongside Azure CLI and Azure portal. PowerShell is a Windows-centric tool, and its mention before Azure CLI (which is cross-platform) in several places subtly prioritizes Windows tooling. However, all management actions are also available via Azure CLI and Azure portal, which are cross-platform, and there are no exclusive Windows-only instructions or examples.
Recommendations
- List Azure CLI before PowerShell when mentioning management tools, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that all management actions (failover, region switching, etc.) can be performed using Azure CLI and Azure portal on any OS, and provide example commands for both CLI and PowerShell where relevant.
- Consider adding a short note that PowerShell is primarily for Windows users, while Azure CLI is recommended for Linux/macOS users.
- Where possible, provide direct CLI command examples in addition to PowerShell, especially in sections about manual failover and region switching.
Migrate
Support for VMware vSphere migration in Azure Migrate
...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally provides parity between Windows and Linux migration scenarios, listing supported Linux distributions and requirements in detail. However, there are minor signs of Windows bias: PowerShell is mentioned as the primary automation interface for configuring replication, and in several places, Windows instructions or references appear before Linux equivalents. Appliance deployment is described as possible via OVA or PowerShell script, but Linux CLI or automation alternatives are not mentioned. No critical migration steps are Windows-only, and Linux users can complete all tasks, but the prominence of Windows/PowerShell may create mild friction.
Recommendations
- When mentioning automation interfaces (e.g., PowerShell), also reference Azure CLI or Bash scripting alternatives for Linux/macOS users.
- Provide Linux/macOS command-line examples or instructions where PowerShell is referenced, especially for appliance deployment and bulk VM replication.
- Alternate the order of Windows and Linux instructions/examples, or present them side-by-side, to avoid implicit prioritization.
- Explicitly state that all migration steps can be performed from Linux/macOS environments, and link to relevant cross-platform tooling.