WEBVTT

00:00:00.150 --> 00:00:01.585
Ladies and gentlemen,

00:00:01.585 --> 00:00:05.102
please welcome Microsoft's
Executive Vice President,

00:00:05.102 --> 00:00:07.477
Cloud + Enterprise,
Scott Guthrie.

00:00:07.477 --> 00:00:16.122
>> [APPLAUSE]
>> Well,

00:00:16.122 --> 00:00:19.160
good morning, everyone,
and welcome to AzureCon.

00:00:19.160 --> 00:00:22.480
It's great to have so many
people joining us here today.

00:00:22.480 --> 00:00:24.430
Both the audience
here in person, but

00:00:24.430 --> 00:00:27.740
the tens of thousands of people
that I'm told are now watching

00:00:27.740 --> 00:00:28.990
this streamed online.

00:00:28.990 --> 00:00:34.140
I want to give a special
shout out to our Azure MVPs,

00:00:34.140 --> 00:00:37.200
who helped organize more than
70 viewing parties around

00:00:37.200 --> 00:00:40.520
the world, where groups of
people are getting together and

00:00:40.520 --> 00:00:42.020
watching the streaming
event live.

00:00:42.020 --> 00:00:44.220
And we have some really
great content and

00:00:44.220 --> 00:00:47.690
announcements that you'll
hear throughout the day,

00:00:47.690 --> 00:00:50.740
that I think you'll
find pretty exciting.

00:00:50.740 --> 00:00:53.320
I'm going to kick off
this day with a keynote

00:00:53.320 --> 00:00:56.240
providing an end-to-end
view of Azure.

00:00:56.240 --> 00:00:58.691
And then throughout the day
we're gonna have more than 60

00:00:58.691 --> 00:01:01.045
breakout sessions, where you
can go much deeper into all

00:01:01.045 --> 00:01:02.332
of the different technology.

00:01:02.332 --> 00:01:07.313
And in addition to watching our
sessions, you can get hands

00:01:07.313 --> 00:01:12.550
on with Azure with our first
ever AzureCon Challenge.

00:01:12.550 --> 00:01:16.570
Basically, we have 15 activities
that you can go ahead and

00:01:16.570 --> 00:01:21.600
if you complete in the first
24 hours, you earn credits

00:01:21.600 --> 00:01:24.530
that you'll be able to use to
get some pretty cool prizes.

00:01:25.790 --> 00:01:29.870
And in addition to today's event
we're also excited to announce

00:01:29.870 --> 00:01:32.887
our new Azure world tour.

00:01:32.887 --> 00:01:35.460
Where the Azure engineering team
is going to be flying around

00:01:35.460 --> 00:01:38.400
the world to more than
20 different cities,

00:01:38.400 --> 00:01:41.710
hosting free in-person,
all day training events.

00:01:41.710 --> 00:01:45.060
And this is a great way to kind
of get more hands-on with Azure,

00:01:45.060 --> 00:01:49.650
and we're really hoping you can
join us at a location near you.

00:01:51.860 --> 00:01:54.470
So we're in the midst of
a generational shift in

00:01:54.470 --> 00:01:58.040
computing right now, and
it represents major changes for

00:01:58.040 --> 00:02:00.980
everyone, Microsoft included.

00:02:00.980 --> 00:02:04.140
And every organization
over the next few years

00:02:04.140 --> 00:02:07.820
is going to need a strategy for
how they move from where they

00:02:07.820 --> 00:02:10.690
are today to take advantage
of what the Cloud offers.

00:02:11.840 --> 00:02:15.040
And they're going to look to
adopt SaaS-based solutions to

00:02:15.040 --> 00:02:17.368
achieve faster time to value.

00:02:17.368 --> 00:02:20.580
They're going to extend their
infrastructure to use the public

00:02:20.580 --> 00:02:24.012
cloud to take advantage of
better agility and cost savings.

00:02:24.012 --> 00:02:26.270
Increasingly, they're
going to take advantage

00:02:26.270 --> 00:02:29.830
of higher-level services,
like machine learning in our new

00:02:29.830 --> 00:02:34.290
Cortana Analytics Suite, to
engage better with customers and

00:02:34.290 --> 00:02:36.720
be able to reinvent
business processes.

00:02:36.720 --> 00:02:40.230
And it's really the combination
of all these three things

00:02:40.230 --> 00:02:43.130
that enable real business
transformation, and

00:02:43.130 --> 00:02:46.240
all of us are here today
are uniquely positioned

00:02:46.240 --> 00:02:47.440
to deliver on this together.

00:02:49.110 --> 00:02:52.600
Microsoft now offers
the most comprehensive

00:02:52.600 --> 00:02:57.210
suite of business SaaS solutions
out there, between Office 365,

00:02:57.210 --> 00:03:00.730
Microsoft Dynamics,
and Power BI.

00:03:00.730 --> 00:03:04.010
We really have kind of a wide
spectrum of capabilities that's

00:03:04.010 --> 00:03:06.700
deployed and
used by more business users

00:03:06.700 --> 00:03:09.290
than any other business
SaaS solutions.

00:03:09.290 --> 00:03:10.660
And with our
Enterprise Mobility Suite,

00:03:10.660 --> 00:03:13.970
we now have the ability for IT
to securely deliver and manage

00:03:13.970 --> 00:03:17.920
these solutions, as well as more
than 2,600 other SaaS based

00:03:17.920 --> 00:03:22.780
applications from non-Microsoft
companies across any device.

00:03:22.780 --> 00:03:25.300
And do it in a way that doesn't
compromise the end user

00:03:25.300 --> 00:03:29.120
experience, while still
keeping their company secure.

00:03:29.120 --> 00:03:32.900
And with Azure, Microsoft offers
a comprehensive set of cloud

00:03:32.900 --> 00:03:35.370
infrastructure in higher
level services and

00:03:35.370 --> 00:03:38.640
tools that enable organizations
to become more agile and

00:03:38.640 --> 00:03:41.320
differentiate their
businesses even more.

00:03:41.320 --> 00:03:44.080
No other company out there
offers the breadth and

00:03:44.080 --> 00:03:47.400
the depth of what the Microsoft
Cloud Platform delivers.

00:03:47.400 --> 00:03:49.360
AWS does infrastructure, but

00:03:49.360 --> 00:03:51.600
doesn't offer SaaS
based offerings.

00:03:51.600 --> 00:03:54.880
Companies like SalesForce have
SaaS, but no infrastructure or

00:03:54.880 --> 00:03:56.480
higher level services.

00:03:56.480 --> 00:04:00.420
And the combined capabilities
of all of these different things

00:04:00.420 --> 00:04:04.220
really enable organizations
to be more agile,

00:04:04.220 --> 00:04:07.960
to really lower their costs, and
ultimately differentiate and

00:04:07.960 --> 00:04:09.400
really transform
their businesses.

00:04:10.840 --> 00:04:12.760
And we not only offer
these capabilities, but

00:04:12.760 --> 00:04:15.110
we do so at hyper-scale.

00:04:15.110 --> 00:04:18.552
These blue circles here on
the map represent Azure regions,

00:04:18.552 --> 00:04:21.790
which are made up of clusters
of data centers where you can

00:04:21.790 --> 00:04:25.098
deploy your code and deliver
your solutions closer to your

00:04:25.098 --> 00:04:27.612
customers and
employees than ever before.

00:04:27.612 --> 00:04:32.290
We now have 24 Azure
regions around the world.

00:04:32.290 --> 00:04:36.500
Put that in perspective, that's
more AWS and Google combined.

00:04:36.500 --> 00:04:40.430
And I'm very excited to announce
today, the general availability

00:04:40.430 --> 00:04:43.990
of three more new Azure
regions in India.

00:04:43.990 --> 00:04:46.897
And Azure's the first
hyper-scale cloud offering

00:04:46.897 --> 00:04:49.480
that's delivering cloud
services in India.

00:04:49.480 --> 00:04:52.854
And we're doing it in three
separate locations across

00:04:52.854 --> 00:04:56.665
the country and as of today, you
can now go sign up for Azure and

00:04:56.665 --> 00:04:59.673
deploy your applications and
solutions there,

00:04:59.673 --> 00:05:01.970
all backed with our
Enterprise SLA.

00:05:01.970 --> 00:05:08.406
>> [APPLAUSE]
>> Now Microsoft

00:05:08.406 --> 00:05:12.101
is one of really only three
hyper-scale cloud providers out

00:05:12.101 --> 00:05:14.090
there in the world.

00:05:14.090 --> 00:05:15.740
And unlike the other two,

00:05:15.740 --> 00:05:19.010
we're unique in that
we enable solutions

00:05:19.010 --> 00:05:23.020
to be deployed not just in our
hyper-scale cloud regions,

00:05:23.020 --> 00:05:27.190
but also in customer and service
provider data centers as well.

00:05:27.190 --> 00:05:30.330
And with our Azure stack
offering, we basically now

00:05:30.330 --> 00:05:33.680
enable you to stand up
a consistent cloud experience.

00:05:33.680 --> 00:05:35.938
That it enables the same
management API,

00:05:35.938 --> 00:05:39.227
the same management portal, and
the same developer APIs and

00:05:39.227 --> 00:05:41.826
experiences as in our
full public cloud Azure.

00:05:41.826 --> 00:05:44.042
And this provides customers and

00:05:44.042 --> 00:05:49.030
partners maximum flexibility as
they journey to use the cloud.

00:05:49.030 --> 00:05:52.170
And enables them to use
a common set of skills and

00:05:52.170 --> 00:05:53.500
assets along the way.

00:05:55.280 --> 00:05:57.520
Now, Azure also
enables customers and

00:05:57.520 --> 00:06:00.910
partners to use the best of
the Windows ecosystem and

00:06:00.910 --> 00:06:03.950
the best of the Linux
ecosystem together.

00:06:03.950 --> 00:06:07.670
We now provide more than 3,400
different applications and

00:06:07.670 --> 00:06:10.740
solutions from a broad
range of partners

00:06:10.740 --> 00:06:12.840
using our Azure Marketplace.

00:06:12.840 --> 00:06:17.420
And this enables both developers
and IT professionals to use

00:06:17.420 --> 00:06:20.260
all of the tools that they're
already familiar with and

00:06:20.260 --> 00:06:22.920
really deliver world class
solutions as a result with them.

00:06:24.350 --> 00:06:27.670
Now some of these solutions are
going to be standalone projects.

00:06:27.670 --> 00:06:30.520
But we also expect many others,
especially going forward in

00:06:30.520 --> 00:06:32.270
the future,
to be ones where you extend and

00:06:32.270 --> 00:06:36.285
integrate your own custom
applications with existing

00:06:36.285 --> 00:06:39.490
SaaS-based solutions that you're
also taking advantage of.

00:06:39.490 --> 00:06:42.795
And we're investing deeply in
enabling great extensibility

00:06:42.795 --> 00:06:45.917
with Office 365, Microsoft
Dynamics, and Power BI.

00:06:45.917 --> 00:06:47.081
And additionally,

00:06:47.081 --> 00:06:50.440
we're also investing heavily
to connect non-Microsoft

00:06:50.440 --> 00:06:53.522
SaaS offerings like Salesforce,
box, and others,

00:06:53.522 --> 00:06:57.530
so that you can build solutions
easily with them on Azure.

00:06:57.530 --> 00:07:00.471
I really think Azure will
provide the best cloud platform

00:07:00.471 --> 00:07:03.290
for building and hosting
these kinds of extensions and

00:07:03.290 --> 00:07:04.160
applications.

00:07:05.240 --> 00:07:09.003
And needless to say, all of the
capabilities that we build need

00:07:09.003 --> 00:07:12.020
to be built on
the foundation of trust.

00:07:12.020 --> 00:07:15.380
And Microsoft continues to
invest heavily in delivering

00:07:15.380 --> 00:07:19.430
security, privacy, and
transparency initiatives.

00:07:19.430 --> 00:07:23.560
And Azure now has the broadest
set of regulatory compliance

00:07:23.560 --> 00:07:27.660
certifications of any cloud
vendor, enabling you to deliver

00:07:27.660 --> 00:07:29.690
solutions to any
business environment.

00:07:31.070 --> 00:07:34.110
Over the last 12 months,
we delivered more than 600 new

00:07:34.110 --> 00:07:36.920
features and
services across Azure, and

00:07:36.920 --> 00:07:39.548
the pace of innovation
continues to accelerate.

00:07:39.548 --> 00:07:40.640
You're going to see
over the next year,

00:07:40.640 --> 00:07:44.260
in particular, just a tremendous
amount of innovation coming out,

00:07:44.260 --> 00:07:46.530
some of which you'll
see here today.

00:07:46.530 --> 00:07:48.110
As we deliver these
new capabilities,

00:07:48.110 --> 00:07:51.098
we're seeing our usage on Azure
continue to grow dramatically.

00:07:51.098 --> 00:07:55.630
More than 90,000 new Azure
customer subscriptions

00:07:55.630 --> 00:07:58.390
are now being signed
up every single month.

00:07:58.390 --> 00:08:02.230
We now have more than 1.5
million SQL Databases hosted and

00:08:02.230 --> 00:08:04.780
running in production on Azure.

00:08:04.780 --> 00:08:08.400
More than 500 million users,
primarily Enterprise users,

00:08:08.400 --> 00:08:10.940
are now in our
Azure Active Directory system,

00:08:10.940 --> 00:08:14.610
enabling single sign on
consistency across both your own

00:08:14.610 --> 00:08:18.050
custom applications as
well as third parties.

00:08:18.050 --> 00:08:22.440
We have more than 1.5 trillion
IoT event messages now being

00:08:22.440 --> 00:08:25.700
processed every single
month using Azure and

00:08:25.700 --> 00:08:27.850
our new Azure IoT suite.

00:08:29.180 --> 00:08:33.785
We've more than 777 trillion
storage transactions being

00:08:33.785 --> 00:08:38.540
processed per day using
our Azure storage system.

00:08:38.540 --> 00:08:41.260
And what's great is we're seeing
just a wide variety of different

00:08:41.260 --> 00:08:41.960
companies and

00:08:41.960 --> 00:08:44.880
developers taking advantage
of all these capabilities.

00:08:44.880 --> 00:08:48.286
And one of the statistics that
often surprises people is that

00:08:48.286 --> 00:08:51.958
more than 40% of our revenue on
Azure comes now from startups as

00:08:51.958 --> 00:08:55.530
well as from ISPs, building and
selling solutions to others.

00:08:56.950 --> 00:08:58.180
And beyond the great
usage growth,

00:08:58.180 --> 00:09:01.195
we also have just some fantastic
customers that are running

00:09:01.195 --> 00:09:03.110
mission-critical workloads
on Azure.

00:09:03.110 --> 00:09:07.150
And this slide contains just a
few of the logos of enterprises

