[MUSIC]
>> I'm joined here with some very special guests.
It's time to learn more about how you can
build multi-Cloud compliance applications.
Joining me is Anne Raheem,
Program Manager at Microsoft,
and Hammad Rajjoub,
Director of Product Marketing at Microsoft.
It's nice to have both of you with us.
>> It's so great to be here.
>> Thank you so much for having us.
>> Let's start with the why.
Can you tell us why
multi-Cloud compliance is so important?
>> We know the vast majority of our
customers have multi-Cloud strategies.
Our customers are looking to reason over
their entire data landscape and not just Microsoft data.
They also want to integrate
Microsoft compliance solutions with
their existing investments into security,
compliance, and identity-related systems.
We're also getting from our developers
that there's a need to bring
Microsoft compliance value to non-Microsoft sources.
That's why we're building
compliance platform as extensible.
We see this as a horizontal capability,
and you all, developers, as a key enabler of this.
>> What are some of the ways that
our customers and developers can
enable multi-Cloud compliance using Microsoft Graph APIs?
>> Absolutely. There are multiple dimensions to that,
a couple of key areas that I want to
share with you all here,
is that, number one, is the multi-Cloud
data access to enable
our customers to reason over their entire data landscape
including Microsoft and non-Microsoft systems,
we have data connector platform.
We have 40 plus, ready-to-use,
built-in connectors available in
the Connector Gallery today,
and, of course, there are many more to come.
For in-place compliance value
across structured and unstructured data,
we have Azure Purview that allows us to bring
compliance value to multiple Cloud data repositories,
such as Amazon's AWS S3 buckets.
We also have multiple migration tools and such,
and that all enables all of
the multi-Cloud data capabilities that we talked about.
The other piece to that is APIs and SDK,
and developers love APIs and SDKs.
To enable system-level integrations,
we have a number of Microsoft Graph APIs
that cut across scenarios,
such as data loss prevention,
advanced eDiscovery, archiving solutions, and such.
All of those APIs are available under Microsoft Graph.
On top of that, of course,
we have Microsoft Information Protection SDK,
or MIP SDK as we call it,
that enables various compliance scenarios,
such as data classification
and governance-related capabilities.
That's available to our developers to use and
build those multi-Cloud applications.
>> Amazing. What is the latest innovation
that we are announcing for compliance in the ecosystem?
>> We're so excited to introduce built-in compliance for
enterprise app data ingested
through Microsoft Graph Connectors.
Utilizing Graph Connectors is a powerful way to surface
your app data across the Microsoft 365 ecosystem.
Participating in experiences like enterprise search,
intelligent discovery, and, of course,
compliance across Teams, Office, and more.
Notably, these are not multiple integrations,
but one to power multiple experiences.
With this single integration,
our app partners could have their content
show up in the same way that
Microsoft 365 content would show up in these experiences.
One of the great benefits of adjusting
your content into Graph Connectors
is easily lighting up
Microsoft Compliance in order to protect your app data.
The first product, we're so
excited to announce an offer to
all customers who ingest their apps through
Microsoft Graph, is Advanced eDiscovery.
Advanced eDiscovery is
a powerful tool allowing you to take
control of your data in
the case of any legal investigation.
Through ingesting your app data in the Graph,
you can also light up Advanced eDiscovery.
Enterprise customers often require
Advanced eDiscovery capabilities
for anything from litigation,
internal investigation, insider threat,
data spillage, and so much more.
All of these can trigger the need for
a legal investigation to know who knew what when.
In these cases, Advanced eDiscovery can empower
you to collect and review
your app data when you need it most.
>> Wow, that sounds really great.
What can our developers do to benefit from it?
>> Of course, well, first,
build a Graph Connector to bring your app data
into the Microsoft 365 ecosystem.
You can find more info at aka.ms/graphconnectors.
When you build a Graph Connector,
we encourage developers to add as
many labels that are applicable to your data,
including the relevant security and compliance
labels to light up the Advanced eDiscovery experience.
Then build a rich preview of
your content in Advanced eDiscovery using adaptive cards.
We're so excited to see your app data be ingested in
Graph Connectors and to offer you
this new service of Advanced eDiscovery.
Wondering how you could benefit from
Advanced eDiscovery in your Graph ingested data?
I'll show two example scenarios
to illustrate this new capability.
First, eCare Vault, one of our app partners.
They're a safe and secure care coordination platform
used by schools to help
coordinate healthcare for their students.
Schools submit referrals to refer their students
to get care from external healthcare providers.
Those referrals must be acted on in
a certain time period in order
for students to receive care quickly.
An example: legal investigation.
We would like to see all the referrals made by
a particular school to see all of them.
Since eCare Vault is already ingested into the graph,
you can easily access and collect and review that data
in order to quickly act on this case
right in the Advanced eDiscovery workflow.
Let me give you another example scenario
highlighting another adapt app partner, Adobe Sign.
Adobe Sign allows you to easily send documents
with certified delivery right within Teams.
Adobe Sign is available in Teams as
an app partner ingested through Microsoft Graph.
In this scenario, let's explore using
Teams and Adobe Sign to help empower clinical trials.
For example, a doctor is explaining
a potential vaccine trial via Teams
to a patient who's considering participating in one.
Once they've reached a consensus,
the patient can sign a patient consent form
to participate in the trial right in Teams.
When required, a compliance admin could use
the Microsoft 365 Compliance portal as a single pane
of glass view to manage Microsoft
365 data sources and
our app partner data sources as well, like Adobe Sign.
In the Advanced eDiscovery review set,
we can see our Adobe Sign content like the consent form
showing up right alongside
conversations from Exchange and Team,
as well as files from OneDrive and SharePoint Online.
>> Wow, this is exciting stuff.