CoreView 20.09 was released October 22, 2020. Thanks for your ongoing feedback, we continue adding your requests to the product! Here’s a summary of the main features:
Improved Governance for Microsoft 365 (M365)
CoreView allows tracking of specific governance objectives, such as monitoring threshold for compliance, enforcing configuration settings that offer higher protection than the defaults, and alerting on undesired situations.
- Monitoring of thresholds and enforcement of configuration settings can be set up in CoreAdmin as KPIs – Key Performance Indicators – and track to the settings that your organization wants to track. They can be established from templates and continuously monitored through a KPI Dashboard, which now includes a KPI Score to make it even easier to assess where you are, compared to where you want to be. Not were someone else told you need to be, but where you have decided you want to be.
Any of the CoreView data in any reporting is exportable asynchronously – thousands of data elements can be exported to a CSV file. Amongst that data, either on reports or exportable, now that is Audit data automatically includes the username (UPN from the object, plus department, country …). This is unlike Microsoft alerts or other Microsoft-supplied audit data, where it is nearly impossible to tell the specific user, since the username is not included in the Microsoft-supplied data. With CoreView, the user name is displayed clearly and automatically in the Audit section of portal.
When it comes to tracking subscription history in license reports, CoreView now provides greater clarity by adding a new field – a new Metadata Note field – that can be added to the Subscription history and provide context and enables organization-specific notes to be saved on user records. This field can be required, as desired. This is in contrast to a list of subscriptions from Microsoft, without the ability to annotate and utilize the information for organization-specific goals.
When it comes to managing Microsoft 365, CoreView not only splits a M365 tenant into virtual tenants and provides granular and clear RBAC – Role Based Access Control – for the functions that each Operator is given. This delegration of the M365 Admin role offers many protections, but also much efficiency for day-to-day tasks. New features include:
- Short-cut for setting up and assigning phone numbers for users – CoreView can assign the next available phone number by default or assign the first available number with a particular prefix after the Operator has typed a few numbers.
Core TeamsAnalytics capabilties recently added the ability to report on Call Quality, whether through Teams or through a standard PSTN telephony network. In addition to metrics, CoreView now provides the Operator and Administration with Call Queue and Auto Attendant reports. These details are easily viewed in the GUI by clicking on the category on the left, and include the ability to create, edit or delete this information and change the structure of call queues, music on hold, etc. all ina single place. Thus a caller can be auto forwarded to the right dept. These structures can be created and viewed within CoreView without needing to go to any Microsoft report or console.
CoreView also provides actions that enable operators to easily create, edit, or delete Distribution groups. Newly added to Distribution group configuration are the Delivery Management and Message Approval sections. These sections enable setting an approval process for a distribution group and who can send messages to this distribution group. Either or both restrictions can be utilized.
Do you want your user to be able to see only a certain group of Addresses? CoreView can now manage and view the Address book policy provided in M365 and enables those policies to be set up with a preferred policy for each Mailbox.
Do you want to track down M365 usage across your users? Do you want to see if your users are using all the E5 apps? Now Microsoft 365 App usage report provides this information, now including when was the last time a particular user actually used a particular M365 app. This is an enhancement from Microsoft and prior CoreView reports because it differentiates between last usage from a desktop app or a browser or from another client device.