(upbeat music)
(audience applauds)
- Hello and welcome to Microsoft Mechanics Live.
Coming up, we'll discuss how Microsoft Teams
is built to ensure a secure
and compliant collaboration environment,
and how you can manage Microsoft Teams
with the controls needed,
while keeping a great experience for your users.
We're gonna share the newest security
and compliance features, such as data loss prevention,
information barriers, and new retention policies.
Then we'll also dig into the controls and tools,
including network planner, Advisor for Teams,
enhanced calling, device management,
and here to show us how, we're joined by Anne Michels
from the Teams group, welcome Anne!
(audience applauds)
- Thank you, it's great to be back!
- Thank you, it's been too long
since you've been on the show.
All right, so we talk a lot on the show
about how Teams really can help everyone
easily access information and collaborate with one another,
but the ability to securely and compliantly manage Teams
is kind of something super important
that's part of the story as well.
Can you share what some of the controls that you use then
as an admin in Teams, and why these are important?
- Absolutely, so as you all know,
Teams gives users the tools they need to work effectively.
But when end users use Teams, it also means
they don't need to use those consumer-grade products
that do not always meet the security
and compliance requirements of your organization.
And that is very important.
We have built Teams so that you can stay in control.
I'm here, in the Microsoft Teams admin center,
and in here, you can manage Teams, messaging policies,
org-wide settings, and much more.
And we continue to add more functionality here
to enable you to more granularly manage the service.
- All right, so can you show us some of the new controls
and capabilities with Teams?
- So let's start with one that I know a lot of you
have been waiting for, private channels.
I am sure you all heard the announcement earlier this week
that private channels are now,
it's generally available in Microsoft Teams.
So here in the admin center, in teams policies,
this is where you can manage what users can do
in channels and in Teams.
And we have added a new global setting
that allows you to enable or disable
the creation of private channels in your tenant.
- All right, so I'm gonna show you what it looks like
from the user perspective.
So, now you can see a couple things here,
indications of private channels.
I'll just zoom in so you can see the lock.
So the lock icon's right here,
and basically, I've got a nice little circle around it,
basically you can see
any time a private channel's been created,
the nice thing is it's really easy to make one of these.
So I'll go ahead and add a channel.
When I do that,
I'm actually given a couple of different options.
I have to give it a name, so I'll just call it demo.
And then we'll go ahead and give it
either a standard or a private demarcation.
Now the nice thing with private
is once I have built this channel,
I can basically invite just the people within a larger team
who need to communicate within that private channel.
So you've got kinda private access
in groups within your teams.
But, now I know that we've added a lot more
in the areas of policy management.
Can you show us what else is new there?
- So, let me jump into PowerShell.
We are adding new policy assignment capabilities.
In the past, when you wanted to assign a policy to a group,
you first had to pipeline it down
to the members of the group,
before you could actually assign the policy.
Now, you can assign a policy to a group
with a single PowerShell command let.
And I know this is a capability
that many of you have been waiting for
because it will save many of you a lot of time scripting.
- Right, and you can get all this, obviously,
from the PowerShell gallery.
You can basically down,
and interject the module that you need.
So, this gives you then the control over the policies,
how they're applied across Teams,
and then the groups that are using automation,
but how do these policies then compare,
'cause we were talking about Teams' policies,
and some things in the Teams admin portal,
with some of the things that we set
through the Microsoft 365 compliance center
or security center?
- So, the way how to think about policies
is that the policies that are specific
to an app or a service, like for example, private channels,
you will configure them in their specialist portal,
like we saw with private channels in the admin center,
right, the Microsoft Teams admin center.
But then for any policies that are across Microsoft 365,
you configure them here,
in the Microsoft 365 compliance center.
Here you can find things like retention, for example.
And the nice thing is when you set a policy here,
you can set it once, and it will directly apply
across all the different apps in Microsoft 365,
including Teams, Outlook, and SharePoint, for example.
Talking about retention,
we have actually added the capabilities,
or enhanced the capabilities that you have here.
You can now create a deletion policy
that is as short as one day.
- All right, so I can see this coming in handy,
especially for things
like privileged information situations,
or mergers and acquisitions, also legal scenarios.
This is a super-handy feature
in terms of having that short retention policy.
- Exactly, and to add to this, earlier this year,
we added data loss prevention
for chat and channel conversations.
So as you all know, we have had DLP
on email and on files for a while,
but now you can also block messages
that contain confidential information.
Here, I'm again, in the Microsoft 365 compliance center,
and I have a policy that blocks any messages
that contain financial information,
like for example, credit card numbers.
Jeremy, why don't you show us
what the end user experience looks like?
- All right, so I'm gonna show you a couple things here.
So here I'm actually logged in,
and I can see that I've tried
to send a social security number,
and you can see that it was blocked.
So I'll just zoom into this.
This time I'll be able to draw a better square
than before I hope.
So we'll go ahead and do that,
and you can see here that because the actual message
contained a social security number, it got blocked.
And you can actually see that, now,
and I can get a nice policy tip here
to see why that was blocked, and I get that here as well.
So I'll cancel out of that.
And if I go into what Nestor saw on his side,
you can see that the message was actually blocked
due to sensitive content.
So he gets a notification effectively
that I've sent something, but it's actually indicated,
there was something in there that was sensitive,
and it shouldn't have been sent.
'Cause sometimes people just don't have that filter,
in terms of knowing what the right thing is to send in chat.
And a lot of times, chat seems like a very familiar,
kind of easy-going place,
but you still don't wanna send things
like credit card information, or social security numbers,
or ID numbers over that as well.
But now, sensitive information can be flagged
for both files, as well as chat.
So you can also get roll-up reports,
and you can also do some really pretty cool things
in terms of things like Safe Links as well, as part of this.
Safe Links is actually part of Teams as well,
and it will flag you
just like Safe Links would do in Office.
And basically you have the ability
to get links that aren't safe blocked
through the experience there as well.
It's all part of advanced threat protection,
part of Office 365, it's gonna protect users
from opening malicious links.
Now what else can we do
in terms of protecting Teams' information?
- We've delivered another highly-requested capability
called information barriers,
which prevents certain internal teams
from communicating with each other.
- All right, so, when would I need something
like information barriers?
- So let me give you an example.
- Okay. - Sometimes you need
to limit information sharing
between certain segments of a business.
- Right. - That is often the case
because you need to adhere to ethical walls,
regulations, or industry standards.
For example, you might be a bank,
and you cannot have your financial advisors team
talk to the merger and acquisitions team.
And that is exactly what we prevent here with this script.
- Okay, so one of the things I can do then as a user.
So let me go into chats here,
and I'm gonna try to actually chat with Alex.
He's actually a suggested member and participant,
and he's in my directory obviously, 'cause it's Alex.
He's in another segment that I'm not allowed to chat with.
So I can see here, that I'm actually not allowed,
by a policy, to talk to Alex.
You can see I've got a nice policy statement again.
And the other thing is if I wanted to go into a team, say,
and add Alex into that team, then if I'm gonna manage that,
and we'll go ahead and try to add member of Alex.
So we'll go ahead and try that out.
And Alex won't be able to be added to the team,
we'll see here in just a second, there we go.
Unable to add the user
due to the admin settings that we have.
So now even though Alex is in the same group,
it's not going to work.
Now if I cancel out of that one,
but try to just join somebody else who's in my segment,
so we'll try Joni Sherman, we'll add her to the team,
and this is gonna actually work in this case,
unless she's already been added.
She hasn't been, so I can add her to the team
as a member or an owner, as you'd expect.
Closing out, she's actually part of the team.
So you can see, selectively,
depending on the segment the user's in,
I'll actually be able to add some people
that are in my segment and not add others,
if they're part of a barriered-off segment effectively.
- And it doesn't just work
in channel and chat conversations,
we are also working on bringing information barriers
to files in Teams.
So not only will your chats be protected,
but also the SharePoint files
attached on the Team SharePoint.
So if a user then tries to share a file in Teams,
information barriers will block that,
according to the policy.
- Right, and this is a really great capability.
It's available across Teams, and also SharePoint.
So, if you want to, let's shift gears
and go to one of my favorite topics, deployment.
I know we're doing a lot there in order to
streamline getting Teams rolled out and deployed,
specifically for folks
that are coming from Skype for Business.
Can you tell us what's new there?
- So for those of you who are on that journey,
we've added a few more options.
Here you can see the controls that you have
as you make your transition.
As you can see, there are now five options
to help you control the level and pace
of your organization moving to Teams.
We have added two new coexistant modes recently.
You can now, for example,
continue to use Skype for Business for meetings,
and use Teams for group collaboration only as a first step.
- Right, and now we actually have more options
in terms of different types of organizations
that are out there.
I know a lot of people are transitioning
from PBX systems to Teams,
and adding Teams' devices as well.
So what's new on the device management front?
- Microsoft phone system is now even better.
We have delivered over 10 updates in the last three months,
and this includes things like enhanced delegation
and reverse number lookup.
Check out the new phone system
administration experience here.
A lot of these capabilities,
they will actually probably look familiar to you,
because we have brought them over
from the Skype for Business admin center.
But we have also added a couple of new ones,
like for example dynamic emergency policies.
- Right, but you mentioned something
I think near and dear to a lot of people,
meeting room devices.
Now, setting up these rooms and really keeping them running
can be challenging, right?
- Right, but it shouldn't be.
And that's why you will soon be able
to manage your Teams Rooms' devices
directly from the admin center.
From assigning configurations, to restarting devices,
and monitoring updates.
You will have access to all the key configuration tools
that you need, directly from here.
- So, basically what you're saying here
is things like the room system summary,
the quality that we have, all the different rooms that,
what they have in terms of devices and manufacturers,
the models, whether or not they're healthy, all of that.
So my favorite column
is actually over here in the health status,
to see how these things are running.
So, really awesome stuff,
in terms of giving you that visibility
across the different rooms that you have configured.
But what other tools then do we have to help onboard Teams?
- So one of the areas that you need to think through
when you provision Teams, is bandwidth.
And, to help you with that,
we just introduced network planner,
which is currently in public preview.
With network planner, you can get an idea
of required bandwidth consumption for your organization
when you move to Teams.
As you can see here in the report,
network planner calculates requirements for deploying Teams
across physical locations of your organization.
- And one of the other things that you can do,
in terms of the process of deploying Teams,
the desktop client apps, or the desktop apps,
thanks to the work that we've done with Microsoft Teams
and kind of including it
as part of the Office deployment packages,
it's actually Click-to-Run based as well.
It's part of the Click-to-Run tool set.
So here, with the Office customization tool,
you go to config.office.com.
And by the way, all of the current apps are there,
and as you'd expect, you have the ability then with Teams
to add that as part of your package, as it's on by default.
One thing to note here is when you select an update channel
for the semi-annual channel itself,
it's gonna have, as of January 2020,
it'll be part of the standard install,
and also the updates for semi-annual channel for Office.
So, we've published an entire series actually
on Microsoft Mechanics, it's five parts.
If you go to aka.ms/officeITseries,
it'll explain everything about Click-to-Run,
how to configure it, how to troubleshoot it,
everything that you'll wanna know,
and how it even uses that within your config manager
or in-tune environments to get it deployed.
So, it's a pretty good round of updates,
but is there anything else that you can add,
in terms of additional capabilities?
- Yes, we are also releasing,
in public preview, Advisor for Teams.
And Advisor for Teams is a new onboarding tool
that helps you bring your project team together
to plan the best possible deployment
of Teams in your organization.
Advisor for Teams gives you a shared collaboration space,
of course in the form of a team, and recommended plans.
So basically step-by-step guidance that walks you through
how to best deploy the core team's workloads
in your organization.
- Right, and this is a really great set of updates.
And I like how we're thinking
across all the major admin areas to improve Teams,
but, where should I go to learn more?
- So if you want to go learn more,
go to aka.ms/SuccessWithTeams.
This is where you can find videos, but also best practices,
and, most importantly, technical documentation.
- Right, and we're also building
an entire "Microsoft Teams for IT" series
on Microsoft Mechanics that are gonna cover the foundation,
it'll cover Skype to Teams,
it'll cover security and compliance,
all coming later this fall.
So stay tuned for updates there.
Go to Microsoft.com/Mechanics,
hit subscribe if you haven't already.
That's all the time we have for today's show.
Thank you for watching, and we will see you next time.
- [Anne] Thank you.
(audience applauds) (upbeat music)