So right off the bat, when I log in, I'll see this wonderful dashboard that gives me some interesting metrics at a very high level about how things are operating for the tenant in.
I can see when the last time I imported data from that tenant is I can see kind of some statistics around license usage consume versus total and so on and so forth.
In this example, we will be referencing 3 tenets but you could imagine I might have 10, 15 tenants and can quickly get out of contorl.
And the best part is I can work with them all from one view.
The top, most section of the tool here are broken into 3 and represent modules of functionality.
For instance, Microsoft Teams, when we first adopt Teams, we may want to put a plan in place to drive that adoption and see statistics about it over time.
Today's focus will be on analyze and manage, and is really just scratching the surface of what CoreView is capable of.
There are several out of the box reports you can use but we are going to focus on a user report to give you a sense of what these reports look like.
Instantly, you wiI see the standard number of results. We have a variety of things that I can kind of pivot off of to seeing information about this data.
You can add columns to this view and these columns for this particular report are essentially pretty much every Azure AD attribute or custom attribute available, that I can then use as a column to then filter down this report. For instance, if I wanna see all those users that have a hold enabled, I can apply that column.And filter as needed.
Maybe I just wanna see those guys that are on hold and just like that in seconds, I've got a new report.
If I go to this managed tab, I might be able to take some actions, whether that means managing their password, managing the licenses, they have applied revoking user sessions, etc.
I can even execute a workflow for all these items. If need be. I can also schedule these reports to occur on frequency basis of my choice.
Simplest and most straight forward report we have are
You might be asking yourself how can you have a Teams Group without an owner? We commonly see with mergers and acquisitions that workforce reductions take place and users/owners may no longer be with the company get removed from Azure AD and thus removed from the team. But that doesn't destroy the team or archive the team, it just removes that user.
We see a lot of enterprises end up in this kind of situation where you have these orphaned teams. Now those teams may or may not be still usable or applicable to current processes. So you will want to identify these particular teams and then take an action on them and assign an owner or remove it.
With CoreView you can create a workflow that identifies empty teams that kicks them into an approval process to archive or delete those teams. We recommend scheduling this report maybe every week to remain compliant.
Let's take an example that 90 day Teams lifecycle report, to help keep your Microsoft Teams compliance continuous.
We set up a workflow to contact the owners of the teams to get next steps.
Workflow are an easy way to set up some lifecycle management and allow us to take actions from within those reports.
We've all heard about the tale of Microsoft Teams sprawl. Teams sprawl is when a company gets way too many teams, hundreds and hundreds of teams. Remember whenever you first deploy teams, the default experience is that anyone in the organization can create a new team. Anyone, anytime.
And that's not necessarily a bad thing, but it becomes a bad thing when that goes unchecked. And you have literally hundreds, if not thousands of teams sitting out there, maybe doing nothing, maybe just frivolously being created back and forth. So maybe you wanna put some governance protocols around the creation of new teams.
Yeah, absolutely - it's that workflow engine. That workflow engine is an incredibly flexible engine and it really allows for a lot of creativity. Now, if you're asking me about specific use cases, sure.
I might be able to rattle off a couple of particular, you know, onboarding and onboarding obviously, but to me, the, the workflow engine itself is so flexible that it really allows you to put on your thinking hat and get really creative with how you approach it.