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 generally provides both Linux and Windows options, but there is a tendency to mention or provide Windows/PowerShell examples before Linux/Azure CLI equivalents. PowerShell is often listed before Azure CLI, and Windows Server DNS configuration is referenced before Linux/BIND in some places. There is also a direct link to Windows Server DNS documentation, while Linux/BIND instructions are more detailed but not always referenced as the primary or only option.
Recommendations
- Present Azure CLI and Linux-based examples before or alongside PowerShell/Windows examples to avoid the appearance of Windows-first bias.
- When referencing DNS server configuration, provide equal prominence and links to both Windows Server and Linux/BIND documentation.
- Ensure that all steps and examples are available for both Linux and Windows environments, and that neither is presented as the default or primary approach.
- In sections where PowerShell is used, always provide an equivalent Azure CLI example immediately adjacent, or vice versa.
- Where possible, clarify that both Windows and Linux DNS servers are supported and provide clear, parallel instructions for each.
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