00:09:07.150 --> 00:09:09.338
who are running
solutions on Azure today.

00:09:09.338 --> 00:09:14.660
More than 80% of
the Fortune 500 companies

00:09:14.660 --> 00:09:17.530
are now taking advantage
of the Microsoft cloud.

00:09:17.530 --> 00:09:20.520
And, we're very fortunate to
have many of these customers,

00:09:20.520 --> 00:09:23.740
who will be actually joining us
on stage throughout the event,

00:09:23.740 --> 00:09:25.860
talking about their
experiences and

00:09:25.860 --> 00:09:28.403
showcasing some of
the solutions that they built.

00:09:28.403 --> 00:09:33.190
You're going to hear, for
example, from jet.com,

00:09:33.190 --> 00:09:36.600
one of the hot startups in
the online retail space.

00:09:36.600 --> 00:09:39.278
From NASCAR,
from Alaska Airlines, from VMob,

00:09:39.278 --> 00:09:42.468
and we're also fortunately to
be joined onstage by Walmart

00:09:42.468 --> 00:09:45.723
who're talking about how they're
using Azure to transform

00:09:45.723 --> 00:09:46.835
their businesses.

00:09:46.835 --> 00:09:50.019
You know one of the things
that makes Azure unique is

00:09:50.019 --> 00:09:52.390
the comprehensive
set of services and

00:09:52.390 --> 00:09:55.514
tools that really enable
you to build great apps.

00:09:55.514 --> 00:09:58.814
And I'm going to spend the rest
of my keynote today Taking

00:09:58.814 --> 00:10:02.046
a closer look at several of
these areas starting with our

00:10:02.046 --> 00:10:04.340
Developer and
Application Platform.

00:10:07.580 --> 00:10:11.820
One of the things that
the cloud gives you is agility.

00:10:11.820 --> 00:10:16.010
The ability to move fast,
respond quickly to customers and

00:10:16.010 --> 00:10:19.320
compete even more effectively
in this global environment.

00:10:19.320 --> 00:10:23.030
And with Azure and our
Visual Studio family of tools,

00:10:23.030 --> 00:10:25.580
we're delivering the services
and tools necessary for

00:10:25.580 --> 00:10:27.310
you to do this even
more effectively.

00:10:28.870 --> 00:10:31.730
Visual Studio Online is
a service that we deliver as

00:10:31.730 --> 00:10:33.650
a SAS based solution for

00:10:33.650 --> 00:10:38.900
Microsoft that enables rich
development lifecycle services.

00:10:38.900 --> 00:10:42.820
It provides version control,
agile planning,

00:10:42.820 --> 00:10:45.710
continuous delivery, and

00:10:45.710 --> 00:10:49.990
application analytics that can
be used by any developer IDE and

00:10:49.990 --> 00:10:52.870
with any programming language or
platform.

00:10:52.870 --> 00:10:55.790
And we now have more than
3.4 million developers

00:10:55.790 --> 00:11:00.225
who have registered with our
Visual Studio Online service and

00:11:00.225 --> 00:11:04.170
were taking advantage of
it to deliver great things.

00:11:04.170 --> 00:11:06.730
And one of the things we focused
a lot on in particular the last

00:11:06.730 --> 00:11:09.370
year is making it a great way

00:11:09.370 --> 00:11:12.940
that you can integrate with
Azure and become even more

00:11:14.380 --> 00:11:18.040
agile as you deliver your
cloud-based solutions.

00:11:18.040 --> 00:11:21.190
So for example, with Visual
Studio Online we now enable you

00:11:21.190 --> 00:11:24.900
to host unlimited private
code repositories for

00:11:24.900 --> 00:11:28.070
free using both Git
as well as TFS.

00:11:28.070 --> 00:11:32.380
Now this means you can basically
check in code with any tool and

00:11:32.380 --> 00:11:36.980
with any language and you get
full change history support,

00:11:36.980 --> 00:11:39.600
code compare,
as well as collaboration tools.

00:11:40.750 --> 00:11:43.855
Visual Studio Online also
enables you now to build your

00:11:43.855 --> 00:11:47.299
code in the cloud using Azure,
as well as run your functional

00:11:47.299 --> 00:11:50.014
unit tasks against that
code once it's built.

00:11:50.014 --> 00:11:52.095
All without having to set up or

00:11:52.095 --> 00:11:57.090
manage your own build server
environment or any custom VMs.

00:11:57.090 --> 00:12:00.290
Using the new build service
capabilities that we released

00:12:00.290 --> 00:12:03.365
just this past summer,
you can now easily set up,

00:12:03.365 --> 00:12:06.135
build pipelines that can
trigger automatically when

00:12:06.135 --> 00:12:09.190
you check in code into any
repository, whether it's

00:12:09.190 --> 00:12:11.985
the code repositories built
individual to you online.

00:12:11.985 --> 00:12:13.695
You can now also point
to external code

00:12:13.695 --> 00:12:15.445
repositories including
ones from GitHub.

00:12:16.545 --> 00:12:19.919
This screenshot here just shows
an example of a canonical built

00:12:19.919 --> 00:12:23.570
pipeline for a programing
environment like .net.

00:12:23.570 --> 00:12:26.960
But you can use it to take
advantage of other languages,

00:12:26.960 --> 00:12:29.378
and other frameworks as well.

00:12:29.378 --> 00:12:31.730
So you can very easily
rearrange your build tasks,

00:12:31.730 --> 00:12:33.540
as well as write custom Bash or

00:12:33.540 --> 00:12:36.150
PowerShell scripts that you
integrate as part of them.

00:12:36.150 --> 00:12:38.924
Here's an example of
a Java build pipeline,

00:12:38.924 --> 00:12:42.363
that's taking advantage of
things like Maven and npm.

00:12:42.363 --> 00:12:46.340
And then, here's an example
of an Android build pipeline.

00:12:46.340 --> 00:12:49.310
We're not only compiling your
Android code in the cloud, but

00:12:49.310 --> 00:12:51.750
you can see, one of
the tasks that we have here

00:12:51.750 --> 00:12:53.540
is an Android code
signing service.

00:12:53.540 --> 00:12:56.290
So we can actually even
sign your code in the cloud

00:12:56.290 --> 00:12:58.930
prior to you submitting
it into an app store.

00:12:58.930 --> 00:13:01.402
And you can even go ahead and
build pipelines for

00:13:01.402 --> 00:13:05.920
your on-premises VMware, HyperV,
or other cloud environments.

00:13:07.340 --> 00:13:10.490
Now Visual Studio Online also
has built-in support for

00:13:10.490 --> 00:13:14.041
what we call load testing, and
allows you to leverage the cloud

00:13:14.041 --> 00:13:17.729
to basically simulate hundreds
of thousands of concurrent users

00:13:17.729 --> 00:13:21.420
hitting your web or mobile
backend before you go live.

00:13:21.420 --> 00:13:22.810
And this enables you to ensure

00:13:22.810 --> 00:13:25.980
that you are really ready to
handle all of the load and

00:13:25.980 --> 00:13:29.060
deliver a great user experience
for your applications.

00:13:29.060 --> 00:13:31.490
Again, all of this can be done
without having to create or

00:13:31.490 --> 00:13:32.890
manage any custom VMs.

00:13:32.890 --> 00:13:35.590
It's as easy as sort of
a click of a button.

00:13:35.590 --> 00:13:37.750
You say how many users
do you wanna simulate.

00:13:37.750 --> 00:13:40.540
What is the traffic pattern that
you wanna go ahead and execute,

00:13:40.540 --> 00:13:43.260
and then it'll go ahead and
automate all of that and

00:13:43.260 --> 00:13:45.620
provide a full stat report for
you.

00:13:45.620 --> 00:13:47.760
So you can go ahead and
see how it's doing.

00:13:47.760 --> 00:13:50.470
And then we also now

00:13:50.470 --> 00:13:53.400
provide built-in release
management support.

00:13:53.400 --> 00:13:55.700
Which enables you to
create policies for

00:13:55.700 --> 00:13:58.160
your development organization,
in particular for

00:13:58.160 --> 00:14:01.340
a team environment, and easily
stand up environments that

00:14:01.340 --> 00:14:04.170
you can use for the various
stages of development.

00:14:04.170 --> 00:14:08.420
And this enables you to both
easily and safely manage

00:14:08.420 --> 00:14:11.320
the deployment of your code
in a very agile way and

00:14:11.320 --> 00:14:14.500
enforce whatever release
policies that you want

00:14:14.500 --> 00:14:15.940
to ensure that high quality.

00:14:15.940 --> 00:14:21.030
And finally, once your app is
live in production you wanna

00:14:21.030 --> 00:14:23.950
make sure you can understand
how it's performing, and

00:14:23.950 --> 00:14:28.320
what is the user experience
of the users hitting it?

00:14:28.320 --> 00:14:30.520
And with our
Application Insights service,

00:14:30.520 --> 00:14:34.310
you now get real-time insights
into how your applications and

00:14:34.310 --> 00:14:35.860
services are doing.

00:14:35.860 --> 00:14:37.855
Both in terms of things
like availability,

00:14:37.855 --> 00:14:38.850
as well as performance,

00:14:38.850 --> 00:14:44.540
as well as in terms of overall
customer usage and satisfaction.

00:14:44.540 --> 00:14:47.670
And what's great is all these
experiences are built in now

00:14:47.670 --> 00:14:50.040
into the Azure Management
Portal, and so

00:14:50.040 --> 00:14:53.540
all of your developers can
easily get access to it and

00:14:53.540 --> 00:14:57.590
basically see these insights in
real time as they're working on

00:14:57.590 --> 00:15:00.360
both building the application,
but

00:15:00.360 --> 00:15:02.220
also then being able to
run it in production.

00:15:02.220 --> 00:15:04.830
And this gives you
really the insight so

00:15:04.830 --> 00:15:08.390
that you can continually
optimize the experience and

00:15:08.390 --> 00:15:12.120
your business results in
a completely integrated way.

00:15:12.120 --> 00:15:15.437
Now one of the great services
that we see that people

00:15:15.437 --> 00:15:19.297
are really using from a high
productivity perspective with

00:15:19.297 --> 00:15:21.730
Azure is our Azure App Service.

00:15:21.730 --> 00:15:24.570
This is an incredible
powerful offering

00:15:24.570 --> 00:15:27.990
that we released earlier this
year and it provides a suite of

00:15:27.990 --> 00:15:32.530
capabilities that enable you to
easily build and scale web and

00:15:32.530 --> 00:15:35.310
mobile solutions anywhere
around the world.

00:15:35.310 --> 00:15:40.260
It has built in support for
.NET, for Java, for Node.js,

00:15:40.260 --> 00:15:44.650
PHP, and Python, and it
provides auto patching support,

00:15:44.650 --> 00:15:46.570
enabling you to focus
more on your apps,

00:15:46.570 --> 00:15:49.770
as opposed to having to worry
and manage your infrastructure.

00:15:49.770 --> 00:15:52.050
It provides built in
auto scaling support, so

00:15:52.050 --> 00:15:53.650
you can automatically
spin up and

00:15:53.650 --> 00:15:57.810
spin down more VMs and resources
to back the application

00:15:57.810 --> 00:16:01.330
depending on the load of
the service in production.

00:16:01.330 --> 00:16:04.900
It also has built in integration
with existing apps, both SASS

00:16:04.900 --> 00:16:07.770
based solutions running in the
cloud and a whole bunch of built

00:16:07.770 --> 00:16:10.630
in connectors that enable you
to easily integrate security

00:16:10.630 --> 00:16:12.250
as well as data with them.

00:16:12.250 --> 00:16:14.940
And then also now has built in
support allowing you to reach

00:16:14.940 --> 00:16:18.790
back on premises and connect to
existing systems that you might

00:16:18.790 --> 00:16:19.900
already have deployed there.

00:16:19.900 --> 00:16:22.810
And then the beauty is that it
integrates seamlessly with both

00:16:22.810 --> 00:16:26.760
Visual Studio Online as well as
other services like GitHub and

00:16:26.760 --> 00:16:30.760
Bit Pocket, enabling a
continuous employment experience

00:16:30.760 --> 00:16:33.140
that enables you to
be super agile and

00:16:33.140 --> 00:16:35.900
super flexible as you
do your development.

00:16:35.900 --> 00:16:38.920
We have more than
350,000 developers now

00:16:38.920 --> 00:16:42.580
running apps in production
using our Azure App Service and

00:16:42.580 --> 00:16:45.530
we're fortunate to have many of
them joining us at today's event

00:16:45.530 --> 00:16:47.160
sharing their experiences.

00:16:47.160 --> 00:16:51.220
You'll see many of them join
many of the talks today

00:16:51.220 --> 00:16:54.110
going into more detail about
what they've done and then

00:16:54.110 --> 00:16:56.860
also some of their experiences,
and some of the learnings

00:16:56.860 --> 00:17:00.400
in terms of how they've
updated their team to do it.

00:17:00.400 --> 00:17:03.870
Both NASCAR and Alaska Airlines
in particular, we are talking

00:17:03.870 --> 00:17:07.590
depth about the solutions
they've built in Bill Staples

00:17:07.590 --> 00:17:10.740
talk, which is right after
the end of my keynote.

00:17:10.740 --> 00:17:12.650
They are using Azure
apps service and

00:17:12.650 --> 00:17:16.440
Azure to build both customer
as well as employee-basing

00:17:16.440 --> 00:17:19.400
solutions that they
host on Azure.

00:17:19.400 --> 00:17:21.675
And both of them have a web and
mobile experience,

00:17:21.675 --> 00:17:24.274
which is one of the nice things
about Azure App Services it

00:17:24.274 --> 00:17:25.593
enables them to build both.

00:17:25.593 --> 00:17:28.756
And they both have to integrate
with existing on-premise

00:17:28.756 --> 00:17:32.260
applications and systems
of record that store data.

00:17:32.260 --> 00:17:34.920
And so it's a great example
of how you can take what you

00:17:34.920 --> 00:17:37.850
already have on-prem,
extend it in the cloud, and

00:17:37.850 --> 00:17:39.940
really open up new
business experiences.

00:17:41.640 --> 00:17:44.590
The other logo here on
this slide is jet.com.

00:17:44.590 --> 00:17:48.940
They launched just a few
weeks ago, and they're really

00:17:48.940 --> 00:17:52.640
disrupting the online retail
experience in a pretty big way.

00:17:52.640 --> 00:17:55.280
A fantastic startup with
very bold ambitions,

00:17:55.280 --> 00:17:58.780
to reach $20 billion
of revenue in 2020 and

00:17:58.780 --> 00:18:02.830
they've built their whole
experience on Azure.

00:18:02.830 --> 00:18:06.310
And what I'd like to do
is invite Mike, who's

