Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | AADDS501 - The managed domain has not been backed up recently. | Azure portal > Azure Active Directory Domain Services > Health > Alerts | -> |
| Affected build range | Windows Server 2022 | OS Build Information | |
| Registry key involved | HKLM\SYSTEM\CurrentControlSet\Services\Netlogon | Registry Editor | -> Netlogon service health |
| Relevant service/endpoint URL | https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ADDomainServices/dnszones/{dnsZoneName} | Azure REST API Documentation | -> DNS zone management |
| Log line signature | Event ID 1308 (NTDS replication failure) and Event ID 4625 (authentication failures from managed domain controller) | Windows Event Viewer > Windows Logs > System |
Log Files to Check
C:\Windows\debug\netlogon.logC:\Windows\System32\winevt\Logs\System.evtx
What This Error Actually Means
The error AADDS501 indicates that Azure Active Directory Domain Services (AAD DS) has detected a critical issue: the managed domain is not being backed up regularly as per best practices and compliance requirements. The health monitoring system within AAD DS evaluates the state of your managed domain every hour, looking for signs of backup activity. If it doesn't detect any recent backups, it raises this alert to notify you that data protection measures are compromised. This error originates from the Health Monitoring component of Azure Active Directory Domain Services, which is responsible for assessing various aspects of the service's health and reporting issues through alerts in the Azure portal. The exact string "AADDS501 - The managed domain has not been backed up recently" appears when you navigate toAzure Active Directory Domain Services > Health > Alerts within your Azure management console.
Affected Versions and Scope
This error is specifically relevant for Windows Server 2022, which is the OS build range mentioned in the context. The issue does not affect other versions of Windows Server or non-Windows server environments managed by AAD DS. It impacts tenants who have enabled Azure Active Directory Domain Services to manage their on-premises domain controllers and ensure that backups are being performed as expected.Where To Look First: Logs and Event IDs
To diagnose the root cause of this issue, start by examining two primary sources of information: 1. **Windows Event Viewer**: Navigate toEvent Viewer > Windows Logs > System. Here, look for specific event IDs that can indicate issues with NTDS replication or authentication failures from managed domain controllers:
- Event ID 1308: This event signifies an NTDS replication failure.
- Event ID 4625: This event indicates failed logon attempts which could be due to network connectivity issues affecting the ability of domain controllers to authenticate.
2. **Netlogon Log File**: Analyze the C:\Windows\debug\netlogon.log file on your domain-joined Windows Server 2022 machine for any signs of replication or authentication errors that might correlate with Event IDs found in the event logs.
Root Causes
The AADDS501 error can stem from several distinct causes, each requiring a different approach to resolve:Inbound Network Security Group (NSG) Rules Blocking Required Ports
One common cause is that NSGs on your Azure Virtual Network subnets are blocking inbound traffic on essential ports such as 443, 5986, and 3389 from theAzureActiveDirectoryDomainServices service tag. This can prevent the domain controller VMs from communicating with necessary services for backup operations.
Lack of Outbound Connectivity to Azure Storage
Another potential issue is that outbound connectivity to your Azure Storage account, where backups are stored, might be blocked by network policies or firewall rules on your virtual machines. Domain controllers need this access to write backup snapshots to the storage account.NTDS Replication Issues
Replication synchronization between domain controllers can break due to various factors such as network latency, DNS resolution problems, or misconfigured replication partners. Checking for NTDS connection errors and Event ID 1308 in your logs will help identify if this is the cause.Fix Procedure
To address the AADDS501 error, follow these steps:- Check NSG Rules: Use
Get-AzNetworkSecurityGroup -Name "your-nsg-name" -ResourceGroupName "your-rg-name"to review your network security group rules. Ensure that the service tagAzureActiveDirectoryDomainServicesis allowed inbound traffic on ports 443, 5986, and 3389. - Analyze Event Logs: Use PowerShell cmdlets like
Get-WinEvent -LogName "System" -FilterXPath "*[System[EventID=1308 or EventID=4625]]"to filter and review relevant events in the Windows event logs. - Validate Storage Connectivity: Confirm that your domain controller VMs have outbound connectivity to Azure Storage. This can be checked via network diagnostics tools or by attempting a test backup operation.
- Re-evaluate Health Status: After making necessary corrections, trigger a health re-evaluation from the
Azure Active Directory Domain Services > [domain name] > Healthblade in the Azure portal. UseGet-AzADDomainService -Name "your-domain-name" -ResourceGroupName "your-rg-name"to check if the issue has been resolved.
Be cautious when adjusting network security rules as this can potentially disrupt communication between your domain controllers and other critical services.
A quick diagnostic shortcut is to use
netdom query fsmo /domain: to verify the FSMO roles are correctly assigned, which often impacts replication health.Error Code Variants
| Error Code | Description | Distinguishing Factors |
|---|---|---|
| AADDS501 | Managed domain not backed up recently | Specific to backup operations and connectivity issues. |
| AADDS402 | Replication failure between DCs | Involves NTDS replication errors, often related to Event ID 1308. |
| AADDS603 | Network connectivity issues | Indicates problems with inbound or outbound network traffic affecting service operations. |
Verification
To verify that the issue has been resolved, look for the following indicators: - In the Azure portal underAzure Active Directory Domain Services > Health > Alerts, ensure there are no AADDS501 alerts present.
- Check the event logs for Event ID 4625 and Event ID 1308 to confirm that authentication failures and replication errors have ceased.
- Review the netlogon.log file at C:\Windows\debug\netlogon.log for any recent entries indicating successful backup operations.