Problem Statement:
Restoring an Entra ID enterprise application from Druva bakup resulted in a status of "successful with errors." Despite the "successful" indication, the application did not appear to be fully or properly restored. Logs indicated an error message similar to "Resource ... does not exist."
Cause:
The issue was caused by an incomplete restore procedure. Restoring only the enterprise application without its corresponding underlying App Registration and the relationship between them leads to inconsistencies and the inability of the restored enterprise application to function correctly. The "Resource does not exist" error refers to the missing or improperly linked App Registration.
Solution:
To correctly restore an Entra ID enterprise application, follow these steps:
Enable "Restore Relationship": During the App Registration restore process, ensure that the option labeled "Restore Relationship" (or similar terminology indicating the restoration of linked objects) is selected. This step is critical for re-establishing the connection between the App Registration and its corresponding enterprise application.
The Enterprise Application Will Be Restored: By restoring the App Registration with the "Restore Relationship" option enabled, the linked enterprise application will be correctly restored as part of this process.