Data Collection Scope

OfficeExpert collects data continuously from the environment and stores it in the virtual appliance's data warehouse. This ensures that the data collected stays available even after server logs have been cleaned up on Microsoft servers. In general, data collection depends on your license:

OfficeExpert Teams Analytics includes:

• Azure interactive sign-in events
• Microsoft Teams data  
• Overall usage data of other Office 365 workloads
• License and subscription data
• Services communication data
  
  
• Graph API Data: Azure Audit Logs, MS Teams (Teams, Channels, Members, Apps, ...), MS Graph Activity Reports, Azure AD (Users and Groups) incl. all attributes
  Graph App permissions: ChannelMessage.Read.All, Reports.Read.All,ServiceHealth.Read, Directory.Read.All, Group.Read.All, AuditLog.Read.All
  
  
  Azure AD User Objects:  All available attributes are retrieved (e.g. Department, Location, ...).
  
  
  
• Mail Analytics:
  Message Trace information is retrieved via the following path:  https://docs.microsoft.com/en-us/previous-versions/office/developer/o365-enterprise-developers/jj984328(v=office.15)
  This requires an account with Exchange admin role.

OfficeExpert Appliance needs to have outbound access to the following URLs:

docker.panagenda.com   (required for online update)
dataminer.panagenda.com    (required for online update)
graph.microsoft.com 
login.microsoftonline.com  
manage.office.com
*.office.com

OfficeExpert Ops Analytics (End User Experience) includes:

• MS Teams Simulation
• MS Exchange Simulation
• MS SharePoint Simulation
• MS OneDrive Simulation
• MS Skype for Business Simulation
• Azure AD Connect Server
• Active Directory Federation Services
• Data sources: Quality of service bots (Skype, Sharepoint, OneDrive, Exchange, network simulations), on-premises server monitoring (Win Services, performance counters), Azure Sync Simulation, Office 365 Service Health, Azure AD (users and groups), mailflow simulations
  
  
  

Information is collected for all available services specified during configuration/setup. For more details please refer to the Setup Guide.

Time Constraints

How often a data collection task runs depends on the kind of data and its source: 

• Data collection every 15 minutes:
  • Server Monitoring and Services communication data feeds
    
    
• Data collection once a day:
  
  • MS Graph Activity Reports, Azure AD, Office 365 Service Health, and on-premises monitoring: data collection feed starts to run at 12:00 am local time
  • MS Teams data: data processing depends on results of particular feeds. Thus feeds run staggered starting from 6:30 pm until around 12:00 am local time
  • Azure Audit Logs: data feed run every 60 minutes
  • Mail Message Trace: data feed run every 60 minutes
• Custom intervals:
  
  • Quality of service bots: intervals for data processing feeds are defined during bot setup
  • Azure Sync Simulation: depends on the centrally configured Azure synchronization cycle. The Cycle Count Threshold can be defined in simulation settings
  • Mailflow simulation: interval can be defined in simulation settings

Related Topics:

User Guide Navigation: