Document Details
Connect On Premises Network
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates some Windows bias by listing PowerShell as a primary automation tool, providing PowerShell examples before Azure CLI, and referencing Windows Server DNS configuration before Linux alternatives in some sections. While Linux is well-represented for the DNS server setup (using Bind on Ubuntu), automation and scripting guidance often defaults to PowerShell, and Windows Server DNS documentation is referenced before or more prominently than Linux equivalents.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples, especially in sections where both are relevant.
- Provide explicit Linux-based DNS server configuration examples and documentation references before or alongside Windows Server DNS references.
- Where PowerShell is mentioned as a prerequisite or tool, also mention Bash/Azure CLI as an equal alternative for Linux/macOS users.
- In sections discussing DNS server configuration, include links to documentation for popular Linux DNS servers (e.g., Bind, dnsmasq) before or alongside Windows Server DNS.
- Audit all example scripts and commands to ensure Linux and cross-platform parity, and avoid implying PowerShell is the default or preferred automation tool.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-09-16 00:00 | #113 | completed |
Clean
|
| 2025-09-15 00:00 | #112 | completed |
Clean
|
| 2025-09-14 00:00 | #111 | completed |
Clean
|
| 2025-09-13 00:00 | #110 | completed |
Clean
|
| 2025-09-12 00:00 | #109 | completed |
Clean
|
| 2025-09-11 00:00 | #108 | completed |
Clean
|
| 2025-09-10 00:00 | #107 | completed |
Clean
|
| 2025-09-09 00:00 | #106 | completed |
Clean
|
| 2025-09-08 00:00 | #105 | completed |
Clean
|
| 2025-09-07 00:00 | #104 | completed |
Clean
|
| 2025-09-06 00:00 | #103 | completed |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
For information on using DNS on **Windows Server 2016**, see the [Add-DnsServerConditionalForwarderZone](/powershell/module/dnsserver/add-dnsserverconditionalforwarderzone) documentation... Once you've configured the on-premises DNS server, you can use `nslookup` from the on-premises network to verify that you can resolve names in the virtual network. The following example