00:18:06.310 --> 00:18:09.930
the CTO of Jet, on stage here
to talk about their experiences,

00:18:09.930 --> 00:18:12.750
what they've built, and
how they're running on Azure.

00:18:12.750 --> 00:18:13.522
Here's Mike.

00:18:13.522 --> 00:18:17.634
>> [APPLAUSE]
>> Thanks very much Scott.

00:18:17.634 --> 00:18:21.169
Hi everyone, so before I talk
a little bit about how jet used

00:18:21.169 --> 00:18:24.493
Azure to build the technology
to support our platform,

00:18:24.493 --> 00:18:27.340
let me talk a little bit
about jet the business.

00:18:28.740 --> 00:18:31.150
jet is a new type
of e commerce site

00:18:31.150 --> 00:18:33.870
that gives customers the
smartest way to shop millions of

00:18:33.870 --> 00:18:35.970
products across
hundreds of categories,

00:18:35.970 --> 00:18:37.920
everything from paper
towels to headphones.

00:18:38.940 --> 00:18:40.080
And I say the smartest way,

00:18:40.080 --> 00:18:42.440
because that's the real
genius of jet.

00:18:42.440 --> 00:18:46.250
Although our prices start low,
they get even lower as you shop.

00:18:46.250 --> 00:18:48.640
As you start adding items
to your basket on jet,

00:18:48.640 --> 00:18:50.040
you'll see your
savings increase.

00:18:51.148 --> 00:18:52.420
Now typically e commerce sites

00:18:52.420 --> 00:18:54.322
are not designed to help
customers save money.

00:18:54.322 --> 00:18:57.440
And in an actual fact they often
direct customers to products

00:18:57.440 --> 00:19:00.430
that are very inefficient
to fulfill at the back end.

00:19:00.430 --> 00:19:02.730
Ultimately those costs have
to get paid by someone and

00:19:02.730 --> 00:19:05.530
that someone is
generally the customer.

00:19:05.530 --> 00:19:07.400
That's the problem,
that we solved at jet?

00:19:09.480 --> 00:19:11.220
We've built a range
of technologies and

00:19:11.220 --> 00:19:13.780
tools that are really focused
on saving our customers' money.

00:19:14.910 --> 00:19:17.860
The most exciting of things
is our Smart Cart technology,

00:19:17.860 --> 00:19:20.950
which evaluates, in real time,
billions of permutations,

00:19:20.950 --> 00:19:23.920
in order to surface the most
economically efficient product

00:19:23.920 --> 00:19:25.470
for any individual
customer's cart.

00:19:26.780 --> 00:19:30.570
As a simple example, imagine
that you have a baseball in your

00:19:30.570 --> 00:19:34.150
shopping cart and now you wanna
shop for a baseball glove.

00:19:34.150 --> 00:19:37.900
Our Smart Cart technology will
run all those permutations and

00:19:37.900 --> 00:19:40.580
will find the baseball
glove that can ship

00:19:40.580 --> 00:19:42.290
along with the baseball.

00:19:42.290 --> 00:19:44.140
Obviously, this results
in fulfillment and

00:19:44.140 --> 00:19:45.600
supply chain savings, and

00:19:45.600 --> 00:19:47.860
these savings are what jet
passes on to his customers.

00:19:49.250 --> 00:19:50.637
In addition to that we have
other options to help our

00:19:50.637 --> 00:19:51.292
customers save money.

00:19:51.292 --> 00:19:53.772
For example, you can wave
your right to return or

00:19:53.772 --> 00:19:56.736
wave your right free returns
rather or you can choose to pay

00:19:56.736 --> 00:19:59.336
with a type of card that has
low interchange rate and

00:19:59.336 --> 00:20:01.414
jet will again will
pass on the savings.

00:20:01.414 --> 00:20:03.096
So that's Jet's business.

00:20:03.096 --> 00:20:07.283
It's really focused on making
e-commerce more efficient for

00:20:07.283 --> 00:20:08.390
our customers.

00:20:10.490 --> 00:20:12.940
And so a little bit about
Jet's technology and

00:20:12.940 --> 00:20:13.980
how we used Azure.

00:20:13.980 --> 00:20:17.015
We had two very big problems
that we needed to solve when we

00:20:17.015 --> 00:20:20.430
were building the Jet technology
platform, both of which Azure

00:20:20.430 --> 00:20:24.150
was absolutely instrumental
in helping us solve.

00:20:24.150 --> 00:20:25.590
The first one was
time to market,

00:20:25.590 --> 00:20:27.274
and the second one was scale.

00:20:27.274 --> 00:20:32.200
At Jet we knew we had about
12 months to build the 20 or

00:20:32.200 --> 00:20:35.030
so major pieces of software
that are needed to run the Jet

00:20:35.030 --> 00:20:36.200
marketplace.

00:20:36.200 --> 00:20:38.496
We've got everything from
product catalogs to search

00:20:38.496 --> 00:20:40.950
systems to warehouse management
systems, customer service

00:20:40.950 --> 00:20:43.819
systems, apps, websites,
and so on and so forth.

00:20:45.410 --> 00:20:48.900
And so we knew that to build
these products quickly,

00:20:48.900 --> 00:20:50.880
we couldn't be overly
prescriptive with our technology

00:20:50.880 --> 00:20:52.970
teams in terms of what
tech they would use.

00:20:53.970 --> 00:20:56.040
We did have some fundamental
patterns that we asked them to

00:20:56.040 --> 00:20:59.330
stick to, the main one being
an event-driven architecture

00:20:59.330 --> 00:21:00.830
implemented via microservices.

00:21:02.422 --> 00:21:05.870
Event-driven architecture
allows us to build

00:21:05.870 --> 00:21:07.520
a lot of services in parallel,

00:21:07.520 --> 00:21:10.758
because our microservices end
up being very highly decoupled.

00:21:10.758 --> 00:21:13.470
All any microservice really
needs to know about is the event

00:21:13.470 --> 00:21:15.960
bus and the contracts of
the event on the event bus.

00:21:17.610 --> 00:21:20.325
And so while the bulk of our
microservices are implemented in

00:21:20.325 --> 00:21:23.820
F#, under the hood we
knew we had to support

00:21:23.820 --> 00:21:26.210
a plethora of different
technologies, middleware, and so

00:21:26.210 --> 00:21:27.370
on and so forth.

00:21:27.370 --> 00:21:29.110
And this is really where
Azure came into its own.

00:21:30.620 --> 00:21:34.170
Obviously we're using the
fundamental cloud services, and

00:21:34.170 --> 00:21:36.720
this is where Azure was
particularly strong.

00:21:36.720 --> 00:21:39.153
We had first-class support for
Linux VMs,

00:21:39.153 --> 00:21:42.902
first class support Windows VMs,
storage, SSD storage, Vnets,

00:21:42.902 --> 00:21:44.168
and so on and so forth.

00:21:44.168 --> 00:21:46.753
But really what
accelerated Jet's time to

00:21:46.753 --> 00:21:49.909
market was a second layer
of services on top of that,

00:21:49.909 --> 00:21:51.700
most of which Jet uses.

00:21:51.700 --> 00:21:54.821
Things like SQL Azure,
SQL Redis, service bus,

00:21:54.821 --> 00:21:57.360
API management, and
so on and so forth.

00:21:58.810 --> 00:22:01.850
And then the final layer for
jet was all the ALM

00:22:01.850 --> 00:22:04.810
tooling, the tight integration
with Visual Studio, all those

00:22:04.810 --> 00:22:07.360
things that really improved our
developer productivity at what

00:22:07.360 --> 00:22:09.832
was an extremely
hectic year at Jet.

00:22:09.832 --> 00:22:13.650
And so we estimated at Jet
that those three layers

00:22:14.730 --> 00:22:17.360
probably accelerated our time to
market somewhere in the region

00:22:17.360 --> 00:22:18.329
of 12 to 14 months.

00:22:19.930 --> 00:22:22.680
The second problem that
Azure really helped us solve

00:22:22.680 --> 00:22:23.465
was one of scaling.

00:22:23.465 --> 00:22:26.355
Jet was very fortunate to be
able to raise [COUGH] a lot of

00:22:26.355 --> 00:22:27.704
money pre-launch, and

00:22:27.704 --> 00:22:30.786
we knew that money was going
to be spent on marketing, and

00:22:30.786 --> 00:22:34.020
we knew we were going to have
to deal with scale from day one.

00:22:34.020 --> 00:22:36.748
Now of course, Azure has a
fantastic auto-scale story, and

00:22:36.748 --> 00:22:39.180
I’m sure many of you
are familiar with that.

00:22:39.180 --> 00:22:40.957
And of course we use
that at Jet, and

00:22:40.957 --> 00:22:43.864
that allows us to scale our
services and systems by various

00:22:43.864 --> 00:22:47.150
metrics such as CPU usage, queue
length, and so on and so forth.

00:22:48.910 --> 00:22:53.780
But the real sort of fundamental
service that we think helped Jet

00:22:53.780 --> 00:22:56.650
harden its systems pre-launch
was the load testing tooling.

00:22:57.960 --> 00:23:00.508
We ran somewhere in the region
of 5 million minutes of load

00:23:00.508 --> 00:23:02.328
tests in the week coming
up to launch, and

00:23:02.328 --> 00:23:04.620
it really helped
harden the Jet system.

00:23:04.620 --> 00:23:05.410
And we're glad we did,

00:23:05.410 --> 00:23:08.810
because on launch day we saw
traffic that was five times

00:23:08.810 --> 00:23:11.370
in excess of what we were
actually planning for.

00:23:11.370 --> 00:23:13.170
And thankfully both
Jet's technology and

00:23:13.170 --> 00:23:16.070
the auto-scaling in Azure worked
flawlessly to provide a really

00:23:16.070 --> 00:23:17.748
good customer experience for
everyone on the day.

00:23:19.260 --> 00:23:22.173
And then finally there's two
other components of Azure that

00:23:22.173 --> 00:23:24.685
made Jet glad that it chose
Azure to be its technology

00:23:24.685 --> 00:23:25.210
partner.

00:23:26.380 --> 00:23:28.330
The first one is
the sheer scale and

00:23:28.330 --> 00:23:31.410
size of the Azure
footprint here in the US.

00:23:31.410 --> 00:23:34.940
As Scott mentioned, Jet hopes
to be a $20 billion GMV company

00:23:34.940 --> 00:23:38.550
by 2020, and there are only
a few cloud providers out there

00:23:38.550 --> 00:23:41.900
that we felt comfortable could
take Jet to that level of scale.

00:23:41.900 --> 00:23:44.750
And in our opinion, there's only
one cloud provider who could

00:23:44.750 --> 00:23:47.599
do that and provide the deep
integration with tooling, IDEs,

00:23:47.599 --> 00:23:48.727
languages, and so on and

00:23:48.727 --> 00:23:51.440
so forth, that we feel are
necessary to make Jet a success.

00:23:51.440 --> 00:23:54.060
And that was Azure, obviously.

00:23:54.060 --> 00:23:55.790
And then the second thing,

00:23:55.790 --> 00:23:58.200
and this was actually
very surprising for

00:23:58.200 --> 00:24:01.990
us at Jet, was Microsoft's
commitment to us as a startup.

00:24:01.990 --> 00:24:05.597
As soon as we reached out to
Azure, Microsoft, just after we

00:24:05.597 --> 00:24:09.205
incorporated Jet, when we were
still a very small company,

00:24:09.205 --> 00:24:11.894
we got nothing but
valuable, concrete, and

00:24:11.894 --> 00:24:14.684
relevant advice from
the team out in New York.

00:24:14.684 --> 00:24:17.810
And it was actually that
advice and that support for

00:24:17.810 --> 00:24:21.225
us as a startup that was really
instrumental to Jet being

00:24:21.225 --> 00:24:23.420
successful on
the Azure platform.

00:24:23.420 --> 00:24:26.361
And so I guess all that's left
for me to say is go to jet.com,

00:24:26.361 --> 00:24:28.611
check it out,
add something to your cart, and

00:24:28.611 --> 00:24:31.117
I think you'd be surprised
at the savings you see.

00:24:31.117 --> 00:24:31.970
Thanks very much.

00:24:31.970 --> 00:24:32.575
Thanks, Scott.

00:24:32.575 --> 00:24:39.968
>> [APPLAUSE]
>> Thank you.

00:24:39.968 --> 00:24:44.386
Now last year we announced our
plans to deeply embrace Docker

00:24:44.386 --> 00:24:48.891
and the Docker ecosystem with
both Azure and Windows Server,

00:24:48.891 --> 00:24:52.184
and make containers
a fundamental element of

00:24:52.184 --> 00:24:55.020
our application platform.

00:24:55.020 --> 00:24:56.550
And we've released
some great support for

00:24:56.550 --> 00:24:59.840
both of them over
the last few months.

00:24:59.840 --> 00:25:02.440
Today we're excited
to announce a new

00:25:02.440 --> 00:25:05.110
service that we're going
to be launching as well,

00:25:05.110 --> 00:25:07.970
that we call our
Azure Container Service.

00:25:07.970 --> 00:25:11.210
The Azure Container Service
provides a fully managed service

00:25:11.210 --> 00:25:13.430
that enables you to
easily deploy and

00:25:13.430 --> 00:25:16.530
orchestrate applications
built using containers.

00:25:17.780 --> 00:25:19.190
Azure Container Service,

00:25:19.190 --> 00:25:24.420
provides deep integration with
Apache Mesos as well as Docker,

00:25:24.420 --> 00:25:27.170
and additional
Open Source components,

00:25:27.170 --> 00:25:31.640
including Mesosphere's DC
operating system, Chronos, and

00:25:31.640 --> 00:25:32.430
Docker Swarm.

00:25:33.800 --> 00:25:38.330
And the nice thing about this
system is that it powers already

00:25:38.330 --> 00:25:43.480
leading brands like Twitter,
Airbnb, Netflix, and Open Table.

00:25:43.480 --> 00:25:46.650
And being able to have
a container service you can spin

00:25:46.650 --> 00:25:48.350
up very, very quickly, and

00:25:48.350 --> 00:25:52.710
be able to host both Linux as
well as Window Server VMs with

00:25:52.710 --> 00:25:57.110
your containers in any language,
will basically give you ultimate

00:25:57.110 --> 00:26:00.925
flexibility to take advantage
of all that technology and

00:26:00.925 --> 00:26:03.930
really deliver some
great solutions with it.

00:26:03.930 --> 00:26:07.280
You're gonna get a first demo
of it in action in Bill Staple's

00:26:07.280 --> 00:26:09.680
talk immediately following mine.

00:26:09.680 --> 00:26:11.910
We think it's an incredibly
exciting new service that's

00:26:11.910 --> 00:26:14.285
really going to
enable a much richer

00:26:14.285 --> 00:26:18.000
microservice-based development
model using Azure and

