Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1751-1775 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/vnet/troubleshooting.md
...lob/main//articles/cloud-shell/vnet/troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes troubleshooting steps using the Azure portal's graphical interface, which is most familiar to Windows users. There are no command-line examples (such as Azure CLI or PowerShell), and no mention of Linux-native tools or workflows. This approach assumes users will interact with Azure via the portal, which can disadvantage Linux users or those who prefer CLI-based management.
Recommendations
- Add equivalent Azure CLI commands for each troubleshooting step, so users can perform checks and changes from Linux, macOS, or Windows terminals.
- Include PowerShell examples if relevant, but always provide Azure CLI examples first or alongside them.
- Explicitly mention that all steps can be performed via the portal, CLI, or PowerShell, and provide links to relevant documentation for each method.
- Where screenshots are used, consider including CLI output examples as well.
- Ensure terminology and instructions do not assume a Windows environment or GUI usage.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/vnet/deployment.md
...ocs/blob/main//articles/cloud-shell/vnet/deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally presents both Azure CLI and Azure PowerShell options for resource creation, but PowerShell is consistently mentioned before CLI in lists and links. In the 'Alternate way to get the Azure Container Instance ID' section, the PowerShell example is given before the Azure CLI example. There are no Linux-specific tools or shell examples, and the ordering and prominence of PowerShell may suggest a Windows-first perspective.
Recommendations
- Alternate the order of Azure CLI and Azure PowerShell examples throughout the documentation, or present CLI examples first to better reflect cross-platform parity.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and clarify that users can use either on Windows, macOS, or Linux.
- Where possible, provide Bash shell examples (e.g., using Azure CLI in Bash) to reinforce Linux parity.
- Ensure that links to CLI and PowerShell documentation are presented with equal prominence and in a neutral order.
- Consider adding a short section or note highlighting that all steps can be performed from any OS, and that both Bash (with Azure CLI) and PowerShell are supported in Cloud Shell.
Azure Docs
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 demonstrates a mild Windows bias. In the sample data, 'DeviceOsName' is set to 'Windows' and 'DeviceBrowser' to 'Edge', with no examples for Linux or other operating systems. While the schema itself is cross-platform, the only concrete example provided is for Windows, and there are no Linux-specific instructions, examples, or references. No Windows-specific tools or PowerShell commands are mentioned, but the lack of Linux parity in examples and sample data is notable.
Recommendations
- Add sample data rows where 'DeviceOsName' is set to 'Linux' and 'DeviceBrowser' to a common Linux browser (e.g., 'Firefox' or 'Chrome').
- Explicitly mention that the schema and metrics apply equally to Linux, macOS, and other platforms.
- If there are any platform-specific considerations (such as log collection or diagnostic settings on Linux), provide guidance or links.
- Wherever sample data or screenshots are shown, ensure a mix of operating systems is represented.
- Consider including a section or FAQ entry addressing cross-platform usage and any differences in log content or collection.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/analytics/logs/sms-logs.md
...unication-services/concepts/analytics/logs/sms-logs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows evidence of Windows bias primarily through the use of Windows-specific values in example logs (e.g., 'PlatformType': 'Microsoft Windows 10.0.17763') and the absence of Linux or cross-platform examples. There are no Linux or macOS equivalents shown, and the only concrete platform reference is to Windows. No PowerShell or Windows command-line tools are mentioned, but the examples implicitly suggest Windows as the default environment.
Recommendations
- Include example logs that show Linux and/or macOS values for the 'PlatformType' field, such as 'Linux' or 'Darwin'.
- Explicitly state that the service and SDKs are cross-platform, and provide examples or notes for non-Windows environments.
- If relevant, add sample usage or troubleshooting steps for Linux and macOS users.
- Avoid using only Windows-specific values in documentation examples; rotate or randomize platform values to reflect real-world diversity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/email/email-headers.md
...communication-services/concepts/email/email-headers.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only a .NET (C#) example and instructs users to run the application using the dotnet CLI, which is cross-platform but most commonly associated with Windows development. There are no Linux- or Unix-specific instructions, nor are there examples in languages or tools more common on Linux (such as Python, curl, or bash). No mention is made of Linux-specific considerations or alternative workflows.
Recommendations
- Add equivalent code examples in languages popular on Linux, such as Python (using the Azure SDK for Python) or JavaScript (Node.js).
- Include instructions for running the example on Linux and macOS, clarifying that dotnet CLI is cross-platform.
- Provide a curl or HTTPie example to demonstrate sending custom headers via direct REST API calls, which is common in Linux environments.
- Explicitly state that the instructions and tools are cross-platform, and mention any OS-specific prerequisites if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/email/email-attachment-allowed-mime-types.md
.../concepts/email/email-attachment-allowed-mime-types.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists a significant number of Microsoft/Windows-specific file types and tools (e.g., .doc, .docx, .xls, .ppt, .pub, .one, .vsd, .wma, .wmv) and their corresponding MIME types, many of which are proprietary to Microsoft Office and Windows platforms. These formats are presented alongside more cross-platform types, but the volume and prominence of Windows-specific formats may suggest a Windows-first or Microsoft-centric perspective. However, there are no explicit examples, commands, or instructions that are Windows- or PowerShell-specific, nor are Linux tools or equivalents discussed or omitted in a way that would constitute 'missing_linux_example' or 'powershell_heavy' bias.
Recommendations
- Add explicit mention of cross-platform and Linux-friendly formats (e.g., .odt, .ods, .odp for OpenDocument formats) to the table to improve parity.
- Include a note or section highlighting that Azure Communication Services supports a wide range of open and cross-platform formats, not just Microsoft/Windows-centric ones.
- Where Microsoft-specific formats are listed, consider also listing their open-source or widely-used alternatives (e.g., .docx alongside .odt, .xlsx alongside .ods).
- If providing usage examples in future documentation, ensure to include both Windows and Linux command-line or scripting examples (e.g., PowerShell and Bash).
- Clarify that the service is platform-agnostic and that the choice of attachment formats should consider the recipient's platform and software.
Azure Docs
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 →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Teams policies using PowerShell modules (e.g., /powershell/module/skype/set-csteamsmeetingpolicy) without mentioning equivalent Linux or cross-platform management options. The focus on Windows-centric tools and terminology (such as Teams policies managed via PowerShell) suggests a Windows-first approach, with no mention of Linux or cross-platform alternatives for managing Teams policies or enabling captions.
Recommendations
- Include information on managing Teams policies using cross-platform tools or interfaces, such as the Microsoft Teams admin center (web-based) or REST APIs, if available.
- Explicitly state whether PowerShell modules referenced are available and supported on Linux/macOS (PowerShell Core), and provide installation/use instructions for those platforms if applicable.
- Where possible, provide examples or links for both Windows and Linux environments, especially for administrative tasks.
- Clarify any platform limitations or requirements for managing Teams interoperability features, so Linux users are aware of their options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/mqtt-client-microsoft-entra-token-and-rbac.md
...ent-grid/mqtt-client-microsoft-entra-token-and-rbac.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by exclusively referencing the Azure portal (a web UI) for role assignment and management, which is most commonly associated with Windows-centric workflows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash) for Linux users, nor are there references to Linux tooling or patterns. The absence of CLI-based instructions or explicit Linux parity may hinder users who prefer or require non-GUI, cross-platform, or automation-friendly approaches.
Recommendations
- Add Azure CLI examples for role assignment and management, which work cross-platform (Windows, Linux, macOS).
- Include Bash or shell script examples for token acquisition and MQTT connection, demonstrating Linux-friendly workflows.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide alternative instructions for users who prefer command-line or automated approaches.
- Where possible, provide PowerShell and CLI examples side by side, or default to CLI for maximum cross-platform compatibility.
- Reference Linux tools (such as curl, mosquitto_pub/sub) for MQTT interactions in addition to any Windows-centric tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/interop/virtual-visits/plan-user-experience.md
...oncepts/interop/virtual-visits/plan-user-experience.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Teams Admin Center and PowerShell as the primary methods for configuration discovery, without mentioning Linux-compatible alternatives or cross-platform tools. There are no Linux-specific instructions or examples, and the only administrative tooling mentioned (PowerShell) is traditionally Windows-centric.
Recommendations
- Include cross-platform alternatives to PowerShell, such as Azure CLI or documented REST API calls, for configuration tasks.
- Explicitly mention whether Teams Admin Center is accessible via web browser on all platforms, including Linux.
- Provide examples or references for performing administrative tasks on Linux systems.
- Clarify if any steps require Windows-only tools, and suggest workarounds or alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/template-samples.md
...ocs/blob/main//articles/event-grid/template-samples.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page lists 'PowerShell samples' before 'CLI samples' in the 'Next steps' section, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux or Bash examples highlighted, and PowerShell is traditionally associated with Windows environments.
Recommendations
- List CLI (az cli) or Bash samples before or alongside PowerShell samples to provide equal visibility for Linux users.
- Explicitly mention that CLI samples are cross-platform and suitable for Linux, macOS, and Windows.
- Add links or references to Bash or shell script examples if available.
- Consider a section or note highlighting cross-platform support for all provided samples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-csharp.md
...tomation/includes/audio-streaming-quickstart-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by linking to Windows-specific resources and using language and examples that assume a Windows environment. The only explicit platform reference in the prerequisites and supporting links is for Windows, and there are no Linux-specific instructions, examples, or parity in tooling guidance. All code samples are in C#, which is cross-platform, but the supporting documentation and context are Windows-centric.
Recommendations
- Provide Linux-specific setup instructions and links, especially for creating Azure Communication Services resources and setting up WebSocket servers.
- Ensure that all referenced documentation (such as WebSocket guides) includes or prioritizes Linux and cross-platform content, not just Windows.
- Add explicit notes or sections for Linux/macOS users, including any differences in .NET installation, environment setup, or troubleshooting.
- Where platform-specific tabs or pivots are used in links, ensure Linux and macOS are included and not just Windows.
- Consider including at least one example using a popular Linux WebSocket server implementation or command-line tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-autoregistration.md
...lob/main//articles/dns/private-dns-autoregistration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, which may suggest a preference for Windows-centric tooling. No explicit Linux examples or Linux-specific tools are mentioned, and the only command-line examples referenced are PowerShell and CLI, with PowerShell listed first.
Recommendations
- List Azure CLI before Azure PowerShell in 'Next steps' to reflect cross-platform parity, as Azure CLI is natively cross-platform.
- Explicitly mention that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS.
- Where possible, provide example commands for both Azure CLI and Azure PowerShell, or link to both sets of instructions equally.
- Consider including a brief note or section on using the feature from Linux environments, especially if there are any platform-specific considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/voice-video-calling/includes/user-facing-diagnostics-android.md
...eo-calling/includes/user-facing-diagnostics-android.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is generally platform-neutral, focusing on Android diagnostics. However, there is a notable Windows bias in the mitigation steps for 'noMicrophoneDevicesAvailable', which references enabling a microphone from the 'device manager'—a Windows-specific tool—without mentioning Linux or macOS equivalents. No Linux-specific tools or troubleshooting steps are provided, and there are no Linux command-line or GUI examples for device management.
Recommendations
- When referencing device management (e.g., enabling a microphone), include Linux and macOS equivalents. For Linux, mention checking audio devices with tools like 'alsamixer', 'pavucontrol', or using 'arecord -l' to list microphones.
- Avoid referencing Windows-specific tools (such as 'device manager') in isolation. If mentioned, always provide cross-platform alternatives or note the equivalent steps for other operating systems.
- Add troubleshooting steps or links for common Linux desktop environments (e.g., GNOME, KDE) regarding audio device management.
- Where possible, provide platform-agnostic language or explicitly state when a step is platform-specific, and direct users to relevant documentation for their OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/mute-participants-how-to-csharp.md
...automation/includes/mute-participants-how-to-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows a mild Windows bias. The prerequisite links and quickstart references default to 'windows' tabs or pivots, and there are no explicit Linux-specific instructions or examples. While the .NET SDK and dotnet CLI are cross-platform, the documentation does not demonstrate parity by showing Linux (or macOS) terminal commands, nor does it mention Linux-specific considerations.
Recommendations
- Provide explicit Linux (and macOS) instructions or examples alongside Windows, especially in prerequisite links and quickstart references.
- Avoid using '?tabs=windows' or similar Windows-default pivots in documentation links; instead, link to platform-neutral or multi-tab pages.
- Add notes or sections clarifying that the dotnet CLI and SDK are cross-platform, and show example commands in both Windows (cmd/PowerShell) and Linux (bash/zsh) terminal formats.
- Ensure that all referenced quickstarts and guides have Linux parity and are discoverable from this documentation page.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/recognize-ai-action-how-to-java.md
...automation/includes/recognize-ai-action-how-to-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking to quickstart and resource creation guides with Windows-specific tabs or pivots by default. There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux-specific considerations. All terminal commands and instructions are generic, but the prerequisite links and pivots prioritize Windows, and there is no guidance for Linux users.
Recommendations
- Update all prerequisite and quickstart links to use a neutral or cross-platform tab/pivot by default, or explicitly mention both Windows and Linux options.
- Where platform-specific instructions exist (such as for resource creation or SDK installation), provide Linux/macOS equivalents alongside Windows instructions.
- Add a note in the prerequisites section clarifying that the Java and Maven instructions apply to both Windows and Linux, and provide any necessary Linux-specific setup steps (e.g., package installation commands).
- Review all referenced guides (such as quickstarts) to ensure Linux parity and cross-link to Linux instructions where available.
- Consider including a table or section summarizing any platform-specific differences or requirements for Java development and Azure Communication Services usage.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-java.md
...automation/includes/audio-streaming-quickstart-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. In the prerequisites, the link to creating an Azure Communication Services resource uses a URL with '?tabs=windows&pivots=platform-azp', which prioritizes Windows instructions. There are no explicit Linux or cross-platform instructions or examples, and the only external WebSocket documentation linked is specific to Windows Azure Web Sites. No Linux-specific tools, patterns, or troubleshooting are mentioned, and there are no shell or Linux command-line examples.
Recommendations
- Update prerequisite links to either be platform-neutral or provide both Windows and Linux tabs equally.
- Include references to Linux-compatible guides for setting up WebSocket servers (e.g., using Jetty, Tomcat, or Netty on Linux).
- Add notes or examples for running the Java application and WebSocket server on Linux, including any OS-specific considerations.
- Where external documentation is referenced (such as WebSocket setup), provide links to both Windows and Linux resources.
- Ensure that any code or configuration steps are clearly marked as cross-platform, or provide platform-specific notes where differences exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/secure-webhook-endpoint-csharp.md
...-automation/includes/secure-webhook-endpoint-csharp.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides only C#/.NET (Microsoft stack) examples and references to NuGet packages, which are primarily associated with Windows development environments. There are no examples or guidance for implementing JWT validation in Linux-preferred languages or frameworks (e.g., Python, Node.js, Java), nor is there mention of cross-platform package managers or tools.
Recommendations
- Include equivalent JWT validation examples in popular Linux/open-source languages such as Python (using PyJWT), Node.js (using jsonwebtoken), and Java (using Nimbus JOSE + JWT).
- Mention cross-platform package managers (e.g., pip, npm, Maven) alongside NuGet.
- Clarify that the JWT validation process is not limited to .NET and provide links to relevant libraries for other platforms.
- Add a section or links to community resources for Linux users or those using non-Microsoft stacks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-csharp.md
...ll-automation/includes/play-audio-quickstart-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In the prerequisites, the link to creating an Azure Communication Services resource uses a Windows-specific tab and pivot by default. There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux-specific considerations. All examples are generic C#/.NET, which are cross-platform, but the documentation does not clarify or demonstrate usage on Linux or macOS, nor does it provide parity in setup or troubleshooting for non-Windows environments.
Recommendations
- Update prerequisite links to use a neutral or cross-platform default tab/pivot, or explicitly provide Linux/macOS instructions alongside Windows.
- Add a note clarifying that all .NET and C# commands/examples work on Linux and macOS, and provide any necessary Linux-specific setup steps (e.g., installing .NET SDK on Linux).
- Where relevant, include Linux/macOS terminal commands or screenshots, or reference platform-agnostic instructions.
- Ensure that any tooling or resource creation steps are described for all major platforms, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/recognize-ai-action-how-to-csharp.md
...tomation/includes/recognize-ai-action-how-to-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the prerequisites section, where links and instructions reference Windows first (e.g., resource creation quickstart with '?tabs=windows'), and there are no explicit Linux-specific instructions or examples. All code samples are platform-agnostic C#, but there is a lack of parity in setup or tooling guidance for Linux users.
Recommendations
- Provide explicit Linux (and macOS) instructions and links alongside or before Windows instructions, especially in the prerequisites and resource creation steps.
- Ensure that quickstart/resource creation links use platform-neutral or multi-platform tabs by default, or clearly indicate how to switch to Linux instructions.
- Include notes or examples for common Linux development environments (e.g., using dotnet CLI on Ubuntu, installing .NET on Linux, handling file paths).
- Audit all referenced documentation for similar bias and ensure Linux users are equally supported throughout the developer journey.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/real-time-transcription-tutorial.md
...os/call-automation/real-time-transcription-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias, particularly in the prerequisites and setup sections. References and links default to Windows (e.g., 'tabs=windows' in resource creation links), and the WebSocket server quickstart links to a Windows Azure Web Sites blog post. There are no explicit Linux or cross-platform examples or instructions, and no mention of Linux-specific tools or deployment patterns.
Recommendations
- Provide equivalent Linux (and macOS, if applicable) instructions and links alongside Windows ones in all setup and prerequisite steps.
- Replace or supplement Windows-specific quickstart links (such as the WebSocket server setup) with cross-platform or Linux-specific guides.
- Ensure that code samples, especially for server setup and SDK usage, are explicitly cross-platform or include Linux-specific notes where relevant.
- Avoid using 'tabs=windows' as the default in documentation links; instead, use a neutral or user-selectable default.
- Mention and link to Azure WebApps/Linux or other Linux-compatible hosting options when discussing deployment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/record-every-call.md
...-services/how-tos/call-automation/record-every-call.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by linking to Windows-specific Azure CLI installation instructions and not mentioning Linux or macOS alternatives. There are no explicit Linux/macOS setup or usage examples, and the only CLI installation link is for Windows. The rest of the instructions are generally cross-platform (e.g., Visual Studio Code, ngrok, Azure CLI commands), but the lack of Linux/macOS parity in prerequisites and setup is notable.
Recommendations
- Provide Azure CLI installation instructions or links for Linux and macOS alongside the Windows link.
- Explicitly state that the steps (e.g., using Visual Studio Code, ngrok, Azure CLI) are cross-platform, and mention any OS-specific considerations if applicable.
- Include example commands or screenshots from Linux/macOS terminals where relevant.
- Ensure all tool download links (e.g., ngrok) point to cross-platform resources or clarify platform support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md
...w-tos/call-automation/teams-interop-call-automation.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation shows a bias towards Windows by referencing Microsoft Teams PowerShell cmdlets (Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) for tenant and user policy configuration, without providing equivalent instructions or examples for Linux or cross-platform environments. No Linux-specific tools or command-line alternatives are mentioned for these administrative steps, and no guidance is given for performing these tasks outside of PowerShell.
Recommendations
- Provide equivalent instructions for configuring Teams federation and external access policies using cross-platform tools, such as the Microsoft Teams admin center web UI or Microsoft Graph API, which are accessible from any OS.
- Explicitly mention that the PowerShell cmdlets require Windows or provide guidance on how to use PowerShell Core on Linux/macOS if possible.
- Include step-by-step examples for Linux users, such as using Azure CLI, Microsoft Graph API via curl or HTTPie, or web-based admin portals, for all administrative tasks currently shown only with PowerShell.
- Add a note clarifying platform requirements for each administrative step, and ensure parity in instructions for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-ios.md
.../calling-sdk/includes/capabilities/capabilities-ios.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation refers specifically to 'Windows' in the introductory sentence for using the capabilities call feature, but all code examples are in Swift (suggesting iOS/macOS), and there are no Linux-specific instructions or examples. There is no mention of Linux support, nor are Linux equivalents or considerations discussed.
Recommendations
- Remove or clarify the reference to 'Windows' if the instructions are not Windows-specific, or provide equivalent instructions/examples for Linux.
- Explicitly mention platform support (Windows, Linux, macOS, iOS) for the feature and code samples.
- If the feature is not available on Linux, state this clearly; if it is, add Linux-specific usage notes or examples.
- Ensure that any platform-specific instructions are grouped or labeled accordingly, rather than defaulting to Windows terminology.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/event-grid/view-events-request-bin.md
...services/how-tos/event-grid/view-events-request-bin.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking only to the Windows-specific Azure CLI installation instructions in both the prerequisites and the configuration steps. There are no Linux or macOS installation links or examples, and the 'tabs' parameter in the Azure CLI link is set to 'azure-cli', which defaults to Windows. No Linux-specific tools, commands, or considerations are mentioned.
Recommendations
- Provide platform-agnostic or platform-specific Azure CLI installation instructions by linking to the main Azure CLI install page or including tabs for Windows, Linux, and macOS.
- Explicitly mention that the Azure CLI commands work cross-platform and, if there are any differences, provide Linux/macOS command examples or notes.
- Avoid using Windows-specific links or defaults unless absolutely necessary; ensure parity in documentation for all major platforms.
- If screenshots or UI instructions are platform-specific, include Linux/macOS equivalents or clarify when instructions are universal.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/chat-sdk/archive-chat-threads.md
...tion-services/how-tos/chat-sdk/archive-chat-threads.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by linking to a 'list chat messages' quickstart with a 'tabs=windows' parameter, suggesting Windows as the default or primary environment. There are no explicit Linux or cross-platform command-line examples, nor are alternative Linux tools or instructions mentioned. The absence of Linux-specific guidance or parity in examples may hinder non-Windows users.
Recommendations
- Ensure all quickstart and example links use neutral or cross-platform tabs (e.g., avoid '?tabs=windows' or provide both Windows and Linux tabs).
- Explicitly mention that the instructions are applicable to both Windows and Linux, or provide separate sections/examples for each platform where relevant.
- Where command-line or scripting is referenced, include both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Audit all referenced quickstarts and linked pages to ensure Linux users are equally supported and not directed to Windows-only instructions.