Please enter search query.
Search <book_title>...
Cohesity Alta SaaS Protection 2.x.x Administrator's Guide
Last Published:
2025-04-24
Product(s):
Veritas Alta SaaS Protection (1.0)
- Introduction to Cohesity Alta SaaS Protection
- API permissions
- Administrator portal (Web UI)
- Manage users and roles
- What is a connector?
- Configure credentials
- Pre-requisites for Microsoft 365 connectors
- Protect Microsoft 365 Multi-Geo tenant
- Protect Exchange Online data
- Protect SharePoint sites and data
- Protect Teams sites
- Protect OneDrive data
- Protect Teams chats
- Protect GoogleDrive data
- Protect Gmail data
- Protect Audit logs
- Protect Salesforce data and metada
- Protect Entra ID objects
- Protect Box data
- Protect Slack data
- Protect Email/Message data
- Configure Retention policies
- Perform backups
- View and share backed-up data
- Analytics
- Perform restores using Administration portal
- Restore SharePoint/OneDrive/Teams Sites and data
- Restore Teams chat messages and Teams channel conversations
- Restore Box data
- Restore Google Drive data
- About Salesforce Data, Metadata, and CRM Content restore and Sandbox seeding
- About Entra ID (Azure AD) objects and records restore
- Restore dashboard
- Install services and utilities
- About the Apps Consent Grant Utility
- Discovery
- Configure Tagging polices
- Configure Tiering policy
- Auditing
- Manage Stors (Storages)
Best practices to restore Entra ID objects
When performing a restore, there can be a case where a set of entities have a relationship with each other. In this case, the restore for that set of entities needs to happen within the same restore job because, during the restore of permanently deleted items, new Entra IDs are generated.
Performing the restore of a subset of these entities in two separate jobs is not supported, as there is no way for the other restore job to identify the corresponding new IDs that have been generated against the ones in the backup.