00:26:18.000 --> 00:26:19.670
leveraging the best
of Open Source.

00:26:21.140 --> 00:26:21.900
Let's switch gears now and

00:26:21.900 --> 00:26:25.400
talk also a little bit about the
data and analytics space, and

00:26:25.400 --> 00:26:28.550
some of the rich services
that Azure provides there.

00:26:30.030 --> 00:26:33.550
More and more data is being
created and stored in the world,

00:26:33.550 --> 00:26:37.070
and that pace is just
gonna accelerate over

00:26:37.070 --> 00:26:38.250
the next few years.

00:26:38.250 --> 00:26:43.260
And there's an ever-increasing
need to be able to gain insight

00:26:43.260 --> 00:26:46.430
from that data and
be able to take action from it.

00:26:46.430 --> 00:26:47.779
And to really understand,

00:26:47.779 --> 00:26:51.550
you know, achieve that you need
to do a couple different things.

00:26:51.550 --> 00:26:55.280
You need to progress from just
using data to understand what

00:26:55.280 --> 00:26:59.240
happened to move to
understanding why did it happen,

00:26:59.240 --> 00:27:02.100
to be able to move to predict
what will happen in the future,

00:27:02.100 --> 00:27:03.820
and then most importantly,

00:27:03.820 --> 00:27:08.060
understand what should you
actually do based on that.

00:27:08.060 --> 00:27:12.890
And with Azure and our Azure
analytics suite of offerings,

00:27:12.890 --> 00:27:15.410
we're now providing
an end-to-end managed solution

00:27:15.410 --> 00:27:17.120
to do just that.

00:27:17.120 --> 00:27:21.350
It includes capabilities to
ingest data from any source,

00:27:21.350 --> 00:27:24.890
save it in its native format
in a flexible way, and

00:27:24.890 --> 00:27:27.800
apply machine learning
models and other advanced

00:27:27.800 --> 00:27:32.620
analytics capabilities against
that data to create insight.

00:27:32.620 --> 00:27:36.000
And then you can then interact
with these data models

00:27:36.000 --> 00:27:39.330
using Power BI, which we'll
demo in just a little bit,

00:27:39.330 --> 00:27:42.420
our new digital personal
assistants like Cortana,

00:27:42.420 --> 00:27:45.540
as well as automate scenarios
by using custom applications,

00:27:45.540 --> 00:27:48.880
just like what you heard Mike
talk about with jet.com in order

00:27:48.880 --> 00:27:51.250
to optimize
the shopping experience.

00:27:51.250 --> 00:27:53.990
And these capabilities really
enable you to transform

00:27:53.990 --> 00:27:56.380
your businesses in radical ways,
and

00:27:56.380 --> 00:28:01.250
really engage with customers and
reinvent business processes, and

00:28:01.250 --> 00:28:05.370
really change how you
actually operate.

00:28:05.370 --> 00:28:07.880
You can take advantage of all of
these different services that I

00:28:07.880 --> 00:28:10.830
have listed here on
the right separately and

00:28:10.830 --> 00:28:12.340
basically just walk
up to Azure and

00:28:12.340 --> 00:28:16.290
deploy any of the individual
services yourself, and

00:28:16.290 --> 00:28:18.877
basically just pay for the
individual service that you use.

00:28:18.877 --> 00:28:22.420
We're also, though, enabling you
now to optionally buy a suite of

00:28:22.420 --> 00:28:26.130
all of these offerings together
at a heavily discounted price,

00:28:26.130 --> 00:28:28.650
and this provides even
greater cost savings

00:28:28.650 --> 00:28:30.980
when you're building
end-to-end solutions.

00:28:30.980 --> 00:28:33.780
And we call the suite of all
of our data services our

00:28:33.780 --> 00:28:35.930
Cortana Analytics Suite, and

00:28:35.930 --> 00:28:38.860
as of this week it's now
available to purchase.

00:28:38.860 --> 00:28:42.883
And it really provides the best
way to gain deep insight from

00:28:42.883 --> 00:28:44.974
any data system out there, and

00:28:44.974 --> 00:28:49.740
a really cost-efficient way to
build end-to-end data solutions.

00:28:49.740 --> 00:28:55.590
There’s many different services
in our Cortana Analytics Suite.

00:28:55.590 --> 00:28:57.460
Just yesterday at
the Strata Conference,

00:28:57.460 --> 00:29:02.220
we talked about our new
Data Lake service that

00:29:02.220 --> 00:29:04.950
we announced a few months ago,
but we talked and

00:29:04.950 --> 00:29:08.290
shared much more details
about yesterday at Strata.

00:29:08.290 --> 00:29:12.700
It allows you to basically
store any amount of data in any

00:29:12.700 --> 00:29:16.360
format in Azure, and with our
new Data Lake analytic service,

00:29:16.360 --> 00:29:20.860
now you can run big data
processing jobs against it

00:29:20.860 --> 00:29:24.500
in a much more easy way, at
a massive scale, where you can

00:29:24.500 --> 00:29:29.360
literally scale from kilobytes
to exabytes of overall storage.

00:29:29.360 --> 00:29:32.120
One of the other services that
we've announced, and it's now

00:29:32.120 --> 00:29:37.000
part of the suite as well, is
our SQL Data Warehouse service.

00:29:37.000 --> 00:29:40.242
And our SQL Data Warehouse
service offering makes it

00:29:40.242 --> 00:29:43.778
incredibly easy to basically
store any amount of data and

00:29:43.778 --> 00:29:47.608
be able to both interactively
query and visualize it, as well

00:29:47.608 --> 00:29:51.160
as operationalize machine
learning models on top of it.

00:29:51.160 --> 00:29:55.265
And one of the great things
about it is this ability to

00:29:55.265 --> 00:29:59.757
effectively scale independently
compute and storage.

00:29:59.757 --> 00:30:04.950
And be able to handle any level
of data that you throw at it.

00:30:04.950 --> 00:30:08.390
So let's walk through a kind
of simple scenario here.

00:30:08.390 --> 00:30:09.400
What's nice about the SQL

00:30:09.400 --> 00:30:11.720
data warehouse service is that
it's really easy to stand up.

00:30:11.720 --> 00:30:13.270
You can literally create one and

00:30:13.270 --> 00:30:15.670
have it running in
a matter of minutes.

00:30:15.670 --> 00:30:18.740
You can then go ahead and
archive data

00:30:18.740 --> 00:30:23.620
from your operational databases
such SQL or any no SQL database.

00:30:23.620 --> 00:30:26.510
But you can also then
aggregate on premises data.

00:30:26.510 --> 00:30:29.550
Like from a SAP or
from a dynamic system.

00:30:29.550 --> 00:30:32.740
And you can also integrate and
aggregate data from

00:30:32.740 --> 00:30:36.590
Hadoop based systems like our
managed HD insight service.

00:30:36.590 --> 00:30:38.670
And once your data is
in the data warehouse,

00:30:38.670 --> 00:30:40.350
you can then easily
visualize and

00:30:40.350 --> 00:30:44.200
interact with that data using
our new power BI service.

00:30:44.200 --> 00:30:47.060
You can run automated
reports against it.

00:30:47.060 --> 00:30:50.260
And then you can also use our
Azure Machine Learning service

00:30:50.260 --> 00:30:53.760
to easily create predictive
models on top of that data.

00:30:53.760 --> 00:30:56.927
And one of the things that makes
our Machine Learning service so

00:30:56.927 --> 00:31:00.212
powerful is that once you create
a predictive model, you can then

00:31:00.212 --> 00:31:03.630
expose it as an API that your
applications can then call.

00:31:03.630 --> 00:31:06.780
And this makes it incredibly
easy to operationalize machine

00:31:06.780 --> 00:31:10.620
learning and use the combination
of data plus analytics

00:31:10.620 --> 00:31:12.580
to make much more
intelligent apps and

00:31:12.580 --> 00:31:14.920
take intelligent
action from them.

00:31:14.920 --> 00:31:17.160
And best of all,
it's really easy to do all this.

00:31:17.160 --> 00:31:20.150
And what I'd like to do
is invite Laura on stage

00:31:20.150 --> 00:31:23.790
to show a demo of creating
a SQL data warehouse And

00:31:23.790 --> 00:31:25.070
then getting insight from it.

00:31:25.070 --> 00:31:25.580
So here's Laura.

00:31:25.580 --> 00:31:26.437
>> Thank you.

00:31:26.437 --> 00:31:31.532
>> [APPLAUSE]
>> Hello.

00:31:31.532 --> 00:31:36.465
In the next few minutes
we are going to log in.

00:31:36.465 --> 00:31:38.245
We're gonna walk through
a couple services in

00:31:38.245 --> 00:31:41.875
Cortona Analytics Suite
that will help you

00:31:41.875 --> 00:31:45.755
understand how to set up
the Azure data warehouse and

00:31:45.755 --> 00:31:48.945
do some processing of
that data using Power BI.

00:31:48.945 --> 00:31:55.431
So if you'll just give
me a minute See if that.

00:31:57.400 --> 00:31:59.340
There we go.

00:31:59.340 --> 00:32:02.870
So first we're gonna stand
up a data warehouse using

00:32:02.870 --> 00:32:05.410
the Azure Sequel Data Warehouse
service.

00:32:05.410 --> 00:32:08.660
This is a massively parallel
data warehouse service

00:32:08.660 --> 00:32:12.010
that can scale from hundred's
of gigabytes up to petabytes

00:32:12.010 --> 00:32:13.750
of data workloads.

00:32:13.750 --> 00:32:16.010
After that, we're going to
set up a couple of reports.

00:32:16.010 --> 00:32:19.320
We're going to create some
visualizations using Power BI.

00:32:19.320 --> 00:32:22.390
This is a business intelligence
service that's available for

00:32:22.390 --> 00:32:26.130
you to, for anybody in
your organization, and

00:32:26.130 --> 00:32:28.520
you can get to it
straight from a browser.

00:32:28.520 --> 00:32:29.580
So let's get started.

00:32:30.900 --> 00:32:34.570
As Scott mentioned,
the Azure SQL data warehouse is

00:32:34.570 --> 00:32:36.500
now available in
full public preview.

00:32:37.650 --> 00:32:42.410
That means that everyone can now
deploy a scalable data warehouse

00:32:42.410 --> 00:32:43.520
with just a few clicks.

00:32:45.000 --> 00:32:47.380
As you notice,
it's very easy to set up.

00:32:47.380 --> 00:32:50.210
You simply select the server and
you give it a server name.

00:32:55.763 --> 00:32:59.042
And once we've done that, we
simply decide how much compute

00:32:59.042 --> 00:33:01.730
power you want to
assign to a server.

00:33:01.730 --> 00:33:02.840
We can scale this up.

00:33:02.840 --> 00:33:03.720
We can scale this down.

00:33:03.720 --> 00:33:06.300
You simply choose
the compute power based

00:33:06.300 --> 00:33:07.500
on what our requirements are..

00:33:07.500 --> 00:33:12.540
And the most beautiful thing is,
this is a zero-risk decision.

00:33:13.650 --> 00:33:15.080
At any time in the future,

00:33:15.080 --> 00:33:17.650
I can scale this up,
I can scale it down.

00:33:17.650 --> 00:33:19.680
And it just works
behind the scenes.

00:33:20.780 --> 00:33:23.910
In fact, unlike other
cloud data warehouses,

00:33:23.910 --> 00:33:25.860
we don't need to move our data.

00:33:25.860 --> 00:33:26.490
It just works.

00:33:27.650 --> 00:33:32.780
So we're going to choose
a mid-level option and

00:33:32.780 --> 00:33:34.880
in addition, when you're
just getting started,

00:33:34.880 --> 00:33:36.490
you can choose a blank database.

00:33:36.490 --> 00:33:38.450
So just load your own data.

00:33:38.450 --> 00:33:40.940
You can also, just to make
it easier to get started,

00:33:40.940 --> 00:33:43.940
choose the new sample
data that's available.

00:33:43.940 --> 00:33:46.900
And the sample data is
our adventure works that

00:33:46.900 --> 00:33:49.400
we've known and
loved for so many years.

00:33:49.400 --> 00:33:51.073
And from here it's
just business as usual.

00:33:51.073 --> 00:33:54.346
So we'll log in.

00:33:57.871 --> 00:34:00.383
And voila.

00:34:01.490 --> 00:34:04.190
We're now deploying
a scalable data warehouse

00:34:04.190 --> 00:34:06.900
with Azure SQL Data Warehouse.

00:34:06.900 --> 00:34:08.990
In fact,
we've now got sample data and

00:34:08.990 --> 00:34:11.830
views that'll get us
started in no time.

00:34:11.830 --> 00:34:13.300
Imagine, in your
own data center,

00:34:13.300 --> 00:34:16.710
this could take months before
you can even begin querying and

00:34:16.710 --> 00:34:19.010
processing, building reports.

00:34:19.010 --> 00:34:21.050
In Azure SQL Data Warehouse,

00:34:21.050 --> 00:34:23.350
about three to five minutes you
have the service available.

00:34:24.780 --> 00:34:26.830
And while this is finishing
it's provisioning,

00:34:26.830 --> 00:34:29.360
what we're going to do is look
at one of our existing data

00:34:29.360 --> 00:34:31.180
warehouses that's
already provisioned.

00:34:32.350 --> 00:34:34.190
What you'll notice is
you can monitor and

00:34:34.190 --> 00:34:37.330
look at the health and activity
of the queries over time.

00:34:37.330 --> 00:34:40.890
You can see patterns
of query activity.

00:34:40.890 --> 00:34:42.930
And that might make you
make some decisions.

00:34:42.930 --> 00:34:44.980
As I mentioned earlier.

00:34:44.980 --> 00:34:48.170
Zero rest decision
about this scale.

00:34:48.170 --> 00:34:51.310
I can scale this up and
down at any time.

00:34:51.310 --> 00:34:53.000
All I need to do is
move the slider.

00:34:53.000 --> 00:34:57.320
I can also script this to run
behind the scenes, all just

00:34:57.320 --> 00:35:00.120
happens behind the scenes,
I don't need to move my data.

00:35:02.320 --> 00:35:05.090
You can open a directly
Visual Studio and

00:35:05.090 --> 00:35:07.490
begin building
your applications.

00:35:07.490 --> 00:35:09.630
You don't need to learn
any new program languages,

00:35:09.630 --> 00:35:13.160
this is SQL, the same SQL that
we've known and loved for years.

00:35:14.580 --> 00:35:18.550
And, we have great integration
with all the data services and

00:35:18.550 --> 00:35:20.880
Cortana Analytic Suite.

00:35:20.880 --> 00:35:24.940
It means that things like Power
BI, we can open with a click.

00:35:26.840 --> 00:35:30.220
As we connect into Power BI,
it's gonna handle

00:35:30.220 --> 00:35:33.290
all of the connection
string information for us.

00:35:33.290 --> 00:35:35.395
All I need to do is
provide a password.

00:35:35.395 --> 00:35:41.974
[SOUND]
And from here, it's

00:35:41.974 --> 00:35:46.830
going to just import a little
connection string information.

00:35:46.830 --> 00:35:49.360
And in just a couple
of seconds we now have

00:35:49.360 --> 00:35:52.280
our dataset available, and
we can begin building reports.

00:35:53.510 --> 00:35:55.070
So imagine in three
to five minutes,

00:35:55.070 --> 00:35:58.180
we've set up the data warehouse
and now we're already reporting

00:35:58.180 --> 00:36:00.350
off of that sample data
that we've made available.

00:36:02.250 --> 00:36:05.980
Power BI has what we call
a direct connection with

00:36:05.980 --> 00:36:07.740
Azure data warehouse.

00:36:07.740 --> 00:36:10.900
That means is that it's only
bringing back the aggregates

00:36:10.900 --> 00:36:13.180
necessary to build
the visualization.

00:36:16.240 --> 00:36:18.920
The way that that equates back
to you is this can operate

00:36:18.920 --> 00:36:22.120
against any size of data,
from hundreds

00:36:22.120 --> 00:36:25.630
of gigabytes to terabytes to
petabyte sized workloads.

00:36:27.010 --> 00:36:28.390
It's all happening
in the massive

00:36:28.390 --> 00:36:30.870
parallel processing
architecture in Azure.

00:36:32.130 --> 00:36:34.640
And let's fill out one
more visualization.

00:36:34.640 --> 00:36:38.650
We'll look at our sales amount
over a period of time and

00:36:38.650 --> 00:36:40.310
maybe make that a line chart.

00:36:44.010 --> 00:36:46.820
And in just a couple of
seconds I've created a nice

00:36:46.820 --> 00:36:50.090
visualization to help me
understand sales data over

00:36:50.090 --> 00:36:53.760
location and time and
some customer demographics.

00:36:54.860 --> 00:36:56.530
And all of this was
done with just a quick

00:36:56.530 --> 00:36:59.170
connection string to
Azure SQL Data Warehouse.

00:37:00.250 --> 00:37:02.580
This is a nice view and
this is a nice report, so

00:37:02.580 --> 00:37:03.470
we'll save this.

00:37:06.080 --> 00:37:07.200
And I can come back to it later.

00:37:07.200 --> 00:37:10.410
I can share it with other
people in the organization.

00:37:10.410 --> 00:37:13.920
And I may want to
pin one of these

00:37:13.920 --> 00:37:16.140
views out to what we
call a dashboard.

00:37:17.300 --> 00:37:20.140
And we'll just pin this to an
existing dashboard I've already

00:37:20.140 --> 00:37:24.100
created that's aggregating data
from multiple different sources.

00:37:25.590 --> 00:37:29.370
As easy as it was for
us to connect and build reports

00:37:29.370 --> 00:37:33.290
using Azure SQL Data Warehouse,
it's just as easy to connect to

00:37:33.290 --> 00:37:37.170
any data service within
Cortana Analytic Suites.

00:37:37.170 --> 00:37:42.120
We can use spark for streaming
real-time data, coming through.

00:37:42.120 --> 00:37:45.338
We can connect it to any of
the other data services that

00:37:45.338 --> 00:37:48.710
are available in Cortana,
as your SQL database, etc.

00:37:50.660 --> 00:37:54.990
And when you wanna hand analysis
directly to your users,

00:37:54.990 --> 00:37:58.630
they can start asking questions
directly of the data.

00:37:59.740 --> 00:38:01.940
And they can use just
natural language.

00:38:03.460 --> 00:38:05.978
And perhaps you wanna
look at things by gender.

00:38:08.691 --> 00:38:12.110
And, we'll look at it
by product category.

00:38:14.070 --> 00:38:18.020
And it renders the visualization
very easily for your end user.

00:38:19.200 --> 00:38:21.840
They can save that
out to our dashboard.

00:38:21.840 --> 00:38:24.420
We'll pin that up.

00:38:24.420 --> 00:38:27.520
And we know have a single view
that's bringing data from our

00:38:27.520 --> 00:38:32.130
data warehouse from our big
data engines up in Azure,

00:38:32.130 --> 00:38:35.190
in addition to our
real time engines.

00:38:35.190 --> 00:38:37.250
And Cortana Analytics Suite
just brings it all together.

00:38:37.250 --> 00:38:39.005
I'm gonna hand it back to Scott.

00:38:39.005 --> 00:38:45.835
>> [APPLAUSE]
>> Thank you.

00:38:45.835 --> 00:38:48.996
>> I think you saw from Laura's
demo, just in terms of the ease

00:38:48.996 --> 00:38:52.032
of use that a lot of these new
data technologies now have,

00:38:52.032 --> 00:38:54.562
and the fact that you can
actually kinda stand up

00:38:54.562 --> 00:38:57.409
those types of environments
literally in minutes and

00:38:57.409 --> 00:39:00.130
see immediate ROI from it
really allows you to kinda

00:39:00.130 --> 00:39:03.000
transform how you
think about problems.

00:39:03.000 --> 00:39:05.690
And really enables you to solve
even harder business solutions.

00:39:07.100 --> 00:39:09.150
So we talked about developer and
app platform.

00:39:09.150 --> 00:39:11.160
We talked about data and
analytics.

00:39:11.160 --> 00:39:12.120
Let's switch gears now and

00:39:12.120 --> 00:39:14.700
talk a little bit about
Internet of Things.

00:39:14.700 --> 00:39:18.470
And some of the IoT solutions
that we're now building out.

00:39:18.470 --> 00:39:20.980
Well it's an incredibly
exciting time right now

00:39:20.980 --> 00:39:23.340
in the IoT space and

00:39:23.340 --> 00:39:26.650
pretty much everything we work
with on a physical level going

00:39:26.650 --> 00:39:31.210
forward is gonna have some IoT
connection to it in the future.

00:39:31.210 --> 00:39:34.250
And that IoT data is gonna be
used both to control devices,

00:39:34.250 --> 00:39:36.710
but also, as you saw
from Laura's demo, you're

00:39:36.710 --> 00:39:41.310
gonna see IoT solutions bring
in data into the cloud, and

00:39:41.310 --> 00:39:45.230
enable businesses, and enable
companies to get much more

00:39:45.230 --> 00:39:48.540
insight in terms of how their
users are using their services.

00:39:48.540 --> 00:39:50.676
And be able to kind of build
much better experiences based on

00:39:50.676 --> 00:39:51.324
those insights.

00:39:51.324 --> 00:39:55.648
One of the things that we
announced earlier this year was

00:39:55.648 --> 00:39:57.307
our Azure IoT suite.

00:39:57.307 --> 00:40:01.600
Which is an offering that
provides a host of IoT

00:40:01.600 --> 00:40:04.900
capabilities on Azure.

00:40:04.900 --> 00:40:08.680
From device connectivity and
security, which is paramount in

00:40:08.680 --> 00:40:13.590
the IoT space, to device data
ingestion and command and

00:40:13.590 --> 00:40:16.290
control scenarios where you
can not only use the cloud to

00:40:16.290 --> 00:40:19.610
aggregate data from devices, but
also use the Cloud to be able to

00:40:19.610 --> 00:40:22.940
reach out and actually control
those devices in a secure way

00:40:22.940 --> 00:40:25.480
and send signals to them.

00:40:25.480 --> 00:40:28.500
We provide stream processing and
predictive analytics.

00:40:28.500 --> 00:40:31.180
So imagine a scenario where you
have a device that's sending

00:40:31.180 --> 00:40:33.620
back health data
about that device.

00:40:33.620 --> 00:40:37.310
How can you use the Cloud to get
that data but also analyze it in

00:40:37.310 --> 00:40:40.890
real time to see is the device
operating properly.

00:40:40.890 --> 00:40:43.090
And be able to predict is
it gonna break down and

00:40:43.090 --> 00:40:46.090
if so what action should I go
ahead and take based on it.

00:40:46.090 --> 00:40:48.260
And then how do I go ahead and
orchestrate all of this so

00:40:48.260 --> 00:40:50.840
I can have complex work flows

00:40:50.840 --> 00:40:53.370
integrated as part of
my business process?

00:40:53.370 --> 00:40:56.510
How do I visualize the health
of this system and

00:40:56.510 --> 00:40:58.310
be able to drive intent on it?

00:40:58.310 --> 00:41:01.430
And then rather than have to
code all this myself, how can I

00:41:01.430 --> 00:41:04.450
actually have pre-configured
solutions for lots of common

00:41:04.450 --> 00:41:08.770
cases, that I can just leverage
and then customize or configure

00:41:08.770 --> 00:41:12.690
in order to get immediate
success and value out of it.

00:41:12.690 --> 00:41:13.590
So we were pretty excited

00:41:13.590 --> 00:41:15.660
about what the Azure IoT
suite provides.

00:41:15.660 --> 00:41:18.290
We're having tons and tons of
customers taking advantage of it

00:41:18.290 --> 00:41:22.140
now In the preview form and I'm
really excited to announce today

00:41:22.140 --> 00:41:24.590
that it's now available for
purchase.

00:41:24.590 --> 00:41:26.690
So you can now go ahead and
actually buy it and

00:41:26.690 --> 00:41:29.030
use it in your own
production systems.

00:41:30.670 --> 00:41:34.777
You know, as an example of some
of the capabilities it offers,

00:41:34.777 --> 00:41:37.730
this is the out of the box
UI that it delivers.

00:41:37.730 --> 00:41:40.430
It allows me to see for any of
the devices that I'm managing,

00:41:40.430 --> 00:41:42.700
where are they geographically.

00:41:42.700 --> 00:41:43.820
I can set up alerts.

00:41:43.820 --> 00:41:45.100
I can set up workflows.

00:41:45.100 --> 00:41:46.980
I can go ahead and
manage those devices and

00:41:46.980 --> 00:41:48.910
look at the telemetry
in real time.

00:41:48.910 --> 00:41:51.890
You can see we’ve integrated
as part of this experience,

00:41:51.890 --> 00:41:54.860
the power BI views that Laura
showed earlier in the power BI

00:41:54.860 --> 00:41:55.680
experience.

00:41:55.680 --> 00:41:59.650
Directly an institute IoT
suite management tool.

00:41:59.650 --> 00:42:00.890
And then you can
also go ahead and

00:42:00.890 --> 00:42:04.480
set up business rules that don't
even require, necessarily,

00:42:04.480 --> 00:42:07.860
developers to actually always
go ahead and code them so

00:42:07.860 --> 00:42:10.620
that you can actually
manage that experience and

00:42:10.620 --> 00:42:12.660
track the health of all
your devices in real time.

00:42:12.660 --> 00:42:15.440
And obviously everything you
can do through UI you can also

00:42:15.440 --> 00:42:18.780
automate and script as well
through a programmatic API.

00:42:18.780 --> 00:42:21.750
And we think the combination of
this really enables a tremendous

00:42:21.750 --> 00:42:25.230
amount of power
in new scenarios.

00:42:25.230 --> 00:42:27.270
As I mentioned, we have lots
of different customers that

00:42:27.270 --> 00:42:31.380
are taking advantage of
this IoT capability today.

00:42:31.380 --> 00:42:35.910
Rockwell Automation is using
it to manage gas dispensers

00:42:35.910 --> 00:42:38.960
across critical infrastructure
around the world.

00:42:38.960 --> 00:42:42.270
Ford is imbedding IoT sensors
into all their vehicles

00:42:42.270 --> 00:42:44.980
going forward and are going
to be streaming the data into

00:42:44.980 --> 00:42:47.510
the Cloud to be able to
understand vehicle intent and

00:42:47.510 --> 00:42:51.212
be able to optimize
the car owner experience.

00:42:51.212 --> 00:42:55.340
And ThyssenKrupp is
the leading manufacturer for

00:42:55.340 --> 00:42:56.510
elevators around the world.

00:42:56.510 --> 00:43:00.150
They're using the IoT solution
in a very innovative way,

00:43:00.150 --> 00:43:03.710
to basically track the health
of their million plus elevators

00:43:03.710 --> 00:43:07.390
deployed around the globe, and
be able to use the signals from

00:43:07.390 --> 00:43:11.100
those elevators to predict when
an elevator is gonna break down.

00:43:11.100 --> 00:43:14.450
And how do they optimize
the service experience,

00:43:14.450 --> 00:43:16.110
both before it breaks down so

00:43:16.110 --> 00:43:19.100
they can fix it before
there's a customer issue, and

00:43:19.100 --> 00:43:21.890
be able to optimize their
business practice around it.

00:43:21.890 --> 00:43:25.830
What I'd like to do is show off
a quick video from ThyssenKrupp

00:43:25.830 --> 00:43:28.300
talking about their solution and
how they're using Azure.

00:43:28.300 --> 00:43:35.052
[MUSIC]

00:43:35.052 --> 00:43:38.569
>> With 3 billion people moving
into the world's cities in

00:43:38.569 --> 00:43:42.086
the next three decades the world
needs tall buildings and

00:43:42.086 --> 00:43:44.000
tall buildings need elevators

00:43:44.000 --> 00:43:49.475
[MUSIC]

00:43:49.475 --> 00:43:52.270
I'm Dr. Rory Smith with
ThyssenKrupp Elevator,

00:43:52.270 --> 00:43:54.098
a leading global manufacturer.

00:43:54.098 --> 00:43:58.830
Maintaining over 1.1 million
of these machines annually and

00:43:58.830 --> 00:44:04.730
keeping them running safely and
reliably, 24/7 is our job one.

00:44:04.730 --> 00:44:07.670
We wanted to better compete
in our industry by offering

00:44:07.670 --> 00:44:10.290
dramatically increased up time.

00:44:10.290 --> 00:44:13.590
So we're taking preventive
maintenance a step further

00:44:13.590 --> 00:44:17.090
to predictive and
even preemptive service.

00:44:17.090 --> 00:44:19.000
We've teamed up
with Microsoft and

00:44:19.000 --> 00:44:22.200
CGI to harness
the Internet of things.

00:44:22.200 --> 00:44:24.720
To collect data by
connecting the sensors and

00:44:24.720 --> 00:44:27.350
systems in each of our
elevators to the Cloud.

00:44:27.350 --> 00:44:30.491
[MUSIC]

00:44:30.491 --> 00:44:34.538
Microsoft Azure draws this data
in to a central Cloud based

00:44:34.538 --> 00:44:38.930
dashboard for a realtime view
of key performance indicators.

00:44:38.930 --> 00:44:40.738
[MUSIC]

00:44:40.738 --> 00:44:44.550
And power BI provides
rich data visualization.

00:44:45.750 --> 00:44:48.510
So we know which cabs
need service and when.

00:44:50.010 --> 00:44:54.030
Microsoft Azure machine learning
feeds data into dynamic,

00:44:54.030 --> 00:44:57.320
predictive models, so
that elevators will actually be

00:44:57.320 --> 00:45:01.010
able to anticipate which
repairs they need.

00:45:01.010 --> 00:45:03.820
Using on app on mobile
devices in the field, or

00:45:03.820 --> 00:45:06.890
the dashboard at one of our
corporate control centers,

00:45:06.890 --> 00:45:10.170
all of our technicians see
the same real time information.

00:45:11.190 --> 00:45:14.100
Now we have the ability to
use live data to define

00:45:14.100 --> 00:45:17.510
a needed repair before
a breakdown happens.

00:45:17.510 --> 00:45:19.930
Reducing cost for
ourselves and for

00:45:19.930 --> 00:45:24.620
our customers, raising elevator
reliability to new heights.

00:45:24.620 --> 00:45:27.415
That's the internet of
ThyssenKrupp things, and

00:45:27.415 --> 00:45:28.655
it's here right now.

00:45:28.655 --> 00:45:35.006
[MUSIC]

00:45:35.006 --> 00:45:38.080
>> Throughout the day you'll
hear more about our IoT suite,

00:45:38.080 --> 00:45:41.215
and go into more depth in terms
of some of the demos and some of

00:45:41.215 --> 00:45:44.810
the new capabilities that
today's offering now enables.

00:45:44.810 --> 00:45:46.460
And we're incredibly
excited about

00:45:46.460 --> 00:45:51.020
all the different use cases that
are now possible with it and

00:45:51.020 --> 00:45:53.950
are really the leading provider
in the cloud space in terms of

00:45:53.950 --> 00:45:57.540
delivering a platform and the
tools necessary to really enable

00:45:57.540 --> 00:46:00.080
those scenarios and
do them securely and at scale.

00:46:00.080 --> 00:46:02.030
Let's switch gears now and

00:46:02.030 --> 00:46:05.770
talk a little bit about
infrastructure and all the rich

00:46:05.770 --> 00:46:10.255
services that Azure provides as
an interest infrastructure cloud

00:46:10.255 --> 00:46:14.100
that you can use to build any
types of solutions on top of.

00:46:14.100 --> 00:46:16.410
And, obviously, all the higher
level capabilities that we've

00:46:16.410 --> 00:46:19.870
already talked about today are
built on top of these same core,

00:46:19.870 --> 00:46:22.210
fundamental infrastructure
components.

00:46:22.210 --> 00:46:24.850
And, really, the combination of
being able to take advantage of

00:46:24.850 --> 00:46:28.420
infrastructure plus these higher
level services like data and

00:46:28.420 --> 00:46:32.750
analytics, IOT, inter-developer,
and Apple platform services

00:46:32.750 --> 00:46:35.110
is really the combination that
makes Azure really unique.

00:46:35.110 --> 00:46:38.020
One of the things
that we've been hard

00:46:38.020 --> 00:46:40.310
at work on over the last
year in particular,

00:46:40.310 --> 00:46:43.180
is building out our set
of infrastructure and

00:46:43.180 --> 00:46:45.580
the capabilities that
we deliver with it.

00:46:45.580 --> 00:46:47.950
We now have an end to
end management platform

00:46:47.950 --> 00:46:51.650
that provides a single
management API that you can use

00:46:51.650 --> 00:46:54.630
to manage any of
the services across Azure.

00:46:54.630 --> 00:46:56.970
And one of the couple big
innovations that we've released

00:46:56.970 --> 00:47:01.250
over the last year are things
like the ability to create

00:47:01.250 --> 00:47:04.530
application templates that
can compose multiple of these

00:47:04.530 --> 00:47:07.360
services together into
a single solution.

00:47:07.360 --> 00:47:10.260
So rather than just create
a SEQUEL data warehouse and

00:47:10.260 --> 00:47:12.480
then create a storage
account and

00:47:12.480 --> 00:47:15.170
then create a hadoop cluster and
then a web app.

00:47:15.170 --> 00:47:18.283
You can now actually, with
a single JSON template indicate

00:47:18.283 --> 00:47:21.085
that you want to create all
four of those resources and

00:47:21.085 --> 00:47:24.510
integrate them together and then
basically send that template to

00:47:24.510 --> 00:47:26.501
Azure with a single
call to go ahead and

00:47:26.501 --> 00:47:29.500
stand up that entire
solution together.

00:47:29.500 --> 00:47:31.520
We've integrated things like
lifecycle management so

00:47:31.520 --> 00:47:34.160
that you can actually
replace and/or tear down

00:47:34.160 --> 00:47:35.910
an entire environment, again,

00:47:35.910 --> 00:47:39.240
in a completely automated way,
across multiple resources.

00:47:39.240 --> 00:47:42.190
And we've also now integrated
things like role base access

00:47:42.190 --> 00:47:45.390
control, the ability to tag
resources so that you can easily

00:47:45.390 --> 00:47:49.760
search for them, as well as the
new billing API that will expose

00:47:49.760 --> 00:47:53.606
the health and billing data of
your services and be able to

00:47:53.606 --> 00:47:56.940
even incorporate those tags, in
order to actually allow you to

00:47:56.940 --> 00:47:59.850
charge back departments or
individual teams within your

00:47:59.850 --> 00:48:03.720
organization based on the
services that they're consuming.

00:48:03.720 --> 00:48:06.700
We've added some great support
with premium storage so

00:48:06.700 --> 00:48:08.020
that you can now go ahead and

00:48:08.020 --> 00:48:11.378
drive massive IO disc
workloads on Azure.

00:48:11.378 --> 00:48:16.110
Greater than 80,000 IOPS per
VM which is the largest in

00:48:16.110 --> 00:48:19.430
the public cloud, with less than
a one millisecond read latency.

00:48:19.430 --> 00:48:22.130
And then we've also come out
with a number of new virtual

00:48:22.130 --> 00:48:23.470
machine sizes.

00:48:23.470 --> 00:48:27.100
You'll hear about two more VM
sizes that we're announcing

00:48:27.100 --> 00:48:29.750
today that enable you to run
even more diverse workloads in

00:48:29.750 --> 00:48:30.365
our cloud.

00:48:30.365 --> 00:48:33.835
Our G series, for example, that
we announced earlier this year,

00:48:33.835 --> 00:48:37.250
and shipped earlier this year
enables still today the largest

00:48:37.250 --> 00:48:40.190
VM's of any cloud provider
out there, with almost a half

00:48:40.190 --> 00:48:44.930
a terabyte of RAM in seven
terabytes of local SSD storage.

00:48:44.930 --> 00:48:48.770
Really enables you to power
the most extreme work loads.

00:48:48.770 --> 00:48:52.050
I'm excited to announce
today a new family of

00:48:52.050 --> 00:48:53.610
VM's that we call our N family.

00:48:54.740 --> 00:48:58.100
These are our first GPU
optimized virtual machines

00:48:58.100 --> 00:48:59.520
running in Azure.

00:48:59.520 --> 00:49:00.480
And they take advantage and

00:49:00.480 --> 00:49:03.980
support the latest
NVIDIA GPU processors.

00:49:03.980 --> 00:49:07.010
We're the first in the public
cloud in order to enable that.

00:49:07.010 --> 00:49:10.700
And also have super fast
RDMA network access.

00:49:10.700 --> 00:49:13.680
As well as enable high
end remote visualization.

00:49:13.680 --> 00:49:16.060
And we're incredibly excited
to have these available.

00:49:16.060 --> 00:49:19.030
And know that they open up
a whole bunch more use cases

00:49:19.030 --> 00:49:21.160
that you can take advantage
of throughout Azure.

00:49:22.410 --> 00:49:25.300
One of the things we're
also focusing a lot on,

00:49:25.300 --> 00:49:28.740
and you're gonna hear more about
today that we're pretty excited

00:49:28.740 --> 00:49:32.460
to announce, is a bunch of
investments that we're doing

00:49:32.460 --> 00:49:34.880
around improving security and

00:49:34.880 --> 00:49:39.870
enabling you to build even more
secure solutions by using Azure.

00:49:39.870 --> 00:49:42.730
And obviously security
right now is a hot topic

00:49:42.730 --> 00:49:45.060
everywhere in the IT space.

00:49:45.060 --> 00:49:47.846
And a week doesn't go by that
you don't hear about some

00:49:47.846 --> 00:49:50.223
organization that's
had a security breach.

00:49:50.223 --> 00:49:53.845
And the reality with security
is it's a nuanced thing where it

00:49:53.845 --> 00:49:57.617
requires all of us to lean in in
order to build secure solutions.

00:49:57.617 --> 00:50:00.961
About end users and
consumers can take advantage of.

00:50:00.961 --> 00:50:05.028
And one of the things that we're
working to do is in launching

00:50:05.028 --> 00:50:07.920
today, is our new
Azure Security Center.

00:50:07.920 --> 00:50:11.360
And what this basically
provides is not only a bunch of

00:50:11.360 --> 00:50:14.640
documentation on how
to build secure apps.

00:50:14.640 --> 00:50:17.450
But really builds in
a management experience

00:50:17.450 --> 00:50:20.610
that allows you to actually
automate the security within

00:50:20.610 --> 00:50:21.750
your systems.

00:50:21.750 --> 00:50:25.010
And be able to have us
proactively tell you

00:50:25.010 --> 00:50:28.890
when we see that you either have
a security issue happening, or

00:50:28.890 --> 00:50:32.240
you're not implementing all of
the best practices necessary to

00:50:32.240 --> 00:50:34.410
build great secure solutions.

00:50:34.410 --> 00:50:37.700
As part of this, we now provide
integrated security, monitoring,

00:50:37.700 --> 00:50:40.540
and policy management, so
you can even have it where

00:50:40.540 --> 00:50:43.690
an organization can set
up policy rules that

00:50:43.690 --> 00:50:47.170
all of the teams within their
organization needs to follow.

00:50:47.170 --> 00:50:49.780
And then basically we'll
automatically be able to flag

00:50:49.780 --> 00:50:53.320
any time you're out of
policy from those particular

00:50:53.320 --> 00:50:54.490
requirements.

00:50:54.490 --> 00:50:57.180
We have built-in threat
detections as well as alerts, so

00:50:57.180 --> 00:50:59.560
we can actually tell you
when you're being DDoSed.

00:50:59.560 --> 00:51:01.859
We can tell you when we
see that someone is trying

00:51:02.910 --> 00:51:07.140
a particular tag on your
system where they're from and

00:51:07.140 --> 00:51:09.950
if you have all the right
safeguards in place.

00:51:09.950 --> 00:51:12.270
And one of these that's unique
about our solution is it's not

00:51:12.270 --> 00:51:16.300
just us building it we've
instead partnered with broad

00:51:16.300 --> 00:51:19.090
ecosystem of different
security providers out there.

00:51:19.090 --> 00:51:21.160
We can see just some of
the logos there at the bottom of

00:51:21.160 --> 00:51:22.660
the slide.

00:51:22.660 --> 00:51:25.606
And enabled their solutions
to work as virtual appliances

00:51:25.606 --> 00:51:28.731
running inside Azure, so that
you can actually if you already

00:51:28.731 --> 00:51:31.737
have a particular security
vendor that you've embraced or

00:51:31.737 --> 00:51:34.039
trusted or
already bought their solutions.

00:51:34.039 --> 00:51:36.098
You can now take
their solutions,

00:51:36.098 --> 00:51:37.944
easily deploy them in Azure and

00:51:37.944 --> 00:51:42.470
integrate them end to end as
part of the security experience.

00:51:42.470 --> 00:51:45.960
As an example, and you'll see
a lot more demos later today.

00:51:45.960 --> 00:51:49.160
We now have a new security
center directly inside the Azure

00:51:49.160 --> 00:51:52.180
management portal that you
saw Laura demo earlier and

00:51:52.180 --> 00:51:55.250
you'll see Cory do some
demos of in a few minutes.

00:51:55.250 --> 00:51:57.880
And you can now pool up for
your subscription or for

00:51:57.880 --> 00:51:59.035
your account.

00:51:59.035 --> 00:52:02.010
An overall summary blade
that'll tell you what resources

00:52:02.010 --> 00:52:04.690
are running and what are we
seeing in terms of the best

00:52:04.690 --> 00:52:07.360
practices that you either are or

00:52:07.360 --> 00:52:09.940
aren't implementing as
part of your solutions.

00:52:09.940 --> 00:52:13.015
You drill in, for example, and
see recommendation that we see

00:52:13.015 --> 00:52:15.287
based on how you've
deployed your solution.

00:52:15.287 --> 00:52:18.325
In other words, do you have an
IP address in front of a web or

00:52:18.325 --> 00:52:21.425
mobile app that's not being
protected with an application

00:52:21.425 --> 00:52:22.750
firewall?

00:52:22.750 --> 00:52:24.772
Not only can we flag the,
hey do you have that issue?

00:52:24.772 --> 00:52:27.095
But you can actually click
on that recommendation and

00:52:27.095 --> 00:52:29.778
one of things that we've done is
integrate as part of the Azure

00:52:29.778 --> 00:52:30.920
marketplace.

00:52:30.920 --> 00:52:34.070
The ability for you to chose
any of the existing application

00:52:34.070 --> 00:52:37.250
firewalls you might have
deployed in your account or

00:52:37.250 --> 00:52:39.890
you can go ahead and choose from
the gallery any of our third

00:52:39.890 --> 00:52:43.530
party application firewalls from
companies like Barracuda or

00:52:43.530 --> 00:52:47.350
F5 or Imperva and others.

00:52:47.350 --> 00:52:51.060
And go ahead and attach it in
front of that IP address and

00:52:51.060 --> 00:52:52.910
with just two or three clicks,

00:52:52.910 --> 00:52:56.920
basically deploy that security
device in front of it.

00:52:56.920 --> 00:52:59.600
Other things, like network
security groups and making sure

00:52:59.600 --> 00:53:03.230
that you don't have open ports
even within your application.

00:53:03.230 --> 00:53:06.510
We will scan automatically
highlight for you and

00:53:06.510 --> 00:53:09.830
then directly in the experience
walk you through how

00:53:09.830 --> 00:53:13.130
you go ahead and improve and
basically make sure that you

00:53:13.130 --> 00:53:15.470
implement all those
best practices.

00:53:15.470 --> 00:53:18.540
I would think without having to
kinda read a bunch of reports or

00:53:18.540 --> 00:53:20.370
read a bunch of documentation.

00:53:20.370 --> 00:53:24.530
You have to remember the beauty
is you can run this any time,

00:53:24.530 --> 00:53:27.360
either through the UI or
through an API and

