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 26-50 of 66 flagged pages
Notification Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-push-bing-spatial-data-geofencing-notification.md
...on-hubs-push-bing-spatial-data-geofencing-notification.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows and Universal Windows Platform (UWP) development, with all examples, tooling, and workflows centered around Visual Studio, UWP APIs, and Windows-specific notification services. There are no examples or guidance for Linux, macOS, or cross-platform development environments, nor are alternative tools or approaches mentioned. The backend sample is .NET-based and assumes Visual Studio usage, and all push notification testing is demonstrated on Windows devices.
Recommendations
- Provide equivalent instructions and code samples for cross-platform or Linux-based development environments, such as using .NET Core on Linux, or alternative backend stacks (Node.js, Python, etc.).
- Include examples for sending push notifications to non-Windows platforms (e.g., Android, iOS) using Azure Notification Hubs.
- Offer guidance for setting up and testing the backend and client apps using open-source editors (e.g., VS Code) and CLI tools instead of Visual Studio.
- Mention and demonstrate use of cross-platform notification libraries or SDKs.
- Clarify which steps are Windows-specific and provide alternatives or notes for Linux/macOS users where possible.
- Add instructions for using cURL, Postman, or other cross-platform tools to interact with the Bing Spatial Data API and Notification Hub endpoints.
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 →
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') without providing equivalent information or examples for Linux environments. There are no Linux-specific instructions, tools, or references, and the only OS-specific guidance outside of mobile platforms is for Windows.
Recommendations
- Add a section or references for checking and configuring TLS support on Linux servers, such as using OpenSSL or updating system libraries.
- Include links to official Linux documentation or community guides for managing TLS versions.
- Provide parity in examples and troubleshooting steps for both Windows and Linux environments.
- Mention common Linux distributions and how to verify or update their TLS support.
Notification Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-baidu-china-android-notifications-get-started.md
...ion-hubs-baidu-china-android-notifications-get-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows development environments and tools. It provides detailed instructions and screenshots for creating and running a .NET console application using Visual Studio, NuGet Package Manager Console, and C#, all of which are Windows-centric. There are no equivalent examples or explicit instructions for Linux or cross-platform environments (e.g., using .NET Core CLI, VS Code, or alternative package managers). The use of Windows-specific terminology and tools (e.g., 'Visual C# console application', 'Package Manager Console', 'F5 in Visual Studio') further reinforces this bias. Linux users are left without guidance for sending notifications from non-Windows systems.
Recommendations
- Provide equivalent instructions for Linux and macOS users, such as using the .NET Core CLI (dotnet new console, dotnet add package) instead of Visual Studio-specific steps.
- Include cross-platform code snippets and terminal commands for installing the Notification Hubs SDK and running the sample app.
- Mention and illustrate the use of VS Code or JetBrains Rider as alternative IDEs that work on Linux/macOS.
- Avoid Windows-specific language (e.g., 'press F5 in Visual Studio') or supplement it with cross-platform alternatives (e.g., 'run dotnet run in your terminal').
- Add explicit notes or sections for Linux/macOS users, especially in areas where the workflow differs from Windows.
- Ensure screenshots and instructions for sending notifications from the Azure portal are platform-agnostic.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio and Windows-specific project structures (e.g., Solution Explorer, .cs files) without mentioning Linux or cross-platform development environments. Windows platforms (MPNS, WNS) are listed before Apple (APNS) and FCM in code examples, and there are no instructions or examples for developing or deploying from Linux or using non-Windows tools.
Recommendations
- Add explicit instructions or notes for users developing on Linux, such as using VS Code, JetBrains Rider, or command-line tools (dotnet CLI) instead of Visual Studio.
- Include alternative steps for navigating project files and folders outside of Visual Studio (e.g., using terminal commands).
- Reorder platform mentions in code and text to avoid always listing Windows first; consider alphabetical or usage-based ordering.
- Provide guidance on how to run, build, and deploy the sample project from Linux or macOS.
- Clarify that the code and Notification Hubs functionality are cross-platform, and highlight any platform-specific caveats for non-Windows users.
Notification Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-aspnet-backend-ios-apple-push-notification-service-apns-rich.md
...-backend-ios-apple-push-notification-service-apns-rich.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio and Windows-centric development patterns for the backend (e.g., Solution Explorer, Properties window, 'Include In Project', 'Build Action: Embedded Resource'), and by instructing users to deploy to Azure Websites via Visual Studio's Publish workflow. There are no instructions or examples for performing equivalent tasks on Linux or macOS, such as using cross-platform .NET CLI tools, editing project files manually, or deploying via command line or Git. This could hinder users on non-Windows platforms from following the tutorial.
Recommendations
- Provide alternative instructions for Linux/macOS users, such as using the .NET CLI (dotnet) to add resources, edit project files, and build/publish the backend.
- Explain how to manually add embedded resources by editing the .csproj file, instead of relying solely on Visual Studio GUI steps.
- Include deployment instructions using cross-platform tools (e.g., Azure CLI, Git-based deployment) rather than only Visual Studio's Publish dialog.
- Clarify that Visual Studio steps are optional and provide parity for users developing on Linux or macOS.
- Where possible, use neutral language (e.g., 'your IDE or editor') and avoid assuming the user is on Windows.
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 →
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 alternatives (such as Node.js, Python, or Java backends). The backend example and all references assume a Windows/.NET development environment, and there are no instructions or code samples for setting up or running the backend on Linux or cross-platform stacks. There is also no mention of how to run or test the backend outside of a Windows context.
Recommendations
- Provide equivalent backend implementation examples using cross-platform technologies such as Node.js (Express), Python (Flask/FastAPI), or Java (Spring Boot), and reference them alongside the ASP.NET example.
- Explicitly mention that the backend can be hosted on Linux and provide instructions for doing so (e.g., using Azure App Service for Linux, Docker, or running locally on Linux).
- Include Linux/macOS-specific setup and testing instructions, such as using curl or HTTPie for API testing, and avoid assuming Visual Studio or Windows-only tooling.
- When referencing the backend, use neutral terminology (e.g., 'your backend API') and provide links to cross-platform backend samples.
- Add a note clarifying that the client-side Android code is agnostic to the backend technology, and that any backend capable of implementing the described REST endpoints can be used.
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 →
Detected Bias Types
Windows First
Windows Tools
Windows Heavy Examples
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Windows (WNS, MPNS) examples and terminology before or more prominently than Linux/Android/iOS equivalents. Windows-specific notification types and credentials are shown first in code samples, and the sample links at the end are all Windows/.NET focused. There are no Linux-specific instructions, nor are there examples or references to Linux command-line tools or environments. The only build instruction ('mvn package') is platform-neutral, but otherwise, the documentation assumes familiarity with Windows notification systems and does not provide parity for Linux users.
Recommendations
- Reorder examples to present cross-platform (Android/iOS) or platform-neutral examples before Windows-specific ones.
- Add explicit Linux/Unix usage notes or examples, such as running the SDK on Linux, or using Linux-based tools for related tasks (e.g., generating SAS tokens, managing storage).
- Include links to Linux/Android/iOS sample projects, not just Windows/.NET ones.
- Balance the coverage of notification platforms in code samples (e.g., show Android/iOS registration and notification examples before or alongside Windows examples).
- Mention that the SDK and examples work on Linux and provide troubleshooting tips for common Linux environments.
Notification Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-enterprise-push-notification-architecture.md
...ication-hubs-enterprise-push-notification-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias throughout. All code samples and application instructions are based on C#/.NET and target Windows platforms (e.g., Windows Store app, Windows toast notifications). The deployment workflow is described exclusively using Visual Studio and Azure WebJobs, both of which are Windows-centric tools. There are no Linux, cross-platform, or non-Windows examples, nor is there mention of how to implement or deploy the solution on Linux or using non-Windows tools.
Recommendations
- Add equivalent sample code and instructions for Linux environments, such as using .NET Core/6+ on Linux, or alternative languages (e.g., Python, Node.js) that are cross-platform.
- Provide examples of deploying the backend listener as an Azure Function or containerized service, which can be developed and run on Linux as well as Windows.
- Include instructions for command-line deployment and management (e.g., using Azure CLI, Bash scripts) instead of or in addition to Visual Studio and right-click workflows.
- Demonstrate how to send notifications to non-Windows mobile platforms (e.g., Android, iOS) using Notification Hubs, with relevant code samples.
- Explicitly mention cross-platform options and clarify which steps are Windows-specific, offering alternatives where possible.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by listing Windows-specific tools and workflows first (e.g., PowerShell, WebMatrix), providing explicit PowerShell/Windows CLI commands, and referencing Windows-centric development environments before their Linux or cross-platform equivalents. Linux and Mac alternatives are mentioned but not given equal prominence or detailed examples.
Recommendations
- Ensure that instructions for creating and deploying Node.js applications include Linux and macOS workflows (e.g., using Bash, Terminal, or cross-platform editors like VS Code) alongside or before Windows-specific tools.
- When mentioning command-line interfaces, list Bash (Linux), Terminal (macOS), and PowerShell (Windows) in a neutral or rotating order, and provide equivalent command examples for each where relevant.
- For retrieving connection strings or performing Azure operations, provide Azure CLI examples (which are cross-platform) before or alongside PowerShell commands.
- Avoid referencing Windows-only tools (such as WebMatrix) without offering cross-platform alternatives.
- Audit all step-by-step instructions to ensure Linux users are not left to infer steps or commands that are only explicitly shown for Windows.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-centric code samples (using C# and Windows APIs), referencing Windows-specific concepts (e.g., ChannelUri, Windows Store apps, ApplicationData), and omitting equivalent Linux or cross-platform examples. There is no mention of Linux client registration, nor are there code samples or guidance for Linux or non-Windows platforms.
Recommendations
- Add code samples for registering devices from Linux clients, using languages and libraries common on Linux (e.g., Python, Java, Node.js).
- Include examples that use cross-platform REST API calls (e.g., using curl, Python requests, or JavaScript fetch) for device registration and installation management.
- Document how to obtain PNS handles and manage registrations on non-Windows platforms, such as Android, iOS, or Linux IoT devices.
- Avoid Windows-specific terminology or, when necessary, provide equivalent explanations and instructions for Linux and other platforms.
- Highlight cross-platform SDKs and tools, and ensure that any Windows-specific features (like secondary tiles) are clearly marked as such, with alternatives or notes for other platforms.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing notification payload examples for Windows platforms (Windows Store, MPNS/Windows Phone) before or instead of Linux/Android equivalents. Windows-specific XML payloads and tile templates are shown in detail, while Android (FCM) and Linux clients are only mentioned in passing, with no concrete examples or guidance. There are no Linux or Android code snippets, and the focus on Windows notification formats and tools (such as tile templates) may alienate non-Windows developers.
Recommendations
- Include concrete payload and template examples for Android (FCM) and other non-Windows platforms alongside Windows and iOS.
- Present platform examples in a neutral or rotating order (e.g., iOS, Android, Windows) to avoid always listing Windows first.
- Add sample code or configuration for Linux-based clients or cross-platform tools (e.g., curl, Python, Node.js) to demonstrate parity.
- Avoid focusing on Windows-specific notification features (like tile templates) without providing equivalent examples or explanations for other platforms.
- Explicitly mention that the concepts apply equally to Linux/Android and provide links or references to relevant documentation for those platforms.
Notification Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/notification-hubs/notification-hubs-push-notification-fixer.md
...tion-hubs/notification-hubs-push-notification-fixer.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing and exclusively referencing Windows-specific tools (Visual Studio, Server Explorer) for diagnostics and management tasks. There are no equivalent examples or guidance for Linux users, nor are cross-platform or command-line alternatives (such as Azure CLI, REST API, or open-source tools) highlighted alongside or before Windows tools. This may hinder Linux or non-Windows users from effectively following the troubleshooting steps.
Recommendations
- Add equivalent instructions and screenshots for performing diagnostics and management tasks using cross-platform tools such as Azure CLI, REST API, or Azure Portal.
- Explicitly mention and provide examples for Linux/macOS users, especially for tasks currently described only with Visual Studio or Server Explorer.
- When referencing Visual Studio or other Windows-only tools, always provide alternative methods (e.g., using Azure CLI, REST API, or Service Bus Explorer) and present them before or alongside the Windows-specific instructions.
- Include sample scripts or commands for common troubleshooting actions (e.g., listing registrations, sending test notifications) using cross-platform tools.
- Clarify in each section whether the described tool or method is Windows-only, and direct users to cross-platform alternatives where available.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias, especially in the validation section, where only a Windows VM is referenced and only a PowerShell command (Resolve-DnsName) is provided for DNS validation. There are no equivalent instructions or examples for Linux users, such as using a Linux VM or common Linux DNS tools (e.g., dig, nslookup). The documentation also links only to Windows VM creation guides, omitting Linux alternatives.
Recommendations
- Provide parallel instructions for creating and using a Linux virtual machine, including a link to the official Azure Linux VM creation guide.
- Include Linux command-line examples for DNS validation, such as using 'dig' or 'nslookup', alongside the PowerShell example.
- When referencing VM creation, mention both Windows and Linux options, or use neutral language (e.g., 'Create a virtual machine' with links to both OS guides).
- Ensure that all CLI and validation steps are presented in a cross-platform manner, highlighting any OS-specific differences where relevant.
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 →
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.
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 →
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.
Notification Hubs
Create an Azure notification hub using Azure Resource Manager template
.../notification-hubs/create-notification-hub-template.md
Medium Priority
View Details →
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 the resource cleanup section. This may create friction for Linux/macOS users who typically use Azure CLI and may not have PowerShell installed.
Recommendations
- Present Azure CLI examples before PowerShell, or side-by-side, to avoid Windows-first bias.
- Include Azure CLI commands for resource cleanup, not just PowerShell.
- Explicitly mention that both CLI and PowerShell are cross-platform, but CLI is pre-installed on most Linux/macOS systems.
- Add notes or links for installing PowerShell on Linux/macOS if PowerShell examples are retained.
Notification Hubs
Azure Notification Hubs Private Link (preview)
...s/blob/main/articles/notification-hubs/private-link.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily in the validation section, where only a Windows VM is referenced and a PowerShell command (Resolve-DnsName) is provided for DNS validation. There are no equivalent instructions or examples for Linux/macOS users, such as using dig or nslookup on a Linux VM. Throughout, the Azure CLI is used for resource creation, which is cross-platform, but validation and VM creation steps are Windows-centric.
Recommendations
- Include instructions for creating and validating with a Linux VM, referencing the official Azure Linux VM quickstart.
- Provide equivalent DNS validation commands for Linux/macOS (e.g., dig, nslookup) alongside the PowerShell example.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, and link to installation guides for all platforms.
- Ensure screenshots and portal instructions do not assume Windows-only environments.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a moderate Windows bias. Windows tools and patterns (PowerShell, WebMatrix, Windows-specific tutorials) are mentioned first or exclusively in several sections. The instructions for creating a Node.js application reference Windows PowerShell and WebMatrix before alternatives, and the retrieval of the connection string highlights PowerShell and the Azure classic CLI, with no mention of Linux/macOS equivalents (such as Bash scripts or Azure CLI v2). While Linux and macOS users can generally follow the instructions, the prominence of Windows tools and ordering may create friction.
Recommendations
- Provide Linux/macOS-specific examples and tools (e.g., Azure CLI v2 commands, Bash scripts) alongside or before Windows examples.
- Reorder instructions to present cross-platform tools (like Azure CLI) before platform-specific ones.
- Mention and link to Linux/macOS-friendly editors and deployment options (e.g., VS Code, nano, vim, direct Azure CLI deployment).
- Clarify that all steps can be performed on Linux/macOS and provide explicit instructions where differences exist.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Windows tools (Visual Studio, UWP, IIS) are required for building and deploying the manager application, and Windows instructions are presented first and in greater detail. There is no mention of Linux alternatives for backend development, deployment, or running the manager application. The troubleshooting section and deployment steps are Windows-specific, and Linux/macOS users are only referenced for iOS development, not for backend or manager app tasks.
Recommendations
- Provide instructions for building and deploying the backend API using cross-platform .NET Core CLI tools, including on Linux/macOS.
- Offer alternatives to Visual Studio, such as Visual Studio Code or JetBrains Rider, and document how to build and run the solution on Linux/macOS.
- Clarify whether the manager application (UWP) can be replaced with a cross-platform desktop app (e.g., Electron, React Native for macOS) and provide guidance if possible.
- Include troubleshooting steps relevant to Linux/macOS environments.
- Present platform-agnostic instructions first, or in parallel, rather than Windows-first.
- Document how to deploy the backend to Azure using Azure CLI or GitHub Actions, not just Visual Studio.
Notification Hubs
Azure Notification Hubs Private Link (preview)
...s/blob/main/articles/notification-hubs/private-link.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily in the validation section, where only Windows VM creation and PowerShell commands are provided for testing the private link connection. There are no equivalent instructions or examples for Linux or macOS users, and the validation workflow assumes a Windows environment. Additionally, the referenced quickstart for VM creation is Windows-specific.
Recommendations
- Provide Linux VM creation instructions and link to the Linux VM quickstart documentation.
- Include equivalent DNS resolution commands for Linux/macOS (e.g., `dig`, `nslookup`, or `host`).
- Mention that the Azure CLI is cross-platform and can be used on Linux/macOS, and clarify any OS-specific steps.
- Present validation examples for both Windows and Linux/macOS users, either side-by-side or in a dedicated section.
Notification Hubs
Create an Azure notification hub using Azure Resource Manager template
.../notification-hubs/create-notification-hub-template.md
Medium Priority
View Details →
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 shown first and is used exclusively for the resource cleanup section. This creates a mild Windows bias, as PowerShell is primarily a Windows tool and Linux/macOS users are more likely to use Azure CLI. No Linux/macOS-specific instructions or examples are given for cleanup.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially for resource cleanup.
- Include explicit instructions and code samples for Linux/macOS users using Azure CLI for all tasks, including resource deletion.
- Clarify that Azure CLI works cross-platform and is recommended for non-Windows environments.
- Add notes or tabs indicating which commands are suitable for which platforms.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell are mentioned first or exclusively in several key places: instructions for creating a Node.js application reference Windows PowerShell before alternatives, and retrieving the connection string prioritizes the PowerShell cmdlet and classic Azure CLI (which is Windows-centric). Linux/macOS equivalents are mentioned, but not with equal prominence or detail.
Recommendations
- Present Linux/macOS tools and workflows alongside Windows options, giving equal prominence.
- Provide explicit Bash and Terminal command examples for Linux/macOS users, not just mention them.
- When referencing command-line tools, list cross-platform options first or in parallel (e.g., Azure CLI, Bash, zsh).
- Include instructions for retrieving the connection string using Azure CLI (az), which is cross-platform, rather than focusing on PowerShell and classic CLI.
- Avoid referencing Windows-specific development environments (e.g., WebMatrix, PowerShell) without Linux/macOS alternatives.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias: Windows and Visual Studio are presented as the primary development environment, with explicit requirements for a Windows computer and UWP application. Instructions for building and deploying the backend focus on Visual Studio and Azure App Service (Windows), with no mention of Linux or macOS equivalents. There are no examples or guidance for using Linux-based development tools, nor any parity for deploying with Linux-based Azure App Service or using cross-platform editors. The troubleshooting and build sections are Windows-specific, and Linux/macOS users are only mentioned as required for iOS development, not for backend or manager app development.
Recommendations
- Add instructions for building and running the backend API using .NET CLI on Linux/macOS, including publishing to Azure App Service (Linux).
- Provide guidance for using cross-platform editors (e.g., VS Code) and terminal commands for Linux/macOS users.
- Include troubleshooting steps relevant to Linux/macOS environments.
- Clarify which components are Windows-only (UWP manager app) and suggest alternatives for Linux/macOS users (e.g., web-based manager app, Electron, or cross-platform desktop frameworks).
- Reorder sections to present cross-platform options first, or at least in parallel with Windows-specific instructions.
Notification Hubs
Create an Azure notification hub using Azure Resource Manager template
.../notification-hubs/create-notification-hub-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for reviewing deployed resources, but PowerShell is listed first, which may subtly prioritize Windows users. The cleanup section only provides a PowerShell example, omitting an equivalent Azure CLI command, which is more cross-platform and preferred on Linux/macOS. There are no explicit references to Windows-only tools, but the ordering and example selection show a mild Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred on Linux/macOS.
- Include Azure CLI commands for resource cleanup alongside PowerShell examples.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS to encourage cross-platform usage.
- Where possible, balance the number and prominence of PowerShell and CLI examples throughout the documentation.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for reviewing deployed resources, but PowerShell is listed first, which may subtly prioritize Windows users. The clean-up instructions only provide a PowerShell example, omitting an equivalent Azure CLI command, which is more cross-platform and preferred on Linux/macOS. There is no explicit mention of Linux-specific tools or workflows, and the overall pattern leans toward Windows-centric tooling.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
- Include Azure CLI commands for resource clean-up alongside PowerShell examples.
- Add notes clarifying that Azure CLI works on Windows, Linux, and macOS, and provide installation links for non-Windows platforms.
- Consider including Bash script examples for common operations, or at least mention their applicability.
- Review future documentation for parity in example coverage between Windows and Linux/macOS environments.