Veritas Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About user risk score
- About bulk assignment of custodians
- Configuring Metadata Framework
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Adding a directory service domain to Data Insight
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp 7-mode file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp 7-mode file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Configuring monitoring of Box accounts
- Configuring OneDrive account monitoring
- Managing cloud sources
- Section VI. Configuring Object Storage Sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Configuring remediation settings
- Section X. Reference
- Appendix A. Data Insight best practices
- Appendix B. Migrating Data Insight components
- Appendix C. Backing up and restoring data
- Appendix D. Data Insight health checks
- About Data Insight health checks
- About Data Insight health checks
- Appendix E. Command File Reference
- Appendix F. Data Insight jobs
- Appendix G. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Add/Edit Azure active directory service
Use this dialog box to add Azure active directory service to Data Insight.
Table: Add/Edit Azure active directory service
Field | Description |
---|---|
Azure Active Directory Name | Enter the name of the active directory that you want to scan. |
Client ID | The client ID is the unique application ID assigned when you create and register an app with Microsoft. You can add up to 5 client IDs. |
Client Secret Key | Client Secret Key: In the Azure active directory, navigate to the Certificates & secrets page. There is a code in the Value column under the Client secret section. You need to use that code as a Client Secret Key while configuring Azure active directory in Data Insight. If you have missed copying the code, go back to the Certificates & secrets page in the Azure active directory and click + New client secret. Copy the code in the Value column and use it as a Client Secret Key in Data Insight. You can add up to 5 client secret keys. Follow the procedure described in the following topic to get these details: Note: Microsoft servers might briefly block certain client credentials for initiating frequent requests. In such scenarios, Data Insight fails to retrieve data from the Microsoft servers. To eliminate such delay, you can add up to 5 client credentials to the Azure active directory. If one account is blocked by Microsoft, another client credential will be used to fetch data. Add one client ID, Client Secret Key, authorize the app and click Add More Apps to add another set of client credentials. |
Tenant ID | Tenant ID: This is an unique ID assigned to an organization |
Authorize | Do the following:
Note: After authorization, do not update the same set of client and secret key. |
Remove App | Click Remove App to remove the application from your account. |