Communication Services

1044
Total Pages
900
Linux-Friendly Pages
144
Pages with Bias
13.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

656 issues found
Showing 451-475 of 656 flagged pages
Communication Services Enable Closed captions with Teams Interoperability ...on-services/concepts/interop/enable-closed-captions.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First ๐Ÿ”ง Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows as a primary supported platform ("client-side SDKs for Web, Windows, iOS and Android") and by linking to Teams policies managed via PowerShell modules (which are Windows-centric tools). There are no explicit Linux examples, nor is Linux mentioned as a supported platform for client SDKs or policy management. The documentation assumes familiarity with Windows tools and patterns, such as PowerShell for Teams policy configuration, without offering Linux alternatives or parity.
Recommendations
  • Explicitly mention Linux support for Azure Communication Services client SDKs if available, or clarify platform limitations.
  • Provide examples or guidance for managing Teams policies on Linux, such as using Microsoft Graph API or cross-platform CLI tools, instead of only referencing PowerShell modules.
  • Include Linux-specific usage notes or troubleshooting tips, especially in sections discussing platform support and known limitations.
  • Ensure that references to tools and configuration steps are cross-platform, or provide equivalent instructions for Linux users.
  • Add a table or section comparing platform support for closed captions, including Linux, to help developers understand parity.
GitHub Create Pull Request
Communication Services Azure logs and metrics for Teams external users ...ervices/concepts/interop/guest/monitor-logs-metrics.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Teams Admin Center and Teams Call Quality Dashboardโ€”both web-based or Windows-centric toolsโ€”without mentioning Linux-compatible alternatives or command-line approaches. There are no examples or instructions for accessing logs or metrics using Linux tools, nor is there any mention of cross-platform CLI utilities or REST API usage that would benefit Linux users.
Recommendations
  • Include instructions or examples for accessing Azure logs and metrics using cross-platform tools such as Azure CLI or REST APIs.
  • Mention whether Teams Admin Center and Call Quality Dashboard are accessible from Linux browsers, and provide alternatives if they are not.
  • Add examples of log retrieval and analysis using Linux shell commands (e.g., curl, jq) or Azure CLI.
  • Explicitly state platform requirements or compatibility for each tool mentioned.
  • Provide parity in documentation by listing both Windows and Linux approaches for monitoring and analyzing logs.
GitHub Create Pull Request
Communication Services include file ...entity/includes/entra-id/support-entra-id-users-net.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 examples or guidance. All instructions and code samples are platform-neutral, but the setup and run instructions implicitly assume familiarity with Windows environments and do not address Linux-specific nuances (such as environment variable setting or editor usage).
Recommendations
  • Explicitly mention Linux and macOS environments alongside Windows when referencing console windows, e.g., 'In a console window (such as cmd, PowerShell, Bash, or Terminal on macOS)...'
  • Provide Linux/macOS-specific instructions for setting environment variables (e.g., 'export ENTRA_CLIENT_ID=...' for Bash) and running the application.
  • Include notes about using text editors available on Linux/macOS (such as nano, vim, or VS Code) when editing Program.cs.
  • Ensure parity by listing Bash or Terminal before or alongside Windows shells when giving command-line instructions.
GitHub Create Pull Request
Communication Services include file ...ces/quickstarts/includes/telemetry-app-insights-net.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page mentions Windows-specific console environments (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or examples. All commands and patterns are platform-neutral (dotnet CLI), but there is a lack of explicit Linux parity in setup, environment variable configuration, and text editor usage.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console windows.
  • Provide explicit instructions for setting environment variables on Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...).
  • Suggest common Linux/macOS text editors (e.g., nano, vim, code) alongside generic 'text editor'.
  • Clarify that all dotnet CLI commands work cross-platform and mention any OS-specific caveats if relevant.
  • Add a short section or note confirming Linux/macOS support and any additional steps required for those platforms.
GitHub Create Pull Request
Communication Services Teams Phone extensibility provisioning .../interop/tpe/teams-phone-extensibility-provisioning.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing cmdlets and administrative patterns that are strongly associated with Windows environments (e.g., Teams Admin using a cmdlet, Microsoft 365 Admin, Resource Account management). There are no examples or instructions for Linux-based administration, nor are cross-platform tools or CLI alternatives mentioned. The documentation assumes the use of Windows-centric tools and workflows, omitting Linux or cross-platform equivalents.
Recommendations
  • Include CLI-based examples using cross-platform tools such as Azure CLI, Microsoft Graph API via curl, or PowerShell Core (pwsh) on Linux.
  • Explicitly mention whether provisioning and authorization steps can be performed from Linux or macOS environments, and provide instructions if so.
  • Add guidance for Linux administrators, including package requirements and environment setup for cross-platform SDKs.
  • Clarify which steps require Windows-only tools and suggest alternatives or workarounds for Linux users.
  • Ensure that all code snippets and administrative commands are provided for both Windows (PowerShell) and Linux (bash/CLI) where possible.
GitHub Create Pull Request
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 →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Missing Linux Example
Summary
The documentation references enabling Teams users for Enterprise Voice via PowerShell and links to a Teams deployment guide that is Windows-centric. There are no Linux equivalents or alternative instructions for Linux administrators, nor are Linux tools or patterns mentioned. The quickstart assumes a Windows-based Teams deployment and management workflow.
Recommendations
  • Provide instructions or links for enabling Teams users for Enterprise Voice using cross-platform tools (if available), or clarify if PowerShell Core on Linux/macOS is supported.
  • Mention whether Teams deployment and management tasks can be performed from non-Windows environments, and provide guidance for Linux administrators.
  • Add notes or examples for Linux users where administrative steps are required, especially for tasks typically done via PowerShell.
  • Ensure that prerequisite links and instructions are inclusive of Linux/macOS environments, or explicitly state platform requirements.
GitHub Create Pull Request
Communication Services Govern Teams meeting experience with Azure Communication Services ...ts/interop/virtual-visits/govern-meeting-experience.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Missing Linux Example
Summary
The documentation focuses exclusively on Microsoft 365, Teams, and Azure tools, which are primarily Windows-centric. There are no examples, instructions, or mentions of Linux-specific tools, patterns, or cross-platform considerations. All administrative actions and recommendations assume use of Microsoft-provided interfaces and services, which are most commonly accessed via Windows environments.
Recommendations
  • Include explicit notes on cross-platform compatibility for Teams and Azure Communication Services administration.
  • Provide examples or references for managing Teams policies and meetings from Linux environments, such as using Azure CLI, Microsoft Graph API, or web interfaces.
  • Clarify whether any features or administrative actions require Windows-only tools (e.g., PowerShell), and offer Linux alternatives where possible.
  • Add documentation links or sections for Linux users on how to perform equivalent tasks, especially for policy management and meeting configuration.
  • Mention any limitations or differences in experience when using Teams and Azure Communication Services from Linux.
GitHub Create Pull Request
Communication Services Include file ...ices/samples/includes/call-automation-ai-javascript.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tabs in prerequisite links and instructing users to open a PowerShell window to run the application, without mentioning Linux or macOS equivalents. There are no Linux-specific instructions or examples provided for running the sample, and the setup steps implicitly assume a Windows environment.
Recommendations
  • Provide explicit instructions for running the sample on Linux and macOS, such as using a terminal instead of PowerShell.
  • Avoid referencing Windows-specific tabs or links unless Linux/macOS alternatives are also provided.
  • Include cross-platform command examples and clarify that the sample can be run on any OS with Node.js installed.
  • Add notes or sections highlighting any OS-specific considerations, such as differences in environment variable configuration or terminal commands.
GitHub Create Pull Request
Communication Services include file ...arts/email/send-email-advanced/includes/prepend-net.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by mentioning Windows-specific consoles (cmd, PowerShell) before Bash, and lacks explicit Linux/macOS examples or instructions. All code and commands are generic .NET/C# and do not reference platform-specific differences, but the guidance and terminology assume a Windows environment as the default.
Recommendations
  • Explicitly mention Linux/macOS terminals (e.g., GNOME Terminal, Terminal.app) alongside Windows consoles.
  • Provide platform-specific instructions or notes for Linux/macOS users, such as installation commands for .NET SDK on those platforms.
  • Include example environment variable setting commands for Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...) in addition to Windows (set ...).
  • Clarify that the .NET SDK and Azure Communication Services Email client library are cross-platform and provide links to Linux/macOS installation guides.
  • Ensure parity in troubleshooting steps and references to platform-specific issues, if any.
GitHub Create Pull Request
Communication Services Messaging Connect overview ...mmunication-services/concepts/sms/messaging-connect.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a web UI most commonly used on Windows), and by providing only C# (.NET) and JavaScript SDK code examples for sending SMS via Messaging Connect. There are no Linux-specific instructions, CLI examples, or references to Linux-native tools (e.g., Bash, curl, Azure CLI). The SDK tutorial omits Python and Java, which are more commonly used in Linux environments, and does not mention or show how to use Messaging Connect from Linux shells or automation scripts.
Recommendations
  • Add examples using Azure CLI and Bash/curl for provisioning and sending SMS, demonstrating how Messaging Connect can be used from Linux environments.
  • Include Python and Java SDK examples as soon as they are available, and update the documentation to highlight cross-platform support.
  • Explicitly mention that all features are accessible from Linux, macOS, and Windows, and provide guidance for developers working outside the Azure portal (e.g., via REST API calls).
  • Add troubleshooting and setup notes for Linux users, such as authentication via service principals, environment variable configuration, and package installation.
  • Where screenshots or step-by-step instructions reference the Azure portal, clarify that the portal is web-based and accessible from any OS, and provide alternative instructions for headless or automated environments.
GitHub Create Pull Request
Communication Services Subscribe to events in Job Router ...cation-services/how-tos/router-sdk/subscribe-events.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias in the quick-start section for creating and running a C# application to receive Event Grid events. While it mentions 'cmd, PowerShell, or Bash' as possible console windows, all command-line examples are generic and do not show any Linux-specific shell commands or considerations. There are no explicit Linux or macOS instructions or troubleshooting tips, and the only deployment button provided is 'Deploy to Azure', which is platform-agnostic. The code and package installation steps use .NET CLI, which is cross-platform, but the lack of explicit Linux/macOS parity in examples or notes may leave Linux users uncertain.
Recommendations
  • Explicitly show Linux/macOS terminal commands and verify that all steps work as expected on those platforms.
  • Add a note or section confirming that the .NET CLI commands and code samples are fully supported on Linux/macOS, and provide troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variables).
  • Where 'cmd, PowerShell, or Bash' is mentioned, consider listing 'Bash' first or providing a separate example for Bash to reinforce cross-platform support.
  • If any platform-specific steps exist (such as setting environment variables or file paths), provide both Windows and Linux/macOS syntax.
GitHub Create Pull Request
Communication Services Quickstart - Manage a room call ...cation-services/quickstarts/rooms/manage-rooms-call.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its linking practices. References to enabling PSTN dial-out and other features point to quickstart guides with Windows-specific tabs or pivots (e.g., '?tabs=windows'), and there is no mention of Linux-specific instructions, tools, or examples. The page does not provide any OS-specific command-line examples (such as PowerShell or Bash), but the navigation and guidance implicitly prioritize Windows by default. There is no explicit parity for Linux users in terms of setup, troubleshooting, or environment-specific notes.
Recommendations
  • Ensure all linked quickstart and how-to guides offer Linux-specific tabs, pivots, or instructions alongside Windows equivalents.
  • Explicitly mention Linux compatibility and provide setup or usage notes for Linux environments where relevant.
  • If any OS-specific steps exist (e.g., environment variables, file paths, CLI usage), provide both Windows and Linux examples.
  • Review all links and references to ensure they do not default to Windows tabs or pivots, but instead offer a neutral or multi-platform starting point.
  • Add troubleshooting or FAQ sections addressing common Linux issues if applicable.
GitHub Create Pull Request
Communication Services include file ...s/quickstarts/router/includes/router-quickstart-net.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when describing where to run commands. All code examples use .NET and C#, which are cross-platform, but there are no explicit Linux-specific instructions, troubleshooting, or examples. There is no mention of Linux package managers, shell differences, or platform-specific considerations for running .NET on Linux. The documentation assumes parity but does not actively demonstrate it.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console environments.
  • Add explicit instructions or troubleshooting notes for running .NET applications on Linux (e.g., permissions, dependencies, environment setup).
  • Mention Linux package managers (such as apt, yum, or snap) for installing .NET, or link to Linux-specific .NET installation guides.
  • Include a note confirming that all steps and code samples work equally on Linux and macOS, and highlight any platform-specific caveats if present.
  • Provide example output or screenshots from a Linux terminal to reinforce cross-platform support.
GitHub Create Pull Request
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 →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a subtle Windows bias in the prerequisites section, where enabling Teams Phone features for users is referenced via a link to a PowerShell-based guide. The instructions for Teams deployment also link to a Microsoft page that is primarily Windows-centric. No Linux-specific instructions, examples, or alternative tooling are provided for these steps, nor is there mention of Linux compatibility for Teams administration. The rest of the tutorial (JavaScript code and web app setup) is cross-platform, but the administrative setup assumes a Windows/PowerShell environment.
Recommendations
  • Provide Linux-compatible instructions for enabling Teams Phone and Enterprise Voice, such as using Microsoft 365 admin center web UI or any available cross-platform CLI tools.
  • Explicitly mention whether the administrative steps (e.g., enabling Enterprise Voice) can be performed from non-Windows platforms, and link to relevant documentation if available.
  • Add a note clarifying that the web app and SDK usage is cross-platform, and highlight any platform-specific limitations or requirements.
  • If PowerShell is required, suggest alternatives or workarounds for Linux/Mac users, such as using PowerShell Core on Linux or web-based admin portals.
GitHub Create Pull Request
Communication Services Contact centers with Azure Communication Services ...les/communication-services/tutorials/contact-center.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in its example links and references. Quickstart and getting started guides are linked with 'tabs=windows' and 'tabs=uwp', which are Windows-specific. There is no mention of Linux equivalents, nor are there examples or pivots for Linux platforms. The documentation does not provide parity for Linux users in terms of guidance, tooling, or example code.
Recommendations
  • Add explicit Linux examples and pivots in quickstart and getting started links, such as 'tabs=linux' or instructions for Linux environments.
  • Ensure all code samples and SDK usage instructions include Linux-compatible steps and highlight cross-platform support.
  • Mention Linux tools and patterns where relevant, such as bash scripts or Linux-native deployment options.
  • Review all referenced quickstarts and tutorials to ensure Linux users are not excluded and have clear, first-class guidance.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/teams-user-calling.md ...cation-services/concepts/interop/teams-user-calling.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page presents feature parity across JavaScript, Windows, Android, and iOS, but does not mention Linux as a supported platform or provide any Linux-specific guidance or examples. Windows is listed as a primary desktop platform, while Linux is omitted entirely, which may lead Linux developers to feel unsupported or unclear about SDK compatibility.
Recommendations
  • Explicitly state whether Linux is supported or not for the Calling SDK. If not supported, clarify this early in the documentation.
  • If Linux is supported (even partially or via JavaScript in browsers), add a dedicated Linux column to the feature matrix, or provide notes about Linux compatibility.
  • Include Linux-specific setup, troubleshooting, or usage examples where relevant, such as installation instructions, environment requirements, or known limitations.
  • If certain features are unavailable or limited on Linux, document these gaps explicitly to set clear expectations for Linux developers.
  • Where platform-specific APIs or tools are referenced (e.g., Microsoft Entra, PowerShell, Windows APIs), provide Linux alternatives or clarify cross-platform approaches.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/manage-teams-identity-net.md ...ices/quickstarts/includes/manage-teams-identity-net.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references Windows-specific consoles (cmd, PowerShell) before Bash, and does not provide any Linux-specific instructions or examples. All commands and environment variable usage are generic, but there is no mention of Linux-specific considerations (e.g., environment variable setting, file editing, or running the app on Linux).
Recommendations
  • Explicitly mention Linux and macOS consoles (e.g., Terminal, zsh) alongside Windows options.
  • Provide Linux/macOS-specific instructions for setting environment variables (e.g., export AAD_CLIENT_ID=...) and running dotnet commands.
  • Include notes about editing files with Linux editors (e.g., nano, vim) as alternatives to generic 'text editor'.
  • Clarify that the .NET SDK and all commands work cross-platform, and link to platform-specific installation guides if available.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/enable-closed-captions.md ...on-services/concepts/interop/enable-closed-captions.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First ๐Ÿ”ง Windows Tools
Summary
The documentation page exhibits mild Windows bias by referencing Windows as a supported platform before Linux and by mentioning Teams policies with direct links to PowerShell modules (which are primarily Windows tools) without Linux equivalents or alternatives. There are no explicit Linux examples, nor is Linux mentioned as a supported platform for client-side SDKs, even though web SDKs are typically cross-platform.
Recommendations
  • Explicitly mention Linux as a supported platform for the Web SDK, clarifying cross-platform compatibility.
  • Provide examples or guidance for Linux users, such as how to interact with Teams policies using cross-platform tools (e.g., Microsoft Graph API) instead of only PowerShell.
  • Include references to Linux environments where applicable, especially in sections discussing SDK usage or policy configuration.
  • Balance references to Windows tools (like PowerShell) with Linux-friendly alternatives or note their limitations on non-Windows platforms.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-provisioning.md .../interop/tpe/teams-phone-extensibility-provisioning.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Teams administration tasks (such as using cmdlets) without specifying cross-platform alternatives or providing Linux/macOS examples. The use of 'cmdlet' and references to Teams Admin tools implicitly suggest PowerShell/Windows environments. No Linux or cross-platform CLI tools or procedures are mentioned, nor are there examples for non-Windows platforms.
Recommendations
  • Explicitly mention whether provisioning and authorization steps can be performed on Linux/macOS, and provide equivalent instructions or examples using cross-platform tools (e.g., Azure CLI, Microsoft Graph API via REST, or PowerShell Core on Linux).
  • Where 'cmdlet' is referenced, clarify if PowerShell Core is supported on non-Windows platforms, or provide alternative commands for Bash/CLI environments.
  • Add Linux/macOS-specific examples or notes to ensure parity and inclusivity for administrators using those platforms.
  • Reference cross-platform documentation or tools (such as Azure CLI or REST API) alongside or before Windows/PowerShell-specific instructions.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/govern-meeting-experience.md ...ts/interop/virtual-visits/govern-meeting-experience.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
๐Ÿ”ง Windows Tools Missing Linux Example
Summary
The documentation exclusively references Microsoft 365, Teams, Azure Communication Services, and related tools (Microsoft Purview, Azure Monitor Logs) without mentioning any cross-platform or Linux-specific equivalents. There are no examples or guidance for Linux administrators or users, nor any mention of Linux-compatible tools or command-line options. The focus is entirely on Microsoft ecosystem tools, which are most commonly used and managed in Windows environments.
Recommendations
  • Include examples or notes on how Linux administrators can manage Teams policies, meeting options, and sensitivity labels, such as through web interfaces or REST APIs.
  • Reference cross-platform management tools (e.g., Microsoft Graph API) and provide sample commands or scripts for Linux environments.
  • Clarify whether all described features and controls are accessible from non-Windows platforms and, if not, provide guidance or workarounds.
  • Add explicit mention of platform compatibility for each tool or feature, highlighting any Linux support or limitations.
  • Provide links to documentation on using Teams and Azure Communication Services from Linux systems, including CLI and browser-based management.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/sms/messaging-connect.md ...mmunication-services/concepts/sms/messaging-connect.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page for Messaging Connect does not provide any platform-specific examples, but all screenshots and step-by-step instructions focus exclusively on the Azure portal UI, which is most commonly accessed from Windows environments. The SDK code examples are only given for C# (.NET) and JavaScript, with no mention of Linux CLI tools, Bash, or PowerShell. There are no Linux-specific instructions, nor are there references to Linux-native tools or workflows. The documentation implicitly assumes a Windows-first experience by omitting Linux parity in examples and setup instructions.
Recommendations
  • Add Linux-specific examples, such as using Azure CLI (az) commands for provisioning and sending SMS, and include Bash or shell script samples.
  • Provide instructions for accessing and managing Messaging Connect resources from Linux environments, including screenshots of the Azure portal in browsers on Linux.
  • Include Python SDK examples when available, and mention their compatibility with Linux.
  • Reference cross-platform tools (e.g., VS Code, Azure CLI) and clarify that Messaging Connect can be managed from any OS.
  • Explicitly state platform independence in the introduction and developer experience sections.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/send-email-with-inline-attachments.md ...d-email-advanced/send-email-with-inline-attachments.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides dedicated pivots for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, which is cross-platform. There are no explicit Linux shell (bash) or platform-specific examples, and PowerShell is listed as a primary option, which may suggest a Windows-first approach. The absence of explicit Linux shell examples or references to Linux-specific tools may make the documentation less approachable for Linux users.
Recommendations
  • Add explicit bash or Linux shell examples alongside PowerShell, especially for command-line usage.
  • Clarify that Azure CLI is cross-platform and provide examples of its usage on Linux and macOS.
  • If PowerShell is included, mention PowerShell Core compatibility on Linux/macOS, or provide bash equivalents.
  • Ensure troubleshooting and resource cleanup sections reference cross-platform tools and workflows, not just Windows-centric ones.
  • Consider adding a 'platform requirements' section to clarify tool availability and usage on different operating systems.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/prepend-net.md ...arts/email/send-email-advanced/includes/prepend-net.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific console environments (cmd, PowerShell) before mentioning Bash, and by omitting Linux/macOS-specific instructions or examples. All terminal commands are presented generically, but there are no explicit Linux or macOS setup steps, nor are there troubleshooting notes for non-Windows platforms. The Azure portal instructions also assume a GUI workflow, which is more common on Windows.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms in the prerequisites and setup steps.
  • Provide Linux/macOS-specific instructions or troubleshooting notes, especially for environment variable setup and .NET installation.
  • When listing console environments, use inclusive language such as 'cmd, PowerShell, Bash, Terminal (Linux/macOS)'.
  • Add examples or notes for using the Azure CLI for resource management, which is cross-platform.
  • Include links to platform-specific .NET installation guides for Linux and macOS.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-net.md ...ity/includes/active-directory/service-principal-net.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a slight Windows bias by listing Windows terminals (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. The examples and instructions are platform-neutral (using dotnet CLI), but the initial mention of Windows tools may suggest a preference for Windows environments. No explicit Linux examples, troubleshooting, or platform-specific notes are provided.
Recommendations
  • List Bash (or Linux/macOS terminal) before Windows terminals when mentioning terminal options, or mention all platforms equally.
  • Add explicit notes or examples for running the quickstart on Linux/macOS, such as verifying .NET installation and using Bash.
  • Include troubleshooting steps or platform-specific caveats for Linux/macOS users if applicable.
  • Clarify that the instructions and code are cross-platform and provide links to .NET installation guides for Linux/macOS.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-cli.md ...ity/includes/active-directory/service-principal-cli.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-based resources and examples when describing how to enable managed identities for Azure resources. All linked articles for configuration (portal, PowerShell, CLI, ARM template, SDKs) explicitly target Windows VMs, with no mention of Linux VM equivalents or guidance. Additionally, there are no Linux-specific instructions or examples for setting environment variables, and the guidance assumes Windows-centric development environments (e.g., Visual Studio).
Recommendations
  • Include links and examples for enabling managed identities on Linux VMs, alongside the Windows VM instructions.
  • Provide Linux-specific guidance for setting environment variables (e.g., using export in bash/zsh, .bashrc/.profile), and mention common Linux development environments.
  • Ensure parity in documentation by presenting both Windows and Linux options for all setup and authentication steps.
  • Add notes or sections clarifying differences (if any) between Windows and Linux workflows for Azure CLI and SDK usage.
GitHub Create Pull Request
← Previous Page 19 of 27 Next →