Troubleshooting Forensics Setup for Public Cloud
Troubleshooting Forensics Setup for Public Cloud
This topic provides common scenarios that you can troubleshoot when you set up Forensics for Public Cloud.
Error message when creating a Forensics Profile for Azure Blob Storage
When creating a Forensics Profile after you’ve enabled Forensics for Azure, you may see the following error message which could be due to inadequate permissions.
Storage account not valid for the instance of Azure Blob Storage
Follow these steps to troubleshoot this issue.
- Create an Azure service principal using the same APP_ID, PASSWORD, and TENANT_ID that were used when onboarding the Azure instance to Netskope. Run the following command in Azure CLI.
az login --service-principal --username <APP_ID> --password <PASSWORD> --tenant <TENANT_ID>
where,
- APP_ID is the Application (client) ID of the Azure AD application you created for Netskope.
To learn more, see Get the Application ID and Directory ID section in Step 1/3: Configure an Azure AD Application for Forensics.
- TENANT_ID is the Directory (tenant) ID of the Azure AD application you created for Netskope.
To learn more, see Get the Application ID and Directory ID section in Step 1/3: Configure an Azure AD Application for Forensics.
- PASSWORD is the authentication key you created for Netskope.
To learn more, see Get the Authentication Key section in Step 1/3: Configure an Azure AD Application for Forensics.
- APP_ID is the Application (client) ID of the Azure AD application you created for Netskope.
- Verify that you can view the storage account defined in your Forensics profile, in your Azure subscription. Run the following command in Azure CLI.
az storage account list
