Document Details
File Sync Networking Endpoints
❌
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
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation demonstrates a Windows bias in several ways: it consistently refers to Windows file servers as the only supported on-premises sync targets, provides PowerShell examples and output before or instead of cross-platform alternatives, and uses Windows-centric terminology and tools (such as PowerShell and Windows DNS output). While Azure CLI and Bash examples are present for many tasks, some critical operations (such as disabling the Storage Sync Service public endpoint) are only possible via PowerShell, with the documentation explicitly stating that Azure CLI does not support the operation. There is also an absence of Linux-specific guidance or examples for managing on-premises endpoints, reflecting the Windows-only support of Azure File Sync agents.
Recommendations:
- Clearly state early in the documentation that Azure File Sync currently only supports Windows file servers as sync agents, and provide a link to feature requests or roadmap for Linux support if available.
- Where PowerShell is the only supported method (e.g., for Storage Sync Service public endpoint configuration), explicitly note the limitation and suggest workarounds or alternatives for Linux users, such as using Azure Portal or REST API if possible.
- For all command-line examples, ensure that Azure CLI/Bash examples are given equal prominence and are not presented after PowerShell by default.
- Where output examples are shown, provide both Windows (PowerShell) and Linux (Bash/CLI) output formats to help users on all platforms recognize expected results.
- If certain features are not available for Linux, explicitly state this in the relevant sections to set user expectations.
- Consider including a summary table at the top of the article indicating which operations are supported on which platforms/tools (PowerShell, Azure CLI, Portal, REST API) for quick reference.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-19 00:01 | #85 | completed | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
Flagged Code Snippets
$storageAccountHostName = [System.Uri]::new($storageAccount.PrimaryEndpoints.file) | `
Select-Object -ExpandProperty Host
Resolve-DnsName -Name $storageAccountHostName
Name : mysssmanagement.westus2.afs.azure.net
Type : CNAME
TTL : 60
Section : Answer
NameHost : mysssmanagement.westus2.privatelink.afs.azure.net
Name : mysssmanagement.westus2.privatelink.afs.azure.net
QueryType : A
TTL : 60
Section : Answer
IP4Address : 192.168.1.4
Name : myssssyncp.westus2.afs.azure.net
Type : CNAME
TTL : 60
Section : Answer
NameHost : myssssyncp.westus2.privatelink.afs.azure.net
Name : myssssyncp.westus2.privatelink.afs.azure.net
QueryType : A
TTL : 60
Section : Answer
IP4Address : 192.168.1.5
Name : myssssyncs.westus2.afs.azure.net
Type : CNAME
TTL : 60
Section : Answer
NameHost : myssssyncs.westus2.privatelink.afs.azure.net
Name : myssssyncs.westus2.privatelink.afs.azure.net
QueryType : A
TTL : 60
Section : Answer
IP4Address : 192.168.1.6
Name : mysssmonitoring.westus2.afs.azure.net
Type : CNAME
TTL : 60
Section : Answer
NameHost : mysssmonitoring.westus2.privatelink.afs.azure.net
Name : mysssmonitoring.westus2.privatelink.afs.azure.net
QueryType : A
TTL : 60
Section : Answer
IP4Address : 192.168.1.7
$storageSyncServiceResourceGroupName = "<storage-sync-service-resource-group>"
$storageSyncServiceName = "<storage-sync-service>"
$storageSyncService = Get-AzStorageSyncService `
-ResourceGroupName $storageSyncServiceResourceGroupName `
-Name $storageSyncServiceName `
-ErrorAction SilentlyContinue
if ($null -eq $storageSyncService) {
$errorMessage = "Storage Sync Service $storageSyncServiceName not found "
$errorMessage += "in resource group $storageSyncServiceResourceGroupName."
Write-Error -Message $errorMessage -ErrorAction Stop
}