Notification Hubs

62
Total Pages
34
Linux-Friendly Pages
28
Pages with Bias
45.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

66 issues found
Showing 1-25 of 66 flagged pages
Notification Hubs Create an Azure notification hub using Azure Resource Manager template .../notification-hubs/create-notification-hub-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. PowerShell examples are provided for resource review and cleanup, with Azure CLI alternatives present only for resource review (not for cleanup). PowerShell is listed before CLI, and the cleanup section only includes PowerShell commands, omitting Azure CLI (Linux-friendly) equivalents. There is no mention of Linux-specific tools or shell patterns, and the workflow assumes familiarity with PowerShell.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all operations, including resource cleanup.
  • List CLI and PowerShell examples in parallel tabs, or alternate the order to avoid implicit prioritization.
  • Explicitly mention that both CLI and PowerShell are cross-platform, and clarify usage on Linux/macOS.
  • Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI.
  • Avoid assuming PowerShell as the default scripting environment; include Bash/CLI alternatives where appropriate.
GitHub Create Pull Request
Notification Hubs Sending push notifications with Azure Notification Hubs and Node.js ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-nodejs-push-notification-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias in several ways: Windows tools and patterns (such as PowerShell and WebMatrix) are mentioned first or exclusively in key sections, especially when creating and deploying Node.js applications. The retrieval of connection strings is described with Windows-specific tools (PowerShell cmdlet) before mentioning the Azure classic CLI. Linux equivalents are referenced only as alternatives and not given equal prominence or detail. There are no Linux-specific examples or instructions for common tasks such as application creation or Azure resource management.
Recommendations
  • Provide Linux-first or cross-platform instructions for creating and deploying Node.js applications, such as using VS Code, CLI, or other popular Linux tools.
  • Include explicit Linux/Bash examples for retrieving Azure connection strings (e.g., using Azure CLI commands like 'az notification-hub show').
  • List command-line interfaces in a neutral order (e.g., Bash, Terminal, PowerShell) and avoid prioritizing Windows tools.
  • Mention and link to Linux-friendly development environments and workflows alongside Windows-specific ones.
  • Ensure all steps and code snippets are platform-agnostic or provide parallel instructions for both Windows and Linux users.
GitHub Create Pull Request
Notification Hubs Send Azure Notification Hubs notifications to Android and iOS applications ...docs/blob/main/articles/notification-hubs/uwp-react.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by prioritizing Windows development tools (Visual Studio, UWP), listing Windows as a required development environment, and providing detailed instructions for Windows setup and troubleshooting. There are no examples or instructions for building or running the backend or manager application on Linux, nor is there mention of Linux-compatible tools or workflows for .NET development. The deployment and build instructions focus exclusively on Visual Studio and Windows App Service, with no parity for Linux users.
Recommendations
  • Add instructions for building and running the backend API using .NET CLI on Linux (e.g., dotnet build, dotnet run), including any necessary environment setup.
  • Include guidance for deploying the backend to Azure App Service for Linux, or running locally on Linux using Kestrel or Nginx reverse proxy.
  • Mention cross-platform editors such as VS Code, and provide steps for using them on Linux.
  • Clarify that the manager application (UWP) is Windows-only, but suggest alternatives for Linux users, such as running the React Native app for Android/iOS or using web-based management tools.
  • Provide troubleshooting steps relevant to Linux environments, if applicable.
  • Ensure that all prerequisites and instructions are inclusive of both Windows and Linux development environments where possible.
GitHub Create Pull Request
Notification Hubs Azure Notification Hubs Private Link (preview) ...s/blob/main/articles/notification-hubs/private-link.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily in the validation section, where only instructions for creating and connecting to a Windows virtual machine are provided, and DNS resolution is shown using a Windows-specific PowerShell command (Resolve-DnsName). There are no equivalent Linux instructions or examples (e.g., using dig or nslookup). The portal and Azure CLI instructions are cross-platform, but the validation and troubleshooting steps focus exclusively on Windows tools and environments.
Recommendations
  • Add instructions for creating a Linux virtual machine in Azure, either alongside or before the Windows VM example.
  • Provide Linux command-line equivalents for DNS resolution, such as 'dig <namespace_name>.privatelink.servicebus.windows.net' or 'nslookup'.
  • Explicitly mention that the Azure CLI steps are cross-platform and can be run from Linux, macOS, or Windows.
  • Where screenshots or portal instructions are given, clarify that the portal is accessible from any OS with a supported browser.
  • Ensure troubleshooting and validation steps include both Windows and Linux environments to improve parity.
