|
1 | 1 | ---
|
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 |
4 | 4 | services: active-directory-ds
|
5 |
| -documentationcenter: '' |
6 | 5 | author: iainfoulds
|
7 |
| -manager: |
8 |
| -editor: |
| 6 | +manager: daveba |
9 | 7 |
|
10 | 8 | ms.assetid: f168870c-b43a-4dd6-a13f-5cfadc5edf2c
|
11 | 9 | ms.service: active-directory
|
12 | 10 | ms.subservice: domain-services
|
13 | 11 | 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 |
18 | 14 | ms.author: iainfou
|
19 | 15 |
|
20 | 16 | ---
|
21 |
| -# Troubleshoot invalid service principal configurations for Azure Active Directory Domain Services |
| 17 | +# Known issues: Service principal alerts in Azure Active Directory Domain Services |
22 | 18 |
|
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. |
24 | 20 |
|
25 |
| -## Alert AADDS102: Service Principal not found |
| 21 | +This article helps you troubleshoot and resolve service principal-related configuration alerts. |
26 | 22 |
|
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 |
28 | 24 |
|
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.* |
30 | 27 |
|
| 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. |
31 | 29 |
|
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 |
34 | 31 |
|
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: |
38 | 33 |
|
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. |
45 | 37 |
|
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) | |
48 | 44 |
|
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 |
51 | 46 |
|
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: |
54 | 50 |
|
55 | 51 | ```powershell
|
56 | 52 | Install-Module AzureAD
|
57 | 53 | Import-Module AzureAD
|
58 | 54 | ```
|
59 | 55 |
|
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: |
67 | 57 |
|
68 | 58 | ```powershell
|
69 | 59 | New-AzureAdServicePrincipal -AppId "2565bd9d-da50-47d4-8b85-4c97f669dc36"
|
70 | 60 | ```
|
71 | 61 |
|
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. |
73 | 63 |
|
| 64 | +## Re-register the Microsoft AAD namespace |
74 | 65 |
|
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: |
77 | 67 |
|
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**. |
86 | 72 |
|
| 73 | +The Azure AD DS managed domain's health automatically updates itself within two hours and removes the alert. |
87 | 74 |
|
88 | 75 | ## Alert AADDS105: Password synchronization application is out of date
|
89 | 76 |
|
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. |
91 | 81 |
|
| 82 | +**Resolution** |
92 | 83 |
|
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). |
95 | 85 |
|
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: |
98 | 87 |
|
99 | 88 | ```powershell
|
100 | 89 | Install-Module AzureAD
|
101 | 90 | Import-Module AzureAD
|
102 | 91 | ```
|
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: |
104 | 94 |
|
105 | 95 | ```powershell
|
106 | 96 | $app = Get-AzureADApplication -Filter "IdentifierUris eq 'https://sync.aaddc.activedirectory.windowsazure.com'"
|
107 | 97 | Remove-AzureADApplication -ObjectId $app.ObjectId
|
108 | 98 | $spObject = Get-AzureADServicePrincipal -Filter "DisplayName eq 'Azure AD Domain Services Sync'"
|
109 | 99 | Remove-AzureADServicePrincipal -ObjectId $app.ObjectId
|
110 | 100 | ```
|
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. |
112 | 101 |
|
| 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. |
113 | 107 |
|
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