Verify
Once deployed, these steps will ensure everything is correctly configured and healthy. There is a section on troubleshooting common problems at the end.
One component installed as part of the solution is the administration website. It’s used to check the basic status of the system and enable deep analytics for Teams if that’s wanted.
Go-to the root address of your app service (as seen from the portal):
If the runtime authentication settings are correct, you’ll be able to login to your app-service & see the status website:
Next up: limiting access to this website.
Depending on your company directory policies, this website may be accessible to anyone with a valid login on the same directory. We recommend you limit access to this site to just specific users that administer the analytics solution.
Here you can set whether only specifically assigned users should have access to the web application or anyone in the organization. We recommend limiting the access to specific administrators:
We need to verify that data is being imported successfully into the SQL database from the two web-jobs.
- In the Azure Portal, under the App Service -> "web-jobs" blade you should see two web-jobs "AppInsightsImporter" and "Office365ActivityImport".
-
They should both say "running".
-
You can click "logs" to open a new tab/window & see the web-job logs to determine any errors.
-
Both web-jobs print their configured values at start-up, so verify these settings if there are any errors.
-
The AppInsightsImporter should look something like this on a good start-up:
The Office365ActivityImporter job should report something like this if it is working fine:
These logs are also available at C:\home\data\jobs\continuous on the app service if you want to look at the full log.
For more logging info, please check Application Insights trace logging– see more info at Monitoring.
At this point, the data-processing part of Office 365 Advanced Analytics Engine is setup!