GitHub Create Pull Request
Notification Hubs Azure Notification Hubs Private Link (preview) ...s/blob/main/articles/notification-hubs/private-link.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing validation instructions exclusively for Windows virtual machines, including a direct link to Windows VM creation and a PowerShell-only DNS resolution example. There are no Linux VM instructions, nor are Linux shell equivalents (e.g., dig, nslookup) provided for DNS validation. The documentation does not mention Linux tools or provide parity in examples for non-Windows environments.
Recommendations
  • Include instructions for creating and validating with a Linux virtual machine, such as linking to the Azure Linux VM quickstart.
  • Provide equivalent Linux shell commands for DNS resolution (e.g., 'dig', 'nslookup') alongside the PowerShell example.
  • Ensure that validation steps and screenshots are platform-neutral or include both Windows and Linux variants.
  • Explicitly mention that the Azure CLI commands work on both Windows and Linux, and clarify any platform-specific differences if present.
GitHub Create Pull Request
Notification Hubs Sending push notifications with Azure Notification Hubs and Node.js ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-nodejs-push-notification-tutorial.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: Windows tools and patterns (such as PowerShell and WebMatrix) are mentioned before or instead of Linux equivalents, and instructions often reference Windows-specific tooling (e.g., PowerShell, WebMatrix) without equal emphasis on Linux alternatives. The retrieval of connection strings highlights PowerShell and the classic Azure CLI, but does not mention the modern cross-platform Azure CLI. The creation and deployment section lists Windows-centric options first and omits Linux-specific guidance.
Recommendations
  • Provide Linux-specific instructions and examples alongside Windows ones, especially for command-line operations.
  • Mention cross-platform tools (such as the modern Azure CLI) before or alongside Windows PowerShell.
  • Include Linux and macOS deployment options and workflows in the 'Create a Node.js Application' section.
  • Avoid listing Windows tools (e.g., WebMatrix, PowerShell) first or exclusively; ensure parity by listing Linux and macOS equivalents.
  • Add explicit Bash and Terminal command examples where PowerShell is referenced.
  • Review references to deprecated or Windows-only technologies (e.g., WebMatrix, Windows Phone) and clarify their relevance or alternatives.
GitHub Create Pull Request
Notification Hubs Send Azure Notification Hubs notifications to Android and iOS applications ...docs/blob/main/articles/notification-hubs/uwp-react.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by prioritizing Windows and Visual Studio as the primary development environment, referencing UWP and Windows-specific deployment steps, and omitting Linux development instructions or tooling. There are no examples or guidance for building, running, or deploying the backend or frontend on Linux systems, nor is there mention of cross-platform alternatives to Visual Studio or IIS. The troubleshooting and deployment sections focus exclusively on Windows issues and workflows.
Recommendations
  • Add instructions for setting up the development environment on Linux, including alternatives to Visual Studio (e.g., VS Code, JetBrains Rider, or CLI tools).
  • Provide examples for building and running the ASP.NET backend using the .NET CLI on Linux/macOS, and deploying to Azure from non-Windows platforms.
  • Include guidance for running the React Native manager application on Linux (e.g., via WSL, or by using cross-platform React Native tooling).
  • Mention Linux-compatible database options (e.g., Azure SQL Edge, PostgreSQL) or clarify how to connect to Azure SQL Server from Linux.
  • Expand troubleshooting to include common issues encountered on Linux/macOS environments.
  • Ensure parity in step-by-step instructions for all major platforms (Windows, Linux, macOS) wherever possible.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/private-link.md ...s/blob/main/articles/notification-hubs/private-link.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows virtual machines for validation steps and providing only PowerShell commands for DNS resolution. There are no Linux-specific instructions or examples for connecting to the VM or validating DNS resolution, and the validation workflow is centered around Windows tools and patterns.
Recommendations
  • Include instructions for creating and connecting to a Linux VM in Azure, alongside the Windows VM example.
  • Provide equivalent Linux shell commands (e.g., 'dig', 'nslookup', or 'host') for DNS resolution validation, in addition to the PowerShell 'Resolve-DnsName' command.
  • Ensure that validation steps are presented for both Windows and Linux environments, ideally in parallel sections or as alternatives.
  • Avoid assuming the user will use Windows by default; mention both platforms where relevant.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-nodejs-push-notification-tutorial.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-nodejs-push-notification-tutorial.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by prioritizing Windows tools and workflows. Windows PowerShell is mentioned first and most prominently for creating and deploying Node.js applications, with Linux and Mac alternatives only briefly referenced. Retrieval of Azure connection strings is described using PowerShell and classic CLI, with no mention of Bash or cross-platform Azure CLI. The examples and instructions frequently reference Windows-specific tools (PowerShell, WebMatrix), and do not provide equivalent Linux-focused guidance or examples.
Recommendations
  • Provide Linux and macOS-specific instructions and examples alongside Windows ones, including using Bash and Terminal for command-line operations.
  • Mention and demonstrate the use of the cross-platform Azure CLI (az) for retrieving connection strings and managing Notification Hubs, rather than focusing on PowerShell and classic CLI.
  • Replace or supplement references to Windows-only tools (e.g., WebMatrix, PowerShell) with platform-neutral or Linux/macOS alternatives.
  • Ensure that all steps (application creation, deployment, management) have clear, tested instructions for Linux and macOS users.
  • Reorder examples so that Windows tools are not always listed first, or present all platforms equally.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/uwp-react.md ...docs/blob/main/articles/notification-hubs/uwp-react.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by prioritizing Windows tools (Visual Studio, UWP), requiring a Windows computer for core development, and providing step-by-step instructions only for Windows environments. There are no examples or guidance for building or running the backend or manager application on Linux, nor is there mention of Linux-compatible tools or workflows. The troubleshooting and deployment sections are also Windows-centric.
Recommendations
  • Add instructions for setting up and running the backend API on Linux (e.g., using .NET Core CLI, VS Code, or JetBrains Rider).
  • Include examples for deploying the backend to Azure from Linux/macOS environments (e.g., using Azure CLI, GitHub Actions, or VS Code).
  • Provide guidance for building and running the React Native manager application on Linux (if supported), or clarify platform limitations.
  • Mention cross-platform alternatives to Visual Studio, such as VS Code or JetBrains Rider, for development.
  • Add troubleshooting steps relevant to Linux environments, if applicable.
  • Clearly state any platform-specific requirements or limitations for the UWP manager application and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-nodejs-push-notification-tutorial.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-nodejs-push-notification-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: Windows tools and patterns (such as PowerShell) are mentioned first or exclusively in instructions for creating and deploying Node.js applications. The retrieval of connection strings highlights Windows PowerShell and Windows-specific CLI tools before Linux alternatives. References to Windows-centric tutorials (e.g., Windows Store Getting Started) and tools (WebMatrix) are present, while Linux equivalents are not provided or are mentioned only in passing. The examples and instructions do not offer Linux-specific guidance or parity.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for command-line operations and deployment.
  • Mention Linux tools (e.g., Bash, Azure CLI on Linux) before or alongside Windows tools like PowerShell.
  • Include links to Linux-focused tutorials for creating and deploying Node.js applications.
  • When referencing commands for retrieving connection strings, include Azure CLI examples for Linux/macOS and clarify cross-platform usage.
  • Avoid referencing Windows-only tools (e.g., WebMatrix) without offering Linux alternatives.
  • Ensure that all steps and screenshots are platform-neutral or provide Linux/macOS equivalents.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/uwp-react.md ...docs/blob/main/articles/notification-hubs/uwp-react.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific tools and workflows, such as Visual Studio and UWP applications, and by omitting Linux development instructions or examples. The prerequisites and build instructions assume a Windows environment, with no mention of Linux equivalents for running the backend or manager application. The troubleshooting section and deployment steps are also focused on Windows-specific issues and solutions.
Recommendations
  • Add explicit instructions for building and running the backend API on Linux, including using .NET Core CLI and alternatives to Visual Studio (e.g., VS Code, JetBrains Rider, or command-line tools).
  • Provide examples for deploying and running the React Native manager application on Linux (e.g., using WSL, or alternative desktop platforms such as Electron).
  • Include troubleshooting steps relevant to Linux environments, such as common build errors or dependency issues.
  • Mention cross-platform database options or clarify how to connect to Azure SQL from Linux.
  • Ensure that all command-line instructions (npm, npx, etc.) are presented in a platform-neutral way, and note any platform-specific caveats.
  • If UWP is required, clarify its Windows-only nature and suggest alternatives for Linux users (such as running the manager app as a web or Electron app).
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/create-notification-hub-template.md .../notification-hubs/create-notification-hub-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples before Azure CLI, using PowerShell exclusively for resource cleanup, and omitting explicit Linux shell/bash examples. The workflow and tooling references (e.g., PowerShell scripts, Read-Host prompts) are more familiar to Windows users, while Linux users may find the lack of bash or shell alternatives limiting.
Recommendations
  • Provide bash/Linux shell equivalents for all PowerShell commands, especially for resource cleanup (e.g., use 'az group delete' with Azure CLI).
  • Present Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
  • Add notes or tabs clarifying which commands are cross-platform and which are Windows-specific.
  • Avoid using PowerShell-specific constructs (like Read-Host) without offering alternatives for Linux/macOS users.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/private-link.md ...s/blob/main/articles/notification-hubs/private-link.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows virtual machines for validation, providing only PowerShell commands for DNS resolution, and linking to Windows-specific VM creation guides. There are no Linux VM creation instructions, nor are Linux shell equivalents (such as dig or nslookup) provided for DNS validation. The examples and screenshots are all based on the Azure portal, which is platform-agnostic, but the command-line validation steps and VM creation guidance are Windows-centric.
Recommendations
  • Add instructions and links for creating a Linux virtual machine in Azure, alongside the Windows VM guide.
  • Provide Linux shell equivalents (e.g., dig, host, nslookup) for DNS validation, in addition to PowerShell.
  • Include examples of connecting to the VM and running validation commands from both Windows and Linux environments.
  • Ensure that references to tools and commands are balanced between Windows and Linux, or explicitly note platform differences.
  • Consider adding a table or section that lists validation commands for both operating systems.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/push-notifications-android-specific-users-firebase-cloud-messaging.md ...ations-android-specific-users-firebase-cloud-messaging.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a bias toward Windows by exclusively using an ASP.NET WebAPI backend for the server-side component, with no mention of Linux-friendly or cross-platform alternatives (such as Node.js, Python, or Java backends). The backend example assumes familiarity with Windows-centric technologies and does not provide guidance or code samples for users on Linux or macOS. There are no references to Linux tools, deployment patterns, or command-line instructions, and the only backend stack shown is one most commonly associated with Windows environments.
Recommendations
  • Provide equivalent backend implementation examples using cross-platform technologies such as Node.js (Express), Python (Flask/FastAPI), or Java (Spring Boot), and reference these alongside the ASP.NET example.
  • Include instructions for deploying and running the backend on Linux (e.g., using Docker, Azure App Service for Linux, or other Linux-based hosting).
  • Add notes or links for users who may be developing on macOS or Linux, clarifying that the client-side (Android) code is platform-agnostic and that the backend can be implemented in any language or framework.
  • Where possible, use neutral terminology (e.g., 'backend API' instead of 'ASP.NET backend') and provide a selector or toggle in the documentation for different backend stacks.
  • Reference tools and workflows that are available on all platforms, and avoid assuming the use of Windows-only development environments.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-aspnet-cross-platform-notification.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-aspnet-cross-platform-notification.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing Windows-specific tools (Visual Studio, Solution Explorer) and platforms (Windows Phone, Windows Store, Universal Windows Platform) before or more prominently than their Linux or cross-platform counterparts. There are no examples or instructions for Linux development environments, and the workflow assumes the use of Visual Studio on Windows.
Recommendations
  • Include instructions and screenshots for performing the same tasks using cross-platform IDEs or editors, such as Visual Studio Code or JetBrains Rider, on Linux.
  • Provide command-line alternatives for project navigation and file editing, suitable for Linux and macOS users.
  • Mention and demonstrate how to run and debug the sample code on Linux (e.g., using .NET CLI commands like 'dotnet run', 'dotnet publish').
  • Balance references to Windows-specific platforms (e.g., Windows Store, UWP) with equivalent information for iOS, Android, and other platforms.
  • Clarify that the tutorial is applicable to non-Windows environments and provide any necessary setup instructions for Linux users.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-tls12.md .../articles/notification-hubs/notification-hubs-tls12.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows-specific resources (such as a link to 'support for TLS protocols on Windows') and omits equivalent Linux guidance or examples. There are no Linux-specific instructions or links, and Windows is mentioned explicitly before Linux. This creates a bias toward Windows users and leaves Linux users without clear guidance.
Recommendations
  • Add a section or examples describing how to verify or configure TLS 1.2 support on common Linux distributions.
  • Include links to Linux-specific documentation or tools (e.g., OpenSSL, curl, or distro-specific TLS configuration guides).
  • Mention Linux and macOS alongside Windows when discussing operating system compatibility and configuration.
  • Provide parity in troubleshooting steps or verification commands for both Windows and Linux environments.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-tags-segment-push-message.md ...on-hubs/notification-hubs-tags-segment-push-message.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows/Windows Phone-specific notification examples (using Windows toast XML and SendWindowsNativeNotificationAsync), mentioning Windows platforms explicitly, and omitting equivalent Linux, Android, or cross-platform notification examples. The SDK usage is shown only for Windows notifications, and there are no Linux command-line, REST API, or cross-platform code samples.
Recommendations
  • Add equivalent examples for sending notifications to Android (using FCM) and iOS (using APNS) with the Notification Hubs SDK.
  • Include REST API examples for sending notifications, which are platform-agnostic and runnable from any OS, including Linux.
  • Provide Node.js or Python code samples that demonstrate sending notifications from non-Windows environments.
  • Rephrase sections that mention Windows platforms first or exclusively, ensuring cross-platform parity in both order and content.
  • Explicitly mention that the SDK and REST APIs can be used from Linux and macOS, not just Windows.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-java-push-notification-tutorial.md ...s/notification-hubs-java-push-notification-tutorial.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Examples
Summary
The documentation demonstrates a clear Windows bias. Windows platforms (WNS, MPNS) and related credential objects are consistently mentioned first and in greater detail than their Linux or cross-platform counterparts. Many code examples focus on Windows-specific push notification services (WNS, MPNS), and Windows credential setup is shown as the primary example. There is no mention of Linux-specific tools, shell commands, or development patterns, and the documentation assumes familiarity with Windows notification concepts.
Recommendations
  • Provide equal prominence to Android (FCM) and iOS (APNS) examples and credential setup, not just Windows.
  • Include Linux/macOS shell command equivalents (e.g., show how to build with Maven using bash/sh, not just 'cmd').
  • Reorder examples so that cross-platform or most widely-used platforms (Android/iOS) are presented before or alongside Windows.
  • Add explicit notes or sections for Linux/macOS users, including troubleshooting and environment setup.
  • Ensure that links and sample projects are not Windows-centric and include cross-platform sample apps.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/private-link.md ...s/blob/main/articles/notification-hubs/private-link.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: it directs users to create and validate private endpoints using Windows-centric tools and workflows, such as referencing the creation of a Windows VM and providing only a PowerShell (Resolve-DnsName) command for DNS validation. There are no equivalent instructions or examples for Linux users (e.g., using dig or nslookup), and the validation steps are explicitly tied to Windows environments. The documentation also references Windows tools and patterns before any cross-platform or Linux alternatives.
Recommendations
  • Provide parallel Linux examples for all validation and management steps, such as using dig or nslookup for DNS resolution.
  • When instructing users to create a VM for validation, offer both Windows and Linux VM creation links and instructions.
  • Avoid referencing only Windows-specific tools (e.g., PowerShell) in validation steps; include cross-platform alternatives.
  • Ensure screenshots and walkthroughs are not exclusively from Windows environments, or supplement them with Linux equivalents.
  • Explicitly state that all CLI steps are cross-platform and clarify any OS-specific requirements or differences.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-aspnet-backend-ios-apple-apns-notification.md ...cation-hubs-aspnet-backend-ios-apple-apns-notification.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using an ASP.NET (Windows-centric) backend for the server-side component, without mentioning or providing examples for Linux-friendly alternatives such as Node.js, Python (Flask/Django), or Java. The backend setup and all code samples assume a Windows development environment and toolchain. There are no instructions or references for setting up or deploying the backend on Linux, nor are there cross-platform command-line or deployment examples. The only backend technology mentioned is ASP.NET, which is traditionally associated with Windows, even though .NET Core is cross-platform.
