You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/recover-from-deletions.md
+22-12Lines changed: 22 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.workload: identity
9
9
ms.subservice: fundamentals
10
10
ms.topic: conceptual
11
-
ms.date: 08/26/2022
11
+
ms.date: 11/14/2022
12
12
ms.author: jricketts
13
13
ms.reviewer: jricketts
14
14
ms.custom: "it-pro, seodec18"
@@ -89,19 +89,25 @@ The most frequent scenarios for application deletion are:
89
89
* An administrator intentionally deletes the application, for example, in response to a support request.
90
90
* An automation script in Microsoft Graph or PowerShell triggers the deletion. For example, you might want a process for deleting abandoned applications that are no longer used or managed. In general, create an offboarding process for applications rather than scripting to avoid unintentional deletions.
91
91
92
-
### Properties maintained with soft delete
92
+
When you delete an application, the application registration by default enters the soft-delete state. To understand the relationship between application registrations and service principals, see [Apps and service principals in Azure AD - Microsoft identity platform](../develop/app-objects-and-service-principals.md).
93
93
94
-
| Object type| Important properties maintained |
95
-
| - | - |
96
-
| Users (including external users)|*All properties are maintained*, including ObjectID, group memberships, roles, licenses, and application assignments. |
97
-
| Microsoft 365 Groups|*All properties are maintained*, including ObjectID, group memberships, licenses, and application assignments. |
98
-
| Application registration|*All properties are maintained.* (See more information after this table.) |
94
+
### Administrative units
99
95
100
-
When you delete an application, the application registration by default enters the soft-delete state. To understand the relationship between application registrations and service principals, see [Apps and service principals in Azure AD - Microsoft identity platform](../develop/app-objects-and-service-principals.md).
96
+
The most common scenario for deletions is when administrative units (AU) are deleted by accident, although still needed.
101
97
102
98
## Recover from soft deletion
103
99
104
-
You can restore soft-deleted items in the Azure portal or with Microsoft Graph.
100
+
You can restore soft-deleted items in the administrative portal, or by using Microsoft Graph. Not all object classes can manage soft-delete capabilities in the portal, some are only listed, viewed, hard deleted, or restored using the deletedItems Microsoft Graph API.
101
+
102
+
### Properties maintained with soft delete
103
+
104
+
|Object type|Important properties maintained|
105
+
|---|---|
106
+
|Users (including external users)|All properties maintained, including ObjectID, group memberships, roles, licenses, and application assignments|
107
+
|Microsoft 365 Groups|All properties maintained, including ObjectID, group memberships, licenses, and application assignments|
108
+
|Application registration | All properties maintained. See more information after this table.|
109
+
|Service principal|All properties maintained|
110
+
|Administrative unit (AU)|All properties maintained|
105
111
106
112
### Users
107
113
@@ -125,15 +131,19 @@ For more information on how to restore soft-deleted Microsoft 365 Groups, see th
125
131
* To restore from the Azure portal, see [Restore a deleted Microsoft 365 Group](../enterprise-users/groups-restore-deleted.md).
126
132
* To restore by using Microsoft Graph, see [Restore deleted item – Microsoft Graph v1.0](/graph/api/directory-deleteditems-restore?tabs=http).
127
133
128
-
### Applications
134
+
### Applications and service principals
129
135
130
136
Applications have two objects: the application registration and the service principal. For more information on the differences between the registration and the service principal, see [Apps and service principals in Azure AD](../develop/app-objects-and-service-principals.md).
131
137
132
138
To restore an application from the Azure portal, select **App registrations** > **Deleted applications**. Select the application registration to restore, and then select **Restore app registration**.
133
139
134
140
[](./media/recoverability/deletion-restore-application.png#lightbox)
135
141
136
-
To restore applications using Microsoft Graph, see [Restore deleted item - Microsoft Graph v1.0.](/graph/api/directory-deleteditems-restore?tabs=http)
142
+
Currently, service principals can be listed, viewed, hard deleted, or restored via the deletedItems Microsoft Graph API. To restore applications using Microsoft Graph, see [Restore deleted item - Microsoft Graph v1.0.](/graph/api/directory-deleteditems-restore?tabs=http).
143
+
144
+
### Administrative units
145
+
146
+
AUs can be listed, viewed, hard deleted, or restored via the deletedItems Microsoft Graph API. To restore AUs using Microsoft Graph, see [Restore deleted item - Microsoft Graph v1.0.](/graph/api/directory-deleteditems-restore?tabs=http).
137
147
138
148
## Hard deletions
139
149
@@ -150,7 +160,7 @@ A hard deletion is the permanent removal of an object from your Azure AD tenant.
150
160
151
161
### When hard deletes usually occur
152
162
153
-
Hard deletes most often occur in the following circumstances.
163
+
Hard deletes might occur in the following circumstances.
0 commit comments