Notification Hubs

124
Total Pages
119
Linux-Friendly Pages
5
Pages with Bias
4.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

10 issues found
Showing 1-10 of 10 flagged pages
Notification Hubs Create an Azure notification hub using Azure Resource Manager template .../notification-hubs/create-notification-hub-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for reviewing deployed resources, but PowerShell examples are shown first and are more prominent in the clean-up section, where only PowerShell is used. This creates a mild Windows bias, as PowerShell is primarily associated with Windows, while Azure CLI is cross-platform. No Linux/macOS-specific tools or instructions are mentioned.
Recommendations
  • Present Azure CLI examples before PowerShell, or side-by-side, to emphasize cross-platform compatibility.
  • Include clean-up instructions using Azure CLI, not just PowerShell.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links if relevant.
  • Avoid implying PowerShell is the default or preferred method unless necessary.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows and Visual Studio are presented as the primary development environment, with explicit requirements for a Windows computer and Visual Studio 2019. The build and deployment instructions focus on Windows tools and workflows (Visual Studio, UWP, IIS), and the troubleshooting section addresses only Windows-specific issues. There are no instructions or examples for building or running the backend/API on Linux or macOS, nor any mention of Linux equivalents for Visual Studio or IIS. Linux/macOS users are referenced only in the context of iOS development, and even then, only for XCode and iOS SDK, not for backend development.
Recommendations
  • Add instructions for building and running the backend/API on Linux/macOS, using .NET Core CLI (dotnet build, dotnet run) and alternative editors like VS Code.
  • Provide deployment steps for Linux-based hosting environments (e.g., Azure App Service for Linux, Docker, Nginx, Apache).
  • Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variables, .NET SDK installation).
  • Present cross-platform instructions first, or in parallel, rather than Windows-first.
  • Mention alternatives to IIS, such as Kestrel or Nginx, for local API hosting.
  • Clarify that Visual Studio is optional and suggest VS Code or JetBrains Rider for Linux/macOS users.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (PowerShell, WebMatrix) are mentioned first or exclusively in several places, such as instructions for creating a Node.js application and retrieving connection strings. Linux/macOS equivalents are referenced but often as secondary options, and some Windows-specific tools (WebMatrix, PowerShell cmdlets) lack direct Linux/macOS alternatives or guidance.
Recommendations
  • Present cross-platform instructions equally, listing Windows, Linux, and macOS tools side-by-side rather than Windows-first.
  • Provide explicit Linux/macOS alternatives for all Windows-specific tools (e.g., suggest VS Code, terminal commands, or other editors instead of WebMatrix).
  • For retrieving connection strings, include Azure CLI (az) commands, which are cross-platform, rather than focusing on PowerShell and classic CLI.
  • Ensure all example commands and workflows are demonstrated in both Windows and Linux/macOS environments.
  • Avoid referencing deprecated or Windows-only technologies (e.g., WebMatrix, Windows Phone) without noting their status and alternatives.
GitHub Create Pull Request
Notification Hubs Azure Notification Hubs Private Link (preview) ...s/blob/main/articles/notification-hubs/private-link.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Windows bias in the validation section, where only instructions for creating and validating a Windows VM are provided, and the DNS resolution example uses PowerShell exclusively. There are no Linux/macOS VM creation or command-line validation examples, nor is there mention of equivalent Linux tools or commands.
Recommendations
  • Add instructions for creating a Linux VM in Azure, either alongside or before the Windows VM example.
  • Provide equivalent Linux/macOS command-line examples for DNS resolution, such as using 'dig' or 'nslookup'.
  • Include screenshots or terminal output from Linux/macOS environments where relevant.
  • Explicitly state that the validation steps can be performed on any OS, and provide cross-platform guidance.
GitHub Create Pull Request
Notification Hubs Create an Azure notification hub using Azure Resource Manager template .../notification-hubs/create-notification-hub-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for reviewing deployed resources, but PowerShell is presented first and is used exclusively for resource cleanup. This ordering and reliance on PowerShell may create friction for Linux/macOS users, as PowerShell is traditionally a Windows tool and not always installed or preferred on non-Windows platforms.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Include Azure CLI commands for resource cleanup alongside PowerShell examples.
  • Clarify that both PowerShell and CLI are supported, and provide installation links for both tools.
  • Consider adding Bash script examples for common tasks.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and patterns (PowerShell, WebMatrix) are mentioned first or exclusively in several places, such as instructions for creating a Node.js application and retrieving connection strings. Linux/macOS equivalents are referenced but often as secondary options, and Windows-centric tools (PowerShell, WebMatrix) are promoted without equal Linux alternatives or ordering.
Recommendations
  • Present cross-platform instructions in parallel, listing Linux/macOS tools (e.g., Bash, Terminal) before or alongside Windows tools.
  • Provide explicit Linux/macOS alternatives for all Windows-specific commands and tools (e.g., show how to retrieve connection strings using Azure CLI on Linux/macOS).
  • Avoid recommending Windows-only tools like WebMatrix; suggest platform-neutral editors and deployment methods.
  • Ensure example commands and tool references are balanced and not Windows-first.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Visual Studio (Windows-only) is listed as a core prerequisite, and the UWP manager application is Windows-specific. Instructions for building and deploying the backend are tailored to Visual Studio and Azure App Service (Windows), with no mention of Linux/macOS alternatives (e.g., VS Code, CLI, or cross-platform .NET tooling). The 'Run React Native frontend application' section lists Windows instructions first and provides no guidance for running the manager app on Linux/macOS. Troubleshooting is focused on Windows-specific issues. There are no examples or instructions for Linux or macOS users to build, deploy, or run the manager application.
Recommendations
  • Provide instructions for building and running the backend using cross-platform .NET CLI tools (dotnet build, dotnet publish) and VS Code.
  • Clarify whether the manager application can be built or run on Linux/macOS, or provide alternatives if not.
  • Include Linux/macOS deployment steps for the backend (e.g., using Azure App Service for Linux, Docker, or manual deployment).
  • Add troubleshooting guidance for Linux/macOS environments.
  • List platform-agnostic prerequisites first, and avoid assuming Visual Studio/Windows as the default.
  • If the UWP manager app is strictly Windows-only, explicitly state this and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Notification Hubs Azure Notification Hubs Private Link (preview) ...s/blob/main/articles/notification-hubs/private-link.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 in the validation section, where only a Windows VM is referenced and a PowerShell command (Resolve-DnsName) is provided to verify DNS resolution. There are no equivalent instructions or examples for Linux/macOS users, such as using dig or nslookup. The CLI instructions are cross-platform, but the validation step assumes a Windows environment.
Recommendations
  • Include instructions for creating and connecting to a Linux VM in Azure, alongside the Windows VM steps.
  • Provide Linux/macOS command-line equivalents for DNS resolution, such as 'dig <namespace_name>.privatelink.servicebus.windows.net' or 'nslookup <namespace_name>.privatelink.servicebus.windows.net'.
  • Explicitly state that the Azure CLI steps are cross-platform and can be run on Windows, Linux, or macOS.
  • Add screenshots or examples showing DNS validation from a Linux shell.
GitHub Create Pull Request
Notification Hubs Create an Azure notification hub using Bicep ...les/notification-hubs/create-notification-hub-bicep.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured equally alongside CLI, and is shown as a primary alternative throughout, which may suggest a slight Windows bias. There are no Linux-specific tools or shell examples (e.g., Bash), and PowerShell is generally associated with Windows environments, although it is cross-platform now. The order of examples (CLI first, then PowerShell) is neutral, but the repeated inclusion of PowerShell may imply a Windows-centric approach.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
  • Mention that PowerShell Core is available cross-platform, or link to installation instructions for Linux/macOS users.
  • Consider adding Bash or shell script examples for Linux users, or explicitly state that CLI commands are suitable for Linux/macOS.
  • Add a note about the availability of Azure CLI and PowerShell on all major platforms to reassure non-Windows users.
GitHub Create Pull Request
Notification Hubs Create an Azure notification hub using Bicep ...les/notification-hubs/create-notification-hub-bicep.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks, but PowerShell is featured equally alongside CLI, and is shown in dedicated tabs. PowerShell is a Windows-centric tool, and its inclusion may suggest Windows as a primary platform. However, Azure CLI examples are present and shown first in each case, which supports Linux/macOS users. No Windows-only tools or patterns are present, and Linux users can complete all tasks using CLI.
Recommendations
  • Explicitly mention that Azure CLI works on Linux/macOS and is the recommended cross-platform tool.
  • Clarify that PowerShell Core is available cross-platform, or link to installation instructions for Linux/macOS if PowerShell is referenced.
  • Consider listing CLI examples before PowerShell, or labeling CLI as the default/recommended approach for non-Windows users.
  • Add a note for Linux/macOS users confirming parity and pointing to relevant setup guides.
GitHub Create Pull Request