Quest Identity Recovery is deployed through Quest's cloud-hosted security management platform. We can also deploy it on-premises as well with Active Directory recovery and the agent installed on a suitable server. The hosted service of Quest Identity Recovery uses cloud infrastructure from Microsoft Azure. We utilize multiple other services running on Azure, from virtual machines to Active Directories and Entra IDs, making Azure our primary cloud provider. We contacted them directly for Quest Identity Recovery, and I believe they provided the necessary information. My advice for others looking into using Quest Identity Recovery is to carefully check your requirements against what the product offers to ensure alignment, and only proceed with deployment if both match. I rate Quest Identity Recovery an eight out of ten because of the granular recovery, protection for identity environments, and the ability to reduce the effort to recover from accidental changes or disasters. The two points I deducted stem from some delays in reflection whenever there is a recovery speed in complex scenarios, along with some automation gaps and storage costs.
A situation that would prompt the use of Quest Identity Recovery for cloud-only Entra ID objects is the accidental deletion of cloud-only users, groups, and other identity objects, administrative errors, or an identity management incident where the object does not have an on-premises source of authority. The key difference observed is that with Entra Connect synchronization, the on-premises Active Directory object is normally the source of authority. If a synchronized user is deleted in Entra ID, recovery can often be performed by restoring the on-premises AD object and allowing synchronization to recreate or restore the cloud representation depending on the scenarios and object state. My advice to others looking into using Quest Identity Recovery is to first identify the most critical identity recovery scenarios before implementing Quest Identity Recovery. Do not view it simply as a backup product, but as a part of an identity disaster recovery strategy. I have been using Quest products for almost ten years and would rate this product an eight out of ten.
Identity Recovery and Security Guardian compete in the identity protection and security management sector. Identity Recovery might have an advantage due to its user-friendly design, while Security Guardian seems superior in security protocols and integration options.Features: Identity Recovery emphasizes identity restoration services, quick breach response, and intuitive navigation. Security Guardian focuses on threat detection, frequent security updates, and diverse capabilities.Ease of...
Quest Identity Recovery is deployed through Quest's cloud-hosted security management platform. We can also deploy it on-premises as well with Active Directory recovery and the agent installed on a suitable server. The hosted service of Quest Identity Recovery uses cloud infrastructure from Microsoft Azure. We utilize multiple other services running on Azure, from virtual machines to Active Directories and Entra IDs, making Azure our primary cloud provider. We contacted them directly for Quest Identity Recovery, and I believe they provided the necessary information. My advice for others looking into using Quest Identity Recovery is to carefully check your requirements against what the product offers to ensure alignment, and only proceed with deployment if both match. I rate Quest Identity Recovery an eight out of ten because of the granular recovery, protection for identity environments, and the ability to reduce the effort to recover from accidental changes or disasters. The two points I deducted stem from some delays in reflection whenever there is a recovery speed in complex scenarios, along with some automation gaps and storage costs.
A situation that would prompt the use of Quest Identity Recovery for cloud-only Entra ID objects is the accidental deletion of cloud-only users, groups, and other identity objects, administrative errors, or an identity management incident where the object does not have an on-premises source of authority. The key difference observed is that with Entra Connect synchronization, the on-premises Active Directory object is normally the source of authority. If a synchronized user is deleted in Entra ID, recovery can often be performed by restoring the on-premises AD object and allowing synchronization to recreate or restore the cloud representation depending on the scenarios and object state. My advice to others looking into using Quest Identity Recovery is to first identify the most critical identity recovery scenarios before implementing Quest Identity Recovery. Do not view it simply as a backup product, but as a part of an identity disaster recovery strategy. I have been using Quest products for almost ten years and would rate this product an eight out of ten.