Recommendations
  • Provide alternative backend implementation examples using popular Linux-friendly stacks (e.g., Node.js/Express, Python/Flask, Java/Spring Boot) alongside the ASP.NET example.
  • Include instructions for deploying the backend on Linux-based environments (e.g., Ubuntu, Docker) and not just Azure App Service.
  • When referencing backend technologies, mention cross-platform options and clarify that .NET Core can run on Linux.
  • Add Linux/macOS command-line instructions where relevant (e.g., for project setup, deployment, or testing), not just Windows/PowerShell.
  • Explicitly state that the backend can be implemented and hosted on Linux, and provide links to relevant documentation for cross-platform development.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-push-notification-registration-management.md ...ication-hubs-push-notification-registration-management.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-centric code examples and patterns. All sample code is written in C# and uses Windows-specific APIs (such as PushNotificationChannelManager and ApplicationData), with no equivalent Linux, Android, or iOS code samples. The documentation discusses secondary tiles and headers specifically for Windows Store apps, and does not mention or demonstrate how to perform similar registration management from non-Windows platforms or with cross-platform tools. There are no Linux command-line, REST/cURL, or non-Windows SDK examples provided.
Recommendations
  • Add code samples for Linux, Android, and iOS platforms, using their respective notification APIs and SDKs.
  • Provide REST API examples using cURL or HTTP libraries in languages common on Linux (e.g., Python, Node.js) to demonstrate cross-platform registration management.
  • Include equivalent instructions and code snippets for managing device registration from non-Windows backends (e.g., running on Linux servers).
  • Document any platform-specific differences or requirements for registration, and ensure that Windows-specific features (like secondary tiles) are clearly marked as such, with alternatives or notes for other platforms.
  • Reorganize sections so that platform-agnostic or cross-platform approaches are presented before or alongside Windows-specific guidance.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-templates-cross-platform-push-messages.md ...tification-hubs-templates-cross-platform-push-messages.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed examples and payloads for Windows Store applications (using XML and Windows-specific notification formats) before or instead of Linux/Android equivalents. Windows notification services (WNS, MPNS) and XML payloads are discussed in detail, while Linux/Android (FCM) are only mentioned in passing, with no concrete example payloads or registration templates shown. There are no Linux command-line or tooling examples, and the documentation assumes familiarity with Windows notification paradigms.
Recommendations
  • Add explicit example payloads and registration templates for Android (FCM) and other non-Windows platforms, showing both JSON and XML formats as appropriate.
  • Ensure that examples are balanced: for every Windows-specific example, provide an equivalent for Linux/Android platforms.
  • Mention Linux/Android tools and notification patterns alongside Windows ones, not just in passing.
  • Consider reordering examples so that no single platform (such as Windows) is always presented first.
  • Include a section or appendix on cross-platform tooling and best practices for Linux/Android developers.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/uwp-react.md ...docs/blob/main/articles/notification-hubs/uwp-react.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. It consistently lists Windows and Visual Studio as primary or required development environments, provides detailed steps for Windows/UWP, and omits equivalent Linux development instructions. There are no examples or guidance for running the backend or frontend on Linux, nor for using cross-platform tools or editors. References to IIS and Azure App Service (Windows) further reinforce the Windows-centric approach.
Recommendations
  • Add explicit instructions for setting up and running the backend API on Linux (e.g., using .NET Core CLI, VS Code, or JetBrains Rider).
  • Include Linux/macOS equivalents for all build and deployment steps, such as using 'dotnet build' and 'dotnet publish' instead of Visual Studio menus.
  • Document how to run the React Native manager app on Linux (if supported), or clarify platform limitations.
  • Provide troubleshooting steps for common Linux/macOS issues, not just Windows-specific errors.
  • Mention cross-platform database options or clarify how to connect to Azure SQL from Linux environments.
  • Avoid assuming Visual Studio is required; mention VS Code and other editors where possible.
  • Ensure all CLI commands (npm, npx, dotnet, etc.) are presented in a platform-agnostic way, and specify any OS-specific differences.
GitHub Create Pull Request
Notification Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-tags-segment-push-message.md ...on-hubs/notification-hubs-tags-segment-push-message.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows/Windows Phone-specific notification examples (using Windows toast XML and SendWindowsNativeNotificationAsync), with no equivalent examples for Linux, Android, or iOS platforms. Windows notification patterns and tools are mentioned exclusively, and cross-platform parity is not demonstrated.
Recommendations
  • Add code examples for sending notifications to Android (using FCM) and iOS (using APNs) alongside the Windows examples.
  • Include sample payloads and SDK usage for non-Windows platforms to illustrate cross-platform capabilities.
  • Reorganize examples so that Windows is not always presented first; consider grouping by platform or showing all platforms equally.
  • Explicitly mention and link to documentation for sending notifications to Linux-based devices (e.g., Android) and iOS.
  • Clarify in the text that Azure Notification Hubs supports multiple platforms, not just Windows, and provide balanced coverage.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →