Communication Services
2083
Total Pages
1869
Linux-Friendly Pages
214
Pages with Bias
10.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
367 issues found
Showing 176-200 of 367 flagged pages
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides PowerShell examples using the Windows-specific Send-MailMessage cmdlet and PSCredential objects. No Linux or macOS equivalent commands (e.g., using sendmail, mailx, or Python's smtplib) are mentioned, nor are cross-platform SMTP tools or scripts provided. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
- Add Linux/macOS examples using common tools such as sendmail, mailx, or Python scripts for SMTP.
- Mention cross-platform alternatives to PowerShell, such as using curl, swaks, or Python's smtplib.
- Clearly indicate which steps/tools are Windows-specific and provide parity instructions for other platforms.
- Consider reordering examples so that platform-neutral or cross-platform solutions are presented first.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure PowerShell commands and modules for all examples and instructions. There are no references to Azure CLI, Bash, or Linux/macOS-specific workflows. The prerequisites and all operational steps assume PowerShell usage, which is most common on Windows, and do not mention or provide alternatives for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions).
- Include installation instructions for Azure CLI and note its cross-platform compatibility.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or provide Bash script alternatives.
- Reorder examples or provide parallel sections for both PowerShell and CLI/Bash to avoid Windows-first presentation.
- Clarify any platform-specific limitations or requirements.
Communication Services
Subscribe to events
...ion-services/quickstarts/events/subscribe-to-events.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure portal, Azure CLI, PowerShell, and .NET SDK. While Azure CLI is cross-platform, PowerShell and .NET SDK are traditionally Windows-centric, and PowerShell is given its own dedicated section. There are no explicit Linux/macOS-specific instructions or examples, and the documentation does not mention Linux tools or shell patterns (e.g., Bash). The ordering and inclusion of PowerShell and .NET SDK may suggest a Windows-first bias, and there is no explicit assurance that all steps work seamlessly on Linux/macOS.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users, especially for webhook setup.
- Clarify that Azure CLI instructions are cross-platform and highlight any OS-specific differences.
- If PowerShell is required, note that PowerShell Core is available on Linux/macOS and provide installation guidance.
- Include troubleshooting or notes for Linux/macOS users where behavior may differ.
- Consider reordering sections so that cross-platform tools (Azure CLI) are presented before Windows-centric tools.
Communication Services
Additional Prerequisites
...ity/includes/active-directory/service-principal-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific setup guides for managed identities (portal, PowerShell, CLI, ARM template, SDK) with URLs that explicitly mention 'windows-vm'. There are no equivalent Linux VM or cross-platform examples or links. The environment variable instructions are generic, but the guidance for setting up managed identities is Windows-centric, and Linux/macOS users may not find relevant instructions for their platforms.
Recommendations
- Include links to managed identity setup guides for Linux VMs and macOS environments.
- Add examples and instructions for setting environment variables on Linux/macOS (e.g., using export in bash/zsh).
- Ensure parity in documentation by providing CLI and SDK examples that are platform-agnostic or explicitly cover Linux/macOS scenarios.
- Avoid using only Windows-specific URLs and terminology; clarify when instructions apply to all platforms.
Communication Services
Register the Event Grid resource provider
...starts/events/includes/register-provider-powershell.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides only PowerShell commands for registering the Event Grid resource provider, which are primarily used on Windows. No equivalent Azure CLI or Bash examples are given for Linux or macOS users, and the instructions implicitly assume a Windows environment.
Recommendations
- Add Azure CLI examples (e.g., 'az provider register --namespace Microsoft.EventGrid') alongside PowerShell commands.
- Clearly indicate that PowerShell is Windows-centric and provide cross-platform alternatives.
- Present both Windows and Linux/macOS instructions in parallel, or use Azure CLI as the default for cross-platform compatibility.
Communication Services
Set up and create access tokens for Teams users
...nication-services/quickstarts/manage-teams-identity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in the administrator troubleshooting section, where only PowerShell commands and modules are provided for resolving service principal issues. There are no equivalent instructions for Linux/macOS users, such as using Azure CLI or Microsoft Graph CLI, and no mention of cross-platform alternatives. The rest of the documentation is mostly platform-neutral, focusing on Azure portal and SDK usage.
Recommendations
- Provide equivalent instructions using Azure CLI or Microsoft Graph CLI, which are cross-platform and work on Linux/macOS.
- Explicitly mention that PowerShell commands require Windows or PowerShell Core, and offer alternatives for non-Windows environments.
- Add troubleshooting steps for Linux/macOS users, including installation and usage of CLI tools.
- Where possible, use web-based or REST API solutions that do not depend on OS-specific tooling.
Communication Services
Teams Phone Extensibility
...uickstarts/tpe/teams-phone-extensibility-quickstart.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias, especially in sections related to provisioning Teams Resource Accounts and bot services. All command-line examples use PowerShell cmdlets and Azure PowerShell modules, with no mention of Bash, Linux CLI alternatives, or cross-platform scripting. The instructions for Teams administration explicitly require PowerShell and reference Windows-centric tools and patterns, with no guidance for Linux/macOS users. Azure CLI is mentioned, but only in the context of installing PowerShell modules. No Linux-specific examples or parity notes are provided.
Recommendations
- Provide equivalent Bash/Azure CLI commands for bot provisioning and resource account management where possible.
- Clarify which steps can be performed using the Azure Portal or REST APIs, which are platform-agnostic.
- Add explicit instructions or links for Linux/macOS users, including how to install and use Azure CLI and any cross-platform alternatives to PowerShell cmdlets.
- Indicate whether PowerShell Core (pwsh) on Linux/macOS is supported for Teams cmdlets, and provide installation guidance if so.
- Reorder examples so that platform-agnostic methods (Azure Portal, REST API, Azure CLI) are presented before Windows/PowerShell-specific instructions.
Communication Services
Access a user's Teams Phone separate from their Teams client
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. The only explicit tooling example for obtaining the Resource Account GUID references the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance), which is a Windows-centric tool. The instructions for enabling Teams users reference the Microsoft 365 admin center, which is web-based but often assumes a Windows environment. There are no Linux/macOS-specific examples or alternative CLI tools mentioned, and no parity shown for Linux users in the critical step of obtaining the Resource Account GUID.
Recommendations
- Provide equivalent Linux/macOS instructions for obtaining the Resource Account GUID, such as using Microsoft Graph API via curl or other cross-platform tools.
- Explicitly mention that the PowerShell cmdlet is Windows-only and offer alternatives for non-Windows users.
- Add examples using REST API calls with curl or HTTPie for steps currently shown only with PowerShell.
- Clarify that the Microsoft 365 admin center is web-based and accessible from any OS, to avoid implicit Windows bias.
Communication Services
Quickstart - How to call to Teams user from an Android app
...ideo-calling/includes/teams-user/teams-user-android.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Teams deployment and enabling Enterprise Voice via PowerShell, which is a Windows-specific tool. There are no Linux/macOS alternatives or instructions for these steps, and the prerequisite links point to Windows-centric guides. The rest of the tutorial is Android-focused and platform-neutral, but the setup steps for Teams users assume Windows environments.
Recommendations
- Provide instructions or links for enabling Enterprise Voice and managing Teams users using cross-platform tools (e.g., Microsoft 365 admin center web UI) or note if PowerShell Core is supported on Linux/macOS.
- Clarify whether Teams deployment and license management can be performed from non-Windows platforms, and offer guidance for Linux/macOS users.
- Explicitly state any platform requirements for administrative steps, and suggest alternatives if available.
Communication Services
Answer Teams Phone calls from Call Automation
...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias. Key setup steps for Teams resource accounts and DevTunnel hosting are shown exclusively with PowerShell commands, which are native to Windows. No Linux or macOS equivalents (e.g., Bash, CLI alternatives) are provided, and references to Windows-centric tools (PowerShell, DevTunnel) appear without cross-platform context. This creates friction for Linux/macOS users, who must find their own workarounds.
Recommendations
- Provide equivalent Bash or Azure CLI commands for all PowerShell examples, especially for Teams resource account creation and DevTunnel setup.
- Explicitly state platform compatibility for DevTunnel and PowerShell commands; if cross-platform, provide installation and usage instructions for Linux/macOS.
- Where possible, link to cross-platform documentation or tools.
- Reorder examples or add parallel Linux/macOS instructions so Windows is not always presented first.
Communication Services
Quickstart - Make a call to Teams user from an iOS app
...ce-video-calling/includes/teams-user/teams-user-ios.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references enabling Teams Phone features using PowerShell, a Windows-centric tool, and links to instructions that are primarily Windows-focused. No Linux/macOS alternatives or parity are provided for this step, and Windows tools are mentioned first and exclusively.
Recommendations
- Provide Linux/macOS-compatible instructions for enabling Teams Phone features, such as using cross-platform PowerShell Core or Azure CLI where possible.
- Explicitly state whether the required PowerShell steps can be performed on Linux/macOS, and link to relevant documentation if available.
- If Windows-only tools are required, clarify this limitation early in the prerequisites and suggest possible workarounds or alternatives for non-Windows users.
Communication Services
References - How to collect diagnostic audio recordings
...ferences/how-to-collect-diagnostic-audio-recordings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The build instructions for the 'unpack_aecdump' tool are exclusively for Windows, referencing Visual Studio 2022 and linking only to Windows-specific Chromium build instructions. There are no Linux or macOS build instructions, nor are alternative tools or commands for those platforms mentioned. The example commands and file paths use Windows conventions (e.g., .exe suffix), and the prerequisites list only Windows tools.
Recommendations
- Add build instructions for Linux and macOS, including required dependencies (e.g., GCC/Clang, Python, depot_tools) and platform-specific steps.
- Reference the appropriate Chromium build documentation for Linux and macOS.
- Provide example commands for running the unpack_aecdump tool on Linux/macOS (e.g., ./unpack_aecdump audio_debug.5.aecdump).
- Clarify that the unpack_aecdump tool can be built and run on multiple platforms, not just Windows.
- Avoid using Windows-only file extensions (.exe) in generic instructions, or provide platform-specific notes.
Communication Services
Quickstart - Make a call to Teams user from a web app
...o-calling/includes/teams-user/teams-user-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page displays a Windows bias in the prerequisites section by referencing Teams deployment and user enablement steps that rely on Windows-centric tools and documentation, such as PowerShell and links to Windows-specific guides. There are no Linux/macOS equivalents or alternative instructions provided for these critical setup steps. The rest of the tutorial (JavaScript code, web app setup) is cross-platform, but the initial environment setup assumes Windows.
Recommendations
- Provide Linux/macOS equivalents for enabling Teams Phone and Enterprise Voice, or clarify if these steps can only be performed on Windows.
- Include links or instructions for Teams deployment and user enablement on Linux/macOS, if possible.
- Explicitly state platform requirements for administrative steps, and suggest workarounds or alternatives for non-Windows users.
- Add a note about the cross-platform nature of the SDK and web app, and clarify which steps are platform-dependent.
Communication Services
Detect sensitive data using Azure AI
...ion-services/samples/email-detect-sensitive-content.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns first (e.g., cmd, PowerShell, registry queries), omitting equivalent Linux/macOS instructions for key setup steps, and not providing parity in environment setup or troubleshooting for non-Windows platforms. All code and terminal examples assume a Windows environment, with no mention of Linux/macOS alternatives.
Recommendations
- Provide Linux/macOS equivalents for registry queries (e.g., use 'dotnet --list-sdks' or 'dotnet --info' instead of 'reg query').
- List Bash or terminal examples before or alongside Windows cmd/PowerShell examples.
- Explicitly mention cross-platform compatibility for .NET and Azure SDKs.
- Add troubleshooting notes for Linux/macOS users (e.g., environment variable setup, file paths).
- Include screenshots or instructions for Linux/macOS where relevant (e.g., terminal usage, environment variable configuration).
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 demonstrates a notable Windows bias by providing PowerShell commands for resource cleanup, which are specific to Windows environments. While Azure CLI examples are included, PowerShell commands are shown for key tasks (like deleting Email Communication Services and Domain resources) without equivalent bash or Linux/macOS shell examples. The structure also presents PowerShell and Windows-centric tools before alternatives, making it less accessible for Linux/macOS users.
Recommendations
- Provide bash or shell equivalents for all PowerShell commands, especially for resource deletion tasks.
- Ensure Azure CLI examples are complete and cover all actions shown in PowerShell.
- Reorder examples so that cross-platform tools (Azure CLI, Python) are presented before or alongside PowerShell.
- Explicitly note platform compatibility for each command and provide guidance for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation repeatedly references Windows-specific tools and patterns, such as PowerShell and Windows terminal, before mentioning generic or cross-platform alternatives. Instructions like 'Open an instance of PowerShell, a Windows terminal, a command prompt, or the equivalent' and 'Open a new PowerShell window' prioritize Windows environments and terminology, even though the sample is Node.js-based and otherwise platform-agnostic. There are no explicit Linux/macOS examples or terminal instructions, and the language assumes familiarity with Windows tools.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., 'Open a terminal (PowerShell, Command Prompt, Terminal on macOS/Linux)') in all relevant steps.
- Provide example commands for Linux/macOS where there may be differences (e.g., environment variable setup, file paths).
- Avoid using Windows-specific terms like 'PowerShell window' as the default; use 'terminal' or 'command line' as the primary term.
- Add a note or section confirming cross-platform compatibility and listing any OS-specific caveats.
Communication Services
Tutorial - Prepare a web app for Azure Communication Services (Node.js)
...communication-services/tutorials/building-app-start.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. The Node.js installation section links only to a Windows-specific tutorial and provides PowerShell commands for nvm usage, with no mention of Linux/macOS equivalents. Folder creation examples use Windows paths (e.g., C:\Users\Documents\ACS\CallingApp) and screenshots appear to be from Windows environments. There are no explicit instructions or examples for Linux/macOS users regarding nvm, npm, or file system paths.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS users, including shell commands for nvm installation and usage.
- Include Linux/macOS file path examples alongside Windows paths.
- Add links to official Node.js/nvm setup guides for all platforms, not just Windows.
- Clarify that Visual Studio Code and all npm/webpack commands work cross-platform.
- Add screenshots or notes indicating that the process is similar on Linux/macOS.
Communication Services
Migrating from Twilio Conversations Chat to Azure Communication Services Chat C#
...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The prerequisites require Visual Studio (Windows-centric), and the only package installation example is given in PowerShell (dotnet add package), with no mention of Linux/macOS alternatives (e.g., Bash, VS Code, or cross-platform editors). There is no explicit mention of Linux or macOS compatibility, nor are alternative setup instructions or examples provided for those platforms.
Recommendations
- Add Linux/macOS setup instructions, including references to cross-platform editors like VS Code.
- Provide Bash or shell examples for package installation (e.g., 'dotnet add package' in Bash, or mention that it works in any terminal).
- Clarify that Azure CLI commands and .NET SDK are cross-platform, and provide links or notes for Linux/macOS installation.
- Include a note that the code samples are platform-agnostic and can be run on Linux/macOS if .NET is installed.
- List prerequisites for Linux/macOS users, such as installing .NET SDK and Azure CLI on those platforms.
Communication Services
Migrating from Twilio Conversations Chat to Azure Communication Services Chat C#
...orials/includes/twilio-to-acs-chat-android-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific tools (Visual Studio) as a prerequisite, providing only PowerShell-based package installation instructions, and omitting Linux/macOS equivalents or alternatives. The Azure CLI example is cross-platform, but the initial setup and package installation steps assume a Windows environment, which may create friction for Linux/macOS users.
Recommendations
- Include instructions for installing the Azure Communication Services Chat SDK using dotnet CLI on Linux/macOS (e.g., bash/zsh).
- Mention cross-platform IDEs such as VS Code or JetBrains Rider as alternatives to Visual Studio.
- Clarify that Azure CLI is available on Linux/macOS and provide explicit instructions for those platforms.
- Add notes or sections highlighting any platform-specific considerations for Linux/macOS users during setup and development.
Communication Services
What's new in Azure Communication Services
...blob/main/articles/communication-services/whats-new.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation frequently references Windows and Windows SDKs, often listing Windows as a supported platform before Linux/macOS. Windows-specific terminology and features (such as Windows SDK, Teams integration, and platform lists) are mentioned throughout, while Linux/macOS equivalents are rarely referenced or omitted. Sample code and platform support statements often prioritize Windows, and there are no explicit Linux or macOS examples, tools, or troubleshooting guidance.
Recommendations
- Explicitly mention Linux and macOS support wherever platform lists are given, and provide parity in feature availability statements.
- Add Linux/macOS-specific examples and troubleshooting steps, especially for SDK usage and platform-dependent features.
- Include sample code and instructions for Linux/macOS environments (e.g., bash, shell, or platform-agnostic code) alongside Windows/Powershell examples.
- Reference cross-platform tools and patterns before or alongside Windows-specific ones.
- Clarify any platform limitations or differences for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash, and does not provide any Linux-specific instructions, examples, or troubleshooting notes. All commands and code are platform-neutral, but the setup and run instructions implicitly assume a Windows environment by listing Windows shells first and omitting Linux-specific context.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
- Explicitly mention that all commands work on Linux/macOS as well as Windows.
- Add notes or examples for common Linux/macOS workflows, such as using Terminal, setting environment variables, and installing .NET SDK on Linux.
- Include troubleshooting tips for Linux users, e.g., permissions, path issues, or package installation differences.
- Ensure parity in instructions for opening and editing files (e.g., suggest 'nano', 'vim', or 'gedit' for Linux users).
Communication Services
Additional Prerequisites
...ity/includes/active-directory/service-principal-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows VM configuration guides for enabling managed identities (portal, PowerShell, CLI, ARM template, SDK), with no mention of Linux VM equivalents. Additionally, there are no Linux-specific examples or instructions for setting environment variables, and Windows-centric development environments (e.g., Visual Studio) are referenced without Linux alternatives.
Recommendations
- Include links and examples for enabling managed identities on Linux VMs alongside Windows VM guides.
- Provide instructions and examples for setting environment variables in Linux shells (e.g., Bash, zsh), in addition to Windows methods.
- Reference cross-platform development environments (such as VS Code) and Linux-specific workflows where relevant.
- Ensure that CLI examples and environment setup steps are clearly applicable to both Windows and Linux, or explicitly note any platform-specific differences.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or examples. All setup and run commands are generic but lack explicit Linux parity (e.g., environment variable setup, editor usage, troubleshooting). No Linux tools or patterns are discussed.
Recommendations
- List Bash (Linux/macOS) first or equally when mentioning console windows.
- Provide explicit Linux/macOS instructions for setting environment variables (e.g., export in Bash).
- Include examples of opening and editing files using common Linux editors (e.g., nano, vim).
- Add troubleshooting notes for Linux/macOS users (e.g., permissions, .NET SDK installation differences).
- Ensure all commands and paths are cross-platform, or provide platform-specific notes where needed.
Communication Services
Set up and obtain access tokens for Microsoft Entra ID users
...ntity/microsoft-entra-id-authentication-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it does provide both REST API and Azure CLI methods for creating service principals, it references the Azure portal and Microsoft Entra admin center extensively, which are primarily accessed via web browsers and are platform-agnostic. However, there are no explicit Linux-specific examples, nor is there mention of Linux shell commands or patterns (e.g., bash, curl, etc.). The Azure CLI example is cross-platform, but the documentation does not clarify this, and there are no Linux terminal screenshots or instructions. There is no mention of Powershell, but the overall pattern is to present Windows-centric tools (Azure portal, admin center) first and exclusively.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Provide Linux shell (bash/curl) examples for REST API calls, e.g., using curl to create a service principal.
- Include screenshots or instructions for Linux terminal environments where relevant.
- Add a note or section highlighting cross-platform compatibility of SDKs and tools.
- Where possible, mention alternative Linux-native tools or workflows (e.g., using az CLI in bash scripts).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/analytics/logs/call-metrics-log-schema.md
...ces/concepts/analytics/logs/call-metrics-log-schema.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. In the sample data, 'DeviceOsName' is set to 'Windows' and 'DeviceBrowser' to 'Edge', with no examples for Linux or macOS. The platform and OS examples and sample logs focus exclusively on Windows, and there are no Linux-specific instructions, tools, or sample data. While the documentation is generally OS-agnostic in its explanations, the absence of Linux (or macOS) examples and the use of Windows as the default in sample data suggest a 'windows_first' and 'missing_linux_example' bias.
Recommendations
- Add sample log entries that use Linux and macOS as 'DeviceOsName' and browsers such as Chrome or Firefox to demonstrate cross-platform support.
- Where platform or OS is mentioned (e.g., in tables or examples), include Linux and macOS alongside Windows to reinforce parity.
- If there are any platform-specific considerations for collecting or analyzing logs (e.g., using Azure CLI on Linux), mention them explicitly.
- Ensure that any referenced tools or dashboards are confirmed to work on Linux and macOS, and note any differences if they exist.