Skip to content

Commit ca7ed5e

Browse files
committed
[AzureADDS] Update heading format
1 parent 91c279c commit ca7ed5e

File tree

3 files changed

+11
-8
lines changed

3 files changed

+11
-8
lines changed

articles/active-directory-domain-services/alert-ldaps.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,11 @@ This article helps you understand and resolve common alerts with secure LDAP acc
2222

2323
## AADDS101: Secure LDAP network security group configuration
2424

25-
**Alert message**
25+
### Alert message
2626

2727
*Secure LDAP over the internet is enabled for the managed domain. However, access to port 636 is not locked down using a network security group. This may expose user accounts on the managed domain to password brute-force attacks.*
2828

29-
**Resolution**
29+
### Resolution
3030

3131
When you enable secure LDAP, it's recommended to create additional rules that restrict inbound LDAPS access to specific IP addresses. These rules protect the Azure AD DS managed domain from brute force attacks. To update the network security group to restrict TCP port 636 access for secure LDAP, complete the following steps:
3232

@@ -46,11 +46,11 @@ The Azure AD DS managed domain's health automatically updates itself within two
4646
4747
## AADDS502: Secure LDAP certificate expiring
4848

49-
**Alert message**
49+
### Alert message
5050

5151
*The secure LDAP certificate for the managed domain will expire on [date]].*
5252

53-
**Resolution**
53+
### Resolution
5454

5555
Create a replacement secure LDAP certificate by following the steps to [create a certificate for secure LDAP](tutorial-configure-ldaps.md#create-a-certificate-for-secure-ldap). Apply the replacement certificate to Azure AD DS, and distribute the certificate to any clients that connect using secure LDAP.
5656

articles/active-directory-domain-services/alert-nsg.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,8 @@ This article helps you understand and resolve common alerts for network security
2222

2323
## Alert AADDS104: Network error
2424

25-
**Alert message**
25+
### Alert message
26+
2627
*Microsoft is unable to reach the domain controllers for this managed domain. This may happen if a network security group (NSG) configured on your virtual network blocks access to the managed domain. Another possible reason is if there is a user-defined route that blocks incoming traffic from the internet.*
2728

2829
Invalid network security group rules are the most common cause of network errors for Azure AD DS. The network security group for the virtual network must allow access to specific ports and protocols. If these ports are blocked, the Azure platform can't monitor or update the managed domain. The synchronization between the Azure AD directory and Azure AD DS managed domain is also impacted. Make sure you keep the default ports open to avoid interruption in service.

articles/active-directory-domain-services/alert-service-principal.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,8 @@ This article helps you troubleshoot and resolve service principal-related config
2222

2323
## Alert AADDS102: Service principal not found
2424

25-
**Alert message**
25+
### Alert message
26+
2627
*A Service Principal required for Azure AD Domain Services to function properly has been deleted from your Azure AD directory. This configuration impacts Microsoft's ability to monitor, manage, patch, and synchronize your managed domain.*
2728

2829
If a required service principal is deleted, the Azure platform can't perform automated management tasks. The Azure AD DS managed domain may not correctly apply updates or take backups.
@@ -74,12 +75,13 @@ The Azure AD DS managed domain's health automatically updates itself within two
7475
7576
## Alert AADDS105: Password synchronization application is out of date
7677
77-
**Alert message**
78+
### Alert message
79+
7880
*The service principal with the application ID “d87dcbc6-a371-462e-88e3-28ad15ec4e64” was deleted and then recreated. The recreation leaves behind inconsistent permissions on Azure AD Domain Services resources needed to service your managed domain. Synchronization of passwords on your managed domain could be affected.*
7981
8082
Azure AD DS automatically synchronizes user accounts and credentials from Azure AD. If there's a problem with the Azure AD application used for this process, credential synchronization between Azure AD DS and Azure AD fails.
8183
82-
**Resolution**
84+
### Resolution
8385
8486
To recreate the Azure AD application used for credential synchronization, use Azure AD PowerShell to complete the following steps. For more information, see [install Azure AD PowerShell](/powershell/azure/active-directory/install-adv2).
8587

0 commit comments

Comments
 (0)