Remote Rendering

81
Total Pages
48
Linux-Friendly Pages
33
Pages with Bias
40.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

51 issues found
Showing 1-25 of 51 flagged pages
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/resources/troubleshoot.md ...in/articles/remote-rendering/resources/troubleshoot.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, particularly in troubleshooting steps that assume a Windows environment. Several instructions reference Windows-specific tools (PowerShell, Windows Explorer, registry commands), and there are no equivalent examples or guidance for Linux or macOS users. File system limitations and codec installation steps are described only for Windows, and the use of Windows terminology and screenshots is pervasive. No Linux or cross-platform alternatives are provided for key troubleshooting scenarios.
Recommendations
  • Provide equivalent troubleshooting steps for Linux and macOS where applicable, especially for tasks like codec installation, file permissions, and file system limitations.
  • Include command-line examples for Linux (bash) alongside PowerShell/cmd examples.
  • When referencing file system limitations, clarify which are Windows-specific and note any differences for Linux/macOS.
  • Avoid assuming the use of Windows Explorer; suggest cross-platform alternatives (e.g., file managers, terminal commands).
  • For package installation and driver updates, provide links or instructions for Linux/macOS where possible.
  • Explicitly state when a step or limitation is Windows-only, and offer guidance or workarounds for other platforms.
  • Add screenshots or terminal output from Linux/macOS environments where relevant.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/conversion/layout-files-for-conversion.md ...ring/how-tos/conversion/layout-files-for-conversion.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific path length limits, using a Windows-style filesystem example (drive letters, backslashes), and omitting any Linux or cross-platform filesystem examples or considerations. There are no Linux or POSIX path examples, and no mention of Linux path length limits or filesystem conventions.
Recommendations
  • Include Linux/POSIX filesystem examples alongside Windows examples, using forward slashes and typical Linux directory structures.
  • Mention Linux path length limits and any relevant differences in file naming or path conventions.
  • Avoid using only Windows drive letters (e.g., G:\) in examples; provide parallel Linux examples (e.g., /mnt/conversion/...).
  • Clarify that the service is cross-platform (if applicable), and note any platform-specific considerations for both Windows and Linux users.
  • Where referencing documentation (such as path length limits), provide links or notes for both Windows and Linux.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/conversion/blob-storage.md ...es/remote-rendering/how-tos/conversion/blob-storage.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell scripts and examples, referencing Windows-specific issues (such as the Windows path length limit), and highlighting tools and workflows (like PowerShell and Azure Storage Explorer) that are more familiar to Windows users. There are no explicit Linux shell (bash) or cross-platform CLI examples, and Linux-specific considerations are absent.
Recommendations
  • Add explicit bash/Azure CLI examples for all steps where PowerShell is referenced, including SAS generation and file upload.
  • Provide sample scripts or command lines for Linux/macOS users, not just PowerShell scripts.
  • Mention Linux/macOS file system considerations where Windows-specific issues (like path length limits) are discussed.
  • Ensure that references to tools like Azure Storage Explorer are accompanied by notes on their cross-platform availability, or suggest alternative CLI methods.
  • Where PowerShell scripts are linked, provide equivalent bash or Python scripts for parity.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/tutorials/native-cpp/hololens/integrate-remote-rendering-into-holographic-app.md ...ens/integrate-remote-rendering-into-holographic-app.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows development, specifically targeting Visual Studio, Windows SDK, and UWP. All instructions, tools, and code samples are tailored exclusively for Windows, with no mention of Linux or cross-platform alternatives. There are no Linux equivalents or guidance for non-Windows environments.
Recommendations
  • Add a section or parallel tutorial for Linux users, outlining how to set up a similar development environment using cross-platform tools (e.g., CMake, GCC/Clang, VS Code).
  • Provide code samples and project setup instructions for Linux, including how to link dependencies and manage project files outside of Visual Studio.
  • Mention and, where possible, support cross-platform graphics APIs or abstractions (e.g., OpenGL, Vulkan) alongside DirectX11.
  • Reference cross-platform package managers (e.g., vcpkg, Conan) for dependency management instead of only NuGet.
  • Clarify early in the documentation that the tutorial is Windows-specific, and provide links or guidance for users on other platforms.
  • If Remote Rendering is not supported on Linux, explicitly state this and provide any available workarounds or roadmap information.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/concepts/graphics-bindings.md ...rticles/remote-rendering/concepts/graphics-bindings.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented towards Windows and Microsoft-specific technologies. All code samples and API references assume the use of Direct3D 11 (D3D11), Windows Mixed Reality, and HoloLens 2, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for using OpenGL, Vulkan, or Linux-based systems, nor any mention of how to set up or use Azure Remote Rendering on non-Windows platforms. The documentation also assumes the use of Windows-specific APIs and tools (e.g., NuGet, ID3D11Device, ISpatialCoordinateSystem), and does not provide parity for Linux users.
Recommendations
  • Add explicit information about platform support, including whether Linux is supported and, if not, state this clearly.
  • If Linux or cross-platform support is available, provide equivalent examples using OpenGL, Vulkan, or other non-Windows graphics APIs.
  • Include setup and usage instructions for Linux environments, including any required dependencies or differences in workflow.
  • Mention Linux tools or package managers (e.g., apt, yum) where NuGet is referenced for Windows.
  • If only Windows is supported, clarify this at the beginning of the documentation to set user expectations.
  • Consider providing a roadmap or guidance for users interested in non-Windows support, or link to relevant community resources.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/authentication.md ...in/articles/remote-rendering/how-tos/authentication.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell scripts as the only code sample in the 'Next steps' section and not providing equivalent Linux/bash examples. There are no explicit Linux or cross-platform command-line examples, and the only script-based guidance is Windows-centric. Additionally, there is no mention of Linux tools or instructions for non-Windows environments.
Recommendations
  • Add equivalent bash or shell script examples alongside PowerShell scripts in the 'Next steps' and sample sections.
  • Explicitly mention that authentication steps and REST calls can be performed from any OS, and provide curl or wget examples for token retrieval.
  • Include references to cross-platform tools (e.g., Azure CLI, curl) and ensure that instructions are not limited to Windows environments.
  • Where PowerShell is referenced, add a note or link to Linux/macOS alternatives to ensure parity.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/render-model.md .../articles/remote-rendering/quickstarts/render-model.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows development environments. All prerequisites and instructions assume Windows, including the use of the Windows SDK, Visual Studio (Windows-only), and Windows-specific tools for Mixed Reality. The command-line instructions reference Windows command prompt and PowerShell scripts, with no mention of Linux or macOS equivalents. There are no examples or guidance for users on Linux or macOS platforms.
Recommendations
  • Provide a section or callout for Linux/macOS users, clarifying platform support for Azure Remote Rendering with Unity.
  • If supported, include Linux/macOS equivalents for all command-line instructions (e.g., bash/zsh commands instead of cmd/PowerShell).
  • List cross-platform tools where possible (e.g., VS Code instead of Visual Studio, or mention Rider/MonoDevelop for Unity development).
  • Clarify whether the Windows SDK and Mixed Reality tools are strictly required, or if alternatives exist for other platforms.
  • Explicitly state platform limitations early in the prerequisites if only Windows is supported, to set user expectations.
  • If PowerShell scripts are required, provide alternative scripts or manual steps for non-Windows users.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/unity/holographic-remoting.md ...remote-rendering/how-tos/unity/holographic-remoting.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively references Windows-specific tools and scenarios, such as HoloLens 2 and Windows Mixed Reality (WMR) VR headsets, without mentioning Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or equivalent tooling discussed, and Windows tools are presented as the default or only option.
Recommendations
  • Add information about whether Holographic Remoting and Azure Remote Rendering are supported on Linux, and if not, clarify this explicitly.
  • If Linux or cross-platform workflows exist (e.g., Unity Editor on Linux), provide equivalent instructions or note any limitations.
  • Mention alternative VR headsets or remoting solutions that are compatible with Linux, if available.
  • Rephrase sections to avoid assuming the user is on Windows, or clearly state platform requirements at the beginning.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/session-rest-api.md .../articles/remote-rendering/how-tos/session-rest-api.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell scripts for interacting with the REST API, mentioning only Windows-centric tools and scripting languages (PowerShell, .NET), and omitting equivalent Linux or cross-platform examples (such as Bash, curl, or Python). There is no mention of Linux command-line tools or scripts, nor are there links to Linux-specific guidance or parity in SDK coverage.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, demonstrating how to interact with the REST API using curl or httpie.
  • Include references to cross-platform tools and scripting languages, such as Python, with sample scripts.
  • Mention Linux and macOS compatibility explicitly where relevant, and ensure that SDKs and tools are described in a platform-neutral manner.
  • Add links to Linux-specific documentation or samples, or clarify if the provided PowerShell scripts are compatible with PowerShell Core on Linux/macOS.
  • Reorder examples and tool mentions to avoid always listing Windows-first (e.g., mention both PowerShell and Bash, or .NET and Java, in parallel).
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/overview/system-requirements.md ...icles/remote-rendering/overview/system-requirements.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric, listing only Windows as a supported desktop platform, referencing only Windows tools (Visual Studio, Windows SDK, Microsoft Store, HEVC Video Extensions), and providing no mention of Linux or macOS support or alternatives. All instructions, requirements, and troubleshooting steps assume a Windows environment, with no Linux equivalents or cross-platform guidance.
Recommendations
  • Clearly state whether Linux and macOS are unsupported, or provide information on their support status.
  • If Linux/macOS are supported or planned, add equivalent instructions for installing dependencies (e.g., Unity, Git, codecs) on those platforms.
  • Mention cross-platform alternatives to Windows-only tools (e.g., Visual Studio Code instead of Visual Studio, open-source codecs instead of Microsoft Store HEVC extensions).
  • Provide troubleshooting steps and requirements for Linux/macOS if applicable.
  • If only Windows is supported, add a prominent note at the top of the page clarifying this to set user expectations.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/tutorials/unity/commercial-ready/commercial-ready.md ...g/tutorials/unity/commercial-ready/commercial-ready.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a Windows bias, particularly in the Diagnostics section, where only Windows-specific tools such as Event Tracing for Windows (ETW), Event Trace Logging (ETL), and the Windows Device Portal are mentioned for tracing and diagnostics. There are no equivalent Linux or cross-platform diagnostic tools referenced, nor are Linux-specific instructions or examples provided. Additionally, OneDrive integration is highlighted, which is more closely associated with Windows environments, and there is a general absence of Linux or cross-platform perspectives throughout the document.
Recommendations
  • Include Linux and cross-platform equivalents for diagnostics, such as referencing syslog, strace, perf, or open-source tracing tools (e.g., LTTng, SystemTap) for Linux users.
  • When mentioning Windows tools (e.g., ETW, Windows Device Portal), also provide guidance or links for achieving similar diagnostics on Linux and macOS.
  • Add examples or references for Linux-based workflows, such as using Azure CLI or PowerShell Core on Linux for session management, analytics, and troubleshooting.
  • Avoid assuming OneDrive is the default or only file storage option; mention alternatives like Dropbox, Google Drive, or generic SFTP/SMB/NFS solutions that are platform-agnostic.
  • Where possible, use neutral language and ordering (e.g., 'Windows, Linux, and macOS' instead of 'Windows and others') to avoid the impression of Windows-first thinking.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/native-cpp/hololens/deploy-native-cpp-tutorial.md ...arts/native-cpp/hololens/deploy-native-cpp-tutorial.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows tools (Visual Studio, Windows SDK, UWP), and provides only Windows command-line and PowerShell references. There are no Linux or cross-platform alternatives mentioned for building, deploying, or managing sessions. All instructions and prerequisites assume a Windows development environment.
Recommendations
  • Add a section or note clarifying whether Linux or macOS development is supported or not. If not, state this explicitly.
  • If cross-platform development is possible, provide equivalent instructions for Linux (e.g., using CMake, VS Code, or other IDEs) and mention any required dependencies.
  • Include Linux/macOS command-line examples for cloning the repository and managing files (e.g., bash equivalents for mkdir/cd/git).
  • If session management can be done via REST API or cross-platform scripts, provide examples using curl or Python instead of only referencing PowerShell scripts.
  • Mention any platform limitations or alternatives for developers not using Windows, and provide guidance or links to relevant resources.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/resources/tools/arr-inspector.md ...cles/remote-rendering/resources/tools/arr-inspector.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (Windows Device Portal), using Windows-style file paths (User Folders\LocalAppData\...), and omitting any mention of Linux or macOS equivalents for accessing files or running the ArrInspector. There are no instructions for users running the application on Linux or macOS, nor are there alternative file path formats or tools mentioned.
Recommendations
  • Include instructions for accessing the StartArrInspector.html file on Linux and macOS, specifying typical file locations and methods for retrieval.
  • Provide cross-platform file path examples (using forward slashes and environment variables where appropriate).
  • Mention and link to any Linux/macOS equivalents to the Windows Device Portal, or clarify if such functionality is unavailable.
  • Explicitly state platform limitations if the tool is only supported on Windows, or otherwise ensure parity in documentation for all supported platforms.
  • Add a section or note addressing how non-Windows users can launch and use ArrInspector, or clarify if only Windows is supported.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/unity/install-remote-rendering-unity-package.md ...ow-tos/unity/install-remote-rendering-unity-package.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools (Mixed Reality Feature Tool), providing only PowerShell scripts for automation, and omitting Linux/macOS equivalents or instructions. All example commands and scripts are either Windows-native or assume a Windows environment, with no mention of cross-platform alternatives or guidance for non-Windows users.
Recommendations
  • Provide explicit instructions for Linux and macOS users, including equivalent shell commands (e.g., bash) for downloading packages.
  • If the Mixed Reality Feature Tool is Windows-only, clarify this and suggest manual installation steps for other platforms.
  • Offer cross-platform scripts or note how to adapt the PowerShell script for other environments (e.g., bash or Python).
  • List both Windows and Linux/macOS approaches side-by-side where possible, or at least acknowledge platform differences.
  • Avoid assuming PowerShell is available; provide npm-based workflows as the primary or parallel method, since npm is cross-platform.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/performance-tracing.md ...ticles/remote-rendering/how-tos/performance-tracing.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily oriented towards Windows, introducing Windows tools (ETW, WPR, WPA) first and in detail, with step-by-step instructions and screenshots. Linux and Android equivalents (Perfetto) are only briefly mentioned, with no Linux desktop examples or instructions. The only non-Windows command-line example uses PowerShell, and there is no mention of Linux profiling tools or workflows for non-Quest Linux clients. The documentation assumes Windows as the default environment for profiling and analysis.
Recommendations
  • Provide equivalent Linux desktop profiling instructions, e.g., using Perfetto or other Linux tracing tools, for users running ARR clients on Linux.
  • Include Linux shell (bash) command-line examples for recording and analyzing traces, not just PowerShell.
  • Present Windows and Linux/Android tools in parallel, rather than introducing Windows tools first and in more detail.
  • Add screenshots and step-by-step guides for Linux workflows, similar to the Windows sections.
  • Clarify which tools and workflows are available or recommended for each supported client OS (Windows, Linux, Android, etc.).
  • If Linux is not supported for client-side tracing, explicitly state this and provide alternatives or workarounds.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/overview/features/late-stage-reprojection.md ...rendering/overview/features/late-stage-reprojection.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows Mixed Reality (WMR), Windows-specific APIs, and Direct3D (D3D11) graphics bindings. All examples and configuration steps reference Windows tools and patterns, with no mention of Linux or cross-platform equivalents. There are no Linux-specific instructions, examples, or references to Linux-compatible graphics APIs (such as Vulkan or OpenGL), and the documentation assumes a Windows development environment.
Recommendations
  • Add equivalent instructions and examples for Linux platforms, including how to configure LSR modes in Unity and native applications using Linux-supported graphics APIs (e.g., Vulkan, OpenGL).
  • Reference cross-platform or Linux-compatible XR runtimes and SDKs, such as Monado or SteamVR, where applicable.
  • Provide code samples and configuration steps that work on Linux, or explicitly state platform limitations if certain features are Windows-only.
  • Avoid using Windows-specific terminology (e.g., WMR, D3D11) as the default; instead, present cross-platform options first or in parallel.
  • Include a section outlining platform support and any differences in feature availability or setup between Windows and Linux.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/convert-model.md ...articles/remote-rendering/quickstarts/convert-model.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. The only provided script-based workflow uses PowerShell, with no mention of Linux or cross-platform alternatives. All scripting instructions, configuration paths, and prerequisite tooling are Windows-centric (e.g., backslash paths, PowerShell, Azure PowerShell module). There are no Bash, CLI, or Linux-native instructions or examples. The documentation assumes the user is on Windows, both in terminology and in the tools referenced.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for Linux/macOS users, alongside PowerShell examples.
  • Use platform-agnostic path examples or show both Windows and Unix-style paths in configuration samples.
  • Explicitly mention cross-platform support and note any platform-specific limitations or requirements.
  • Include instructions for installing and using the Azure CLI (which is cross-platform) as an alternative to Azure PowerShell.
  • Add a section or callout for Linux/macOS users, outlining any differences in setup or usage.
  • Ensure screenshots and UI instructions clarify when steps are platform-independent (e.g., Azure Portal) versus platform-specific.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/resources/troubleshoot.md ...in/articles/remote-rendering/resources/troubleshoot.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a significant Windows bias. Troubleshooting steps and examples are almost exclusively presented for Windows environments, especially in codec installation and file system troubleshooting. PowerShell and Windows Explorer are referenced without Linux or cross-platform alternatives. File system limitations and tools are described only in the context of Windows, and there are no Linux-specific instructions or parity in examples.
Recommendations
  • Provide Linux (and macOS, if applicable) equivalents for all command-line instructions, such as using bash or terminal commands instead of only PowerShell.
  • When referencing file system limitations, include notes about Linux file system behaviors and path length limits.
  • If certain features or troubleshooting steps are Windows-only, explicitly state this and, where possible, suggest workarounds or alternatives for Linux users.
  • Include examples or troubleshooting steps for installing codecs and managing permissions on Linux systems.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group them under OS-specific headings.
  • Reference cross-platform tools (e.g., Azure CLI, VS Code) where possible, rather than only Windows-native tools.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/tokens.md .../blob/main/articles/remote-rendering/how-tos/tokens.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only a PowerShell example for obtaining service access tokens, with no equivalent Linux or cross-platform (e.g., curl, bash, Python) examples. The 'Next steps' section also points to more PowerShell scripts, reinforcing a Windows-centric approach. There is no mention of Linux tools or guidance for non-Windows users.
Recommendations
  • Add equivalent examples using curl and/or wget for Linux/macOS users.
  • Provide a cross-platform example in a language like Python that works on both Windows and Linux.
  • Mention that the API can be accessed from any platform and clarify that PowerShell is just one option.
  • Include links or references to Linux/macOS documentation or scripts where appropriate.
  • Reorder or balance examples so that Windows and Linux approaches are presented with equal prominence.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/conversion/blob-storage.md ...es/remote-rendering/how-tos/conversion/blob-storage.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently referencing PowerShell scripts, mentioning PowerShell and Windows-specific issues (such as Windows path length limits), and providing example scripts only in PowerShell. While cross-platform tools like Azure CLI and SDKs are mentioned, concrete examples and links are predominantly for PowerShell. There are no explicit Linux shell (bash) or macOS-specific examples, and Windows tools/patterns are often listed before or instead of Linux equivalents.
