Skip to content

Commit ee76ff6

Browse files
committed
[AzureADDS] Service principal alerts updates
1 parent d3714f1 commit ee76ff6

File tree

1 file changed

+52
-58
lines changed

1 file changed

+52
-58
lines changed
Lines changed: 52 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -1,115 +1,109 @@
11
---
2-
title: 'Azure Active Directory Domain Services: Troubleshoot service principals | Microsoft Docs'
3-
description: Troubleshooting Service Principal configuration for Azure AD Domain Services
2+
title: Resolve service principal alerts in Azure AD Domain Services | Microsoft Docs
3+
description: Learn how to troubleshoot service principal configuration alerts for Azure Active Directory Domain Services
44
services: active-directory-ds
5-
documentationcenter: ''
65
author: iainfoulds
7-
manager:
8-
editor:
6+
manager: daveba
97

108
ms.assetid: f168870c-b43a-4dd6-a13f-5cfadc5edf2c
119
ms.service: active-directory
1210
ms.subservice: domain-services
1311
ms.workload: identity
14-
ms.tgt_pltfrm: na
15-
ms.devlang: na
16-
ms.topic: conceptual
17-
ms.date: 05/14/2019
12+
ms.topic: troubleshooting
13+
ms.date: 09/20/2019
1814
ms.author: iainfou
1915

2016
---
21-
# Troubleshoot invalid service principal configurations for Azure Active Directory Domain Services
17+
# Known issues: Service principal alerts in Azure Active Directory Domain Services
2218

23-
This article helps you troubleshoot and resolve service principal-related configuration errors that result in the following alert message:
19+
[Service principals](../active-directory/develop/app-objects-and-service-principals.md) are applications that the Azure platform uses to manage, update, and maintain an Azure AD DS managed domain. If a service principal is deleted, functionality in the Azure AD DS managed domain is impacted.
2420

25-
## Alert AADDS102: Service Principal not found
21+
This article helps you troubleshoot and resolve service principal-related configuration alerts.
2622

27-
**Alert message:** *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.*
23+
## Alert AADDS102: Service principal not found
2824

29-
[Service principals](../active-directory/develop/app-objects-and-service-principals.md) are applications that Microsoft uses to manage, update, and maintain your managed domain. If they are deleted, it breaks Microsoft's ability to service your domain.
25+
**Alert message**
26+
*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.*
3027

28+
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.
3129

32-
## Check for missing service principals
33-
Use the following steps to determine which service principals need to be recreated:
30+
### Check for missing service principals
3431

35-
1. Navigate to the [Enterprise Applications - All Applications](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AllApps) page in the Azure portal.
36-
2. In the **Show** dropdown, select **All Applications** and click **Apply**.
37-
3. Using the following table, search for each application ID by pasting the ID into the search box and pressing enter. If the search results are empty, you must recreate the service principal by following the steps in the "resolution" column.
32+
To check which service principal is missing and needs to be recreated, complete the following steps:
3833

39-
| Application ID | Resolution |
40-
| :--- | :--- |
41-
| 2565bd9d-da50-47d4-8b85-4c97f669dc36 | [Recreate a missing service principal with PowerShell](#recreate-a-missing-service-principal-with-powershell) |
42-
| 443155a6-77f3-45e3-882b-22b3a8d431fb | [Re-register to the Microsoft.AAD namespace](#re-register-to-the-microsoft-aad-namespace-using-the-azure-portal) |
43-
| abba844e-bc0e-44b0-947a-dc74e5d09022 | [Re-register to the Microsoft.AAD namespace](#re-register-to-the-microsoft-aad-namespace-using-the-azure-portal) |
44-
| d87dcbc6-a371-462e-88e3-28ad15ec4e64 | [Re-register to the Microsoft.AAD namespace](#re-register-to-the-microsoft-aad-namespace-using-the-azure-portal) |
34+
1. In the Azure portal, select **Azure Active Directory** from the left-hand navigation menu.
35+
1. Select **Enterprise applications**. Choose *All applications* from the **Application Type** drop-down menu, then select **Apply**.
36+
1. Search for each of the application IDs. If no existing application is found, follow the *Resolution* steps to create the service principal or re-register the namespace.
4537

46-
## Recreate a missing Service Principal with PowerShell
47-
Follow these steps if a service principal with the ID ```2565bd9d-da50-47d4-8b85-4c97f669dc36``` is missing from your Azure AD directory.
38+
| Application ID | Resolution |
39+
| :--- | :--- |
40+
| 2565bd9d-da50-47d4-8b85-4c97f669dc36 | [Recreate a missing service principal](#recreate-a-missing-service-principal) |
41+
| 443155a6-77f3-45e3-882b-22b3a8d431fb | [Re-register the Microsoft.AAD namespace](#re-register-to-the-microsoft-aad-namespace) |
42+
| abba844e-bc0e-44b0-947a-dc74e5d09022 | [Re-register the Microsoft.AAD namespace](#re-register-to-the-microsoft-aad-namespace) |
43+
| d87dcbc6-a371-462e-88e3-28ad15ec4e64 | [Re-register the Microsoft.AAD namespace](#re-register-to-the-microsoft-aad-namespace) |
4844

49-
**Resolution:**
50-
You need Azure AD PowerShell to complete these steps. For information on installing Azure AD PowerShell, see [this article](https://docs.microsoft.com/powershell/azure/active-directory/install-adv2?view=azureadps-2.0.).
45+
### Recreate a missing Service Principal
5146

52-
To address this issue, type the following commands in a PowerShell window:
53-
1. Install the Azure AD PowerShell module and import it.
47+
If application ID *2565bd9d-da50-47d4-8b85-4c97f669dc36* is missing from your Azure AD directory, use Azure AD PowerShell to complete the following steps. For more information, see [install Azure AD PowerShell](/powershell/azure/active-directory/install-adv2).
48+
49+
1. Install the Azure AD PowerShell module and import it as follows:
5450

5551
```powershell
5652
Install-Module AzureAD
5753
Import-Module AzureAD
5854
```
5955
60-
2. Check whether the service principal required for Azure AD Domain Services is missing in your directory by executing the following PowerShell command:
61-
62-
```powershell
63-
Get-AzureAdServicePrincipal -filter "AppId eq '2565bd9d-da50-47d4-8b85-4c97f669dc36'"
64-
```
65-
66-
3. Create the service principal by typing the following PowerShell command:
56+
1. Now recreate the service principal using the [New-AzureAdServicePrincipal][New-AzureAdServicePrincipal] cmdlet:
6757
6858
```powershell
6959
New-AzureAdServicePrincipal -AppId "2565bd9d-da50-47d4-8b85-4c97f669dc36"
7060
```
7161
72-
4. After you have created the missing service principal, wait two hours and check your managed domain's health.
62+
The Azure AD DS managed domain's health automatically updates itself within two hours and removes the alert.
7363
64+
## Re-register the Microsoft AAD namespace
7465
75-
## Re-register to the Microsoft AAD namespace using the Azure portal
76-
Follow these steps if a service principal with the ID ```443155a6-77f3-45e3-882b-22b3a8d431fb``` or ```abba844e-bc0e-44b0-947a-dc74e5d09022``` or ```d87dcbc6-a371-462e-88e3-28ad15ec4e64``` is missing from your Azure AD directory.
66+
If application ID *443155a6-77f3-45e3-882b-22b3a8d431fb*, *abba844e-bc0e-44b0-947a-dc74e5d09022*, or *d87dcbc6-a371-462e-88e3-28ad15ec4e64* is missing from your Azure AD directory, complete the following steps to re-register the *Microsoft.AAD* resource provider:
7767
78-
**Resolution:**
79-
Use the following steps to restore Domain Services on your directory:
80-
81-
1. Navigate to the [Subscriptions](https://portal.azure.com/#blade/Microsoft_Azure_Billing/SubscriptionsBlade) page in the Azure portal.
82-
2. Choose the subscription from the table that is associated with your managed domain
83-
3. Using the left-hand navigation, choose **Resource Providers**
84-
4. Search for "Microsoft.AAD" in the table and click **Re-register**
85-
5. To ensure the alert is resolved, view the health page for your managed domain in two hours.
68+
1. In the Azure portal, search for and select **Subscriptions**.
69+
1. Choose the subscription associated with your Azure AD DS managed domain.
70+
1. From the left-hand navigation, choose **Resource Providers**.
71+
1. Search for *Microsoft.AAD*, then select **Re-register**.
8672
73+
The Azure AD DS managed domain's health automatically updates itself within two hours and removes the alert.
8774
8875
## Alert AADDS105: Password synchronization application is out of date
8976
90-
**Alert message:** 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.
77+
**Alert message**
78+
*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.*
79+
80+
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.
9181
82+
**Resolution**
9283
93-
**Resolution:**
94-
You need Azure AD PowerShell to complete these steps. For information on installing Azure AD PowerShell, see [this article](https://docs.microsoft.com/powershell/azure/active-directory/install-adv2?view=azureadps-2.0.).
84+
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).
9585
96-
To address this issue, type the following commands in a PowerShell window:
97-
1. Install the Azure AD PowerShell module and import it.
86+
1. Install the Azure AD PowerShell module and import it as follows:
9887
9988
```powershell
10089
Install-Module AzureAD
10190
Import-Module AzureAD
10291
```
103-
2. Delete the old application and object using the following PowerShell commands
92+
93+
2. Now delete the old application and object using the following PowerShell cmdlets:
10494
10595
```powershell
10696
$app = Get-AzureADApplication -Filter "IdentifierUris eq 'https://sync.aaddc.activedirectory.windowsazure.com'"
10797
Remove-AzureADApplication -ObjectId $app.ObjectId
10898
$spObject = Get-AzureADServicePrincipal -Filter "DisplayName eq 'Azure AD Domain Services Sync'"
10999
Remove-AzureADServicePrincipal -ObjectId $app.ObjectId
110100
```
111-
3. After you have deleted both, the system will remediate itself and recreate the applications needed for password synchronization. To ensure the alert has been remediated, wait two hours and check your domain's health.
112101
102+
After you delete both applications, the Azure platform automatically recreates them and tries to resume password synchronization. The Azure AD DS managed domain's health automatically updates itself within two hours and removes the alert.
103+
104+
## Next steps
105+
106+
If you still have issues, [open an Azure support request][azure-support] for additional troubleshooting assistance.
113107
114-
## Contact Us
115-
Contact the Azure Active Directory Domain Services product team to [share feedback or for support](contact-us.md).
108+
<!-- INTERNAL LINKS -->
109+
[azure-support]: ../active-directory/fundamentals/active-directory-troubleshooting-support-howto.md

0 commit comments

Comments
 (0)