00:53:27.360 --> 00:53:31.450
immediately be able to assess
what your current situation is.

00:53:32.540 --> 00:53:35.770
We're also, then, integrating
security alert capability and

00:53:35.770 --> 00:53:38.620
one of the cool things is we're
actually ingesting security

00:53:38.620 --> 00:53:42.210
events from all these
different security providers,

00:53:42.210 --> 00:53:43.280
into a single system.

00:53:43.280 --> 00:53:47.390
So effectively, we're running a
giant dupe big data solution for

00:53:47.390 --> 00:53:50.170
you analyzing the security
attacks that are happening

00:53:50.170 --> 00:53:53.010
on top of your applications.

00:53:53.010 --> 00:53:55.940
And then what's nice is we're
also being able to take

00:53:55.940 --> 00:53:59.000
other signals that we subscribe
to, so for example if we know

00:53:59.000 --> 00:54:03.110
that a particular IP address Is
compromised with malware, or

00:54:03.110 --> 00:54:05.550
has basically been taken
over by an attacker.

00:54:05.550 --> 00:54:07.930
We can automatically
scan our network to see,

00:54:07.930 --> 00:54:11.420
is anyone attacking your
application from that location

00:54:11.420 --> 00:54:13.090
and immediately alert
you as part of it.

00:54:13.090 --> 00:54:16.067
And so DDoS attacks,
SQL injection attacks,

00:54:16.067 --> 00:54:19.119
and others will automatically
show up as part of

00:54:19.119 --> 00:54:23.088
security alert system and we
can even pinpoint the activity,

00:54:23.088 --> 00:54:27.242
the frequency, and the location
of those particular attacks.

00:54:27.242 --> 00:54:30.386
Again, all within our management
portal and then what's nice is

00:54:30.386 --> 00:54:33.247
we've also exposing as part
of this solution APIs that'll

00:54:33.247 --> 00:54:36.395
integrate with existing systems
like Arcsite or Splunk that your

00:54:36.395 --> 00:54:39.388
company might already be using
for their seam architecture.

00:54:39.388 --> 00:54:43.083
And so your existing security
office and/or security IT team

00:54:43.083 --> 00:54:45.783
can integrate the solutions
they already use

00:54:45.783 --> 00:54:48.412
on-premise with
the solutions in the cloud

00:54:48.412 --> 00:54:52.108
to basically get a comprehensive
coverage of security that no

00:54:52.108 --> 00:54:54.860
other cloud provider
out there offers.

00:54:54.860 --> 00:54:57.020
So you'll hear a lot more
in-depth about this later today,

00:54:57.020 --> 00:55:00.320
we really think this is a great
example of a type of enterprise

00:55:00.320 --> 00:55:04.130
grade capability that we're
looking to provide on Azure, and

00:55:04.130 --> 00:55:06.920
some of the unique services
that we can provide above and

00:55:06.920 --> 00:55:09.630
beyond base infrastructure
that no one else does.

00:55:11.280 --> 00:55:12.740
In addition to things
like security,

00:55:12.740 --> 00:55:15.990
the other big investment that
we're making is around how do we

00:55:15.990 --> 00:55:18.160
actually provide even
richer troubleshooting and

00:55:18.160 --> 00:55:20.890
support experiences
on top of Azure.

00:55:20.890 --> 00:55:24.700
And enable you as you build your
applications both to hopefully

00:55:24.700 --> 00:55:27.360
have a really great cloud
provider that runs your

00:55:27.360 --> 00:55:31.100
services, but also to be able to
debug your own applications and

00:55:31.100 --> 00:55:33.105
help you when you
do run into issues,

00:55:33.105 --> 00:55:36.785
identify what is the issue,
where is it at, and

00:55:36.785 --> 00:55:40.115
how do I fix it,
in as fast a way as possible.

00:55:40.115 --> 00:55:42.615
We are pleased to announce
a bunch of things that are gonna

00:55:42.615 --> 00:55:44.375
be coming out,
some of which are live today,

00:55:44.375 --> 00:55:47.145
some of which will be coming
out over the next couple weeks.

00:55:47.145 --> 00:55:49.985
What I'd like to is invite
Corey onstage to give a demo of

00:55:49.985 --> 00:55:50.665
a bunch of them.

00:55:50.665 --> 00:55:51.263
So here's Corey.

00:55:51.263 --> 00:55:56.840
>> [APPLAUSE]
>> Yeah, thanks.

00:55:56.840 --> 00:56:00.374
Great, let me get
logged in here.

00:56:00.374 --> 00:56:01.529
Excellent [COUGH].

00:56:01.529 --> 00:56:06.237
Fantastic, so over the last few
years working with a lot of

00:56:06.237 --> 00:56:10.767
customers on Azure of many
different shapes and sizes.

00:56:10.767 --> 00:56:14.292
I frequently hear questions
around how best to debug and

00:56:14.292 --> 00:56:16.617
diagnose problems
on the platform?

00:56:16.617 --> 00:56:19.669
And I'm excited today to be able
to walk you through some new

00:56:19.669 --> 00:56:22.904
tools and capabilities that's
gonna make this really easy and

00:56:22.904 --> 00:56:24.820
fun, even, on Azure.

00:56:24.820 --> 00:56:28.700
And so let me start here
with my session that I'll

00:56:28.700 --> 00:56:30.180
quickly reload.

00:56:30.180 --> 00:56:33.440
And [COUGH] the application that
I've got running right now,

00:56:33.440 --> 00:56:36.220
is a for instance application.

00:56:36.220 --> 00:56:38.875
It's got two VMs running in
my front end that are running

00:56:38.875 --> 00:56:41.830
Nginx and Linux and then I've
got two running in my back end

00:56:41.830 --> 00:56:43.310
which are running SQL Server.

00:56:43.310 --> 00:56:46.660
And so I've obviously got the HA
across these solutions and so it

00:56:46.660 --> 00:56:50.120
makes sure that my Apple stay up
even when an instance goes down.

00:56:50.120 --> 00:56:50.900
And already,

00:56:50.900 --> 00:56:53.690
you can see I've got a couple
alerts that have fired.

00:56:53.690 --> 00:56:56.680
And so these alerts are
configured to make sure I know

00:56:56.680 --> 00:56:58.700
what issues are going
to happen with my VM so

00:56:58.700 --> 00:57:00.250
that I can respond.

00:57:00.250 --> 00:57:03.510
Some new capabilities we even
just announced called WebHooks

00:57:03.510 --> 00:57:07.470
allow me to wire that straight
into page of duty, or SNS, or

00:57:07.470 --> 00:57:08.610
even a slap channel,

00:57:08.610 --> 00:57:11.180
to be able to track when those
things are happening without

00:57:11.180 --> 00:57:12.870
necessarily having to
come onto the portal.

00:57:13.890 --> 00:57:15.720
And so now that I see
that these are an issue,

00:57:15.720 --> 00:57:17.430
I'm gonna go ahead and
drill in and

00:57:17.430 --> 00:57:20.850
take a look at nginx2 and
see what may be going on.

00:57:20.850 --> 00:57:22.742
So you can see here
right away to the right,

00:57:22.742 --> 00:57:24.550
I've got a new section.

00:57:24.550 --> 00:57:27.360
This section is up at the top,
called Support and

00:57:27.360 --> 00:57:28.610
Troubleshooting.

00:57:28.610 --> 00:57:29.420
What this is,

00:57:29.420 --> 00:57:32.600
is a set of tools and
capabilities that we've added

00:57:32.600 --> 00:57:36.550
that are very easy to go find
and use to make it super simple

00:57:36.550 --> 00:57:39.620
to go to solve problems that
may be happening with your VM.

00:57:39.620 --> 00:57:41.940
It's a one stop shop for
solutions and

00:57:41.940 --> 00:57:44.830
will continue to add things as
we learn more and more about

00:57:44.830 --> 00:57:47.700
the way customers wanna
interact with this experience.

00:57:47.700 --> 00:57:50.590
Some examples here you can reset
your password directly from this

00:57:50.590 --> 00:57:54.470
experience, you can even resize
your virtual machine right here.

00:57:54.470 --> 00:57:57.040
So for investigating
this specific problem and

00:57:57.040 --> 00:58:00.260
your next two being down, the
first thing I wanna look at is

00:58:00.260 --> 00:58:03.120
maybe some changes happened to
this that I wasn't quite aware

00:58:03.120 --> 00:58:05.200
of or
happened without me knowing.

00:58:05.200 --> 00:58:07.210
And I'll click into
the audit logs, and so,

00:58:07.210 --> 00:58:10.360
quickly you can see,
I take a look at my audit logs.

00:58:10.360 --> 00:58:13.120
And I can see some of the most
recent actions that have

00:58:13.120 --> 00:58:15.310
happened against my
merch virtual machine.

00:58:15.310 --> 00:58:16.960
So on Sunday, a couple days ago,

00:58:16.960 --> 00:58:20.110
I see quite a few operations
that look a little strange,

00:58:20.110 --> 00:58:22.800
someone was deallocating and
restarting my machine.

00:58:22.800 --> 00:58:24.580
Well this may be part
of the problem, so

00:58:24.580 --> 00:58:26.070
let me find out who did that and

00:58:26.070 --> 00:58:30.035
I can go talk to them and see
what improvements we wanna make.

00:58:30.035 --> 00:58:32.892
[SOUND] So it was ScottRedshirt,
that made those changes so

00:58:32.892 --> 00:58:35.720
I kind of regret giving
him access to my machines.

00:58:35.720 --> 00:58:38.940
So now that I know who
made these changes,

00:58:38.940 --> 00:58:42.710
the next big question is, what's
actually going on with them?

00:58:42.710 --> 00:58:46.140
So if I zoom back over to my
troubleshooting section and

00:58:46.140 --> 00:58:48.000
go into boot diagnostics.

00:58:48.000 --> 00:58:50.890
This is a new capability
available today, on your virtual

00:58:50.890 --> 00:58:53.900
machines to be able to take
a look at the serial output

00:58:53.900 --> 00:58:57.060
of your Linux machines directly
in the portal experience.

00:58:57.060 --> 00:58:59.940
So I can go into here, this
gives the output of the kernel,

00:58:59.940 --> 00:59:01.470
it gives the output
of the driver,

00:59:01.470 --> 00:59:04.290
even applications if they're
piped into that serial output.

00:59:04.290 --> 00:59:05.480
It's fully searchable and so

00:59:05.480 --> 00:59:08.460
I can go in and look for
the word failed, and zoom down

00:59:08.460 --> 00:59:11.810
here to the ones at the end and
sure enough it looks like

00:59:11.810 --> 00:59:14.530
there's something going wrong
where this machine can't boot.

00:59:14.530 --> 00:59:17.350
It's failing to find some of the
applications that it's looking

00:59:17.350 --> 00:59:18.660
and so now I know the problem.

00:59:18.660 --> 00:59:21.420
Within a matter of seconds,
I'm able to quickly determine

00:59:21.420 --> 00:59:23.880
what was the problem with this
instance and I can go fix it.

00:59:25.970 --> 00:59:27.330
Now that's great on Linux and

00:59:27.330 --> 00:59:29.180
the serial output's
really powerful.

00:59:29.180 --> 00:59:32.350
But of course on Windows we
don't really have that luxury.

00:59:32.350 --> 00:59:35.380
There isn't a lot of information
that pipes out on Serium.

00:59:35.380 --> 00:59:37.550
So what we've
enabled on Windows,

00:59:37.550 --> 00:59:40.520
one of the first of the big
cloud providers to do this,

00:59:40.520 --> 00:59:42.750
is outputting
the counsel output.

00:59:42.750 --> 00:59:45.520
So you can see here for
a healthy Windows machine,

00:59:45.520 --> 00:59:48.380
I can detect that this
login screen is there and

00:59:48.380 --> 00:59:51.100
the machine is up and
running in a healthy way.

00:59:51.100 --> 00:59:52.300
Right in my portal experience.

00:59:52.300 --> 00:59:55.972
If I go back to the machine
that was actually unhealthy and

00:59:55.972 --> 00:59:59.719
take a look there Here you can
see the failure screen that it

00:59:59.719 --> 01:00:01.729
has not successfully booted.

01:00:01.729 --> 01:00:04.979
It's failing to boot because
it can't find the colonel,

01:00:04.979 --> 01:00:07.431
actually, and so
it has failed to launch and

01:00:07.431 --> 01:00:11.290
now I know my problem, and I
actually know how to go fix it.

01:00:11.290 --> 01:00:12.930
I'm not quite sure why
people were deleting

01:00:12.930 --> 01:00:15.665
files from my machines, but at
least I've solved the problem.

01:00:15.665 --> 01:00:19.460
[COUGH] As we continue to
grow this experience in

01:00:19.460 --> 01:00:22.260
troubleshooting and support,
we'll keep adding tools and

01:00:22.260 --> 01:00:25.610
capabilities, things like being
able to reset your firewall or

01:00:25.610 --> 01:00:29.160
actually configure alerts
directly in this experience.

01:00:29.160 --> 01:00:30.440
One of the diagnostics or

01:00:30.440 --> 01:00:34.610
capabilities we will be adding
as well is on the network side.

01:00:34.610 --> 01:00:36.550
You may see all your virtual
machines as healthy.

01:00:36.550 --> 01:00:38.280
They all may be
booting correctly, but

01:00:38.280 --> 01:00:39.760
you can't access them.

01:00:39.760 --> 01:00:41.450
And the likely problem
there might be the network

01:00:41.450 --> 01:00:43.500
configuration that
you've set up.

01:00:43.500 --> 01:00:47.710
So a new addition in the coming
months offers network analytics.

01:00:47.710 --> 01:00:50.460
Where you can take the output
of all of the rules

01:00:50.460 --> 01:00:53.010
configured across your
network infrastructure into

01:00:53.010 --> 01:00:54.460
a single storage account.

01:00:54.460 --> 01:00:57.290
To then be viewed in
a variety of viewers.

01:00:57.290 --> 01:00:59.100
Here, I’ve actually
got it set up to view

01:00:59.100 --> 01:01:01.600
directly in operations
management suite.

01:01:01.600 --> 01:01:03.670
So using the tooling that
I’m using to manage all of

01:01:03.670 --> 01:01:07.640
my instances, I can see the
denied flow traffic right here.

01:01:07.640 --> 01:01:11.930
And see, wow, 275,000 denied
flows to these instances.

01:01:11.930 --> 01:01:14.060
This is probably my problem.

01:01:14.060 --> 01:01:16.260
I need to go look at that
network security rule and

01:01:16.260 --> 01:01:17.380
maybe make a few changes.

01:01:18.690 --> 01:01:20.370
Zooming back over.

01:01:20.370 --> 01:01:23.150
One of the next additional
changes that we will add.

01:01:23.150 --> 01:01:25.690
Support into
the troubleshooting section

01:01:25.690 --> 01:01:29.760
is a new area called
the resource health check.

01:01:29.760 --> 01:01:33.180
This is going to offer you
a view of your instances

01:01:33.180 --> 01:01:34.620
from the platform perspective.

01:01:35.820 --> 01:01:39.260
Instead of offering a giant map
that shows you all the problems

01:01:39.260 --> 01:01:41.020
that the platform
may be experiencing,

01:01:41.020 --> 01:01:43.890
instead we'd like to make sure
that we showed you the problems

01:01:43.890 --> 01:01:46.500
that are going to impact
you when you wanna see them

01:01:46.500 --> 01:01:48.070
on your instances.

01:01:48.070 --> 01:01:50.310
And so what we're offering as
part of this new service in

01:01:50.310 --> 01:01:53.570
the coming months, is the
ability to take a look at your

01:01:53.570 --> 01:01:57.300
instances from our perspective,
using our operational logs and

01:01:57.300 --> 01:01:58.630
our knowledge of
what's going on.

01:01:58.630 --> 01:02:01.220
And so here you can see
the same four instances

01:02:01.220 --> 01:02:03.650
are shown as part
of this experience.

01:02:03.650 --> 01:02:06.500
And when problems may come up,
you can actually click in and

01:02:06.500 --> 01:02:07.800
see if there are workarounds or

01:02:07.800 --> 01:02:11.440
options to prepare the instance
when it's in this state.

01:02:11.440 --> 01:02:12.240
You can even go in and

01:02:12.240 --> 01:02:15.450
create a support request
directly from this experience

01:02:15.450 --> 01:02:18.910
without having to memorize a
long GUID or the name of the VM.

01:02:18.910 --> 01:02:21.540
It's all in context
with your support plan

01:02:21.540 --> 01:02:24.510
ready to go personalized to you.

01:02:24.510 --> 01:02:27.100
So across the overall
section we've added a new

01:02:27.100 --> 01:02:30.330
troubleshooting section, that is
brand new and available today.

01:02:30.330 --> 01:02:33.500
It offers connection with serial
output and console output to

01:02:33.500 --> 01:02:35.820
be able to track the health
of your instances.

01:02:35.820 --> 01:02:37.850
We will be releasing
these network analytics,

01:02:37.850 --> 01:02:40.410
to make it very easy to
track the security and

01:02:40.410 --> 01:02:42.560
the health of your
network infrastructure.

01:02:42.560 --> 01:02:45.860
We will also be releasing this
new resource health check,

01:02:45.860 --> 01:02:48.160
that will tell you the state
of your instances, but

01:02:48.160 --> 01:02:49.890
from the platform perspective.

01:02:49.890 --> 01:02:52.170
Overall, I think these will
make it much easier and

01:02:52.170 --> 01:02:55.630
much simpler to use the platform
when problems do arise.

01:02:55.630 --> 01:02:56.406
Thank you so much.

01:02:56.406 --> 01:03:02.106
[APPLAUSE]

01:03:02.106 --> 01:03:04.740
>> Switch back to

01:03:04.740 --> 01:03:05.810
the slides there.

01:03:05.810 --> 01:03:09.740
It's always, kind of,
Corey showed the ease

01:03:09.740 --> 01:03:13.020
of use in terms of, that we're
trying to really bake in, even

01:03:13.020 --> 01:03:16.440
in terms of the troubleshooting
and support experience.

01:03:16.440 --> 01:03:20.520
And how it really enables you to
basically have kind of a really

01:03:20.520 --> 01:03:24.070
great finished experience that
enables you to kind of run your

01:03:24.070 --> 01:03:27.600
solutions with confidence,
on top of our infrastructure.

01:03:28.770 --> 01:03:31.500
And obviously, in addition
to running the experiences,

01:03:31.500 --> 01:03:34.580
we want to be able to provide
as cost effective an experience

01:03:34.580 --> 01:03:36.440
as possible when you do so.

01:03:36.440 --> 01:03:39.160
And one of the things that we've
committed to in terms from

01:03:39.160 --> 01:03:42.060
a price matching perspective is

01:03:42.060 --> 01:03:44.690
across the board to make sure
that for all of our commodity

01:03:44.690 --> 01:03:47.450
infrastructure services
that we match

01:03:47.450 --> 01:03:50.110
all of the growing rates of any
of the other cloud providers.

01:03:50.110 --> 01:03:52.640
That's something that we've done
over the last several years.

01:03:52.640 --> 01:03:55.370
One of the things that we're
also excited to announce today

01:03:55.370 --> 01:03:57.760
is a new pricing program.

01:03:57.760 --> 01:04:02.600
That would be available
in the coming weeks

01:04:02.600 --> 01:04:05.471
which we call our Azure
compute pre-purchase plan.

01:04:05.471 --> 01:04:09.810
And what this allows you to do
is pre-purchase compute hours

01:04:09.810 --> 01:04:12.560
that you can leverage as
part of your solutions.

01:04:12.560 --> 01:04:16.230
And it allows you to
save up to 63% off

01:04:16.230 --> 01:04:19.270
of the standard
Azure compute costs.

01:04:19.270 --> 01:04:21.710
This will be available
globally and

01:04:21.710 --> 01:04:26.028
we think provides the most cost
effective way to go ahead and

01:04:26.028 --> 01:04:29.510
pre-purchase Azure resources and

01:04:29.510 --> 01:04:34.030
to enable us to pass on
even more savings to you.

01:04:34.030 --> 01:04:36.300
That you can take advantage
of as you build and

01:04:36.300 --> 01:04:37.510
deploy your solutions.

01:04:37.510 --> 01:04:40.780
I will be talking a lot more
about this throughout the day.

01:04:42.080 --> 01:04:44.740
As we built out these
infrastructure services as

01:04:44.740 --> 01:04:48.020
we build out things like
security, troubleshooting tools,

01:04:48.020 --> 01:04:50.300
and provide even
better cost savings.

01:04:50.300 --> 01:04:52.650
We're seeing just
a huge number of

01:04:52.650 --> 01:04:55.420
customers that
are increasingly moving.

01:04:55.420 --> 01:04:58.702
Not just their customer
facing applications but

01:04:58.702 --> 01:05:02.545
increasingly their core IT
infrastructure services and

01:05:02.545 --> 01:05:04.636
systems to run on top of Azure.

01:05:04.636 --> 01:05:07.482
And you're going to hear more
about them from a number of

01:05:07.482 --> 01:05:10.270
these customers throughout
todays' events in some of

01:05:10.270 --> 01:05:11.880
the breakout talks.

01:05:11.880 --> 01:05:12.720
For example,

01:05:12.720 --> 01:05:15.710
in Jason Zanders talk a little
bit later on today, we're going

01:05:15.710 --> 01:05:18.830
to be very fortunate to have
Walmart join us on stage and

01:05:18.830 --> 01:05:22.530
talk about how they're starting
to take Walmart IT and

01:05:22.530 --> 01:05:25.280
be able to migrate
solutions to run on Azure.

01:05:25.280 --> 01:05:26.998
And some of the reasons
behind it and

01:05:26.998 --> 01:05:29.700
some of their experiences and
learnings from doing so.

01:05:29.700 --> 01:05:32.410
You've heard of Ventenimos and

01:05:32.410 --> 01:05:34.750
others that are building
things like banking solutions.

01:05:34.750 --> 01:05:37.430
And running them on top
of our cloud as well.

01:05:37.430 --> 01:05:41.760
And then one of the customers
that we're particularly excited

01:05:41.760 --> 01:05:45.180
about because it really
illustrates how the cloud can

01:05:45.180 --> 01:05:47.710
not only be used from
a commercial perspective but

01:05:47.710 --> 01:05:50.300
can really be used from
a humanitarian perspective to

01:05:50.300 --> 01:05:54.020
really change the world, is the
United Nations, which is running

01:05:54.020 --> 01:05:57.690
a lot of their disaster relief
systems now on top of Azure.

01:05:57.690 --> 01:06:00.580
And are able to take advantage
and use it in a variety of

01:06:00.580 --> 01:06:03.790
different disaster scenarios to
be able to immediately stand up

01:06:03.790 --> 01:06:08.130
infrastructure in places that
most need it after a disaster.

01:06:08.130 --> 01:06:11.100
And be able to leverage that
global reach of the cloud and

01:06:11.100 --> 01:06:13.900
the agility that the cloud
provides to do it as fast as

01:06:13.900 --> 01:06:15.590
possible when human
lives matter.

01:06:15.590 --> 01:06:18.030
What I would like to do is
actually show a quick video

01:06:18.030 --> 01:06:20.685
of some of their experiences
of doing this in Nepal.

01:06:20.685 --> 01:06:27.579
[SOUND]
>> The future

01:06:27.579 --> 01:06:29.690
can offer hope and possibility.

01:06:30.740 --> 01:06:32.260
We help shape it
with our character,

01:06:32.260 --> 01:06:34.410
and build it with our dreams.

01:06:35.790 --> 01:06:39.620
But the future can also present
us obstacles that test our will

01:06:39.620 --> 01:06:40.589
and determination.

01:06:41.970 --> 01:06:44.184
This is how we find
the power within us.

01:06:44.184 --> 01:06:46.585
[MUSIC]

01:06:46.585 --> 01:06:49.227
>> The frantic search for
survivors goes on around

01:06:49.227 --> 01:06:52.869
the clock following Nepal's
biggest earthquake in 80 years.

01:06:52.869 --> 01:06:59.296
[MUSIC]

01:06:59.296 --> 01:07:02.175
Disaster relief is
always overwhelming.

01:07:02.175 --> 01:07:04.730
There's too much to do, too
many people that need help, and

01:07:04.730 --> 01:07:06.405
never enough time or resources.

01:07:06.405 --> 01:07:10.715
The United Nations Development
Program is a global network of

01:07:10.715 --> 01:07:13.375
knowledge, experience,
and resources.

01:07:13.375 --> 01:07:15.810
We're a group focused on
building sustainable communities

01:07:15.810 --> 01:07:16.730
and empowering people.

01:07:18.320 --> 01:07:21.010
And now, partnering with
Microsoft our frontline

01:07:21.010 --> 01:07:23.820
responders in Nepal
are testing a new approach.

01:07:23.820 --> 01:07:27.270
Using the Microsoft Cloud
to store and process data.

01:07:27.270 --> 01:07:30.880
Helping obtain the insights we
need to help our programs have

01:07:30.880 --> 01:07:32.234
the greatest impact.

01:07:32.234 --> 01:07:35.121
With over 600,000 buildings
destroyed in the quake,

01:07:35.121 --> 01:07:37.951
The Debris Management Program
was established to bring fast

01:07:37.951 --> 01:07:41.190
acting relief and recovery to
support the hardest hit areas.

01:07:41.190 --> 01:07:42.610
In four short months,

01:07:42.610 --> 01:07:44.990
we've equipped local engineers
with mobile devices and

01:07:44.990 --> 01:07:48.490
a custom application to expedite
damage assessments, prepare for

01:07:48.490 --> 01:07:51.400
safe demolition, and
track our efficiency.

01:07:51.400 --> 01:07:54.266
Completing over 3,200
assessments and 2,000 saved

01:07:54.266 --> 01:07:57.830
demolition projects, paving
the way for reconstruction.

01:07:57.830 --> 01:08:00.030
This application will
also become essential

01:08:00.030 --> 01:08:01.130
to our emergency
employment acts.

01:08:01.130 --> 01:08:04.080
And combined with QR
card distribution,

01:08:04.080 --> 01:08:07.130
we'll be able to provide
critical daily cash payments

01:08:07.130 --> 01:08:09.900
to thousands of workers
helping to clear debris.

01:08:09.900 --> 01:08:10.780
Putting money back into

01:08:10.780 --> 01:08:12.220
communities that
need it the most.

01:08:14.680 --> 01:08:17.720
Additionally, a joint poverty
alleviation initiative

01:08:17.720 --> 01:08:20.700
between the UNVP and
the government of Nepal is

01:08:20.700 --> 01:08:23.820
using the cloud to collaborate
with other partner organizations

01:08:23.820 --> 01:08:26.970
providing support to over
13,000 micro enterprises.

01:08:26.970 --> 01:08:30.830
Helping them get their
businesses back on their feet.

01:08:32.130 --> 01:08:35.250
Disasters create unique
opportunities for innovation.

01:08:35.250 --> 01:08:38.507
Our partnerships and our work
here in Nepal are strengthening

01:08:38.507 --> 01:08:41.199
the UNDP's current operation
while allowing us to

01:08:41.199 --> 01:08:43.954
develop new cloud programs
that will revolutionize

01:08:43.954 --> 01:08:46.789
the way relief organizations
operate in the future.

01:08:46.789 --> 01:08:48.971
[MUSIC]

01:08:48.971 --> 01:08:52.083
>> The Nepali people have shown
dedication, tenacity, and

01:08:52.083 --> 01:08:52.660
resolve.

01:08:52.660 --> 01:08:54.901
And with our continued support,

01:08:54.901 --> 01:08:58.188
they will be empowered to
build a better future.

01:08:58.188 --> 01:09:08.188
[MUSIC]

01:09:17.205 --> 01:09:21.644
We continue to kind of be amazed
with the types of solutions that

01:09:21.644 --> 01:09:25.749
are being built using The Cloud
and just the imagination,

01:09:25.749 --> 01:09:27.257
the creativity, and

01:09:27.257 --> 01:09:31.220
the way that it can really
change the world for all of us.

01:09:31.220 --> 01:09:33.800
And we're really excited to
spend the rest of the day going

01:09:33.800 --> 01:09:36.781
to much more depth in terms of
what we're building with Azure,

01:09:36.781 --> 01:09:40.010
again be able to share more
customer success stories

01:09:40.010 --> 01:09:42.610
as well as learnings in terms of
how people are taking advantage

01:09:42.610 --> 01:09:46.370
of the cloud and the lessons
that can be learned from that.

01:09:46.370 --> 01:09:48.933
And stay tuned throughout the
rest of the event for more than

01:09:48.933 --> 01:09:52.130
60 different breakout sessions
that will be streamed online.

01:09:52.130 --> 01:09:53.240
We've got a number of great

01:09:53.240 --> 01:09:56.030
additional keynotes that will
be coming right after me.

01:09:56.030 --> 01:09:59.050
Going into more depth, in terms
of building applications,

01:09:59.050 --> 01:10:02.080
data and insights in IOT,
as well as the infrastructure

01:10:02.080 --> 01:10:04.930
announcements we made today,
and we're really excited

01:10:04.930 --> 01:10:08.060
to see what you build with them,
and I want to thank everyone for

01:10:08.060 --> 01:10:09.815
participating, so
thank you very much.

01:10:09.815 --> 01:10:12.520
>> [APPLAUSE]