Recommendations
  • Add concrete bash (Linux/macOS) command-line examples alongside PowerShell examples for all relevant steps (e.g., generating SAS tokens, uploading files).
  • Provide sample scripts or links for Linux/macOS users, not just PowerShell.
  • When listing tools, alternate or randomize the order, or explicitly state cross-platform compatibility.
  • Include notes or troubleshooting tips relevant to Linux/macOS users, not just Windows-specific issues.
  • Where PowerShell scripts are referenced, provide equivalent bash scripts or Python scripts.
  • Clarify that Azure CLI and SDKs are cross-platform and provide usage examples for non-Windows environments.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/conversion/conversion-rest-api.md ...te-rendering/how-tos/conversion/conversion-rest-api.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing a PowerShell script as the provided example for interacting with the REST API. There are no equivalent examples or scripts for Linux users (e.g., Bash, curl), and the only tooling mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Provide equivalent example scripts for Linux environments, such as Bash scripts using curl or wget to interact with the REST API.
  • Mention cross-platform tools (e.g., curl, httpie, Postman) alongside PowerShell to ensure inclusivity.
  • Explicitly state that the REST API can be accessed from any OS and provide at least one non-Windows example.
  • If possible, add SDK usage examples for other popular languages/platforms (e.g., Python, Node.js) that are commonly used on Linux.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/conversion/model-conversion.md ...emote-rendering/how-tos/conversion/model-conversion.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a bias towards Windows by only referencing PowerShell scripts as examples for using the conversion service, without mentioning or providing equivalent Linux/bash examples. The 'Examples' section specifically highlights PowerShell scripts and does not offer cross-platform alternatives or guidance for Linux users.
Recommendations
  • Add Linux/bash shell script examples for interacting with the conversion service, especially for uploading models, triggering conversions, and polling status.
  • Explicitly mention that the conversion process can be performed from any platform using the REST API, and provide curl or other cross-platform command-line examples.
  • Include links or references to Linux-compatible tools (e.g., az CLI, curl, bash scripts) alongside PowerShell scripts.
  • Ensure that all sample scripts and instructions are available for both Windows and Linux users, or clearly indicate platform-specific steps.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/authentication.md ...in/articles/remote-rendering/how-tos/authentication.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive reference to PowerShell scripts in the 'Next steps' section, with no mention of Linux or cross-platform alternatives (such as Bash or curl). There are no Linux-specific examples or guidance, and the only scripting samples referenced are for PowerShell, a Windows-centric tool. Additionally, the documentation does not provide command-line examples using tools common on Linux, nor does it mention Linux authentication workflows or tools, implicitly prioritizing Windows users.
Recommendations
  • Add equivalent Bash or shell script examples for Linux users alongside PowerShell scripts.
  • Include command-line examples using curl or wget for REST API calls, which are cross-platform.
  • Reference Linux authentication tools (such as Azure CLI on Linux) and provide sample usage.
  • Ensure that any scripting or automation guidance is provided for both Windows and Linux environments.
  • Explicitly state cross-platform compatibility where applicable, and avoid assuming a Windows-only environment.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/create-an-account.md ...articles/remote-rendering/how-tos/create-an-account.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell sample scripts as the primary example for configuration (arrconfig.json), mentioning PowerShell in the context of usage, and linking to PowerShell-specific samples in the 'Next steps' section. There are no equivalent Linux or cross-platform CLI (e.g., Azure CLI, Bash) examples or references, and all instructions are oriented around the Azure Portal UI, which is platform-agnostic but the only scripting example is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples alongside or instead of PowerShell scripts for configuration and automation tasks.
  • Reference cross-platform tools (e.g., Azure CLI) in the main documentation flow, not just in separate samples.
  • Include Linux/macOS-specific instructions or notes where relevant, especially for tasks that can be automated or performed via command line.
  • In the 'Next steps' section, add links to Linux/Bash/Azure CLI samples and documentation, not just PowerShell.
  • Ensure that configuration file examples (like arrconfig.json) are presented in a way that is not tied to a specific scripting environment.
GitHub Create Pull Request
Remote Rendering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/conversion/layout-files-for-conversion.md ...ring/how-tos/conversion/layout-files-for-conversion.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific path limitations, using a Windows-style filesystem example (drive letters and backslashes), and linking only to Windows documentation for path length limits. There are no Linux or cross-platform examples or guidance, and Linux path conventions are not mentioned.
Recommendations
  • Include Linux/Unix filesystem examples alongside or instead of Windows examples (e.g., use /home/user/CONVERSION or /mnt/CONVERSION with forward slashes).
  • Mention Linux/Unix path length limitations and link to relevant documentation, not just Windows.
  • Use neutral or dual-path examples (show both Windows and Linux path formats) to illustrate concepts.
  • Clarify that the conversion service is cross-platform (if applicable) and note any platform-specific considerations.
  • Avoid assuming drive letters or backslash path separators; explain that both styles may be encountered depending on the user's OS.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →