Arctera Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Arctera 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 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 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
- Configuring Azure Netapp Files Device
- 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
Creating an application in the Microsoft Azure portal
To create and register an application with Microsoft
- Login as a global admin user or minimum privilege user to https://portal.azure.com/#home and search App Registrations.
- On the Register an application page, enter a desired name for the app.
- In Supported account types select Accounts in this organizational directory only (<organization-name> only - Single tenant)
- On the Register an application page, click Register to register the app. (Redirect URI can be provided later.)
Your new application is created and the app Overview page is displayed.
- Copy-save the Application (Client ID) and Directory (Tenant) ID. You will be required to provide it later while adding an account in Data Insight.
- On the left sidebar of your app dashboard, click Certificates and Secrets.
- In the Client secrets section, click New client secrets to generate the access token required for calling the required APIs
- Set the expiry to 180 days and click Add.
- Copy the Client Secret Value is generated. You will be required to provide it later while adding an account in Data Insight.
- Then you need to grant permissions to the app to use the Microsoft Graph and Microsoft 365 APIs.
On the left sidebar of your app, click API permissions, and then click Add a permission.
- On the Request API permissions panel that opens, select Microsoft Graph and Microsoft 365 respectively, click Application permissions and grant the permissions as per the table given below:
API
Permission name
Microsoft Graph
Files.Read.All
Group.Read.All
RoleManagement.Read.Directory
Sites.Read.All
User.Read.All
Microsoft 365 Management APIs
ActivityFeed.Read
ActivityFeed.ReadDlp
SharePoint
Sites.FullControl.All
Note:
As per Microsoft guidelines, while using minimum permissions application, few advanced permissions like limited access permissions given to Limited Access System Group for the folder, permissions of sites, Site collections, Document Library will not be visible. To fetch those permission, add Sites.FullControl.All scope to MS Application
- Then click Grant admin consent for.., and confirm.
- Now add the redirect URI.
Go to the Overview page of the app and click Add redirect URI. The Authentication page opens
- Click Add a platform
- On the Configure platforms panel that opens, click Web
- Provide the Data Insight Management Server IP address, as a redirect URI in the following format: https://<Management Server IP address>/spOnline
For more details, refer https://docs.microsoft.com/en-us/azure/active-directory/develop/reply-url.
You can authenticate using FQDN in the redirect URL by setting node Level property.
To set the node Level property,
Navigate to Settings > Servers and click the configured Management Server and then click Advance Settings tab.
In the Advance Settings tab, clickSet custom properties
In the Property Name box, add node.sponline.auth.via.fqdn
In the Property Value box, add true
Click Save and Close.
Note:
Property value should be set to true for authenticating via FQDN and false for authenticating via IP.
If you want to modified any existing property value,
change the redirect URI in the Azure App accordingly.
Delete the cookie from <DATA_DIR>\connectors\sponline\cookie\dataStore on the collector node.
Re-authorize the application.
- Click Configure to save it.
Once the app is created, anybody in the organization can access the app. As per Microsoft recommendation, restrict the access to specific users.
For information on how to require the user assignment for an app via the Azure portal, refer to Configure an application to require user assignment Azure documentation
For information on how to assign users or groups to an app via the Azure portal, refer to Assign users to an app Azure documentation