WEBVTT

01:59:56.650 --> 00:00:00.296
MICROSOFT CORPORATE VICE PRESIDENT,
00:00:00.296 --> 00:00:05.728
JULIA WHITE. >> GOOD MORNING. THANK
00:00:05.728 --> 00:00:09.656
YOU FOR JOINING US AT THE AZURE
00:00:09.656 --> 00:00:11.089
TECHNICAL QUEKEYNOTE. HOPEFULLY
00:00:11.089 --> 00:00:15.913
YOU WERE INSPIRED BY WHAT YOU SAW
00:00:15.913 --> 00:00:19.172
FROM SATYA. AND WE HAVE INFRASTRUCTURE,
00:00:19.172 --> 00:00:22.375
APP DEV, DATA, AND A. I. MANY OF
00:00:22.375 --> 00:00:23.936
YOU HAVE FRONT ROW SEATS TO THE DIGITAL
00:00:23.936 --> 00:00:24.683
TRANSFORMATION THAT'S HAPPENING
00:00:24.683 --> 00:00:29.557
IN YOUR ORGANIZATION AND ACROSS
00:00:29.557 --> 00:00:30.987
TECHNOLOGY. WE'RE THE CRITICAL DRIVERS,
00:00:30.987 --> 00:00:32.956
THE CHANGE AGENTS THAT ARE HELPING
00:00:32.956 --> 00:00:36.450
MAKE THAT DIGITAL TRANSFORMATION
00:00:36.450 --> 00:00:42.319
A REAL. THIS TAKES TIME. IT DOESN'T
00:00:42.319 --> 00:00:44.280
HAPPEN IN A SINGLE MOVE OR MOMENT.
00:00:44.280 --> 00:00:45.996
THAT'S HAPPENS, THE OUTCOMES, THE
00:00:45.996 --> 00:00:47.655
STORIES THAT YOU ARE ACHIEVING ARE
00:00:47.655 --> 00:00:51.101
TRULY INSPIRING TO US. I WANTED
00:00:51.101 --> 00:00:52.385
TO SHARE A COUPLE OF THOSE STORIES
00:00:52.385 --> 00:00:57.666
THIS MORNING. FIRST IS THIS ORGANIZATION.
00:00:57.666 --> 00:00:58.748
THEY'RE HIRING MORE DEVELOPERS THAN
00:00:58.748 --> 00:01:00.616
FACEBOOK. THEY EMPLOY SOME OF THE
00:01:00.616 --> 00:01:02.200
TOP DATA A. I. SCIENTISTS IN THE
00:01:02.200 --> 00:01:04.034
WORLD. THEY'VE DEPLOYED A. I. TECHNOLOGIES
00:01:04.034 --> 00:01:05.426
THAT ARE HAVING MATERIAL IMPACT
00:01:05.426 --> 00:01:07.343
ON THEIR BOTTOM LINE. THEY HAVE
00:01:07.343 --> 00:01:09.441
IN THEIR COOL, HIP, FUNKY OFFICE
00:01:09.441 --> 00:01:11.256
IN AUSTIN TO SHOW FOR THEIR TECH
00:01:11.256 --> 00:01:13.354
CULTURE. AND THIS ORGANIZATION,
00:01:13.354 --> 00:01:15.464
IT'S WALMART. THEY HAVE TRANSFORMED
00:01:15.464 --> 00:01:18.437
TO BECOME A DIGITAL ORGANIZATION.
00:01:18.437 --> 00:01:20.964
NOW THIS COMPANY IS BASED IN JAPAN.
00:01:20.964 --> 00:01:23.004
AND THEY'VE DEVELOPED A. I. MODELS
00:01:23.004 --> 00:01:25.328
FOR THE HOSPITALITY INDUSTRY, THUS
00:01:25.328 --> 00:01:26.824
DELIVERING SUSTAINED BUSINESS GROWTH
00:01:26.824 --> 00:01:29.885
FOR THEIR CLIENTS. AND THEIR LEAD
00:01:29.885 --> 00:01:30.931
DATA SCIENTIST IS NOW PRODUCING
00:01:30.931 --> 00:01:33.471
A. I. MODELS THAT ARE WITHIN 1 OF
00:01:33.471 --> 00:01:35.756
ACCURACY OF THEIR ACTUAL BUSINESS
00:01:35.756 --> 00:01:37.862
RESULTS. THIS ORGANIZATION IS A
00:01:37.862 --> 00:01:41.056
TINY FAMILY-OWNED RESTAURANT CALLED
00:01:41.056 --> 00:01:44.276
EBIA. AND THIS WAITRESS HERE IS
00:01:44.276 --> 00:01:46.777
THEIR LEAD DATA SCIENTIST. SHE IS
00:01:46.777 --> 00:01:48.525
FREE -- HAS FREE ONLINE TRAININGS
00:01:48.525 --> 00:01:50.990
AND CLASSES TO LEARN AZURE MACHINE
00:01:50.990 --> 00:01:52.504
LEARNING AND POWER BI, AND HER WORK
00:01:52.504 --> 00:01:54.116
IS LEADING TO SHIFTS IN THE RESTAURANT'S
00:01:54.116 --> 00:01:55.997
LAYOUT, THE MENU, EVEN THE SERVICES
00:01:55.997 --> 00:01:59.280
THAT HAS LED TO A TENX INCREASE
00:01:59.280 --> 00:02:01.381
IN THEIR SALES. THEIR TECHNOLOGY
00:02:01.381 --> 00:02:03.112
HAS CAUGHT FIRE IN THE SMALL BUSINESS
00:02:03.112 --> 00:02:04.526
COMMUNITY ACROSS JAPAN, AND NOW
00:02:04.526 --> 00:02:07.180
IS BEING USED IN SOME OF THE LARGEST
00:02:07.180 --> 00:02:10.216
BRANDS IN THE COUNTRY. NOW LAST,
00:02:10.216 --> 00:02:11.343
LET'S LOOK AT THE MANUFACTURING
00:02:11.343 --> 00:02:14.343
PLANT LINE. THIS IS A PLACE WHERE
00:02:14.343 --> 00:02:15.825
TECHNOLOGY HASN'T ALWAYS REACHED.
00:02:15.825 --> 00:02:18.259
WHEN YOU'RE HEADS-UP, HANDS ON,
00:02:18.259 --> 00:02:19.300
TECHNOLOGY ISN'T ALWAYS AVAILABLE.
00:02:19.300 --> 00:02:21.485
AND WHEN IT IS, IT MAY NOT BE VERY
00:02:21.485 --> 00:02:23.466
USEFUL. WHILE MANY OF US IN THIS
00:02:23.466 --> 00:02:26.636
ROOM HERE TODAY HAVE SEEN OUR LIVES
00:02:26.636 --> 00:02:29.397
AND OUR LIVELIHOODS CHANGED BY TECHNOLOGY,
00:02:29.397 --> 00:02:31.131
IT HASN'T ALWAYS NECESSARILY BEEN
00:02:31.131 --> 00:02:33.508
TRUE FOR ALL EMPLOYEES ACROSS THE
00:02:33.508 --> 00:02:36.284
GLOBE. NOW, WITH THE CLOUD AND THE
00:02:36.284 --> 00:02:39.814
EDGE WORKING TOGETHER, THIS IS CHANGING.
00:02:39.814 --> 00:02:42.082
THIS IS CHELSEA POTTS. SHE'S A SINGLE
00:02:42.082 --> 00:02:44.967
MOM WITH A HIGH SCHOOL DEGREE. AND
00:02:44.967 --> 00:02:47.224
SHE'S HISTORICALLY ONLY HAD ACCESS
00:02:47.224 --> 00:02:49.307
TO MINIMUM WAGE JOBS. AND SHE WAS
00:02:49.307 --> 00:02:53.245
THRILLED TO LAND A HIGH-PAYING JOB
00:02:53.245 --> 00:02:54.668
AT PACCAR BECAUSE PACCAR IS USING
00:02:54.668 --> 00:02:57.308
A COP BINGZ OF HOLLOW LENS, AZURE,
00:02:57.308 --> 00:03:01.097
AND DYNAMICS 365 MIXED REALITY APPLICATIONS.
00:03:01.097 --> 00:03:02.328
CHELSEA'S GUIDED STEP BY STEP THROUGH
00:03:02.328 --> 00:03:04.688
THE COMPLEX PROCESS OF PUTTING TOGETHER
00:03:04.688 --> 00:03:07.837
THIS TRUCK PART. AND THIS HAS FUNDAMENTALLY
00:03:07.837 --> 00:03:09.384
CHANGED CHELSEA'S ECONOMIC OPPORTUNITY
00:03:09.384 --> 00:03:12.833
AND HER ABILITY TO PROVIDE FOR HER
00:03:12.833 --> 00:03:14.768
FAMILY. THESE STORIES ARE GREAT
00:03:14.768 --> 00:03:17.400
EXAMPLES OF HOW CUSTOMERS ARE INVENTING
00:03:17.400 --> 00:03:19.307
WITH PURPOSE ON AZURE. AND IT'S
00:03:19.307 --> 00:03:21.443
THIS FOCUS ON YOUR OUTCOMES THAT
00:03:21.443 --> 00:03:23.954
HELPS US INVENT WITH PURPOSE THE
00:03:23.954 --> 00:03:26.152
PLATFORM AND THE FEATURES THAT YOU
00:03:26.152 --> 00:03:28.549
NEED TO BE SUCCESSFUL. TO DO THIS,
00:03:28.549 --> 00:03:30.797
IT STARTS WITH ENSURING THAT YOU
00:03:30.797 --> 00:03:32.454
HAVE A FUTURE-READY PLATFORM, THAT
00:03:32.454 --> 00:03:34.404
WE HAVE THE TECHNOLOGIES AND CAPABILITIES
00:03:34.404 --> 00:03:36.065
YOU NEED TODAY BUT ALSO INVESTING
00:03:36.065 --> 00:03:37.629
AHEAD OF THE CURVE AND MANY OF THE
00:03:37.629 --> 00:03:38.951
THINGS THAT YOU HEARD SATYA TALK
00:03:38.951 --> 00:03:40.840
ABOUT TO ENSURE YOU HAVE WHAT YOU
00:03:40.840 --> 00:03:42.994
NEED FOR THE NEXT 50 YEARS, AS WELL.
00:03:42.994 --> 00:03:44.371
FOR DEVELOPERS, IT'S ABOUT ENSURING
00:03:44.371 --> 00:03:45.524
THAT YOU CAN BUILD WITH THE TOOLS
00:03:45.524 --> 00:03:46.741
YOU WANT, WITH THE LANGUAGES YOU
00:03:46.741 --> 00:03:49.024
WANT, AND ON THE PLATFORMS YOU WANT,
00:03:49.024 --> 00:03:51.846
SO YOU CAN INNOVATE FOR YOUR ORGANIZATION
00:03:51.846 --> 00:03:54.166
IN WAYS THEY EXPECT YOU TO DELIVER.
00:03:54.166 --> 00:03:57.657
AND ON THE AZURE TEAM, WE HAVE ALWAYS
00:03:57.657 --> 00:04:00.126
UNDERSTOOD THE IMPORTANCE OF THE
00:04:00.126 --> 00:04:01.434
HYBRID APPROACH ACROSS PREMISES,
00:04:01.434 --> 00:04:03.023
CLOUD, AND THE EDGE. YOU CAN COUNTY
00:04:03.023 --> 00:04:05.511
ON US TO MAKE SURE YOU CAN RUN YOUR
00:04:05.511 --> 00:04:07.066
ENVIRONMENT SEAMLESSLY AND WITH
00:04:07.066 --> 00:04:09.606
CONSISTENCY ACROSS MANAGEMENT, GOVERNANCE,
00:04:09.606 --> 00:04:11.733
SECURITY, WHEREVER MULTIPLE LOCATIONS
00:04:11.733 --> 00:04:13.825
WHERE YOUR APPLICATION RESIDES.
00:04:13.825 --> 00:04:16.876
AND ULTIMATELY, IT'S ABOUT TRUST.
00:04:16.876 --> 00:04:18.505
WE'RE FOCUSED ON TRUST EVERY SINGLE
00:04:18.505 --> 00:04:19.732
DAY BECAUSE WE KNOW TRUST IS EARNED
00:04:19.732 --> 00:04:22.624
IN THE LONG TERM BUT CAN BE LOST
00:04:22.624 --> 00:04:24.428
IN SECONDS. THAT'S WHY WE INVEST
00:04:24.428 --> 00:04:27.900
$1 BILLION A YEAR IN CYBERSECURITY
00:04:27.900 --> 00:04:29.435
AND WHY WE HAVE ALWAYS HAD MORE
00:04:29.435 --> 00:04:31.308
COMPLIANT CERTIFICATIONS THAN ANY
00:04:31.308 --> 00:04:32.777
OTHER PRIVATE CLOUD PROVIDER. IT'S
00:04:32.777 --> 00:04:35.238
ALSO ABOUT BEING CLEAR THAT WE ARE
00:04:35.238 --> 00:04:36.220
A TECHNOLOGY COMPANY AND WE'RE NOT
00:04:36.220 --> 00:04:39.898
GOING TO COMPETE WITH OUR CUSTOMERS.
00:04:39.898 --> 00:04:42.698
I'M INCREDIBLY PROUD THAT 95 OF
00:04:42.698 --> 00:04:45.116
THE FORTUNE 500 HAS TRUSTED AZURE
00:04:45.116 --> 00:04:46.976
FOR THEIR BUSINESS. EACH OF THESE
00:04:46.976 --> 00:04:49.498
ORGANIZATIONS ON THIS SLIDE IS USING
00:04:49.498 --> 00:04:51.318
AZURE IN MEANINGFUL WAYS SO THAT
00:04:51.318 --> 00:04:54.787
THEY CAN INVENT WITH PURPOSE. NOW,
00:04:54.787 --> 00:04:57.297
TO HEAR MORE ABOUT THE INNOVATIONS
00:04:57.297 --> 00:05:00.074
THAT'S POWERING ALL OF THIS, PLEASE
00:05:00.074 --> 00:05:02.378
HELP ME WELCOME JAYSON ZANDER, EXECUTIVE
00:05:02.378 --> 00:05:11.124
VICE PRESIDENT OF AZURE. [ MUSIC
00:05:11.124 --> 00:05:13.510
] >> GOOD MORNING, EVERYBODY. I
00:05:13.510 --> 00:05:15.518
WANT TO ADD MY WELCOME, AS WELL,
00:05:15.518 --> 00:05:18.524
TO IGNITE. THIS IS ONE OF MY FAVORITE
00:05:18.524 --> 00:05:20.053
CONFERENCES FROM THE ENGINEERING
00:05:20.053 --> 00:05:21.318
TEAM, AND IT'S A GREAT OPPORTUNITY
00:05:21.318 --> 00:05:23.156
FOR THE WHOLE TEAM TO COME HERE.
00:05:23.156 --> 00:05:24.721
WE LOVE TO SHOW OFF SOME OF THE
00:05:24.721 --> 00:05:25.745
TECHNOLOGY THAT WE HAVE BUILT. WE
00:05:25.745 --> 00:05:27.485
ALSO LOVE TO HEAR THE FEEDBACK FROM
00:05:27.485 --> 00:05:29.603
YOU. NOW, WE'VE GOT A HUGE AGENDA
00:05:29.603 --> 00:05:31.824
HERE. WE'RE GOING TO COVER EVERYTHING
00:05:31.824 --> 00:05:33.720
FROM INFRASTRUCTURE THROUGH ARTIFICIAL
00:05:33.720 --> 00:05:35.099
INTELLIGENCE. LET'S GO AHEAD AND
00:05:35.099 --> 00:05:37.656
GET GOING. I WANT TO START OFF AT THE
00:05:37.656 --> 00:05:39.420
BASE WITH INFRASTRUCTURE. AND THE
00:05:39.420 --> 00:05:40.294
INFRASTRUCTURE PIECE STARTS OFF
00:05:40.294 --> 00:05:42.060
WITH THE REGIONS THAT WE HAVE AROUND
00:05:42.060 --> 00:05:44.987
THE WORLD. 54. NOW THESE ARE DESIGNED
00:05:44.987 --> 00:05:47.156
SPECIFICALLY TO GET YOU AS CLOSE
00:05:47.156 --> 00:05:48.827
AS POSSIBLE TO YOUR CUSTOMERS, AS
00:05:48.827 --> 00:05:51.212
WELL AS YOUR OWN EMPLOYEESY TO YOU
00:05:51.212 --> 00:05:53.705
CAN GET MAXIMUM REACH AND EXPAND
00:05:53.705 --> 00:05:55.270
YOUR BUSINESS. MOST RECENTLY SINCE
00:05:55.270 --> 00:05:57.841
THE LAST TIME YOU PROBABLY SAW THIS
00:05:57.841 --> 00:05:59.180
SLIDE, WE HAVE BROUGHT TO GENERAL
00:05:59.180 --> 00:06:01.567
AVAILABILITY, NEW REGIONS IN GERMANY
00:06:01.567 --> 00:06:02.795
AND SWITZERLAND. AND WE HAVE A NEW
00:06:02.795 --> 00:06:04.369
REGION WE'VE ANNOUNCED COMING IN
00:06:04.369 --> 00:06:06.352
NORWAY. NOW IT'S NOT JUST ABOUT
00:06:06.352 --> 00:06:08.194
THESE DOTS. THEY'RE BIG, MASSIVE
00:06:08.194 --> 00:06:09.298
DATA CENTER REGIONS THAT WE HAVE
00:06:09.298 --> 00:06:13.360
HERE. WE ALSO HAVE 130, 000 MILES
00:06:13.360 --> 00:06:16.996
OF FIBER. BOTH ON TOP OF CONTINENTS
00:06:16.996 --> 00:06:19.037
AND IN THE OCEAN SO WE CAN CONNECT
00:06:19.037 --> 00:06:20.118
THESE TOGETHER. THAT BRINGS US TO
00:06:20.118 --> 00:06:21.554
THE MOST RELIABLE NETWORK THAT WE'VE
00:06:21.554 --> 00:06:24.446
PUT TOGETHER HERE. WE'VE GOT OVER
00:06:24.446 --> 00:06:27.448
160 EDGE SITES, 20, 000 CONNECTIONS,
00:06:27.448 --> 00:06:31.140
AND WE CAN RUN 30 BILLION PACKETS
00:06:31.140 --> 00:06:33.890
PER SECOND OVER THE WAN SO YOU CAN
00:06:33.890 --> 00:06:35.002
GET MAXIMUM CONNECTIVITY. WE HAVE
00:06:35.002 --> 00:06:37.417
GLOBAL REACH, AND THAT ALLOWS YOU
00:06:37.417 --> 00:06:39.655
TO CONNECT YOUR DATA CENTERS ACROSS
00:06:39.655 --> 00:06:43.513
THIS WAN TOGETHER. NOW OF COURSE
00:06:43.513 --> 00:06:45.814
INFRASTRUCTURE STARTS OFF WITH COMPREHENSIVE
00:06:45.814 --> 00:06:46.818
VM OFFERINGS. THAT'S THE BASE FOR
00:06:46.818 --> 00:06:48.890
THE WORKLOADS THAT WE'RE RUNNING,
00:06:48.890 --> 00:06:52.419
FOR ALL THE CONTAINER AND SERVICE
00:06:52.419 --> 00:06:54.602
WORKS. THEY START OFF WITH VMS AND
00:06:54.602 --> 00:06:57.029
MOVE UP. WE WANT A BROAD VARIETY
00:06:57.029 --> 00:06:58.570
FOR EVERY WORKLOAD YOU'RE GOING
00:06:58.570 --> 00:07:00.880
TO HAVE. WHETHER IT'S A DEMANDING
00:07:00.880 --> 00:07:01.997
WORKLOAD WITH LOTS OF TRANSACTIONS
00:07:01.997 --> 00:07:03.860
OR A GAMING WORKLOAD THAT WOULD
00:07:03.860 --> 00:07:05.527
PREFER A LOT MOTHER NATURE RAM AND
00:07:05.527 --> 00:07:08.192
CPU. FROM COST-EFFECTIVE ENTRY-LEVEL
00:07:08.192 --> 00:07:10.596
VMS TO INTRODUCING THE LARGEST VM
00:07:10.596 --> 00:07:12.864
IN THE PUBLIC CLOUD WITH 12 TERABYTES
00:07:12.864 --> 00:07:14.497
OF RAM WE'VE GOT YOU COVERED FOR
00:07:14.497 --> 00:07:17.418
EVERY ONE OF THOSE TASKS. NOW I
00:07:17.418 --> 00:07:19.453
MENTIONED SOME OF THESE REALLY HIGH-END
00:07:19.453 --> 00:07:21.315
DATA SYSTEMS. I MIGHT BE RUNNING
00:07:21.315 --> 00:07:23.612
SOMETHING LIKE S. A. P. HANNA OR
00:07:23.612 --> 00:07:25.513
A LARGE SEQUEL SERVER WORKLOAD.
00:07:25.513 --> 00:07:27.540
I WANT TO HAVE ULTRA DISTORT. THE
00:07:27.540 --> 00:07:29.600
HIGHEST PERFORMING DISCS IN THE
00:07:29.600 --> 00:07:31.849
CLOUD. I CAN SUPPORT UP TO 160,
00:07:31.849 --> 00:07:31.850
000 IOPS, TWO GIGA BITS PER SECOND
00:07:31.850 --> 00:07:37.766
PER DISC. AND 64 TERABYTES IN SIZE.
00:07:37.766 --> 00:07:40.977
THIS ONE'S SUPER IMPORTANT. ALL
00:07:40.977 --> 00:07:42.028
MY READ RIGHT LATEENSY IS GOING
00:07:42.028 --> 00:07:45.010
TO BE LESS THAN A MILLISECOND. FOR
00:07:45.010 --> 00:07:45.873
THOSE REALLY SUPER DEMANDING WORKLOADS
00:07:45.873 --> 00:07:47.409
THAT I HAVE ON THE BACK END, WE'VE
00:07:47.409 --> 00:07:48.991
GOT FANTASTIC VIRTUAL MACHINES,
00:07:48.991 --> 00:07:50.952
AND I COMPARE IT WITH DISKS AND
00:07:50.952 --> 00:07:54.035
CAN RUN THEM WITH NO PROBLEM. THE
00:07:54.035 --> 00:07:55.548
NEXT THING WE WANT TO DO IS HAVE
00:07:55.548 --> 00:07:57.564
THE VIRTUAL DESKTOP ENVIRONMENT.
00:07:57.564 --> 00:07:59.734
WE MOST RECENTLY BROUGHT TO G. A.
00:07:59.734 --> 00:08:01.757
WINDOWS VIRTUAL DESKTOP. THERE'S
00:08:01.757 --> 00:08:04.773
OVER 13, 000 CUSTOMERS USING WVD
00:08:04.773 --> 00:08:07.002
ALREADY. COMPANIES LIKE FIDELITY
00:08:07.002 --> 00:08:09.096
INFORMATION SERVICES. AND THIS IS
00:08:09.096 --> 00:08:12.351
THE ONLY BDI SOLUTION OUT THERE
00:08:12.351 --> 00:08:14.512
THAT HAS MULTIUSER WINDOWS 10 WITH
00:08:14.512 --> 00:08:15.749
DESKTOP EXPERIENCE, AND YOU ONLY
00:08:15.749 --> 00:08:17.281
PAY FOR WHAT YOU'RE GOING TO USE
00:08:17.281 --> 00:08:20.058
IT. WE HAVE AN EXTENSIVE IKE SYSTEM
00:08:20.058 --> 00:08:22.450
WITH AWESOME PARTNERS LIKE CITRIX
00:08:22.450 --> 00:08:24.252
SO I CAN RUN VIRTUAL APPS AND DESKTOPS
00:08:24.252 --> 00:08:25.508
IN THE ENVIRONMENT. IF YOU'RE PARTNERING
00:08:25.508 --> 00:08:26.884
WITH US, YOU'RE GOING TO BE IN GOOD
00:08:26.884 --> 00:08:28.970
SHAPE. AND LATER THIS YEAR, WE'RE
00:08:28.970 --> 00:08:33.132
GOING TO PREVIEW A V. M. WARE VERIZON
00:08:33.132 --> 00:08:34.748
CLOUD SUPPORT, AS WELL. WE DIDN'T
00:08:34.748 --> 00:08:36.460
STOP THERE. BECAUSE WE KNOW THAT
00:08:36.460 --> 00:08:39.420
IN YOUR DATA CENTERS, YOU MAY ALSO
00:08:39.420 --> 00:08:41.048
HAVE OTHER TYPES OF COMPUTE AND
00:08:41.048 --> 00:08:43.497
WORKLOADS THAT YOU'RE RUNNING. SO
00:08:43.497 --> 00:08:45.567
WE BUILT -- PURPOSE BUILT INFRASTRUCTURE.
00:08:45.567 --> 00:08:47.621
EVERYTHING FROM CRAY, NET APP, S.
00:08:47.621 --> 00:08:48.993
A. P. , AND V. M. WARE TO MAKE SURE
00:08:48.993 --> 00:08:50.661
THAT THERE WAS NO FRICTION OR BLOCKERS
00:08:50.661 --> 00:08:52.639
FOR YOU TO BE ABLE TO TAKE YOUR
00:08:52.639 --> 00:08:54.436
WORKLOADS AND GET THEM INTO THE
00:08:54.436 --> 00:08:56.425
AZURE DATA CENTERS. NOW WE'RE THE
00:08:56.425 --> 00:08:58.041
ONLY CLOUD THAT HAS THIS RELATIONSHIP
00:08:58.041 --> 00:09:00.409
WITH CRAY, FOR EXAMPLE. AND YOU
00:09:00.409 --> 00:09:02.726
CAN GET ACCESS TO THE HIGHEST PERFORMANCE
00:09:02.726 --> 00:09:04.111
HPC FILE SYSTEMS WITH CRAY CLUSTER
00:09:04.111 --> 00:09:07.794
STORE IN AZURE. WE'RE ALSO THE ONLY
00:09:07.794 --> 00:09:09.248
PUBLIC WITH NET APP FILE SUPPORT,
00:09:09.248 --> 00:09:11.588
AS WELL, SO YOU CAN GET THE FASTEST
00:09:11.588 --> 00:09:15.339
POSSIBLE IOPS WITH OUR PARTNERS.
00:09:15.339 --> 00:09:17.032
S. A. P. ANNOUNCED THAT AZURE IS
00:09:17.032 --> 00:09:18.286
THEIR PREFERRED CLOUD. AND WE'VE
00:09:18.286 --> 00:09:19.493
DONE A SIGNIFICANT AMOUNT OF WORK
00:09:19.493 --> 00:09:21.091
IN OUR PARTNERSHIP WITH THEM TO
00:09:21.091 --> 00:09:23.084
MAKE SURE THAT WE ARE THE BEST CLOUD
00:09:23.084 --> 00:09:25.406
ENVIRONMENT TO RUN S. A. P. HANNA.
00:09:25.406 --> 00:09:28.136
WE'RE ABLE TO SCALE UP TO 24 TERABYTES
00:09:28.136 --> 00:09:30.085
OF RAM ON ONE MACHINE, AND WE CAN
00:09:30.085 --> 00:09:33.212
SCALE OUT TO 120 TERABYTES WITH
00:09:33.212 --> 00:09:35.104
THIS PURPOSE-BUILT HARD DRIVE. WE'VE
00:09:35.104 --> 00:09:39.033
DONE 31 S. A. P. CERTIFIED CONFIGURATIONS.
00:09:39.033 --> 00:09:40.597
ALSO BY ADDING THE NET APPS FILE
00:09:40.597 --> 00:09:42.848
SYSTEM THAT I MENTIONED JUST BEFORE,
00:09:42.848 --> 00:09:44.454
WE CAN ACTUALLY GET THE EXTREME
00:09:44.454 --> 00:09:46.732
PERFORMANCE OF UP TO 300, 000 IOPS
00:09:46.732 --> 00:09:48.918
PER SECOND FOR THAT WORKLOAD. AGAIN,
00:09:48.918 --> 00:09:51.223
GOING TO EVEN THE NEXT LEVEL UP.
00:09:51.223 --> 00:09:53.036
SO YOU'RE GOING TO BE ABLE TO ACCELERATE
00:09:53.036 --> 00:09:55.007
THE BUSINESS ZIN SIGHT AND BE ABLE
00:09:55.007 --> 00:09:57.471
TO GET ACCESS, AND AS YOU CAN SEE AS
00:09:57.471 --> 00:09:58.876
A PREFERRED CLOUD, WE'VE GOT A LOT
00:09:58.876 --> 00:10:00.324
OF CUSTOMERS IN MULTIPLE INDUSTRIES
00:10:00.324 --> 00:10:03.338
THAT HAVE TAKEN THE BET FOR THEIR
00:10:03.338 --> 00:10:04.700
ENTERPRISE-LEVEL WORKLOADS FOR S.
00:10:04.700 --> 00:10:07.340
A. P. AND THIS PARTNERSHIP. I'VE
00:10:07.340 --> 00:10:08.397
ALSO EXTENDED OUR PARTNERSHIP AND
00:10:08.397 --> 00:10:09.813
WORK THAT WE'VE DONE DOING WITH
00:10:09.813 --> 00:10:12.634
V. M. WARE TO INTRODUCE AZURE V.
00:10:12.634 --> 00:10:15.729
M. WARE SOLUTIONS. THERE IS BASICALLY
00:10:15.729 --> 00:10:17.469
ALLOWING US TO RUN V. M. WARE SOLUTIONS
00:10:17.469 --> 00:10:19.002
IN THE AZURE DATA CENTERS. THIS
00:10:19.002 --> 00:10:20.630
IS AWESOME BECAUSE IT MEANS THAT
00:10:20.630 --> 00:10:21.740
YOU CAN LEVERAGE THE INVESTMENTS
00:10:21.740 --> 00:10:24.644
THAT YOU HAVE ALREADY MADE IN PARTNERING
00:10:24.644 --> 00:10:25.954
WITH V. M. WARE. FOR THOSE OF YOU
00:10:25.954 --> 00:10:27.605
THAT ARE TRAINED AND SKILLED IN
00:10:27.605 --> 00:10:29.582
THE V. M. WARE ECOSYSTEM AND THOSE
00:10:29.582 --> 00:10:31.048
TOOLS IT MEANS YOU CAN USE ALL THE
00:10:31.048 --> 00:10:33.400
TOOLS IN THE EXPERIENCE THAT YOU
00:10:33.400 --> 00:10:34.470
HAVE TO TARGET THIS ENVIRONMENT.
00:10:34.470 --> 00:10:36.148
AND ALSO BECAUSE OF THIS DIRECT
00:10:36.148 --> 00:10:37.908
INTEGRATION THAT'S HERE, IT'S COMING
00:10:37.908 --> 00:10:39.969
DIRECTLY FROM MICROSOFT, YOU CAN
00:10:39.969 --> 00:10:42.469
ALSO ENHANCE THOSE V. M. WARE WORK
00:10:42.469 --> 00:10:44.471
BLOGS IF YOU'D LIKE TO ADD ADDITIONAL
00:10:44.471 --> 00:10:45.863
SUPPORT FOR THINGS LIKE ANALYTICS
00:10:45.863 --> 00:10:49.886
AND A. I. GOING FORWARD. THERE ARE
00:10:49.886 --> 00:10:52.671
THOUSANDS OF CUSTOMERS THAT ARE
00:10:52.671 --> 00:10:53.899
ACTUALLY MAKING THIS MIGRATION MOVE
00:10:53.899 --> 00:10:56.188
TODAY TO GET INTO AZURE. LOOKING
00:10:56.188 --> 00:10:57.265
FOR OPERATIONAL EFFICIENCY THAT'S
00:10:57.265 --> 00:11:00.140
SECURITY AND CLIENTS IN THE APPLICATION
00:11:00.140 --> 00:11:01.266
INNOVATION. LET'S GO AHEAD AND TAKE
00:11:01.266 --> 00:11:11.864
A LOOK AT SOME EXAMPLES. >> AT THE
00:11:11.864 --> 00:11:09.869
IN OUR ADDITIONAL PLATFORMS TO MEET
00:11:09.869 --> 00:11:13.499
COMPANY WE HAVE INVESTED HEAVILY
00:11:13.499 --> 00:11:18.032
THE CHANGING DEPARTMENT OF OUR CUSTOMERS.
00:11:18.032 --> 00:11:21.556
WE TRACTION ALL -- TRANSACTION ALL
00:11:21.556 --> 00:11:24.824
OF OUR CUSTOMER-FACING APPS IN AZURE.
00:11:24.824 --> 00:11:26.268
>> WE HAVE DEV-OPS TEAMS WORKING
00:11:26.268 --> 00:11:28.585
TOGETHER WITH MICROSOFT TO COME
00:11:28.585 --> 00:11:31.705
UP WITH A PLAN FOR MIGRATION. >>
00:11:31.705 --> 00:11:32.991
OUR MICROSOFT REVOLUTION HELPS US
00:11:32.991 --> 00:11:37.911
LEVERAGE THEIR INNOVATION TO POWER
00:11:37.911 --> 00:11:42.183
OURS. >> THERE'S A STORIED HISTORY,
00:11:42.183 --> 00:11:43.912
THE TAX INDUSTRY HAS EVOLVED TREMENDOUSLY
00:11:43.912 --> 00:11:45.620
OVER THE LAST SIX YEARS. >> WE KNEW
00:11:45.620 --> 00:11:47.394
THAT CLOUD MIGRATION WAS IMPORTANT.
00:11:47.394 --> 00:11:49.096
WE NEEDED TO MODERNIZE -- >> IT
00:11:49.096 --> 00:11:51.881
IS VERY CRITICAL THAT WE PICK OUR DATA
00:11:51.881 --> 00:11:54.855
PLATFORMS WITH SCALEABILITY, RELIABILITY,
00:11:54.855 --> 00:11:59.924
AND SECURITY. THAT'S A BIG PART.
00:11:59.924 --> 00:12:03.274
WE USE OUR DIY AND APPLICATIONS
00:12:03.274 --> 00:12:05.038
RUNNING IN AZURE. >> MIGRATION TO
00:12:05.038 --> 00:12:08.194
AZURE HAS REALLY HELPED US ACCELERATE
00:12:08.194 --> 00:12:13.193
OUR JOURNEY. >> THE P. H. SCALE
00:12:13.193 --> 00:12:15.896
WAS INVENTED -- WE ARE ABOUT THE
00:12:15.896 --> 00:12:18.128
SCIENCE COMPANY. WE WANTED TO GET
00:12:18.128 --> 00:12:21.374
REALLY SCALEABLE, EFFICIENT, SECURE,
00:12:21.374 --> 00:12:24.645
LOW-COST I. T. TO COME UP FOR A
00:12:24.645 --> 00:12:26.152
DIGITAL SOLUTION FOR MARKET AT SCALE.
00:12:26.152 --> 00:12:27.731
THE CLOUD MIGRATION WAS A WAY TO
00:12:27.731 --> 00:12:29.799
STREAMLINE AND CLEAN UP OUR I. T.
00:12:29.799 --> 00:12:32.533
>> WE WENT VISUAL FOR S. A. P. BECAUSE
00:12:32.533 --> 00:12:34.200
THEY'VE ATTRACTED WHAT WE NOW A
00:12:34.200 --> 00:12:36.954
FOUNDATION THAT WILL ALLOW US TO
00:12:36.954 --> 00:12:38.636
SCALE ALL OF THE SOLUTIONS ACROSS
00:12:38.636 --> 00:12:43.619
EVERY MARKET, ACROSS EVERY REGION.
00:12:43.619 --> 00:12:45.894
>> THANK YOU SO MUCH. NOW I'M NOW
00:12:45.894 --> 00:12:49.494
JOINED BY A DI TIA FROM H&R BLOCK.
00:12:49.494 --> 00:12:50.943
TELL US ABOUT YOUR DECISION TO MOVE
00:12:50.943 --> 00:12:52.901
TO THE CLOUDS. >> ABSOLUTELY. A
00:12:52.901 --> 00:12:55.056
PLEASURE TO BE HERE. >> ABSOLUTELY.
00:12:55.056 --> 00:12:58.164
>> H&R BLOCK, WE'RE A TAX CORPORATION
00:12:58.164 --> 00:12:59.929
AND BUSINESS COMPANY, FOUNDED IN
00:12:59.929 --> 00:13:02.555
1955. OVER THE LAST 60 TO 70 YEARS,
00:13:02.555 --> 00:13:04.340
THERE HAVE BEEN TREMENDOUS CHANGES
00:13:04.340 --> 00:13:09.827
IN THE INDUSTRY. AND AS WE LIVE
00:13:09.827 --> 00:13:11.852
TODAY, BLOCK IS THE ONLY COMPANY
00:13:11.852 --> 00:13:13.216
IN THE TAX INDUSTRY THAT OFFERS
00:13:13.216 --> 00:13:15.450
THE RANGE OF CHOICES TO CLIENTS
00:13:15.450 --> 00:13:17.338
IN HOW THEY WANT TO GET HELP FOR
00:13:17.338 --> 00:13:19.072
PREPARING TAXES, WHETHER THEY WANT
00:13:19.072 --> 00:13:22.826
TO DO IT IN PERSON OR ON LINE. AND
00:13:22.826 --> 00:13:24.058
WE OF COURSE ARE A SEASONAL BUSINESS.
00:13:24.058 --> 00:13:26.677
BUT TO JUST GIVE YOU AN IDEA OF
00:13:26.677 --> 00:13:30.136
THAT SEASONALITY, WE DO -- WE FIND
00:13:30.136 --> 00:13:34.985
OVER 25 OF OUR TERMS FOR THE VOLUME
00:13:34.985 --> 00:13:36.477
IS DONE OVER A PERIOD OF TWO WEEKS
00:13:36.477 --> 00:13:40.262
IN THE SEASON. >> WOW. >> AND THAT,
00:13:40.262 --> 00:13:42.939
OF COURSE, REQUIRES OUR VERY RESILIENT
00:13:42.939 --> 00:13:44.319
AND ELASTIC INFRASTRUCTURE BECAUSE
00:13:44.319 --> 00:13:47.162
YOU WANT THE RESILIENCY WHEN IT
00:13:47.162 --> 00:13:48.973
REALLY COUNTS. AND THAT -- THAT
00:13:48.973 --> 00:13:52.641
MAKES IT A PERFECT CANDIDATE FOR
00:13:52.641 --> 00:13:53.984
LEVERAGING CLOUD-BASED DELIVERY
00:13:53.984 --> 00:13:56.288
MODEL. TO REALLY DELIVER THE EXPERTISE
00:13:56.288 --> 00:13:58.214
AND CARE THAT OUR CLIENTS EXPECT
00:13:58.214 --> 00:14:01.268
AND NEED EVERY SINGLE TIME THEY
00:14:01.268 --> 00:14:03.087
INTERACT -- >> THAT'S MASSIVE SEASONALITY.
00:14:03.087 --> 00:14:04.521
A PERFECT IDEA TO THINK OF TAKING
00:14:04.521 --> 00:14:05.805
ADVANTAGE OF THE CLOUD WITH THAT.
00:14:05.805 --> 00:14:07.056
YOU MADE THE DECISION, WHAT DID
00:14:07.056 --> 00:14:08.767
THE ACTUAL JOURNEY TO MOVING THE
00:14:08.767 --> 00:14:10.376
CLOUD -- WHAT WAS YOUR APPROACH
00:14:10.376 --> 00:14:12.388
TO MOVING TO THE CLOUD? >> FOR US,
00:14:12.388 --> 00:14:13.866
ACTUALLY MIGRATION TO THE CLOUD
00:14:13.866 --> 00:14:17.588
WAS REALLY A PART OF A BROADER TRANSFORMATION
00:14:17.588 --> 00:14:19.122
THAT'S GOING ON AT BLOCK. AND FROM
00:14:19.122 --> 00:14:21.129
THAT PERSPECTIVE, AS WE LOOK AT
00:14:21.129 --> 00:14:24.332
THE KEY DRIVERS, OF COURSE THE BLOCK
00:14:24.332 --> 00:14:27.696
-- WE SAW CLOUD MIGRATION AS A KEY
00:14:27.696 --> 00:14:28.963
ACCELERATOR TO THE DIGITAL TRANSFORMATION.
00:14:28.963 --> 00:14:31.878
AND FOR THAT REASON, WE TOOK A VERY
00:14:31.878 --> 00:14:33.074
AGGRESSIVE APPROACH TO MIGRATING
00:14:33.074 --> 00:14:36.304
TO THE CLOUD. WE LOOKED AT DIFFERENT
00:14:36.304 --> 00:14:39.310
OPTIONS, AND WE REALIZED THAT ACTUALLY
00:14:39.310 --> 00:14:40.970
-- WE WEREN'T LEARNING WHAT WE HAD
00:14:40.970 --> 00:14:43.096
NEEDED TO LEARN BY OPERATING IN
00:14:43.096 --> 00:14:44.564
THE CLOUD BY JUST DIPPING OUR TOES
00:14:44.564 --> 00:14:46.075
IN THE WATER. WE HAD TO DIVE IN.
00:14:46.075 --> 00:14:47.708
THAT'S WHAT WE CHOSE. WE TOOK A
00:14:47.708 --> 00:14:48.701
AGGRESSIVE APPROACH, AND WE DOVE
00:14:48.701 --> 00:14:50.966
IN LAST YEAR. >> THAT'S INTERESTING
00:14:50.966 --> 00:14:54.092
BECAUSE I KNOW WHEN WE TALKED ABOUT
00:14:54.092 --> 00:14:55.954
H&H IN GENERAL IT WAS MORE CONSERVATIVE.
00:14:55.954 --> 00:14:57.340
YOU DECIDED TO GO IN -- WE'RE NOT
00:14:57.340 --> 00:14:58.751
GOING TO LEARN AS MUCH IF WE DON'T
00:14:58.751 --> 00:15:00.936
JUMP IN. INTERESTED IN HOW YOU DID THAT.
00:15:00.936 --> 00:15:02.536
>> I THINK PART OF IT IS REALLY
00:15:02.536 --> 00:15:06.136
WHEN YOU LOOK AT IT MORE FROM A
00:15:06.136 --> 00:15:07.644
DIGITAL TRANSFORMATION PERSPECTIVE,
00:15:07.644 --> 00:15:07.645
THE WAY YOUR CALCULUS FOR RISK AND
00:15:07.645 --> 00:15:12.050
REWARD SHIFTS, RIGHT, BECAUSE YOU
00:15:12.050 --> 00:15:14.078
WANT TO DRIVE THE TRANSFORMATION
00:15:14.078 --> 00:15:15.331
FASTER AND GET TO THE MARKET BENEFITS
00:15:15.331 --> 00:15:17.595
THAT YOU WANT TO GET TO. AND DELIVER
00:15:17.595 --> 00:15:18.814
THE CAPABILITIES YOU WANT TO DELIVER
00:15:18.814 --> 00:15:20.418
TO OUR CLIENTS FASTER, AND THAT
00:15:20.418 --> 00:15:21.905
KIND OF SHIFTED OUR APPROACH TO
00:15:21.905 --> 00:15:24.507
TAKE A MORE AGGRESSIVE APPROACH
00:15:24.507 --> 00:15:26.254
AS OPPOSED TO MAYBE TAKE THREE YEARS
00:15:26.254 --> 00:15:28.088
TO GET THERE. >> AS YOU SAID, ONCE
00:15:28.088 --> 00:15:29.728
YOU GO IN, YOU REALLY LEARN. YOU
00:15:29.728 --> 00:15:32.189
CAN BE AGILE IN LEARNING AND CHANGING
00:15:32.189 --> 00:15:33.790
ONCE YOU'VE KIND OF DONE SOMETHING
00:15:33.790 --> 00:15:35.565
MATERIAL. RIGHT? >> YES. AND I THINK
00:15:35.565 --> 00:15:38.305
PARTS OF THAT LEARNING IS REALLY
00:15:38.305 --> 00:15:41.105
JUST TO COME AND LEARN WITH THE
00:15:41.105 --> 00:15:42.437
PARTNERSHIP THAT AT MICROSOFT AND
00:15:42.437 --> 00:15:43.907
THE TEAMS TO LEARN TOGETHER AND
00:15:43.907 --> 00:15:45.750
WORK THROUGH THOSE ISSUES. >> ABSOLUTELY,
00:15:45.750 --> 00:15:48.182
YEAH. YOU MIGRATED SIGNIFICANT APPLICATIONS
00:15:48.182 --> 00:15:49.602
TO AZURE. AND INTERESTED IN WHAT
00:15:49.602 --> 00:15:51.408
ARE YOU SEEING FOR THAT? WHAT KIND
00:15:51.408 --> 00:15:53.565
OF RESULTS ARE YOU SEEING? >> WE
00:15:53.565 --> 00:15:56.632
ACTUALLY -- WE LOOKED AT OUR PORTFOLIO,
00:15:56.632 --> 00:15:58.861
AND JUST WHAT A-- OVER A PERIOD
00:15:58.861 --> 00:16:01.144
OF SIX TO NINE MONTHS LEADS UP TO
00:16:01.144 --> 00:16:03.568
THE PAST TAX SEASON. WE MIGRATED
00:16:03.568 --> 00:16:05.084
SOME OF OUR CRITICAL KEY CLIENTS
00:16:05.084 --> 00:16:06.428
SERVING APOLITICIANS, AND SERVED
00:16:06.428 --> 00:16:11.181
OVER 20 MILLION CLIENTS IN 2019
00:16:11.181 --> 00:16:14.057
TAX SEASON ON AZURE. THEY ARE USING
00:16:14.057 --> 00:16:17.091
THE PLATFORM, THEY WERE USING THE
00:16:17.091 --> 00:16:18.240
SERVICES ON AZURE PLATFORM. >> YES.
00:16:18.240 --> 00:16:22.191
>> AS WE LOOKED BACK AT THAT, REALLY
00:16:22.191 --> 00:16:24.999
THIS WAS HAND IN HAND WITH ALL THE
00:16:24.999 --> 00:16:27.127
TRANSFORMATION THAT WE'RE DRIVING
00:16:27.127 --> 00:16:29.836
THERE, WE STARTED TO DRIVE STRONGER
00:16:29.836 --> 00:16:33.260
ADOPTION OF ADO AND DEV OPS PRACTICES
00:16:33.260 --> 00:16:36.376
WITHIN OUR DEVELOPMENT TEAMS. THAT
00:16:36.376 --> 00:16:37.937
MEANT JUST DELIVERING ITERATIONS
00:16:37.937 --> 00:16:41.524
FASTER AND DEPLOYING QUICKER. AND
00:16:41.524 --> 00:16:45.025
WE ALSO REALLY STARTED TO HEAVILY
00:16:45.025 --> 00:16:47.388
LEVERAGE AZURE DATA SERVICES AND
00:16:47.388 --> 00:16:48.867
AZURE SERVICES TO ACTUALLY BUILD
00:16:48.867 --> 00:16:50.872
SMARTER, MORE INTELLIGENT SOLUTIONS
00:16:50.872 --> 00:16:53.272
AND MODELS THAT -- THAT GIVE OUR
00:16:53.272 --> 00:16:54.984
CLIENT MORE PERSONALIZED EXPERIENCE
00:16:54.984 --> 00:16:57.327
AND AN EXPERIENCE THAT'S MUCH MORE
00:16:57.327 --> 00:16:58.749
RELATED TO THEIR TAX SITUATION.
00:16:58.749 --> 00:17:00.684
GIVING THEM TAX TIPS THAT ARE MOST
00:17:00.684 --> 00:17:03.568
RELEVANT TO WHERE THEY ARE. >> RIGHT.
00:17:03.568 --> 00:17:04.356
STARTING WITH THE MIGRATION, BUT
00:17:04.356 --> 00:17:05.915
MOVING INTO SHAPING THAT DATA CULTURE
00:17:05.915 --> 00:17:07.994
THAT YOU'RE WORKING TOWARD, ABSOLUTELY.
00:17:07.994 --> 00:17:09.636
THANK YOU SO MUCH FOR BEING HERE
00:17:09.636 --> 00:17:10.630
AND JOINING US TODAY. THANK YOU
00:17:10.630 --> 00:17:15.603
AGAIN. >> ABSOLUTELY. >> TAKE CARE.
00:17:15.603 --> 00:17:18.536
PERFECT. NOW WE'VE HAD A CHANCE
00:17:18.536 --> 00:17:20.176
TO WORK CLOSELY WITH CUSTOMERS LIKE
00:17:20.176 --> 00:17:22.781
H&R BLOCK AND THOUSANDS OF OTHERS
00:17:22.781 --> 00:17:24.388
AROUND MIGRATION TO AZURE. WE'VE
00:17:24.388 --> 00:17:25.886
BROUGHT THIS EXPERIENCE TOGETHER
00:17:25.886 --> 00:17:27.877
INTO A SINGLE PROGRAM FOR EVERY
00:17:27.877 --> 00:17:29.766
CUSTOMER CALLED THE AZURE MIGRATION
00:17:29.766 --> 00:17:31.734
PROGRAM. AND WHAT AZURE MIGRATION
00:17:31.734 --> 00:17:32.494
PROGRAM DOES, IT BRINGS TOGETHER
00:17:32.494 --> 00:17:34.808
THE BEST PRACTICES, THE TOOLS, THE
00:17:34.808 --> 00:17:36.883
RESOURCES, AND THE EXPERTISE BOTH
00:17:36.883 --> 00:17:39.341
FROM WITHIN MICROSOFT AS WELL AS
00:17:39.341 --> 00:17:40.653
OUR BEST SPECIALIZED PARTNERS IN
00:17:40.653 --> 00:17:43.324
THIS AREA, AS WELL. AND EVERY CUSTOMER,
00:17:43.324 --> 00:17:45.604
LARGE OR SMALL, CAN TAKE ADVANTAGE
00:17:45.604 --> 00:17:48.149
OF THE AZURE MIGRATION PROGRAMS.
00:17:48.149 --> 00:17:49.512
WE CERTAINLY ENCOURAGE YOU TO DO
00:17:49.512 --> 00:17:51.786
THAT. BEYOND MIGRATION, WE'VE ALSO
00:17:51.786 --> 00:17:54.196
HEARD FROM YOU THAT YOU WANT BEST
00:17:54.196 --> 00:17:55.597
PRACTICE GUIDANCE ON REAL -- BASED
00:17:55.597 --> 00:17:57.757
ON REAL-WORLD EXPERIENCES, AND HOW
00:17:57.757 --> 00:18:00.109
TO BEST USE AZURE AND RUN YOUR SYSTEMS
00:18:00.109 --> 00:18:02.571
OVER TIME. AND THIS IS WHY WE CREATED
00:18:02.571 --> 00:18:04.369
THE CLOUD ADOPTION FRAMEWORK THAT
00:18:04.369 --> 00:18:06.476
BRINGS TOGETHER KIND OF THAT TRUE
00:18:06.476 --> 00:18:07.570
REAL-WORLD, PRUFB EXPERIENCE FOR
00:18:07.570 --> 00:18:09.106
THE ENTIRE -- PROVEN EXPERIENCE
00:18:09.106 --> 00:18:11.177
FOR THE ENTIRE LIFE CYCLE FROM PLANNING
00:18:11.177 --> 00:18:13.128
AND READINESS AND AADOPTION INTO
00:18:13.128 --> 00:18:14.890
ONGOING MANAGEMENT AND GOVERNANCE
00:18:14.890 --> 00:18:16.766
OF YOUR ENVIRONMENT IN AZURE. NOW
00:18:16.766 --> 00:18:18.369
THE CLOUD ADOPTION FRAMEWORK IS
00:18:18.369 --> 00:18:20.014
BASED ON, AGAIN, PROVEN EXPERIENCE.
00:18:20.014 --> 00:18:22.400
SO YOU GET THAT DIRECT ACCESS TO
00:18:22.400 --> 00:18:24.280
WISDOM AND INSIGHTS ABOUT HOW TO
00:18:24.280 --> 00:18:26.094
TAKE ADVANTAGE OF THE CLOUD IN THE
00:18:26.094 --> 00:18:28.727
MOST OPTIMAL WAY. WITH THAT, BACK
00:18:28.727 --> 00:18:37.573
TO JASON. >> THANK YOU, JULIA. NOW
00:18:37.573 --> 00:18:39.740
I WANT TO DIG NEXT INTO HYBRID.
00:18:39.740 --> 00:18:41.392
AND THE KEY THING FOR US, THIS HAS
00:18:41.392 --> 00:18:42.973
ALWAYS BEEN TRUE. HYBRID, WE BELIEVE,
00:18:42.973 --> 00:18:45.252
IS A PERMANENT STATE. IT'S NOT JUST
00:18:45.252 --> 00:18:47.457
A TRANSITION. WE MADE HYBRID THE
00:18:47.457 --> 00:18:49.260
STANDARD SOLUTION WHERE OUR COMPETITORS
00:18:49.260 --> 00:18:50.639
FRANKLY WERE PAYING IT LIP SERVICE.
00:18:50.639 --> 00:18:52.248
WE THINK IT'S SUPER IMPORTANT FOR
00:18:52.248 --> 00:18:53.524
YOUR EVERYDAY WORK THAT YOU'RE DOING,
00:18:53.524 --> 00:18:54.459
AND I WANT TO TELL YOU WHAT WE'RE
00:18:54.459 --> 00:18:56.287
DOING. NOW THE FIRST QUESTION IS,
00:18:56.287 --> 00:18:57.848
WELL, WHY HYBRID? FOR ONE THING
00:18:57.848 --> 00:18:59.293
WE ALL HAVE OUR OWN DATA CENTERS
00:18:59.293 --> 00:19:00.873
IN A LOT OF CASES, AND I NEED TO
00:19:00.873 --> 00:19:03.114
GET THEM. I'M GOING TO KEEP RUNNING
00:19:03.114 --> 00:19:04.265
THEM EVEN WHILE I'M LEVERAGING THE
00:19:04.265 --> 00:19:05.958
CLOUD. I'VE ALSO GOT EDGE DEPLOYMENTS.
00:19:05.958 --> 00:19:07.666
MAYBE YOU'RE RUNNING A FACTORY IF
00:19:07.666 --> 00:19:09.274
YOU'RE AN INDUSTRIAL, MAYBE YOU'RE
00:19:09.274 --> 00:19:10.656
RUNNING SMART BUILDINGS, HOTELS,
00:19:10.656 --> 00:19:12.377
TAKE YOUR PICK. I WANT TO BE ABLE
00:19:12.377 --> 00:19:14.109
TO RUN THEM DISCONNECTED. DON'T
00:19:14.109 --> 00:19:16.129
EVER TELL PEA THAT MY FACTORY IS
00:19:16.129 --> 00:19:18.016
GOING TO STOP WORKING BECAUSE SOMEBODY
00:19:18.016 --> 00:19:21.140
TOOK A BACK HOE THROUGH A FIBER
00:19:21.140 --> 00:19:22.390
LINK. YOU NEED DISCONNECTED SOLUTIONS.
00:19:22.390 --> 00:19:23.831
YOU MAY WANT TO ADDITIONAL REGULATORY
00:19:23.831 --> 00:19:25.096
REQUIREMENTS. OF COURSE, WE WANT
00:19:25.096 --> 00:19:28.398
TO HAVE THAT CLOUD MODERN APPLICATION
00:19:28.398 --> 00:19:30.041
PROGRAMMING MODEL. AND SO WE'VE
00:19:30.041 --> 00:19:31.794
MOVED TO CREATE HYBRID. AND WE'VE
00:19:31.794 --> 00:19:33.372
EMBRACED AND SUPPORTED HYBRID SINCE
00:19:33.372 --> 00:19:35.575
DAY ONE, AND IT'S ONLY GETTING BETTER.
00:19:35.575 --> 00:19:37.001
WE WANT YOU TO BE ABLE TO CONTINUE
00:19:37.001 --> 00:19:37.961
TO MAKE LEVERAGE OF WHAT YOU'VE
00:19:37.961 --> 00:19:39.708
GOT AND THE NEW SCENARIOS THAT ARE
00:19:39.708 --> 00:19:42.147
THERE. NOW WE THINK THAT THE HYBRID
00:19:42.147 --> 00:19:43.882
EXISTENCE, IT REQUIRES SEVERAL KEY
00:19:43.882 --> 00:19:46.759
CAPABILITIES. UNIFIED GOVERNANCE,
00:19:46.759 --> 00:19:49.805
CONSISTENT MANAGEMENT, COMPREHENSIVE
00:19:49.805 --> 00:19:52.503
SECURITY, INTEGRATED IDENTITY, AND
00:19:52.503 --> 00:19:54.516
UNIVERSAL DEVOPS. NOW LET'S GO AHEAD
00:19:54.516 --> 00:19:56.143
AND LOOK FURTHER INTO OUR HYBRID
00:19:56.143 --> 00:19:57.467
SOLUTIONS, AND I WANT TO START OFF
00:19:57.467 --> 00:20:01.191
WITH TWO PARTS OF THIS. AZURE IOT
00:20:01.191 --> 00:20:02.896
AND WITH AZURE STACK. AS BUSINESSES
00:20:02.896 --> 00:20:04.072
CONTINUE TO EXPAND THE COMPUTE TO
00:20:04.072 --> 00:20:05.894
THE EDGE, THEN THE CAPABILITIES
00:20:05.894 --> 00:20:07.466
THAT WE BUILD THERE HAVE TO BE NOT
00:20:07.466 --> 00:20:09.790
ONLY THE APPS BUT THE MANAGEMENT
00:20:09.790 --> 00:20:12.732
OF THAT. LET'S START WITH AZURE
00:20:12.732 --> 00:20:14.899
IOT. THIS IS A CASE WHERE WE HAVE
00:20:14.899 --> 00:20:16.662
THOUSANDS OF IOT CERTIFIED DEVICES.
00:20:16.662 --> 00:20:18.282
THIS IS SUPER INTERESTING BECAUSE,
00:20:18.282 --> 00:20:20.424
OF COURSE, EVERY INDUSTRY HAS GOTTEN
00:20:20.424 --> 00:20:22.886
UNIQUE THINGS THAT IT NEEDS TO DO.
00:20:22.886 --> 00:20:24.499
AND THAT MEANS THAT YOU'RE LIKELY
00:20:24.499 --> 00:20:26.344
GOING TO WIND UP WITH CERTAIN REQUIREMENTS
00:20:26.344 --> 00:20:28.251
IN YOUR DEVICES. EVERYTHING FROM
00:20:28.251 --> 00:20:29.838
THE SMALLEST MICROCONTROLLER UNIT
00:20:29.838 --> 00:20:31.836
THAT MIGHT BE THE SIZE OF YOUR FINGERNAIL
00:20:31.836 --> 00:20:33.562
UP TO LARGER SYSTEMS THAT ARE GOING
00:20:33.562 --> 00:20:36.168
TO RUN ADVANCED SENSOR NETS IN ADDITION
00:20:36.168 --> 00:20:37.355
TO POTENTIALLY DOING COMMAND AND
00:20:37.355 --> 00:20:39.444
CONTROL FOR ROBOTICS AND OTHER BIGGER
00:20:39.444 --> 00:20:42.448
USES LIKE THAT. NOW WE'VE ALSO BUILT
00:20:42.448 --> 00:20:45.149
OUT A LARGE PARTNER NETWORK. AND
00:20:45.149 --> 00:20:47.322
THE PARTNERS KNOW BOTH DEVICES AND
00:20:47.322 --> 00:20:48.452
THEY'RE INDUSTRY EXPERTS. IF YOU'RE
00:20:48.452 --> 00:20:51.420
IN MANUFACTURING, WE CAN HELP YOU
00:20:51.420 --> 00:20:52.572
FIND SOMEBODY THAT'S FOUND THE BEST
00:20:52.572 --> 00:20:54.726
WAY TO PAIR UP THE DEVICE ECOSYSTEM
00:20:54.726 --> 00:20:56.386
AND GIVE YOU THE BEST RETURN ON
00:20:56.386 --> 00:20:58.403
THAT. NOW IN ADDITION TO THAT, WE'VE
00:20:58.403 --> 00:21:00.317
DONE SOME ADDITIONAL WORK DIRECTLY
00:21:00.317 --> 00:21:02.216
INSIDE OF AZURE AND ACROSS THE COMPANY
00:21:02.216 --> 00:21:04.140
WITH AZURE EDGE DEVICES. STARTING
00:21:04.140 --> 00:21:06.540
OFF WITH SPHERE, MICROCONTROL UNIT
00:21:06.540 --> 00:21:07.940
WITH SECURITY BUILT IN. YOU CAN
00:21:07.940 --> 00:21:09.892
SEE ONE OF THE CHIPS ON THIS DEV
00:21:09.892 --> 00:21:12.437
KIT ON THE LEFT. HOLLOW LENS WHICH
00:21:12.437 --> 00:21:13.982
BRINGS BASICALLY VIRTUAL INTO THE
00:21:13.982 --> 00:21:15.342
PHYSICAL WORLD WHERE I CAN START
00:21:15.342 --> 00:21:16.875
DOING REALLY COOL THINGS LIKE LOOKING
00:21:16.875 --> 00:21:18.420
AT TIME SERIES DATA, BUT ACTUALLY
00:21:18.420 --> 00:21:21.557
IN THE PHYSICAL WORLD. AZURE CONNECT
00:21:21.557 --> 00:21:22.598
WHICH IS THE DEPTH CAMERAS, THE
00:21:22.598 --> 00:21:24.673
NEW WAY TO DO IMAGE RECOGNITION.
00:21:24.673 --> 00:21:27.627
AND OF COURSE, THE AZURE STACK PORT
00:21:27.627 --> 00:21:29.485
FOAL WHICH IS DESIGNED TO GIVE --
00:21:29.485 --> 00:21:32.403
PORTFOLIO COME IS DESIGNED TO GIVE
00:21:32.403 --> 00:21:33.769
US UBIQUITOUS COMPUTER WITH THE
00:21:33.769 --> 00:21:35.664
EDGE AND ABILITY TO RUN A. I. THAT'S
00:21:35.664 --> 00:21:37.409
WHY WE'RE PLEASED TO HAVE INTRODUCED
00:21:37.409 --> 00:21:39.429
TODAY AND HOPEFULLY YOU SAW IN SATYA'S
00:21:39.429 --> 00:21:42.031
KEYMOAT AND THE DEMO FLOOR THE NEW
00:21:42.031 --> 00:21:43.407
AZURE STACK EDGE SOLUTION WE'VE
00:21:43.407 --> 00:21:46.282
GOT. THIS IS, AGAIN, DESIGNED TO
00:21:46.282 --> 00:21:47.437
BRING THAT COMPUTE A. I. OFF TO
00:21:47.437 --> 00:21:49.225
THE EDGE. WE HAVE A COMMERCIAL SERIES,
00:21:49.225 --> 00:21:52.756
YOU CAN SEE HERE. THIS IS A WRAPABLE
00:21:52.756 --> 00:21:54.137
VERSION WHICH MEANS I -- RACKAGE
00:21:54.137 --> 00:21:56.775
VERSION WHICH MEANS I CAN STICK
00:21:56.775 --> 00:21:58.028
IT INTO A RACK ON THE RETAIL FLOOR,
00:21:58.028 --> 00:21:58.029
FACTORY STORE, OR BUILDINGS, WHEREVER
00:21:58.029 --> 00:22:01.843
I NEED TO HAVE IT. AND WE CAME ALONG
00:22:01.843 --> 00:22:03.381
AND ADDED THE RUGGED VERSION, AS
00:22:03.381 --> 00:22:05.299
WELL. YOU CAN SEE HERE IT COMES
00:22:05.299 --> 00:22:07.605
WITH BATTERY POWER. AND IT'S BEEN
00:22:07.605 --> 00:22:09.323
RUGGEDIZED SO IT CAN BE MORE PORTABLE.
00:22:09.323 --> 00:22:10.754
I CAN TAKE IT WITH ME IF I HAVE
00:22:10.754 --> 00:22:12.695
TO. IT'S GOING TO GET BOUNCED AROUND,
00:22:12.695 --> 00:22:15.098
AND THAT'S OKAY. WE'RE ALSO INTRODUCING
00:22:15.098 --> 00:22:16.977
IN PREVIEW NECK SUPPORT. IN THIS
00:22:16.977 --> 00:22:22.319
CASE, WE'RE INTRODUCING SUPPORT
00:22:22.319 --> 00:22:23.076
FOR PRIVATE LTE OR FI5G ACCESS THAT
00:22:23.076 --> 00:22:24.076
YOU CAN INCLUDE WITH AZURE STACK
00:22:24.076 --> 00:22:28.200
EDGE. THAT GIVES ME SUPPORT FOR
00:22:28.200 --> 00:22:30.363
BEPC, THAT BASICALLY MEANS I HAVE
00:22:30.363 --> 00:22:32.760
K HAVE CUSTOMIZED NETWORKS WITHOUT
00:22:32.760 --> 00:22:35.146
REQUIRING SPECIALIZED HARDWARE.
00:22:35.146 --> 00:22:35.692
WE THINK THAT'S GOING TO OPEN UPA
00:22:35.692 --> 00:22:36.912
LOT OF GREAT OPPORTUNITIES. NOW
00:22:36.912 --> 00:22:38.206
WE'LL HAVE AZURE STACK EDGE AND CONNECT
00:22:38.206 --> 00:22:43.889
A LOT OF DEVICES TO IT.WE TOOK IT ONE STEP FURTHER, AS WELL.AND WE
00:22:43.889 --> 00:22:47.663
ACTUALLY INTRODUCED A BACKPACK VERSION.
00:22:47.663 --> 00:22:48.806
LIKE THE VERSION YOU SEE HERE, A
00:22:48.806 --> 00:22:49.698
RUGGEDIZED VERSION. IT WEIGHS SEVEN
00:22:49.698 --> 00:22:51.908
POUNDS. IT HAS AN ON-BOARD BATTERY
00:22:51.908 --> 00:22:52.976
AND IS DESIGNED SPECIFICALLY TO
00:22:52.976 --> 00:22:55.258
GET ON THE GO. AS YOU CAN SEE HERE,
00:22:55.258 --> 00:22:57.611
WE HAVE SOME SEARCH AND RESCUE VOLUNTEERS
00:22:57.611 --> 00:22:58.829
ACTUALLY IN THE CASCADE MOUNTAIN
00:22:58.829 --> 00:23:00.756
RANGE OF WASHINGTON STATE. AND THIS
00:23:00.756 --> 00:23:02.133
IS AN OPPORTUNITY TO BOTH -- YOU
00:23:02.133 --> 00:23:04.136
CAN SEE THE RUGGED VERSION ON THE
00:23:04.136 --> 00:23:05.249
TRUCK, YOU CAN BOUNCE AROUND AS
00:23:05.249 --> 00:23:06.908
MUCH AS IT WANTS, BUT THE BACKPACK
00:23:06.908 --> 00:23:08.240
VERSION. IMAGINE BEING ABLE TO TAKE
00:23:08.240 --> 00:23:10.848
A DRONE WITH YOU ON SEARCH AND RESCUE.
00:23:10.848 --> 00:23:12.358
DO INFRARED SEARCH ON CAMERAS AND
00:23:12.358 --> 00:23:15.420
BE ABLE TO EXECUTE THE A. I. ON
00:23:15.420 --> 00:23:16.888
YOUR BACK. PART OF OUR GOAL FOR
00:23:16.888 --> 00:23:19.254
SOME OF THE SOLUTION IS TO TRY AND
00:23:19.254 --> 00:23:21.556
TAKE TECHNOLOGY AND LET IT HELP
00:23:21.556 --> 00:23:22.749
PEOPLE IN CASES WHERE THEY REALLY
00:23:22.749 --> 00:23:25.076
NEED IT, BRING THE COMPUTE TO WHERE
00:23:25.076 --> 00:23:26.777
THE PROBLEMS ARE. BASICALLY TAKE
00:23:26.777 --> 00:23:28.644
THE INTELLIGENT EDGE ANYWHERE YOU
00:23:28.644 --> 00:23:30.383
NEED TO GO. SO WITH THAT, LET'S
00:23:30.383 --> 00:23:31.748
GO AHEAD AND TAKE A LOOK AT THE
00:23:31.748 --> 00:23:35.835
DEMO. I WANT TO INVITE CHRIS DICKENS
00:23:35.835 --> 00:23:41.018
ON STAGE. CHRIS? >> THANKS. HURRICANE
00:23:41.018 --> 00:23:42.591
MICHAEL WAS A HEARTBREAKING NATURAL
00:23:42.591 --> 00:23:46.569
DISASTER THAT IMPACTED MANY OF THE
00:23:46.569 --> 00:23:47.586
COMMUNITIES IN THIS REGION. AFTER
00:23:47.586 --> 00:23:49.599
THE HURRICANE THE FLORIDA CIVIL
00:23:49.599 --> 00:23:51.577
AIR PATROL FLEW PLANES AROUND THE
00:23:51.577 --> 00:23:54.293
AREA CAPTURING IMAGES OF THE DAMAGE.
00:23:54.293 --> 00:23:56.084
TODAY I'M GOING TO SHOW HOW THE
00:23:56.084 --> 00:23:58.573
DEVICE JASON TALKED ABOUT COULD
00:23:58.573 --> 00:23:59.767
HELP FIRST RESPONDERS UNDERSTAND
00:23:59.767 --> 00:24:02.388
THE IMPACT OF TRAGEDIES LIKE THIS
00:24:02.388 --> 00:24:09.851
AND HELP PLAN THE RESPONSE. TO ANALYZE
00:24:09.851 --> 00:24:11.791
THE IMAGES, WE LOADED THEM ON TO
00:24:11.791 --> 00:24:14.445
ONE OF THESE RUGGED PORTABLE AZURE
00:24:14.445 --> 00:24:20.748
STACK EDGE APPLIANCES, THEN WE USE
00:24:20.748 --> 00:24:23.294
SOFTWARE FROM EZRY TO BUILD A MAP
00:24:23.294 --> 00:24:26.871
VIEW BY STITCHING THE IMAGES TOGETHER
00:24:26.871 --> 00:24:29.029
THAT FIRST RESPONDERS CAN VIEW ON
00:24:29.029 --> 00:24:31.623
SITE FROM JUST A BROWSER. BUT TO
00:24:31.623 --> 00:24:34.884
HELP THEM UNDERSTAND THE CONDITIONS
00:24:34.884 --> 00:24:38.442
THAT EVEN INCLUDES A 3D VIEW THAT'S
00:24:38.442 --> 00:24:44.218
BUILT FROM A. I. AND M. L. TECHNIQUES.
00:24:44.218 --> 00:24:46.234
I'M GOING TO HAVE CASSIE KIND OF
00:24:46.234 --> 00:24:47.830
WALK THROUGH THE MAP AREA WHILE
00:24:47.830 --> 00:24:52.058
I SHOW YOU THE DEVICE. BEING IN
00:24:52.058 --> 00:24:53.307
THE FIELD IS DIFFERENT THAN BEING
00:24:53.307 --> 00:24:55.526
IN A DATA CENTER. LOTS OF THINGS
00:24:55.526 --> 00:24:56.905
CAN HAPPEN. FOR EXAMPLE, YOU CAN
00:24:56.905 --> 00:24:59.108
LOSE POWER. BUT THAT'S OKAY BECAUSE
00:24:59.108 --> 00:25:03.589
OF THE INCLUDED BATTERY. AND THEN
00:25:03.589 --> 00:25:05.725
ALSO BECAUSE CONDITIONS CAN BE HARSH,
00:25:05.725 --> 00:25:08.279
THE DEVICE NEEDS TO BE ABLE TO GET
00:25:08.279 --> 00:25:14.562
BUMPED OR BOUNCED OR EVEN FALL.
00:25:14.562 --> 00:25:17.977
BUT AS YOU CAN SEE, IT'S STILL RUNNING,
00:25:17.977 --> 00:25:20.461
AND CASSIE IS TILL ABLE TO BROWS
00:25:20.461 --> 00:25:22.270
AROUND THE MAP. WITH OUR RUGGED
00:25:22.270 --> 00:25:24.415
SERIES OF AZURE STACK EDGE APPLIANCES,
00:25:24.415 --> 00:25:25.880
WE'RE BRINGING THE POWER OF AZURE
00:25:25.880 --> 00:25:28.515
TO WHERE YOU NEED IT, TO GET YOUR
00:25:28.515 --> 00:25:31.393
CRITICAL JOBS DONE NO MATTER THE
00:25:31.393 --> 00:25:32.126
CONDITIONS. THANK YOU ALL. BACK
00:25:32.126 --> 00:25:41.043
TO YOU, JASON. >> AWESOME. THANK
00:25:41.043 --> 00:25:42.976
YOU. YES, HE DID DROP THAT. WE TRIED
00:25:42.976 --> 00:25:45.798
IT A FEW EXTRA TIMES JUST TO MAKE
00:25:45.798 --> 00:25:47.945
SURE. BUT IT NEEDS TO KEEP ON WORKING.
00:25:47.945 --> 00:25:49.807
THAT IS DEFINITELY THE GOAL. SO
00:25:49.807 --> 00:25:51.231
LET'S FINISH UP AND TAKE A LOOK
00:25:51.231 --> 00:25:53.221
AT AZURE ARC WHICH IS SOMETHING
00:25:53.221 --> 00:25:54.206
YOU HOPEFULLY SAW THIS MORNING IF
00:25:54.206 --> 00:25:56.953
YOU WENT TO THE KEYFLOAT AND SAW
00:25:56.953 --> 00:25:58.137
ADDITIONAL WORK THAT'S THERE. FIRST
00:25:58.137 --> 00:26:00.119
OF ALL, LET'S THINK ABOUT THE PROBLEMS
00:26:00.119 --> 00:26:01.558
THAT WE NEED TO BE ABLE TO DEAL
00:26:01.558 --> 00:26:03.996
WITH. IN PARTICULAR TODAY, AS I
00:26:03.996 --> 00:26:05.253
MENTIONED, YOU MIGHT BE TARGETING
00:26:05.253 --> 00:26:06.385
MULTIPLE CLOUDS ALREADY. YOU MIGHT
00:26:06.385 --> 00:26:08.333
HAVE YOUR ON-PREMISES DATA CENTER
00:26:08.333 --> 00:26:10.599
AND YOU'VE GOT EDGE DEPLOYMENTS.
00:26:10.599 --> 00:26:11.696
LIKE MENTIONED, THE FACTORY AND
00:26:11.696 --> 00:26:13.497
THINGS LIKE THAT, AS WELL. YOU KNOW,
00:26:13.497 --> 00:26:15.010
THE TRUTH IS IS BUSINESSES CONTINUE
00:26:15.010 --> 00:26:18.022
TO EXPAND TO THE EDGE, YOU'RE GOING
00:26:18.022 --> 00:26:19.467
TO GET EVEN MORE TYPES OF SOLUTION
00:26:19.467 --> 00:26:21.123
AND YOU'RE PROBABLY IN A CASE WHERE
00:26:21.123 --> 00:26:23.292
YOU MIGHT HAVE MULTIPLE DIFFERENT
00:26:23.292 --> 00:26:25.265
TYPES OF TECHNOLOGIES OR HAVING
00:26:25.265 --> 00:26:27.207
PULLED TOGETHER. WHICH BASICALLY
00:26:27.207 --> 00:26:28.217
MAKES IT EVEN HARDER TO MAKE SURE
00:26:28.217 --> 00:26:29.749
THAT EVERYTHING IS SECURE, IT'S
00:26:29.749 --> 00:26:31.519
BEING MANAGED IN A CONSISTENT KIND
00:26:31.519 --> 00:26:34.474
OF WAY. THAT'S WHY I'M PLEASED TODAY
00:26:34.474 --> 00:26:37.203
TO ANNOUNCE AZURE ARC AND THE PREVIEW
00:26:37.203 --> 00:26:39.035
FOR AZURE ARC. IT'S TECHNOLOGIES
00:26:39.035 --> 00:26:42.013
THAT BRINGS AZURE SERVICES, GOVERNANCE,
00:26:42.013 --> 00:26:43.570
AND MANAGEMENT TO ANY INFRASTRUCTURE.
00:26:43.570 --> 00:26:45.301
YOU CAN ADOPT THE CLOUD PRACTICES
00:26:45.301 --> 00:26:47.567
THAT WE HAVE ON PREMISES INCLUDING
00:26:47.567 --> 00:26:48.775
DEVOPS AND MANAGING INFRASTRUCTURE
00:26:48.775 --> 00:26:50.057
TEAMS, CONTROL, ET CETERA, AND OF
00:26:50.057 --> 00:26:52.483
COURSE WE BRING ALL OF THOSE SECURITY
00:26:52.483 --> 00:26:54.568
WORK. IF YOU'RE ALREADY OR HAVE
00:26:54.568 --> 00:26:56.623
CREATED THINGS LIKE SECURITY POLICY
00:26:56.623 --> 00:26:57.857
OR MANAGEMENT TECHNIQUES AND ROLES
00:26:57.857 --> 00:26:59.254
THAT YOU'VE GOT AND YOU LEVERAGE
00:26:59.254 --> 00:27:01.309
THEM IN AZURE, AZURE ARC GIVES YOU
00:27:01.309 --> 00:27:03.119
A WAY TO EXTEND THAT. NOW THINK
00:27:03.119 --> 00:27:07.610
ABOUT THOSE USE CASES. THERE ARE
00:27:07.610 --> 00:27:10.912
SEVERAL THINGS TO WE WANT TO ACCOMPLISH
00:27:10.912 --> 00:27:12.272
IN SCALE. AND ADDITION WE WANT TO
00:27:12.272 --> 00:27:13.815
HAVE ACCESS TO DATA AND THE MODERN
00:27:13.815 --> 00:27:14.889
DATA TECHNIQUES THAT ARE THERE.
00:27:14.889 --> 00:27:16.763
WE'VE GOT THE DATA SERVICES AND
00:27:16.763 --> 00:27:18.414
HAVE THEM RUN ANYWHERE. MOST IMPORTANTLY,
00:27:18.414 --> 00:27:20.273
WE WANT TO MAKE SURE WE ORGANIZE,
00:27:20.273 --> 00:27:22.001
GOVERN, AND SECURE ACROSS ALL OF
00:27:22.001 --> 00:27:24.101
THESE ENVIRONMENTS. BECAUSE I KNOW
00:27:24.101 --> 00:27:26.223
AS SOME POINT MY CISO IS GOING TO
00:27:26.223 --> 00:27:27.590
TALK TO ME, AND THEY'RE GOING TO
00:27:27.590 --> 00:27:29.271
BASICALLY SAY, YOU KNOW, WE'RE DEPLOYING
00:27:29.271 --> 00:27:32.503
TO OUR RETAIL SITES. ARE WE SECURE?
00:27:32.503 --> 00:27:33.418
CAN YOU HELP PROVE WE'RE IN A GOOD
00:27:33.418 --> 00:27:35.881
SPOT BECAUSE WE'RE GOING TO PROTECT
00:27:35.881 --> 00:27:37.491
THE COMPANY. IT NEEDS TO BE A CORE
00:27:37.491 --> 00:27:39.526
PART OF ANY SOLUTION WE PUT IN PLACE.
00:27:39.526 --> 00:27:41.537
NOW MOST OF OUR WORKLOADS OUT THERE,
00:27:41.537 --> 00:27:43.001
THEY'RE GOING TO HAVE SOME KIND
00:27:43.001 --> 00:27:44.312
OF COMPUTE. THEY ALMOST ALWAYS HAVE
00:27:44.312 --> 00:27:45.951
DATA. THAT'S WHY WE'RE PLEASED TO
00:27:45.951 --> 00:27:50.193
BRING THE PREVIEW OF AZURE SQL DATA
00:27:50.193 --> 00:27:52.371
BASE AND FOR SQL AS PART OF OUR
00:27:52.371 --> 00:27:55.756
AZURE DATA SERVICES ANYWHERE. THIS
00:27:55.756 --> 00:27:57.995
REALLY ALLOWS YOU TO BE ABLE TO TAKE THE SAME DATA BASE TECHNOLOGY THAT
00:27:57.995 --> 00:27:59.948
YOU'VE BEEN USING IN AZURE AND GIVE US THE
00:27:59.948 --> 00:28:01.520
OPPORTUNITY TO RUN IT ELSEWHERE,
00:28:01.520 --> 00:28:03.463
AS WELL. NOW I CAN ACTUALLY MAKE
00:28:03.463 --> 00:28:05.634
SURE I'M ALWAYS UP TO DATE. I'VE
00:28:05.634 --> 00:28:07.174
GOT ELASTIC SCALE, AND I ONLY PAY
00:28:07.174 --> 00:28:09.523
FOR WHAT I USE. AND MOST IMPORTANTLY,
00:28:09.523 --> 00:28:12.436
YOU CAN RUN ON ANY HARDWARE THAT
00:28:12.436 --> 00:28:15.589
YOU HAVE IN ANY DISTRIBUTION OF
00:28:15.589 --> 00:28:18.795
KUBERNETES. LET'S LOOK AT ALL THE
00:28:18.795 --> 00:28:21.146
STUFF IN ACTION. GABE, TAKE IT AWAY.
00:28:21.146 --> 00:28:24.763
>> THANKS, JASON. HI, EVERYONE.
00:28:24.763 --> 00:28:28.787
IN SATYA'S KEYNOTE, WE SAW HOW AZURE
00:28:28.787 --> 00:28:32.626
ARC ENABLES AZURE DATA SERVICES,
00:28:32.626 --> 00:28:35.120
BRINGING POWERFUL DATA BASE TO ANY
00:28:35.120 --> 00:28:36.002
STRUCTURE. LET'S SEE IF HOUCK USE
00:28:36.002 --> 00:28:40.134
AZURE ARC TO ORGANIZE AND SECURE
00:28:40.134 --> 00:28:41.261
KUBERNETES ON ANY INFRASTRUCTURE
00:28:41.261 --> 00:28:43.867
INCLUDING ON-PREM DATA CENTERS,
00:28:43.867 --> 00:28:46.177
ANY CLOUD, OR AT THE EDGE. SO HOW
00:28:46.177 --> 00:28:48.237
DOES THIS WORK AT A HIGH LEVEL?
00:28:48.237 --> 00:28:50.747
STEP ONE, WE EXTEND AZURE MANAGEMENT
00:28:50.747 --> 00:28:51.975
ACROSS ALL OUR INFRASTRUCTURE USING
00:28:51.975 --> 00:28:56.430
AZURE ARC. GIVING US A SECURE, ORGANIZED,
00:28:56.430 --> 00:28:58.084
AND GOVERNED FOUNDATION. STEP TWO,
00:28:58.084 --> 00:29:00.553
WE USE AZURE POLICY TO ALLOW DEVELOPERS
00:29:00.553 --> 00:29:02.708
TO SAFELY AND SECURELY DELIVER APPLICATIONS
00:29:02.708 --> 00:29:05.488
AND DATA SERVICES TO ANY INFRASTRUCTURE.
00:29:05.488 --> 00:29:08.623
LET'S SEE THIS IN ACTION. SO GLOBAL
00:29:08.623 --> 00:29:11.304
BANK I. T. HAS 300 LOCATIONS WORLDWIDE,
00:29:11.304 --> 00:29:14.311
AND THEY'RE STRUGGLING TO KEEP INFRASTRUCTURE
00:29:14.311 --> 00:29:16.633
COMPLIANT AND UP TO DATE. IT'S TAKING
00:29:16.633 --> 00:29:19.943
A FULL YEAR TO REFRESH APPLICATIONS,
00:29:19.943 --> 00:29:21.348
THAT'S ABOUT TO CHANGE. LET'S SEE
00:29:21.348 --> 00:29:23.251
WHAT IT WOULD LOOK LIKE TO DEPLOY
00:29:23.251 --> 00:29:25.757
A NEW APP FULLY COMPLIANT WITH BANK
00:29:25.757 --> 00:29:27.650
SECURITY PRACTICES USING AZURE ARC.
00:29:27.650 --> 00:29:29.646
LET'S START WITH THE AZURE PORTAL
00:29:29.646 --> 00:29:33.701
AND VIEW OUR EUROPEAN BRANCH OFFICES.
00:29:33.701 --> 00:29:35.691
NOW, HERE YOU SEE -- WE HAVE A LOT
00:29:35.691 --> 00:29:37.113
OF CLUSTERS TO MANAGE IN EUROPE,
00:29:37.113 --> 00:29:37.114
ATHENS, BUDAPEST, COPENHAGEN, NOW
00:29:37.114 --> 00:29:41.752
LOTS OF LOCATIONS MEANS IT'S EASY
00:29:41.752 --> 00:29:44.981
TO MISS THINGS AND MAKE MISTAKES.
00:29:44.981 --> 00:29:46.759
FOR EXAMPLE, ACCIDENTALLY LEAVING
00:29:46.759 --> 00:29:48.325
PORTS EXPOSED HAS LED TO SECURITY
00:29:48.325 --> 00:29:50.017
INCIDENTS ACROSS THE FINANCIAL SERVICES
00:29:50.017 --> 00:29:51.609
INDUSTRY. THE BIG SECURITY TEAM
00:29:51.609 --> 00:29:53.937
HAS SAID THAT NOW, DEVELOPERS CANNOT
00:29:53.937 --> 00:29:56.489
UPDATE ANY APPLICATIONS UNTIL I.
00:29:56.489 --> 00:29:58.948
T. CAN PROVE NETWORK PORTS ARE LOCKED
00:29:58.948 --> 00:30:00.804
DOWN. NOW I. T. ALREADY USES AZURE
00:30:00.804 --> 00:30:02.861
POLICY TO ENFORCE LOCKDOWN FOR SERVERS
00:30:02.861 --> 00:30:05.548
AND CLUSTERS IN THE CLOUD. AZURE
00:30:05.548 --> 00:30:11.077
ARC EXTENDS AZURE POLICY ON PREMISES,
00:30:11.077 --> 00:30:11.594
ENABLING I. T. TO INVENTORY, ORGANIZE,
00:30:11.594 --> 00:30:14.741
AND GOVERN BRANCH LOCATIONS THE
00:30:14.741 --> 00:30:16.360
SAME WAY. WE HAVE ONE SYSTEM TO
00:30:16.360 --> 00:30:17.236
MANAGE SYSTEMS ACROSS CLOUD AND
00:30:17.236 --> 00:30:20.263
EDGE. BY CLICKING ON POLICIES, WE
00:30:20.263 --> 00:30:27.141
CAN GO AHEAD AND SEARCH FOR PORT.
00:30:27.141 --> 00:30:29.161
AND YOU CAN SEE THAT WE ALREADY
00:30:29.161 --> 00:30:31.026
HAVE THIS POLICY TO LOCK DOWN NETWORK
00:30:31.026 --> 00:30:33.545
PORTS. IT'S ALREADY APPLIED, AND
00:30:33.545 --> 00:30:34.904
AT 100 COMPLIANCE. THIS IS MORE
00:30:34.904 --> 00:30:37.366
THAN A ONE-TIME CONFIGURATION. AS
00:30:37.366 --> 00:30:39.164
SOON AS NEW CLUSTERS, YOU KNOW,
00:30:39.164 --> 00:30:40.513
ARE CONNECTED TO AZURE, POLICIES
00:30:40.513 --> 00:30:42.817
ARE AUTOMATICALLY APPLIED ON MANAGEMENT
00:30:42.817 --> 00:30:46.968
GROUP, SUBSCRIPTION, RESOURCE GROUP,
00:30:46.968 --> 00:30:48.712
OR TACK. NOW THAT I. T. HAS SECURED
00:30:48.712 --> 00:30:50.605
THE INFRASTRUCTURE AND CAN DEMONSTRATE
00:30:50.605 --> 00:30:52.691
100 COMPLIANCE, WE'RE FLEE TO DEPLOY
00:30:52.691 --> 00:30:53.837
THE FRAUD APPLICATION. FOR THIS
00:30:53.837 --> 00:30:55.421
WE'RE ALSO GOING TO USE AZURE POLICY
00:30:55.421 --> 00:30:57.017
THROUGH AZURE ARC. SO LET'S SEE
00:30:57.017 --> 00:30:59.524
WHAT IT WOULD LOOK LIKE FOR I. T.
00:30:59.524 --> 00:31:01.309
TO ENABLE DEVELOPERS TO QUICKLY
00:31:01.309 --> 00:31:02.577
AND SAFELY SHIP APPLICATIONS. I.
00:31:02.577 --> 00:31:05.957
T. STARTS BY ASSIGNING A NEW POLICY.
00:31:05.957 --> 00:31:07.737
SO YOU'RE GOING TO GO TO THE SEARCH
00:31:07.737 --> 00:31:10.235
FIELD FOR POLICY DEFINITIONS, AND
00:31:10.235 --> 00:31:13.216
WE'RE GOING TO SEARCH FOR POLICIES
00:31:13.216 --> 00:31:14.724
LABELED KUBERNETES. AND HERE'S A
00:31:14.724 --> 00:31:17.195
POLICY THAT USES GET HUB TO MANAGE
00:31:17.195 --> 00:31:20.015
WORKLOADS ON A KUBERNETES CLUSTER.
00:31:20.015 --> 00:31:24.327
LET'S USE THAT. LOOKING NEXT, WE'LL
00:31:24.327 --> 00:31:26.892
BRING UP -- SORRY, PREVIOUS, CLICKING
00:31:26.892 --> 00:31:31.280
NEXT, WE'LL BRING UP THE POLICY
00:31:31.280 --> 00:31:33.473
CONFIGURATION SCREEN. NOW THIS POLICY
00:31:33.473 --> 00:31:36.826
CONNECTS CLUSTERS TO A SPECIFIC
00:31:36.826 --> 00:31:39.719
GIT REPO REPOSITORY. ANY APPS ARE
00:31:39.719 --> 00:31:41.453
AUTOMATICALLY DEPLOYED TO ONE OR
00:31:41.453 --> 00:31:43.385
MORE LINK CLUSTERS. LIKE WE USE
00:31:43.385 --> 00:31:45.959
POLICY TO KEEP APPLICATIONS -- LIKE
00:31:45.959 --> 00:31:47.228
WE KEEP USE POLICY TO LOCK DOWN
00:31:47.228 --> 00:31:48.721
PORTS, WE'RE ALSO GOING TO USE POLICY
00:31:48.721 --> 00:31:51.063
TO KEEP APPLICATIONS UP TO DATE.
00:31:51.063 --> 00:31:52.886
NOW EVEN BETTER, IF AN APPLICATION
00:31:52.886 --> 00:31:55.469
IS MODIFIED AT A BRANCH LOCATION,
00:31:55.469 --> 00:31:56.867
THAT CHANGE IS QUICKLY REVERTED
00:31:56.867 --> 00:31:59.128
SO THE INFRASTRUCTURE REMAINS COMPLIANT.
00:31:59.128 --> 00:32:06.167
LET'S GO AHEAD AND APPLY THIS. GREAT.
00:32:06.167 --> 00:32:07.551
WHILE THE APPLICATION POLICY ACTIVATES
00:32:07.551 --> 00:32:09.199
IN THE BACKGROUNDS, LET'S SUMMARIZE
00:32:09.199 --> 00:32:10.776
WHAT WE'VE SEEN. THE CLUSTERS AT
00:32:10.776 --> 00:32:11.848
OUR BRANCH LOCATIONS ARE MANAGED
00:32:11.848 --> 00:32:13.894
THROUGH AZURE ARC AND AZURE POLICY.
00:32:13.894 --> 00:32:15.781
WE HAVE ONE POLICY THAT LOCKS DOWN
00:32:15.781 --> 00:32:17.627
NETWORK PORTS, AND WE HAVE A SECOND
00:32:17.627 --> 00:32:19.461
POLICY THAT DEPLOYS APPS TO OUR
00:32:19.461 --> 00:32:23.535
CLUSTERS. AZURE ARC AND POLICY ACTIVELY
00:32:23.535 --> 00:32:24.763
ENSURES THE APPS STAY IN COMPLIANCE
00:32:24.763 --> 00:32:26.693
AND UP TO DATE. LET'S PUT ON OUR
00:32:26.693 --> 00:32:28.092
DEVELOPER HAT AND SEE WHAT IT LOOKS
00:32:28.092 --> 00:32:31.193
LIKE FOR A BANK DEVELOPER TO SECURELY
00:32:31.193 --> 00:32:32.601
DELIVER APPLICATIONS USING AZURE
00:32:32.601 --> 00:32:35.495
ARC. A MINUTE AGO WE SAW HOE I.T.
00:32:35.495 --> 00:32:40.941
LINKED THEIR CLUFT FORCE TGITHUB
00:32:40.941 --> 00:32:42.361
REPOSEORATORIY. THEY CAN OPEN A
00:32:42.361 --> 00:32:44.010
POLAR QUEST THE SAME WAY THEY WOULD
00:32:44.010 --> 00:32:44.968
UPDATE ANY CODE THEY'RE WORKING
00:32:44.968 --> 00:32:47.859
ON. THIS IS THE POLAR QUEST WE'RE
00:32:47.859 --> 00:32:50.502
GOING TO USE TO DEPLOY THE FRAUD
00:32:50.502 --> 00:32:53.577
APP. NOW WHEN WE MERGE THIS REQUEST,
00:32:53.577 --> 00:32:55.861
THIS WILL STOP THE UPDATE PROCESS,
00:32:55.861 --> 00:32:57.574
SEAMLESSLY DEPLOYING THE APPLICATION
00:32:57.574 --> 00:33:02.759
TO ONE, FIVE, AND HUNDREDS OF BANK
00:33:02.759 --> 00:33:05.250
LOCATIONS.USING A GIT-BASED WORK
00:33:05.250 --> 00:33:06.582
FLOW ALLOWS PROFESSIONALS AND STAKEHOLDER
00:33:06.582 --> 00:33:09.085
TO VIEW, COMMENT, AND APPROVE ANY
00:33:09.085 --> 00:33:11.109
PRUPGZ UPDATES. BECAUSE CHANGES
00:33:11.109 --> 00:33:14.069
ARE IN GITHUB, GLOENL BANK I. T.
00:33:14.069 --> 00:33:16.137
STREAMLINES CHANGE MANAGEMENT WITH
00:33:16.137 --> 00:33:17.509
AUTOMATED TESTING, SIGNOFF, AND
00:33:17.509 --> 00:33:19.393
LOGGING FOR COMPLIANCE AND AUDIT.
00:33:19.393 --> 00:33:25.298
SO LET'S GO AHEAD AND MERGE THIS
00:33:25.298 --> 00:33:30.382
REQUEST. WITH THE REQUEST MERGED,
00:33:30.382 --> 00:33:31.818
IT'S DEPLOYING IN THE BACKGROUNDS.
00:33:31.818 --> 00:33:34.970
AZURE ARC ENABLED ON-DEMAND DEVELOPER
00:33:34.970 --> 00:33:38.437
SELF-SERVICE WITH CENTRALIZED ODDSITYING
00:33:38.437 --> 00:33:43.974
COMPLIANCE BUILT IN AND THE DEVELOPERS
00:33:43.974 --> 00:33:44.821
NEVER HAD TO LEAVE GITHUB. BEATS A ONCE IN
00:33:44.821 --> 00:33:48.197
A YEAR REFRESH CYCLE. LET'S SWITCH
00:33:48.197 --> 00:33:50.357
TO NEW YORK MY-- TO NORTH AMERICA
00:33:50.357 --> 00:33:52.080
AND LOOK AT THE MAP. WE'LL DRAW
00:33:52.080 --> 00:33:54.300
ON NORTH AMERICA, I'LL LOOK AT DETROIT.
00:33:54.300 --> 00:33:57.514
AND FIRST YOU LOOK AT POLICIES.
00:33:57.514 --> 00:34:00.372
AND WE CAN SEE THAT THE PORT IN
00:34:00.372 --> 00:34:03.589
NETWORK POLICIES ARE -- ARE ALREADY
00:34:03.589 --> 00:34:04.577
APPLIED AND COMPLIANT. IF WE GO
00:34:04.577 --> 00:34:07.519
TO CONFIGURATIONS AND OPEN UP THE
00:34:07.519 --> 00:34:10.447
FRAUD APP, WE CAN SEE THAT THE FRAUD APP HAS
00:34:10.447 --> 00:34:12.331
BEEN DEPLOYED SUCCESSFULLY. HOW
00:34:12.331 --> 00:34:15.078
COOL IS THAT? BUT GLOBAL BANK I.
00:34:15.078 --> 00:34:16.359
T. 'S WORK ISN'T DONE. EVERYTHING
00:34:16.359 --> 00:34:18.499
THEY HAVE DEPLOYED SO FAR IS ON
00:34:18.499 --> 00:34:20.107
EXISTING HARDWARE. WITH EXPANSION
00:34:20.107 --> 00:34:22.147
PLANS FOR 50 NEW BRANCH LOCATIONS,
00:34:22.147 --> 00:34:24.754
THEY'VE CHOSEN TO STANDARDIZE ON
00:34:24.754 --> 00:34:26.801
AZURE STACK EDGE. WITH UPCOMING
00:34:26.801 --> 00:34:27.738
KUBERNETES SUPPORT ON AZURE STACK
00:34:27.738 --> 00:34:29.386
EDGE, IT COULDN'T BE EASIER FOR
00:34:29.386 --> 00:34:32.625
I. T. TO BRING A NEW BRANCH ON LINE.
00:34:32.625 --> 00:34:34.468
SELECT CREATE A CLUSTER, CONFIGURE
00:34:34.468 --> 00:34:37.789
THE CLUSTER, HIT APPLY. AZURE STACK
00:34:37.789 --> 00:34:39.561
EDGE AUTOMATICALLY PROVISIONS KUBERNETES
00:34:39.561 --> 00:34:41.774
AND INCLUDES AZURE ARC OUT OF THE
00:34:41.774 --> 00:34:43.577
BOX. THIS MEANS GLOBAL BANK I. T.
00:34:43.577 --> 00:34:44.955
CAN TAKE AN AZURE STACK EDGE, PLUG
00:34:44.955 --> 00:34:47.602
IT IN, POWER IT ON, AND A FEW MINUTES
00:34:47.602 --> 00:34:50.379
LATER THE NEW BRANCH IS ON LINE,
00:34:50.379 --> 00:34:51.961
INVENTORIED, FULLY COMPLIANT, RUNNING
00:34:51.961 --> 00:34:53.750
ALL THE LATEST APPS, WITH CENTRAL
00:34:53.750 --> 00:34:57.856
MANAGEMENT AND GOVERNANCE FROM AZURE.
00:34:57.856 --> 00:35:00.611
THANKS TO THE POWER OF AZURE ARC,
00:35:00.611 --> 00:35:02.514
IT CAN IN ON LINE OVER LUNCH INSTEAD
00:35:02.514 --> 00:35:04.305
OF WAITING DAYS OR WEEKS. AZURE
00:35:04.305 --> 00:35:06.197
ARC MAKES IT EASY TO ADOPT CLOUD
00:35:06.197 --> 00:35:08.584
PRACTICES ON PREMISES, TO EMPOWER
00:35:08.584 --> 00:35:09.869
DEVELOPERS WITH SELF-SERVICE CAPABILITIES,
00:35:09.869 --> 00:35:11.547
AND THE ABILITY TO CHOOSE THEIR
00:35:11.547 --> 00:35:13.947
OWN TOOLS, ALL WITH CENTRAL I. T.
00:35:13.947 --> 00:35:15.807
GUIDANCE AND GOVERNANCE FROM AZURE.
00:35:15.807 --> 00:35:17.492
NOW THIS STUFF IS BRAND NEW, SO
00:35:17.492 --> 00:35:18.656
WE'VE ADDED A BUNCH OF SESSIONS
00:35:18.656 --> 00:35:20.743
TO THE CATALOG. CHECK THAT OUT.
00:35:20.743 --> 00:35:21.633
THE NEW SESSIONS WERE JUST ADDED
00:35:21.633 --> 00:35:30.771
TODAY. THANKS, EVERYONE. >>> IN
00:35:30.771 --> 00:35:32.260
THE ENERGY INDUSTRY WE HAVE A VAST
00:35:32.260 --> 00:35:34.800
AMOUNT OF DATA. NOW MACHINE LEARNING
00:35:34.800 --> 00:35:36.449
AND DIGITAL TECHNOLOGIES MAKE IT
00:35:36.449 --> 00:35:38.550
POSSIBLE TO EARN MORE INSIGHTS AND
00:35:38.550 --> 00:35:40.719
TRANSFORM OUR BUSINESS. >> DEVOPS
00:35:40.719 --> 00:35:42.857
AS A METHODOLOGY ALLOWS US TO BRING
00:35:42.857 --> 00:35:44.701
THEMES TOGETHER AND TO MOVE QUICKLY
00:35:44.701 --> 00:35:47.021
AND GENERATE TREMENDOUS VALUE, PARTICULARLY
00:35:47.021 --> 00:35:48.450
THROUGH THE ENERGY TRANSITION. AS
00:35:48.450 --> 00:35:51.079
WE MOVE FROM MOLECULES TO ELECTRONS.
00:35:51.079 --> 00:35:53.674
>> WE'VE BEEN ON AN EXPONENTIAL
00:35:53.674 --> 00:35:55.971
GROWTH COURSE, WE HAVE A DATA SCIENCE
00:35:55.971 --> 00:35:58.637
NETWORK OF AROUND 2, 000. WITH THAT
00:35:58.637 --> 00:36:00.634
SORT OF SCALE WE NEED STANDARDIZE
00:36:00.634 --> 00:36:02.357
THE WAY WE WORK. THAT'S WHY DEFENSE
00:36:02.357 --> 00:36:06.023
OPS IS SO IMPORTANT. AS WE TRY TO
00:36:06.023 --> 00:36:07.613
STANDARDIZE ALE. AND THE WAY IN
00:36:07.613 --> 00:36:08.531
WHICH WE DEVELOP NEW SOLUTIONS,
00:36:08.531 --> 00:36:11.685
WE'VE BEEN WORKING WITH MICROSOFT
00:36:11.685 --> 00:36:13.358
TO LEVERAGE PRODUCTS LIKE AZURE
00:36:13.358 --> 00:36:16.153
BOARDS, AZURE PIPELINES, GITHUB
00:36:16.153 --> 00:36:18.681
ENTERPRISE, IN ORDER TO ENSURE THAT
00:36:18.681 --> 00:36:21.069
OUR ENGINEERS AND OUR DATA SCIENTISTS
00:36:21.069 --> 00:36:22.482
ARE WORKING CONSISTENTLY, THAT THEY
00:36:22.482 --> 00:36:24.191
CAN SHARE CODES, AND THEY CAN DEPLOY
00:36:24.191 --> 00:36:26.640
THEM TO THE EDGE AND THE CLOUD EASILY.
00:36:26.640 --> 00:36:28.447
THAT'S CHANGED OUR DEVELOPMENT CYCLES
00:36:28.447 --> 00:36:31.258
FROM MONTHS TO WEEKS. >> HAVING
00:36:31.258 --> 00:36:32.723
DETAILED ENTERPRISE INTEGRATED WITH
00:36:32.723 --> 00:36:36.001
AZURE MAKES IT REALLY SIMPLE FOR
00:36:36.001 --> 00:36:39.939
ANY COLLABORATOR IN THE PROJECT
00:36:39.939 --> 00:36:41.773
TO PULL THE HEAR CYCLE OF THE CODE,
00:36:41.773 --> 00:36:43.748
KNOWING WHERE IT'S AT, WHERE IT'S
00:36:43.748 --> 00:36:50.097
BEEN DEPLOYED AND DEPLOYED SUCCESSFULLY.
00:36:50.097 --> 00:36:51.718
>> THAT'S A GREAT EXAMPLE OF CUSTOMERS
00:36:51.718 --> 00:36:54.170
WHO ADOPT GITHUB AND AZURE FOR THEIR
00:36:54.170 --> 00:36:55.640
DEVELOPMENT AND DEVOPS PRACTICES.
00:36:55.640 --> 00:36:57.527
SO I WANT TO DRILL NEXT INTO SOME
00:36:57.527 --> 00:36:59.573
OF THESE NATIVE DEVELOPER TOOLS
00:36:59.573 --> 00:37:01.041
AND THE WORK THAT WE CAN DO WITH
00:37:01.041 --> 00:37:02.505
CLOUD APPLICATIONS. LET'S START
00:37:02.505 --> 00:37:06.007
OFF WITH DEV TOOLS AND DEVOPS. THINK
00:37:06.007 --> 00:37:07.252
ABOUT THIS, WE'RE GOING TO START
00:37:07.252 --> 00:37:08.432
WITH VISUAL STUDIO. THE BEST IN
00:37:08.432 --> 00:37:09.640
CLASS FOR EVERY DEVELOPER THAT'S
00:37:09.640 --> 00:37:11.322
OUT THERE. WE START OFF WITH OUR
00:37:11.322 --> 00:37:12.922
VISUAL STUDIO, THE RICH IDE THAT
00:37:12.922 --> 00:37:15.179
CAN RUN ON WINDOWS, IT CAN RUN ON
00:37:15.179 --> 00:37:17.253
THE MCINTOSH, OR VISUAL STUDIO CODE
00:37:17.253 --> 00:37:20.197
THAT I CAN RUN IN MULTIPLE PLATFORMS.
00:37:20.197 --> 00:37:22.197
AND ALSO THE INTRODUCTION THAT WE
00:37:22.197 --> 00:37:23.311
ANNOUNCED EARLIER THIS YEAR WITH
00:37:23.311 --> 00:37:23.312
VISUAL STUDIO ON LINE, WHICH I CAN
00:37:23.312 --> 00:37:26.794
DO COLLABORATIVE DEVELOPMENT AND
00:37:26.794 --> 00:37:29.311
NOT REALLY LOSE MY PLACE AS I GO.
00:37:29.311 --> 00:37:31.551
NOW THERE WAS A RECENT SURVEY STACK
00:37:31.551 --> 00:37:34.628
OVERFLOW DID OF OVER 90, 000 DEVELOPERS.
00:37:34.628 --> 00:37:36.604
THEY FOUND THAT NEARLY ONE-THIRD
00:37:36.604 --> 00:37:38.469
OF DEVELOPERS LISTED VISUAL STUDIO
00:37:38.469 --> 00:37:43.355
AS THEIR CORE USAGE TOOL. OVER 50
00:37:43.355 --> 00:37:44.972
ARE LEVERAGING VISUAL STUDIO CODE.
00:37:44.972 --> 00:37:46.267
AND THE POPULARITY CONTINUES TO
00:37:46.267 --> 00:37:49.351
INCREASE AND WE SEE A TON OF ADOPTION.
00:37:49.351 --> 00:37:51.637
NOW WE'RE VERY PLEASED TODAY TO
00:37:51.637 --> 00:37:53.883
ANNOUNCE IN PUBLIC PREVIEW VISUAL
00:37:53.883 --> 00:37:55.174
STUDIO ON LINE. VISUAL STUDIO ON
00:37:55.174 --> 00:37:57.561
LINE IS DESIGNED AS AN ON-DEMAND
00:37:57.561 --> 00:37:58.758
DEVELOPMENT ENVIRONMENT AND IS DESIGNED
00:37:58.758 --> 00:38:01.214
IN THE CLOUD. I CAN USE VISUAL STUDIO
00:38:01.214 --> 00:38:03.547
CODE DIRECTLY, OR I CAN USE IT RIGHT
00:38:03.547 --> 00:38:05.081
OUT OF THE EDITOR IF I NEED IT.
00:38:05.081 --> 00:38:06.408
THERE'S A FULL EXTENSION MARKETPLACE
00:38:06.408 --> 00:38:08.754
THAT'S THERE, AND YOU HAVE COLLABORATIVE
00:38:08.754 --> 00:38:09.889
FEATURES LIKE LIVE SHARE ALREADY
00:38:09.889 --> 00:38:11.770
BUILT IN. THIS IS AN AWESOME WAY
00:38:11.770 --> 00:38:13.433
TO KEEP FOCUSED ON THE WORK THAT
00:38:13.433 --> 00:38:15.563
YOU'RE DOING, EVEN IN THE FACE OF
00:38:15.563 --> 00:38:18.618
INTERRUPTIONS COMING FROM THE TEAM.
00:38:18.618 --> 00:38:20.511
GITHUB IS AT THE HEART OF THE OPEN-SOURCE
00:38:20.511 --> 00:38:22.186
COMMUNITY. IT WILL ALWAYS BE AN
00:38:22.186 --> 00:38:24.461
OPEN PLATFORM AND SUPPORTS ALL DEVS.
00:38:24.461 --> 00:38:25.709
THERE'S OVER 40 MILLION DEVELOPERS
00:38:25.709 --> 00:38:29.398
IN THE ECOSYSTEM. OVER 100 MILLION
00:38:29.398 --> 00:38:32.067
REPOSITORIES. AND IT'S USED BY 2.
00:38:32.067 --> 00:38:33.963
1 MILLION BUSINESSES AND ORGANIZATIONS.
00:38:33.963 --> 00:38:36.077
SO IT'S CLEARLY AT THE CORE OF A
00:38:36.077 --> 00:38:38.387
LOT OF WORK THAT WE DO EVERY DAY.
00:38:38.387 --> 00:38:40.919
NOW THIS CULMINATION OF GITHUB AND
00:38:40.919 --> 00:38:42.177
AZURE DEVOPS PROVIDES US REALLY
00:38:42.177 --> 00:38:43.594
NICE END-TO-END SOLUTION FOR DEVELOPMENT
00:38:43.594 --> 00:38:45.682
TEAMS. WHEN I GET UP AND RUNNING,
00:38:45.682 --> 00:38:49.143
OF COURSE I NEED TO HAVE THE FANTASTIC
00:38:49.143 --> 00:38:50.581
CICD LOOP. I WANT THE EXPERIENCE
00:38:50.581 --> 00:38:52.938
TO BE ABLE TO DEPLOY TO ANY ENVIRONMENT
00:38:52.938 --> 00:38:55.257
SUCH AS KUBERNETES ON AZURE OR ON
00:38:55.257 --> 00:38:56.915
PREMISES OR IN THE CLOUD, BASICALLY
00:38:56.915 --> 00:38:58.672
WHAT YOU SAW GABE JUST SHOW OFF.
00:38:58.672 --> 00:39:00.481
SO THAT BASICALLY IS THE MOTIVATION
00:39:00.481 --> 00:39:02.608
FOR PULLING THESE TOOLS TOGETHER.
00:39:02.608 --> 00:39:04.100
NOW WE'VE GOT SOME COOL FEATURES
00:39:04.100 --> 00:39:06.117
HERE I WANT TO INVITE DONOVAN BROWN
00:39:06.117 --> 00:39:08.299
ON STAGE, AND HE'S GOING TO GO THROUGH
00:39:08.299 --> 00:39:13.218
ALL OF OUR DEVELOPER TOOLS UPDATES.
00:39:13.218 --> 00:39:22.985
DONOVAN? DONOVAN? >> THANK YOU SO MUCH,
00:39:22.985 --> 00:39:25.304
JASON. I REMEMBER THE FIRST TIME
00:39:25.304 --> 00:39:27.598
I USED A COMPUTER, I WAS STARING
00:39:27.598 --> 00:39:30.330
AT A DOS SCREEN, COMPLETELY CONFUSED,
00:39:30.330 --> 00:39:32.564
AND I HAD NO IDEA WHAT I WAS SUPPOSED
00:39:32.564 --> 00:39:34.341
TO TYPE. AND THEN WINDOWS CAME OUT,
00:39:34.341 --> 00:39:36.233
I THOUGHT THIS -- THIS IS HOW YOU'RE
00:39:36.233 --> 00:39:37.675
SUPPOSED TO USE A COMPUTER. I WAS
00:39:37.675 --> 00:39:38.938
SO EXCITED, I WANTED TO LEARN HOW
00:39:38.938 --> 00:39:40.438
TO PROGRAM. THEN I WAS RIGHT BACK
00:39:40.438 --> 00:39:44.780
AT THE COMMAND LINE BECAUSE OF MY
00:39:44.780 --> 00:39:46.377
COMPILER REIGN AT THE COMMAND LINE,
00:39:46.377 --> 00:39:49.046
MY LINKER RUN AT THE COMMAND LINE.
00:39:49.046 --> 00:39:49.985
TODAY OUR LERNTS AND MANAGEMENT
00:39:49.985 --> 00:39:52.678
AND CIDC SYSTEMS RUN FROM THE COMMAND
00:39:52.678 --> 00:41:03.761
LINE. SO IT'S -- THE ABILITY TO
00:41:03.761 --> 00:41:05.058
CUSTOMIZE IT. WHEN I WAS A YOUNG
00:41:05.058 --> 00:41:08.829
BOY, THERE WAS A MOVIE THAT I LIKED.
00:41:08.829 --> 00:41:10.174
IT INSPIRED ME ABOUT COMPUTERS AND
00:41:10.174 --> 00:41:11.406
TAUGHT ME HOW POWERFUL THEY WERE.
00:41:11.406 --> 00:41:12.637
THE MAJORITY OF THE MOVIE WAS DONE
00:41:12.637 --> 00:41:14.773
INSIDE OF A TERMINAL. I WAS WONDERING,
00:41:14.773 --> 00:41:16.409
IS THERE ANY WAY I CAN CUSTOMIZE
00:41:16.409 --> 00:41:17.441
THIS TERMINAL TO LOOK LIKE THAT
00:41:17.441 --> 00:41:19.628
ONE AND TAKE ME BACK IN TIME. THIS MOVIE
00:41:19.628 --> 00:41:21.297
WAS INCREDIBLE. AND THEN I REALIZED
00:41:21.297 --> 00:41:22.965
THAT I CAN DO THAT. SO WHAT I'M
00:41:22.965 --> 00:41:25.051
GOING TO DO IS SHOW HOW I CAN CUSTOMIZE
00:41:25.051 --> 00:41:27.433
THIS SCREEN OVER HERE. LET'S CLEAR
00:41:27.433 --> 00:41:29.245
THIS OUT. THEN I'M GOING TO GO OVER
00:41:29.245 --> 00:41:31.441
HERE AND CHANGE THE COLOR OF MY
00:41:31.441 --> 00:41:33.578
CURSOR, FOR EXAMPLE. AND THEN I'M
00:41:33.578 --> 00:41:34.997
GOING TO CHANGE THE SHAPE OF THE
00:41:34.997 --> 00:41:36.479
OCCURSTOR MAKE IT MORE RETRO. I
00:41:36.479 --> 00:41:37.917
WANT TO CHANGE THE FONT FACE THAT
00:41:37.917 --> 00:41:39.915
I'M USING, AND I'M EVEN GOING TO
00:41:39.915 --> 00:41:41.763
CHANGE THE SCHEMA THAT I'M USING.
00:41:41.763 --> 00:41:44.518
WHEN I CLICK ON SAVE, YOU CAN SEE
00:41:44.518 --> 00:41:46.274
I HAVE THIS COOL KIND OF RETRO FEEL.
00:41:46.274 --> 00:41:50.055
CAN ANYONE GUESS WHAT MOVIE THIS
00:41:50.055 --> 00:41:53.079
IS? EVERYONE THAT'S SMILING AND
00:41:53.079 --> 00:41:57.665
LAUGHING, THEY'RE OLD, OKAY. NEVERTHELESS,
00:41:57.665 --> 00:41:59.837
THIS IS A COOL FEATURE THAT IS --
00:41:59.837 --> 00:42:01.392
YOUR TOOLS THAT YOU DEVELOP ARE
00:42:01.392 --> 00:42:03.851
LIKE THE INSTRUMENTS THAT WE PLAY.
00:42:03.851 --> 00:42:05.225
THE WAY THAT WE SHARE OUR CREATIVITY.
00:42:05.225 --> 00:42:06.655
YOU WANT TO CUSTOMIZE THEM AND MAKE
00:42:06.655 --> 00:42:08.884
THEM FIT LIKE A GLOVE. HERE AT MICROSOFT,
00:42:08.884 --> 00:42:10.789
WE WANT TO MAKE SURE THAT ALL DEVELOPERS
00:42:10.789 --> 00:42:12.277
FEEL UNIFIED, NO MATTER WHAT LANGUAGE
00:42:12.277 --> 00:42:14.069
YOU PROGRAM IN OR WHAT PLATFORM
00:42:14.069 --> 00:42:16.904
YOU TARGET. WHICH IS WHY WE ACTUALLY
00:42:16.904 --> 00:42:18.221
SUPPORT MULTIPLE PLATFORMS WITH
00:42:18.221 --> 00:42:20.443
OUR TERMINAL. IF YOU'RE USING WINDOWS
00:42:20.443 --> 00:42:23.353
SUBSYSTEM FOR LINUX, EVERY DISC
00:42:23.353 --> 00:42:24.599
THAT YOU INSTALL WILL SHOW UP HERE
00:42:24.599 --> 00:42:28.236
AS AN OPTION FOR YOU. FOR EXAMPLE,
00:42:28.236 --> 00:42:30.827
I CAN COME DOWN HERE AND CHOOSE
00:42:30.827 --> 00:42:32.541
MBUTU. I'M USING THE POWER OF LINUX
00:42:32.541 --> 00:42:34.585
WITH THE PRODUCTIVITY OF WINDOWS.
00:42:34.585 --> 00:42:38.634
LET ME C. D. INTO A -- THIS IS A
00:42:38.634 --> 00:42:40.207
GITHUB REPOSITORY I HAVE OF AN APPLICATION.
00:42:40.207 --> 00:42:42.314
IT'S RUNNING INSIDE OF LINUX, SO
00:42:42.314 --> 00:42:44.009
I HAVE A DIFFERENT VERSION OF PYTHON
00:42:44.009 --> 00:42:45.689
INSTALLED. I'M USING LINUX TOOLS,
00:42:45.689 --> 00:42:47.382
BUT I WANT TO USE CODE ON WINDOWS.
00:42:47.382 --> 00:42:50.549
WHAT I CAN DO IS TYPE CODE DOT AND
00:42:50.549 --> 00:42:51.758
PRESS ENTER. WHAT'S GOING TO HAPPEN
00:42:51.758 --> 00:42:54.595
IS CODE IS GOING TO LAUNCH ON MY
00:42:54.595 --> 00:42:55.999
ACTUAL WINDOWS MACHINE. IN THE CORNER,
00:42:55.999 --> 00:42:57.621
YOU CAN SEE THAT I'M CONNECTED TO
00:42:57.621 --> 00:42:59.686
LINUX ON THE BACK END. THIS TERMINAL
00:42:59.686 --> 00:43:01.950
IS ALSO CONNECTED TO LINUX. IF I
00:43:01.950 --> 00:43:03.846
WERE TO COME TO MY EXTENSIONS, SOME
00:43:03.846 --> 00:43:06.218
OF MY EXTENSIONS ARE INSTALLED LOCALLY,
00:43:06.218 --> 00:43:08.167
AND THE EXTENSIONS I NEED INSIDE
00:43:08.167 --> 00:43:09.790
OF MY LINUX ENVIRONMENT ARE ONLY
00:43:09.790 --> 00:43:14.545
INSTALLED THERE. I HAVE THESE NICE
00:43:14.545 --> 00:43:15.545
N NON-CONTAMINATED REQUIREMENTS
00:43:15.545 --> 00:43:17.925
FOR MY DEVELOPMENT. TO DEBUG THIS
00:43:17.925 --> 00:43:19.644
I NEED TO HAVE A PART OF THE SYSTEM
00:43:19.644 --> 00:43:20.996
START OCCUPY LINUX, ANOTHER PART
00:43:20.996 --> 00:43:22.379
START UP ON WINDOWS, AND I WANT
00:43:22.379 --> 00:43:24.356
TO BE ABLE TO DEBUG THIS THE SAME
00:43:24.356 --> 00:43:26.288
WAY. IF WE COME TO DEBUGGING, I
00:43:26.288 --> 00:43:28.531
PRESS ON START. THAT'S EXACTLY WHAT'S
00:43:28.531 --> 00:43:29.573
HAPPENING NOW. IN THE BACKGROUNDS
00:43:29.573 --> 00:43:32.441
I HAVE ONE PIECE, IN THE FOREGROUND,
00:43:32.441 --> 00:43:35.802
I HAVE ANOTHER. I CAN USE AND DEBUG
00:43:35.802 --> 00:43:37.101
MY APPLICATION SHOULD I NEED TO.
00:43:37.101 --> 00:43:38.364
HAVE YOU EVER HAD THE FEELING THAT
00:43:38.364 --> 00:43:39.988
YOU SEE THE NAME ON YOUR CALLER
00:43:39.988 --> 00:43:42.145
I. D. AND YOU'RE LIKE, I SHOULD
00:43:42.145 --> 00:43:43.345
NOT ANSWER THIS PHONE CALL. I'M
00:43:43.345 --> 00:43:45.201
HAVING THAT FEELING RIGHT NOW. BUT
00:43:45.201 --> 00:43:47.765
LET'S SEE WHAT SCOTT HAS TO SAY.
00:43:47.765 --> 00:43:50.108
WHAT'S GOING ON, SCOTT? >> HEY.
00:43:50.108 --> 00:43:52.051
HOW'S IT GOING THERE, BUDDY? YOU
00:43:52.051 --> 00:43:53.457
BUSY? >> I'M KIND OF IN THE MIDDLE
00:43:53.457 --> 00:43:54.619
OF SOMETHING, YEAH, ACTUALLY. >>
00:43:54.619 --> 00:43:57.037
NO, NO, YOU GOT TIME FOR THIS. LISTEN,
00:43:57.037 --> 00:44:02.562
I'VE GOT A REALLY IMPORTANT THING
00:44:02.562 --> 00:44:02.934
I GOT TO GO TO NOW.I'VE GOT A GITHUB ISSUE I NEED YOU TO
00:44:02.934 --> 00:44:04.350
TAKE CARE OF. I HAVE BRUNCH WITH
00:44:04.350 --> 00:44:07.213
JAY AND BEY. CAN YOU TAKE CARE OF
00:44:07.213 --> 00:44:09.776
THIS? I SENT YOU A LINK TO THE GITHUB
00:44:09.776 --> 00:44:12.447
ISSUE. >> I APPRECIATE IT, SCOTT.
00:44:12.447 --> 00:44:14.350
THIS IS GOING TO TURN INTO A TEACHABLE
00:44:14.350 --> 00:44:16.028
MOMENT BECAUSE WE'VE ALL BEEN THERE.
00:44:16.028 --> 00:44:17.975
WE'RE WORKING ON ONE THING, THEN
00:44:17.975 --> 00:44:19.144
A CONTEXT SWITCHED TO SOMETHING
00:44:19.144 --> 00:44:20.771
ELSE. THE CONTEXT SWITCH ISN'T THE
00:44:20.771 --> 00:44:22.158
BOTHER. THE BOTHER IS MAKING SURE
00:44:22.158 --> 00:44:23.102
THAT YOUR ENVIRONMENT IS SET UP
00:44:23.102 --> 00:44:24.397
SUCH THAT YOU CAN HELP THE OTHER
00:44:24.397 --> 00:44:25.567
INDIVIDUAL. IT MIGHT BE IN A DIFFERENT
00:44:25.567 --> 00:44:26.603
LANGUAGE IT MIGHT BE ON A DIFFERENT
00:44:26.603 --> 00:44:28.642
PLATFORM. IT MIGHT BE ON A DIFFERENT
00:44:28.642 --> 00:44:29.871
OPERATING SYSTEM. BUT LUCKILY FOR
00:44:29.871 --> 00:44:31.629
ME, I CAN GO AHEAD AND CLICK ON
00:44:31.629 --> 00:44:33.333
THIS ISSUE, JUMP INTO GITHUB, AND
00:44:33.333 --> 00:44:35.044
SEE IF WE CAN GET SOMETHING TO WORK
00:44:35.044 --> 00:44:36.500
HERE. DOWN HERE WE HAVE THIS LINK
00:44:36.500 --> 00:44:39.689
THAT SAYS "VISUAL STUDIO ON LINE.
00:44:39.689 --> 00:44:41.312
" HALF OF YOU ARE HAVING A MOMENT
00:44:41.312 --> 00:44:43.962
SAYING, HEY, I'VE HEARD OF VISUAL
00:44:43.962 --> 00:44:44.732
STUDIO ON LINE BEFORE, AND YOUR
00:44:44.732 --> 00:44:46.382
NEXT THOUGHT IS, DONOVAN, DO NOT
00:44:46.382 --> 00:44:47.721
CLICK THAT, THAT IS NOT WHAT YOU
00:44:47.721 --> 00:44:49.154
THINK IT IS, RIGHT? BUT I'M TELLING
00:44:49.154 --> 00:44:51.192
YOU, WE USE THE EXACT SAME NAME,
00:44:51.192 --> 00:44:52.424
AND IT IS EXACTLY WHAT YOU THINK
00:44:52.424 --> 00:44:54.570
IT IS NOW. WHEN I CLICK ON THIS,
00:44:54.570 --> 00:44:57.037
I AM TAKEN TO AN AREA WHERE I CAN
00:44:57.037 --> 00:44:58.532
SPIN UP AN SBIERP ENVIRONMENT. THAT
00:44:58.532 --> 00:45:00.001
LINK KNOWS EXACTLY WHAT REPOSITORY
00:45:00.001 --> 00:45:01.741
I'M USING, IT KNOWS EXACTLY WHAT
00:45:01.741 --> 00:45:03.353
CODE I NEED TO GET TO. IT TELLS
00:45:03.353 --> 00:45:04.760
ME HOW BIG THE MACHINE NEEDS TO
00:45:04.760 --> 00:45:07.096
BE, AND EVEN WHAT LANGUAGE OR PLATFORM
00:45:07.096 --> 00:45:08.508
THE MACHINE NEEDS TO BE ON. WHEN
00:45:08.508 --> 00:45:10.252
I CLICK ON CREATE, IF GOES OFF AND
00:45:10.252 --> 00:45:11.436
STARTS TO CREATE THIS ENVIRONMENT
00:45:11.436 --> 00:45:13.432
FOR ME IN THE CLOUD. WHEN I'M DONE,
00:45:13.432 --> 00:45:15.508
I THROW IT AWAY. WHEN I NEED IT,
00:45:15.508 --> 00:45:16.865
IT'S THERE FOR ME. I'VE ALREADY
00:45:16.865 --> 00:45:18.405
SPUN ONE OF THEM UP. I WILL COME
00:45:18.405 --> 00:45:20.684
OVER HERE AND FIRE IT UP FOR YOU.
00:45:20.684 --> 00:45:22.774
NOW THIS JUST ISN'T AN ENVIRONMENT,
00:45:22.774 --> 00:45:22.775
THIS IS NOW MY ENVIRONMENT. ALL
00:45:22.775 --> 00:45:26.561
OF MY SETTINGS HAVE ROAMED WITH
00:45:26.561 --> 00:45:30.077
ME. MY KEYBOARD SHORT CUTS, THE
00:45:30.077 --> 00:45:31.745
CUSTOMIZATION INSIDE OF THE TERMINAL.
00:45:31.745 --> 00:45:33.151
THE COLOR SCHEME I USE INSIDE OFTHE I.
00:45:33.151 --> 00:45:34.619
D. , THIS FEELS LIKE HOME TO ME.
00:45:34.619 --> 00:45:36.154
AND I CAN INSTANTLY START GETTING
00:45:36.154 --> 00:45:38.360
READY TO HELP THIS INDIVIDUAL WITH
00:45:38.360 --> 00:45:39.306
THEIR WORK. WHAT I WANT TO DO IS
00:45:39.306 --> 00:45:40.867
GO DOWN, I THINK THE PROBLEM IS
00:45:40.867 --> 00:45:42.285
PROBABLY GOING TO BE OVER HERE.
00:45:42.285 --> 00:45:44.781
I-95 WORKED WITH SCOTT BEFORE. AND
00:45:44.781 --> 00:45:46.851
I'M GOING TO PRESS F5. THINK WITH
00:45:46.851 --> 00:45:48.163
B WHAT HAPPENED. I'M USING A MACHINE
00:45:48.163 --> 00:45:49.574
THAT'S OUT IN THE CLOUD, BUT I'M
00:45:49.574 --> 00:45:51.067
TRYING TO DEBUG IT HERE LOCALLY.
00:45:51.067 --> 00:45:52.809
IF I COME AND CLICK ON THIS LINK
00:45:52.809 --> 00:45:54.289
HERE, WHAT SHOULD HAPPEN IS IT'S
00:45:54.289 --> 00:45:56.623
GOING TO START TO REDIRECT ME, FIGURE
00:45:56.623 --> 00:45:58.711
OUT ALL THE NETWORK CONFIGURATION
00:45:58.711 --> 00:46:01.165
NECESSARY, RUN IT IN THE CLOUD BUT
00:46:01.165 --> 00:46:02.847
LET ME DEBUG THIS ITEM LOCALLY.
00:46:02.847 --> 00:46:04.077
THE ISSUE SAYS WHEN YOU RUN THIS
00:46:04.077 --> 00:46:05.709
PARTICULAR API YOU'RE NOT GETTING
00:46:05.709 --> 00:46:07.127
ANY OF THE RESULTS BACK. IF I COME
00:46:07.127 --> 00:46:09.189
BACK OVER HERE, YOU'LL NOTICE I'VE
00:46:09.189 --> 00:46:10.762
ALREADY HIT THE BREAK POINT. IF
00:46:10.762 --> 00:46:12.393
IT'S WIRED UP FOR ME, I'VE HIT THE
00:46:12.393 --> 00:46:13.817
BREAK POINT, LET'S LOOK AROUND HERE
00:46:13.817 --> 00:46:17.493
QUICK. THIS SAYS IT'S NONE FOR F10
00:46:17.493 --> 00:46:18.941
PASS THIS, THEN I'M GOING TO QUERY
00:46:18.941 --> 00:46:20.295
-- THIS DOESN'T MAKE SENSE. WHY
00:46:20.295 --> 00:46:22.574
WOULD I CHECK THAT IT'S NONE AND
00:46:22.574 --> 00:46:24.552
FILTER MY LIFE AGAINST NONE? LET'S
00:46:24.552 --> 00:46:26.670
LET THIS RUN THROUGH. AS YOU SEE,
00:46:26.670 --> 00:46:27.876
WE HAVE NO RESULTS COMING BACK.
00:46:27.876 --> 00:46:29.541
WHAT I THINK THIS NEEDS TO BE IS
00:46:29.541 --> 00:46:36.554
NOT NONE. LET'S PUT NOT HERE INSTEAD.
00:46:36.554 --> 00:46:36.769
LET'S GO AHEAD AND SAVE THIS.I'M GOING TO SAVE THIS
00:46:36.769 --> 00:46:39.622
OFF. NOT NONE. GOOD. RESTART MY
00:46:39.622 --> 00:46:41.472
DEBUG SESSION. COME BACK AND PRESS
00:46:41.472 --> 00:46:43.191
F5. WHAT WE SHOULD SEE NOW IS I
00:46:43.191 --> 00:46:46.292
WAS ABLE TO USE THAT ENVIRONMENT,
00:46:46.292 --> 00:46:47.205
REHIT THIS PARTICULAR ENVIRONMENT
00:46:47.205 --> 00:46:48.811
HERE, AND IT SHOULD COME BACK IN
00:46:48.811 --> 00:46:50.350
AND SHOW ME THAT I WAS ABLE TO MAKE
00:46:50.350 --> 00:46:51.712
THE CORRECTION. IT'S NOT GOING TO
00:46:51.712 --> 00:46:53.749
POP UP HERE --A WE'LL START ANOTHER
00:46:53.749 --> 00:46:55.585
ONE. LET ME CLICK THIS LINK AND
00:46:55.585 --> 00:46:56.866
SEE WHAT HAPPENS INSTEAD. IT'S SPINNING
00:46:56.866 --> 00:46:59.350
UP IN THE BACKGROUNDS, USING RESOURCES,
00:46:59.350 --> 00:47:01.099
AND BOOM, WE HAVE THIS ENORMOUS
00:47:01.099 --> 00:47:02.553
AMOUNT OF JAYSON COMING BACK WHICH
00:47:02.553 --> 00:47:04.753
MEANS I WAS ABLE TO GO IN AND QUICKLY
00:47:04.753 --> 00:47:05.705
FIX A PROBLEM ON AN ENVIRONMENT
00:47:05.705 --> 00:47:07.985
THAT I DID NOT HAVE TO SET UP. THAT
00:47:07.985 --> 00:47:09.469
SAVED ME HOURS POTENTIALLY OF TRYING
00:47:09.469 --> 00:47:11.149
TO MAKE SURE THAT I HAD THE RIGHT
00:47:11.149 --> 00:47:12.641
OPERATING SYSTEM, THE RIGHT PACKAGES,
00:47:12.641 --> 00:47:15.291
THE RIGHT VERSIONS OF EVERYTHING.
00:47:15.291 --> 00:47:16.764
MICROSOFT WAS A COMPANY CREATED
00:47:16.764 --> 00:47:18.225
BY DEVELOPERS. AS YOU CAN SEE WITH
00:47:18.225 --> 00:47:19.830
OUR INVESTMENTS IN THE TERMINAL,
00:47:19.830 --> 00:47:21.306
INSIDE OF VISUAL STUDIO ON LINE,
00:47:21.306 --> 00:47:24.181
WE ARE STILL OBSESSED WITH DEVELOPERS.
00:47:24.181 --> 00:47:25.420
WE WANT TO MAKE SURE THAT EVERYBODY,
00:47:25.420 --> 00:47:27.040
NO MATTER WHAT LANGUAGE YOU PROGRAM
00:47:27.040 --> 00:47:28.940
IN OR PLATFORM THAT YOU TARGET OR
00:47:28.940 --> 00:47:30.825
R ABLE TO DO YOUR BEST WORK. THANK
00:47:30.825 --> 00:47:42.729
YOU SO MUCH, EVERYONE. >> THANKS.
00:47:42.729 --> 00:47:43.978
I THINK THEY NEED TO INVITE YOU
00:47:43.978 --> 00:47:46.276
TO THAT LUNCH, MAN. IF GIVES YOU
00:47:46.276 --> 00:47:47.340
AN GOOD OPPORTUNITY TO HAVE THE
00:47:47.340 --> 00:47:50.953
COLLABORATION. AS WE CONTINUE OUR
00:47:50.953 --> 00:47:52.238
JOURNEY HERE THROUGH CLOUD DATA
00:47:52.238 --> 00:47:55.533
APPLICATION, I WANT TO TALK ABOUT
00:47:55.533 --> 00:47:57.136
AZURE SERVERLESS. YOU WANT TO FOCUS
00:47:57.136 --> 00:47:58.555
ON THE APPS AND NOT THE INFRASTRUCTURE.
00:47:58.555 --> 00:48:00.477
LET US DEAL WITH DYNAMIC SCALE,
00:48:00.477 --> 00:48:02.003
LET YOU GO FASTER AND MAKE BETTER
00:48:02.003 --> 00:48:03.851
USE OF YOUR RESOURCES. WE'VE CREATED
00:48:03.851 --> 00:48:05.997
A BROAD SET OF AZURE SERVERLESS
00:48:05.997 --> 00:48:08.685
COMPUTE SOLUTIONS. IT STARTS OFF
00:48:08.685 --> 00:48:11.051
WITH THE APP SERVICE WHERE I CAN
00:48:11.051 --> 00:48:13.011
HOST WEBSITES IN ADDITION TO MOBILE
00:48:13.011 --> 00:48:14.569
APPLICATIONS. WE CAN ALSO MOVE TO
00:48:14.569 --> 00:48:15.561
AZURE FUNCTIONS. THIS IS WHERE YOU
00:48:15.561 --> 00:48:17.621
WANT TO FOCUS ON YOUR CODE. AND
00:48:17.621 --> 00:48:19.650
THE BUSINESS LOGIC AND NOT ON THE
00:48:19.650 --> 00:48:21.765
PLUMBING. AFTER ALL, AS A DEVELOPER,
00:48:21.765 --> 00:48:23.010
ONLY YOU CAN WRITE THE CODE THAT
00:48:23.010 --> 00:48:26.072
YOU CAN WRITE. SO LET'S MAKE SURE
00:48:26.072 --> 00:48:27.397
YOU CAN CONCENTRATE AND FOCUS ON
00:48:27.397 --> 00:48:29.685
THAT. I FOLLOWED IT UP WITH AZURE
00:48:29.685 --> 00:48:32.908
KUBERNETES SERVICE, AKS, TO FULLY
00:48:32.908 --> 00:48:33.947
MALL MANAGED CONTAINER ORCHESTRATION
00:48:33.947 --> 00:48:36.133
FOR YOUR WORKLOADS. WE'LL TAKE CARE
00:48:36.133 --> 00:48:37.518
OF OPERATING AND MONITORING AND
00:48:37.518 --> 00:48:38.136
MAINTAINING THE SYSTEMS. YOU DON'T
00:48:38.136 --> 00:48:40.645
HAVE TO WORRY ABOUT DOWNTIME. NOW,
00:48:40.645 --> 00:48:43.250
AKS ITSELF HAS BEEN THE FASTEST
00:48:43.250 --> 00:48:44.422
GROWING AZURE COMPUTE SERVICE THAT
00:48:44.422 --> 00:48:45.986
WE'VE HAD, AND YOU CAN SEE MANY
00:48:45.986 --> 00:48:48.293
CUSTOMER THAT'S HAVE TAKEN A BET
00:48:48.293 --> 00:48:50.948
ON AKS. IT CONTINUES TO GROW AS
00:48:50.948 --> 00:48:52.960
WE ADD NEW FUNCTIONALITY, IN PARTICULAR
00:48:52.960 --> 00:48:55.394
WE'RE VERY PLEASED TO ANNOUNCE THAT
00:48:55.394 --> 00:48:57.284
GENERAL AVAILABILITY OF -- AVAILABILITY
00:48:57.284 --> 00:49:00.202
ZONE SUPPORT, AUTO SCALING, MULTIPLE
00:49:00.202 --> 00:49:02.035
NODE POOLS, WE'RE INTRODUCING THE
00:49:02.035 --> 00:49:04.895
PREVIEW OF DEV SPACES TO BE ABLE
00:49:04.895 --> 00:49:05.344
TO DEVELOP AND TEST LOCALLY. AND
00:49:05.344 --> 00:49:07.289
IN ADDITION TO THE PREVIEW FOR AZURE
00:49:07.289 --> 00:49:09.645
SECURITY CENTER, THEY GIVE US FULL
00:49:09.645 --> 00:49:11.929
INTEGRATION FOR AKS. SO IT REALLY
00:49:11.929 --> 00:49:13.832
IS THE BEST KUBE ENVIRONMENT THAT
00:49:13.832 --> 00:49:15.641
YOU CAN RUN ON TODAY. IF YOU LOOK
00:49:15.641 --> 00:49:17.277
AT ALL OF THESE EXAMPLES WE'VE SHOWN,
00:49:17.277 --> 00:49:19.159
ALL OF THIS HARDWARE ON THE EDGE,
00:49:19.159 --> 00:49:21.189
THE WORK FLOW, THE TOOLS, THE THINGS
00:49:21.189 --> 00:49:23.280
WE CAN PULL TOGETHER, THERE'S SOME
00:49:23.280 --> 00:49:24.269
FANTASTIC EXAMPLES OF WHAT I CAN
00:49:24.269 --> 00:49:27.035
DO WITH THAT TAG. NOW ONE OF THE
00:49:27.035 --> 00:49:29.041
BEST EXAMPLES THAT WE HAVE IS WITH
00:49:29.041 --> 00:49:33.708
IOT. LET'S LOOK AT SOME OF THOSE
00:49:33.708 --> 00:50:05.622
EXAMPLES. [ MUSIC ] [ MUSIC ] [
00:50:05.622 --> 00:50:27.783
MUSIC ] >> NOW AZURE'S THE UNDISPUTED
00:50:27.783 --> 00:50:29.617
LEADER IN IOT WHEN IT COMES TO THE
00:50:29.617 --> 00:50:32.053
CLOUD. WE'VE BEEN INVESTING OVER
00:50:32.053 --> 00:50:34.774
$5 BILLION IN OUR IOT ECOSYSTEM
00:50:34.774 --> 00:50:36.991
FROM PRODUCTS AND INTO OUR PARTNER
00:50:36.991 --> 00:50:38.179
ECOSYSTEM. AS YOU SAW WE'VE GOT
00:50:38.179 --> 00:50:39.551
THOUSANDS OF DEVICES FROM VIRTUALLY
00:50:39.551 --> 00:50:42.338
EVERY INDUSTRY OUT THERE THAT IS
00:50:42.338 --> 00:50:43.405
CONNECTED WITH AZURE. WE'RE WORKING
00:50:43.405 --> 00:50:45.447
HARD WITH OUR PARTNERS, AS WELL,
00:50:45.447 --> 00:50:47.014
TO EMPOWER CUSTOMERS TO GIVE YOU
00:50:47.014 --> 00:50:48.464
THAT IMPORTANT DEVICE INSIGHTS.
00:50:48.464 --> 00:50:50.847
WE REALLY WANT TO HELP YOU TRANSFORM
00:50:50.847 --> 00:50:53.551
THOSE BUSINESS PRACTICES. THERE'S
00:50:53.551 --> 00:50:55.376
ALSO THOUSANDS OF AZURE IOT CUSTOMERS
00:50:55.376 --> 00:50:56.942
OUT THERE ACROSS MANY, MANY INDUSTRIES.
00:50:56.942 --> 00:50:59.374
FROM, FOR EXAMPLE, BUHLER, MAKING
00:50:59.374 --> 00:51:00.752
SUPPLY CHAIN SAFER FOR THE FOOD
00:51:00.752 --> 00:51:03.973
THAT WE EAT. SO ROLLS ROYCE IN THE
00:51:03.973 --> 00:51:05.321
VIDEO, JET FUEL EFFICIENCY AND BEING
00:51:05.321 --> 00:51:07.518
ABLE TO FIGURE OUT HOW TO HELP AIRLINES
00:51:07.518 --> 00:51:09.391
OPERATE AT THE BEST COST POSSIBLE.
00:51:09.391 --> 00:51:11.574
AS WELL AS STARBUCKS, THINK ABOUT
00:51:11.574 --> 00:51:13.064
PREDICTABLE MAINTENANCE ON EQUIPMENT
00:51:13.064 --> 00:51:15.280
THAT WILL HELP PARTNERS IN THE STORE
00:51:15.280 --> 00:51:16.394
AND CUSTOMERS TO MAKE SURE THEY
00:51:16.394 --> 00:51:22.915
HAVE A FANTASTIC EXPERIENCE. WE
00:51:22.915 --> 00:51:24.792
DESIGNED AZURE IOT TO HELP TRANSFORM
00:51:24.792 --> 00:51:26.825
YOUR BUSINESS. WE WANTED TO MAKE
00:51:26.825 --> 00:51:30.707
SURE IT WAS A COMPREHENSIVE SECLUSION,
00:51:30.707 --> 00:51:32.578
NEEDS TO BE SECURE. WITH THAT WE'VE
00:51:32.578 --> 00:51:33.960
INTRODUCED THIS INDUSTRY LEADING
00:51:33.960 --> 00:51:35.099
SET OF PRODUCTS AND SOLUTIONS HERE
00:51:35.099 --> 00:51:37.755
FROM EDGE TO THE CLOUD. THE COOL
00:51:37.755 --> 00:51:40.521
THING ABOUT THIS, AND FOR THOSE OF YOU THAT
00:51:40.521 --> 00:51:42.412
ARE ARCHITECTS AND DEVELOPERS, WE
00:51:42.412 --> 00:51:43.946
DESIGNED THIS THING IN A LAYERED
00:51:43.946 --> 00:51:45.765
FASHION ON PURPOSE. IT BASICALLY
00:51:45.765 --> 00:51:47.517
MEANS THAT YOU CAN ENGAGE THE PORTFOLIO
00:51:47.517 --> 00:51:48.970
WHERE IT MAKES SENSE. I CAN START
00:51:48.970 --> 00:51:50.419
OFF WITH INFRASTRUCTURE IF I WANT,
00:51:50.419 --> 00:51:52.245
I CAN MOVE UP AND LEVERAGE THINGS
00:51:52.245 --> 00:51:54.489
LIKE TIME SERIES OR DIGITAL TWINS
00:51:54.489 --> 00:51:56.376
AS TECHNOLOGY THAT'S JUST BUILT
00:51:56.376 --> 00:51:58.204
IN AT THE LAYER OR GO INTO FULLY
00:51:58.204 --> 00:52:00.801
MANAGED SAS SERVICES THAT JUST GIVE
00:52:00.801 --> 00:52:02.296
ME THOSE SOLUTIONS. AND THE COOL
00:52:02.296 --> 00:52:04.048
THING IS ONCE YOU GET INTO THE SAS
00:52:04.048 --> 00:52:07.146
SOLUTION, IF YOU NEED TO DROP DOWN
00:52:07.146 --> 00:52:10.246
INTO THE P PAS MODE AND ADD POWER,
00:52:10.246 --> 00:52:11.933
COMPUTE, MORE A. I. OF YOUR OWN,
00:52:11.933 --> 00:52:13.333
YOU CAN ABSOLUTELY DO THAT. YOU
00:52:13.333 --> 00:52:14.738
DON'T HAVE TO REWRITE YOUR ASSETS.
00:52:14.738 --> 00:52:17.070
WE FINALLY DELIVERED ENTERPRISE-READY
00:52:17.070 --> 00:52:17.966
INDUSTRY SOLUTION ACTION ASSEMBLY
00:52:17.966 --> 00:52:19.832
RARITIES THINGS LIKE FOR FUNDING
00:52:19.832 --> 00:52:21.985
TREES, FOR EXAMPLE, THAT A LOU YOU
00:52:21.985 --> 00:52:23.954
TO GET GOING -- ALLOW YOU TO GET
00:52:23.954 --> 00:52:25.981
GOING AS FAST AS POSSIBLE. SPEAKING
00:52:25.981 --> 00:52:27.349
OF TIME VALUE WE INTRODUCED THE
00:52:27.349 --> 00:52:29.291
SOLUTION HERE, THE FIRST IN THE
00:52:29.291 --> 00:52:32.753
IOT SPACE. AZURE IOT CENTRAL. IOT
00:52:32.753 --> 00:52:34.736
CENTRAL TREATS THINGS LIKE CRM TREATS
00:52:34.736 --> 00:52:36.177
CUSTOMERS. IT MAKES IT SUPER EASY
00:52:36.177 --> 00:52:38.733
TO GET UP AND RUNNING WHEN IT STARTED.
00:52:38.733 --> 00:52:40.306
PART OF THE QUICKNESS WE HAVE IS
00:52:40.306 --> 00:52:42.192
WITH AZURE IOT PLUG AND PLAY. A
00:52:42.192 --> 00:52:43.656
PLUG AND PLAY STANDARD THAT WE ARE
00:52:43.656 --> 00:52:44.931
PUSHING OUT FOR THE INDUSTRY TO
00:52:44.931 --> 00:52:46.644
BE ABLE TO LEVERAGE. WE'RE ALL FAMILIAR
00:52:46.644 --> 00:52:49.165
WITH BEING ABLE TO ADD DEVICES AND
00:52:49.165 --> 00:52:50.682
PERIPHERAL INTO OUR P. C. S. IMAGINE
00:52:50.682 --> 00:52:52.779
BEING ABLE TO DO THE SAME THING
00:52:52.779 --> 00:52:54.658
WITH IOT DEVICES IN THE ECOSYSTEM.
00:52:54.658 --> 00:52:54.659
AND AGAIN HAVING THE INDUSTRY SOLUTIONS
00:52:54.659 --> 00:52:58.296
ALLOWS ME TO GET UP AND RUNNING
00:52:58.296 --> 00:53:01.522
AS FAST AS POSSIBLE. WE'VE TALKED
00:53:01.522 --> 00:53:03.087
A LOT ABOUT SECURITY. THAT'S SUPER,
00:53:03.087 --> 00:53:04.610
SUPER IMPORTANT. SO WE'VE ALSO WANTED
00:53:04.610 --> 00:53:05.982
TO MAKE SURE THAT WE PUT SECURITY
00:53:05.982 --> 00:53:08.745
INTO ALL OF THIS. WE START OFF WITH
00:53:08.745 --> 00:53:11.151
AZURE SPHERE. SILICON THAT WE'VE
00:53:11.151 --> 00:53:12.063
LITERALLY DESIGNED WITH SECURITY
00:53:12.063 --> 00:53:13.765
BUILT IN. IT'S DESIGNED TO MAKE
00:53:13.765 --> 00:53:15.198
SURE THAT YOU'RE ALWAYS UP TO DATE
00:53:15.198 --> 00:53:16.503
WITH YOUR PATCHES. YOU CAN MAKE
00:53:16.503 --> 00:53:18.005
SURE THAT WE'RE NOT GOING TO HAVE,
00:53:18.005 --> 00:53:19.635
YOU KNOW, THIS PROBABILITY OF GETTING
00:53:19.635 --> 00:53:21.383
HACKED BECAUSE WE'RE OUT OF DATE.
00:53:21.383 --> 00:53:24.250
WE'VE ALSO TEND ITTED AZURE STUART
00:53:24.250 --> 00:53:26.161
-- ALSO SECURED AZURE SECURITY CENTER
00:53:26.161 --> 00:53:28.618
NOW OFF TO THE IOT ENVIRONMENTS.
00:53:28.618 --> 00:53:30.080
AND WE'VE EXTENDED AZURE SENTINEL,
00:53:30.080 --> 00:53:32.938
AS WELL. I CAN HUNT TO OR RESPOND
00:53:32.938 --> 00:53:34.452
FOR ACTIVE THREATS SPANNING THE
00:53:34.452 --> 00:53:35.596
ENTIRE ENTERPRISE, THAT INCLUDES
00:53:35.596 --> 00:53:38.094
NOT ONLY THE EDGE, BUT ALSO YOUR
00:53:38.094 --> 00:53:39.742
ON-PREMISES SOLUTIONS THAT YOU HAVE
00:53:39.742 --> 00:53:43.211
AND THE CLOUD. I CAN SEE THE ENTIRE
00:53:43.211 --> 00:53:45.160
THING FROM END TO END. WE'RE VERY
00:53:45.160 --> 00:53:47.425
PLEASED TO ANNOUNCE TODAY THAT WE'RE
00:53:47.425 --> 00:53:49.873
GOING TO PREVIEW WITH FARM BEATS.
00:53:49.873 --> 00:53:51.836
FARM BEATS IS AN END-TO-END SOLUTION
00:53:51.836 --> 00:53:53.939
THAT WE'VE PRODUCED IN THE AGRICULTURE
00:53:53.939 --> 00:53:55.950
SPACE. THIS IS ACTUALLY SUPER IMPORTANT.
00:53:55.950 --> 00:53:57.281
FOR ONE THING, IT IS ACTUALLY A
00:53:57.281 --> 00:54:00.228
GREAT WAY TO SHOW HOW ALL OF THIS
00:54:00.228 --> 00:54:01.485
TECHNOLOGY COMES TOGETHER. MORE
00:54:01.485 --> 00:54:03.672
IMPORTANTLY IN THIS SPACE, BY 2050,
00:54:03.672 --> 00:54:04.741
WE'RE EXPECTING THAT WE'RE GOING
00:54:04.741 --> 00:54:07.535
TO NEED ABOUT 70 MORE FOOD TO FEED
00:54:07.535 --> 00:54:10.037
THE PEOPLE ON THE PLANET. AND OVER
00:54:10.037 --> 00:54:12.269
HALF OF THE WORLD'S FRESH WATER
00:54:12.269 --> 00:54:15.292
WILL BE LEVERAGED FOR AGRICULTURE.
00:54:15.292 --> 00:54:16.609
NOW WE HAVE SCARCE RESOURCES THERE.
00:54:16.609 --> 00:54:18.505
THE WATER IS SCARCE, THE LAND THAT
00:54:18.505 --> 00:54:20.014
WE CAN FARM ON IS ALSO SCARE. WE
00:54:20.014 --> 00:54:21.856
HAVE TO MAKE SURE THAT WE'RE DOING
00:54:21.856 --> 00:54:23.983
A GOOD JOB. WE BELIEVE THAT BRINGING
00:54:23.983 --> 00:54:26.014
TECHNOLOGIES TO BEAR AND PRECISION
00:54:26.014 --> 00:54:27.436
AGRICULTURE IS GOING TO BE A GREAT
00:54:27.436 --> 00:54:29.575
WAY FOR US TO HELP OUT WITH THAT.
00:54:29.575 --> 00:54:31.707
SO I WANT TO SEND IT BACK OVER TO
00:54:31.707 --> 00:54:33.125
THE SHOW BECAUSE WE'VE GOT FARM
00:54:33.125 --> 00:54:34.817
BEATS SET UP AND READY TO GO. I'M
00:54:34.817 --> 00:54:36.724
GOING TO HAND IT OVER TO JEFF. JEFF,
00:54:36.724 --> 00:54:39.361
SHOW US THE DEMO. >> WHAT IS UP,
00:54:39.361 --> 00:54:42.103
EVERYONE? I AM HAVING A BLAST HERE
00:54:42.103 --> 00:54:44.533
AT THE FARM BEATS STATION. AND I'M
00:54:44.533 --> 00:54:45.921
ACTUALLY PROUD TO SHOW YOU ALL SOME
00:54:45.921 --> 00:54:47.973
OF THE TECHNOLOGY HERE ABOUT HOW
00:54:47.973 --> 00:54:49.247
MICROSOFT IS HELPING SOLVE SOME
00:54:49.247 --> 00:54:51.421
OF THE WORLD'S TOUGHEST PROBLEMS.
00:54:51.421 --> 00:54:55.381
LET ME GET DOWN HERE FROM MY TRACTOR.
00:54:55.381 --> 00:54:59.063
BY -- UH-OH. BY 2050, IT'S ESTIMATED
00:54:59.063 --> 00:55:01.810
THAT THE WORLD WILL NEED TO PRODUCE
00:55:01.810 --> 00:55:03.581
70 MORE FOOD THAN WE ARE. WHICH
00:55:03.581 --> 00:55:07.544
IS A DAUNTING TASK BECAUSE THE AMOUNT
00:55:07.544 --> 00:55:11.259
OF AERATABLE LAND WE HAVE IS DECREASING.
00:55:11.259 --> 00:55:12.820
FARMERS WILL NEED TO FIND NEW WAYS
00:55:12.820 --> 00:55:14.690
TO PRODUCE A LARGER CROP. ONE OF
00:55:14.690 --> 00:55:16.532
THE WAYS THIS WILL BE MADE POSSIBLE
00:55:16.532 --> 00:55:19.113
IS THROUGH DATA FROM IOT DEVICES
00:55:19.113 --> 00:55:20.777
LIKE THIS ONE. I CAN USE THIS SENSOR
00:55:20.777 --> 00:55:22.568
TO ASSESS THE HEALTH AND THE MOISTURE
00:55:22.568 --> 00:55:25.171
OF THE SOIL. BUT THERE'S A FEW CHALLENGES
00:55:25.171 --> 00:55:26.789
THAT COME WHEN IMPLEMENTING A SOLUTION
00:55:26.789 --> 00:55:29.655
LIKE THIS AT SCALE. ONE OF THEM
00:55:29.655 --> 00:55:31.165
IS COST. IN ORDER TO HAVE ENOUGH
00:55:31.165 --> 00:55:33.480
SENSORS TO FILL UP AN ENTIRE FARM
00:55:33.480 --> 00:55:35.793
CAN COST TENS OF THOUSANDS OF DOLLARS
00:55:35.793 --> 00:55:37.317
WHICH IS AN INVESTMENT THAT'S OUT
00:55:37.317 --> 00:55:39.939
OF REACH FOR MUCH OF THE WORLD.
00:55:39.939 --> 00:55:41.653
SO FARM BEATS HAS PROVIDED A SOLUTION
00:55:41.653 --> 00:55:43.538
THAT INSTEAD OF REQUIRING HUNDREDS
00:55:43.538 --> 00:55:45.840
OF SENSORS, I ONLY NEED A FEW. BUT
00:55:45.840 --> 00:55:48.410
I USE THE DATA FROM THAT SAMPLE,
00:55:48.410 --> 00:55:49.961
AND I COMBINE IT WITH MACHINE LEARNING
00:55:49.961 --> 00:55:51.366
TO GIVE ME AN ACCURATE PICTURE OF
00:55:51.366 --> 00:55:53.293
THE ENTIRE FARM. SO LET'S CHECK
00:55:53.293 --> 00:55:55.955
IT OUT NOW. I'M SHOWING HERE A FARM
00:55:55.955 --> 00:55:57.603
BEATS DASHBOARD. YOU CAN SEE THIS
00:55:57.603 --> 00:55:59.658
IS ONE OF OUR FARMS. I ONLY HAVE
00:55:59.658 --> 00:56:01.588
A FEW DEVICES HERE THAT WE'VE ADDED.
00:56:01.588 --> 00:56:04.453
WHEN I COMBINE THE DATA FROM THOSE
00:56:04.453 --> 00:56:07.137
FEW DEVICES WITH AERIAL AND SATELLITE
00:56:07.137 --> 00:56:09.337
IMAGING, I CAN RUN IT THROUGH MACHINE
00:56:09.337 --> 00:56:11.716
LEARNING AND GET A HEAT MAP OF THE
00:56:11.716 --> 00:56:14.269
ENTIRE FARM. NOW I HAVE DATA FOR
00:56:14.269 --> 00:56:15.919
MY ENTIRE FARM REGARDLESS OF THE
00:56:15.919 --> 00:56:18.793
SIZE. AND THIS TYPE OF INNOVATION
00:56:18.793 --> 00:56:20.289
MAKES IOT MORE ECONOMICAL FOR THESE
00:56:20.289 --> 00:56:22.650
TYPES OF FARMING SCENARIOS. BUT
00:56:22.650 --> 00:56:23.982
THERE'S ANOTHER CHALLENGE THAT I
00:56:23.982 --> 00:56:26.455
HAVE WHEN I'M DEALING WITH IOT AND
00:56:26.455 --> 00:56:27.802
REALLY ANY INDUSTRY, AND THAT'S
00:56:27.802 --> 00:56:30.001
AS I'M USING IOT I'M LIKELY GOING
00:56:30.001 --> 00:56:32.142
TO HAVE A NUMBER OF DIFFERENT DEVICES,
00:56:32.142 --> 00:56:35.567
EACH ONE OF THESE DEVICES FROM A
00:56:35.567 --> 00:56:36.156
DIFFERENT MANUFACTURER, IT SENDS
00:56:36.156 --> 00:56:37.565
DATA IN DIFFERENT WAYS IT HAS DIFFERENT
00:56:37.565 --> 00:56:40.152
TYPES OF DATA. I CONNECT TO IT DIFFERENTLY.
00:56:40.152 --> 00:56:41.808
IT'S REALLY CHALLENGING TO START
00:56:41.808 --> 00:56:43.738
TO ON-BOARD AND INTEGRATE ALL THESE
00:56:43.738 --> 00:56:45.744
DEVICES AT SCALE WITH MY APPLICATION.
00:56:45.744 --> 00:56:47.637
AND THAT'S WHERE I CAN START TO
00:56:47.637 --> 00:56:50.261
USE AZURE IOT CENTRAL WITH IOT PLUG
00:56:50.261 --> 00:56:54.283
AND PLAY. SO IOT CENTRAL IS A SINGLE
00:56:54.283 --> 00:56:56.552
SOLUTIONS PLATFORM FOR EVERY IOT
00:56:56.552 --> 00:56:59.147
PROJECT, FARMING, HEALTH CARE, MANUFACTURING.
00:56:59.147 --> 00:57:01.177
A SINGLE SPOT THAT I CAN MANAGE
00:57:01.177 --> 00:57:02.963
AND MONITOR MY DEVICES. AND WITH
00:57:02.963 --> 00:57:05.816
IOT PLUG AND PLAY, THESE DEVICES
00:57:05.816 --> 00:57:07.920
CAN ACTUALLY REGISTER THEMSELVES
00:57:07.920 --> 00:57:09.533
AND INTEGRATE THEIR APP -- INTEGRATE
00:57:09.533 --> 00:57:11.231
THEIR DATA WITH MY APP. SO I WANT
00:57:11.231 --> 00:57:13.566
TO SHOW YOU THAT NOW. LET'S GO AHEAD
00:57:13.566 --> 00:57:16.195
HERE AND SWITCH BACK TO OUR IOT
00:57:16.195 --> 00:57:18.230
CENTRAL DASHBOARD. SO I ALREADY
00:57:18.230 --> 00:57:20.761
HAVE A FEW DEVICES THAT I'VE ON-BOARDED,
00:57:20.761 --> 00:57:22.481
IN THIS CASE FOR MY FARM, YOU CAN
00:57:22.481 --> 00:57:24.718
SEE HERE I HAVE SOME SIMPLE SOIL
00:57:24.718 --> 00:57:26.524
SENSORS AND A GATEWAY THAT I CAN
00:57:26.524 --> 00:57:28.664
MANAGE HERE IN IOT CENTRAL. BUT
00:57:28.664 --> 00:57:31.135
NOW I HAVE A BRAND-NEW DEVICE. THIS
00:57:31.135 --> 00:57:32.692
IS A DEVICE FROM A MANUFACTURER
00:57:32.692 --> 00:57:34.788
THAT I HAVEN'T YET ADDED TO MY SOLUTION,
00:57:34.788 --> 00:57:37.498
I KNOW IT HAS SOME TEMPERATURE AND
00:57:37.498 --> 00:57:39.535
HUMIDITY SENSORS, BUT I DON'T QUITE
00:57:39.535 --> 00:57:42.203
KNOW HOW TO CONNECT TO IT. I DON'T
00:57:42.203 --> 00:57:43.113
KNOW THE FORMAT OF THE DATA THAT'S
00:57:43.113 --> 00:57:44.724
GOING TO BE COMING IN. I DON'T HAVE
00:57:44.724 --> 00:57:46.481
TO WORRY ABOUT THAT WITH IOT PLUG
00:57:46.481 --> 00:57:48.737
AND PLAY. IN FACT, ALL THAT I HAVE
00:57:48.737 --> 00:57:52.180
TO DO IS POWER ON THE DEVICE. SO
00:57:52.180 --> 00:57:54.572
LET ME DO THAT NOW. AND WHAT'S HAPPENING,
00:57:54.572 --> 00:57:58.033
AS THIS DEVICE IS POWERING ON, IT'S
00:57:58.033 --> 00:58:00.768
CONNECTING SECURELY TO MY IOT CENTRAL
00:58:00.768 --> 00:58:02.412
APP. IT'S LETTING IOT CENTRAL KNOW
00:58:02.412 --> 00:58:03.668
ABOUT THE TYPE OF DEVICE THAT IT
00:58:03.668 --> 00:58:05.496
IS. THINK ABOUT HOW IT CAN TAKE
00:58:05.496 --> 00:58:07.444
ANY PRINTER, PLUG IT INTO A WINDOWS
00:58:07.444 --> 00:58:09.304
MACHINE, AND WINDOWS PLUG AND PLAY
00:58:09.304 --> 00:58:11.415
MEANS THAT THE DRIVERS AND EVERYTHING
00:58:11.415 --> 00:58:13.013
GETS CONFIGURED FOR ME. IOT PLUG
00:58:13.013 --> 00:58:15.075
AND PLAY IS DOING THE SAIL THING.
00:58:15.075 --> 00:58:17.426
THE DWIGHT IS SAYING, HEY -- DEVICE
00:58:17.426 --> 00:58:19.496
IS SAYING, HEY, THIS IS MY DEVICE
00:58:19.496 --> 00:58:20.323
CAPABILITY MODEL. THESE ARE THE
00:58:20.323 --> 00:58:21.614
SENSORS THAT I HAVE, TEMPERATURE,
00:58:21.614 --> 00:58:22.889
HUMIDITY, THIS IS THE FORMAT OF
00:58:22.889 --> 00:58:24.262
THE DATA THAT'S GOING TO BE FLOWING
00:58:24.262 --> 00:58:28.452
IN. IN FACT, WITH IOT CENTRAL, MANUFACTURERS
00:58:28.452 --> 00:58:30.808
CAN EVEN REGISTER THEIR DEVICE WITH
00:58:30.808 --> 00:58:33.146
THE IOT PLUG AND PLAY GALLERY. SO
00:58:33.146 --> 00:58:35.105
THESE DEVICES ARE EXTREMELY DISCOVERABLE,
00:58:35.105 --> 00:58:37.695
BUT I CAN ALSO INCLUDE WITH THEM
00:58:37.695 --> 00:58:41.494
PACKAGE DASHBOARDS. SO I CAN IMMEDIATELY
00:58:41.494 --> 00:58:44.360
START TO VISUALIZE AND PLAY WITH
00:58:44.360 --> 00:58:45.956
THAT DATA. THE RESULT IS WHEN I
00:58:45.956 --> 00:58:47.929
COME BACK HERE TO THE DEVICE LIST
00:58:47.929 --> 00:58:50.799
AND CLICK REFRESH, WE SHOULD NOW
00:58:50.799 --> 00:58:54.724
SEE HERE A BRAND-NEW DEVICE TYPE,
00:58:54.724 --> 00:58:55.896
HAS AUTOMATICALLY BEEN ADDED. THIS
00:58:55.896 --> 00:58:58.413
IS MY IOT DEVICE. IT GETS EVEN BETTER.
00:58:58.413 --> 00:59:00.600
WHEN I CLICK TO OPEN THIS DEVICE,
00:59:00.600 --> 00:59:03.215
I HAVE A PREBUILT DASHBOARD WITH
00:59:03.215 --> 00:59:04.986
DATA THAT IS ALREADY STARTING TO
00:59:04.986 --> 00:59:08.526
FLOW IN. THIS TRULY IS PLUG AND
00:59:08.526 --> 00:59:10.426
PLAY. NOW THIS INCREDIBLE TECHNOLOGY
00:59:10.426 --> 00:59:12.463
CAN THEN BE INTEGRATED WITH THE
00:59:12.463 --> 00:59:13.976
AERIAL IMAGING AND THE SATELLITE
00:59:13.976 --> 00:59:15.661
FROM BEFORE TO POWER SOLUTIONS LIKE
00:59:15.661 --> 00:59:17.906
FARM BEATS. AND FARM BEATS IS USING
00:59:17.906 --> 00:59:19.750
THE TECHNOLOGY TO HELP FEED THE
00:59:19.750 --> 00:59:21.612
WORLD. BUT EVERY SINGLE PERSON HERE
00:59:21.612 --> 00:59:23.668
AT THIS CONFERENCE CAN USE THESE
00:59:23.668 --> 00:59:26.758
SAME TOOLS AND TECHNOLOGY TO TAKE
00:59:26.758 --> 00:59:29.400
ADVANTAGE OF IOT EDGE, IOT CENTRAL
00:59:29.400 --> 00:59:31.174
AND IOT PLUG AND PLAY, COMBINE THAT
00:59:31.174 --> 00:59:32.935
WITH AN INTELLIGENT EDGE AND AN
00:59:32.935 --> 00:59:35.038
INTELLIGENT CLOUD. TO START TO SELL
00:59:35.038 --> 00:59:37.224
PROBLEMS THAT CAN LITERALLY CHANGE
00:59:37.224 --> 00:59:38.260
THE WORLD. SO THANK YOU SO MUCH,
00:59:38.260 --> 00:59:40.476
I'VE GOT TO GET BACK HERE TO MANAGING
00:59:40.476 --> 00:59:43.173
MY CROPS. I'M GOING TO PASS IT BACK
00:59:43.173 --> 00:59:49.560
TO YOU AT THE CONFERENCE. >> AWESOME.
00:59:49.560 --> 00:59:51.235
AND IF YOU'RE GOING TO KEEP BRINGING
00:59:51.235 --> 00:59:52.867
THOSE MICROPHONES TO THE TRACTOR,
00:59:52.867 --> 00:59:54.525
WE'VE GOT TO GET THE RUGGEDIZED
00:59:54.525 --> 00:59:56.029
VERSION OF THAT ONE, TOO. ALL RIGHT.
00:59:56.029 --> 00:59:57.414
YOU CAN TAKE A LOOK AT THAT, GO
00:59:57.414 --> 00:59:58.832
OVER TO THE FLOOR. THERE'S A BUNCH
00:59:58.832 --> 01:00:00.650
OF COOL THINGS THERE. I WANT TO
01:00:00.650 --> 01:00:00.651
MOVE ON INTO DATA AND ANALYTICS.
01:00:00.651 --> 01:00:04.364
AND WHEN WE THINK ABOUT DATA AND
01:00:04.364 --> 01:00:05.728
ANALYTICS, OF COURSE, IT'S ONE OF
01:00:05.728 --> 01:00:06.817
THE CORE THINGS THAT WE'RE GOING
01:00:06.817 --> 01:00:09.348
TO HAVE AS PART OF OUR SOLUTIONS.
01:00:09.348 --> 01:00:11.138
WE WANTED A SPECTRUM OF OPTIONS
01:00:11.138 --> 01:00:13.492
FROM RELATIONAL, NON-RELATIONAL,
01:00:13.492 --> 01:00:15.245
DATA WAREHOUSE AND BIG DATA. I'M
01:00:15.245 --> 01:00:18.592
GOING TO START OFF, OF COURSE, WITH
01:00:18.592 --> 01:00:20.316
RELATIONAL. AND WITH US IT STARTS
01:00:20.316 --> 01:00:22.473
WITH SEQUEL WITH SEQUEL SERVER.
01:00:22.473 --> 01:00:25.468
WHERE WE'VE HAD TREMENDOUS SUCCESS
01:00:25.468 --> 01:00:27.535
IN SQL SERVER ITSELF. I'M PLEASED
01:00:27.535 --> 01:00:28.968
TO ANNOUNCE THE GENERAL AVAILABILITY
01:00:28.968 --> 01:00:33.011
OF SQL SERVER 2019. YEAH, SQL USERS,
01:00:33.011 --> 01:00:35.152
THERE YOU GO. YEAH. WE'RE VERY HAPPY
01:00:35.152 --> 01:00:36.758
WITH THIS. AND THE KEY THING TO
01:00:36.758 --> 01:00:38.576
REMEMBER ABOUT SQL SERVER, IT'S
01:00:38.576 --> 01:00:41.442
NOT JUST A DATA BASE. WE'VE -- WE'VE
01:00:41.442 --> 01:00:42.573
ESSENTIALLY CONTINUED TO EVOLVE
01:00:42.573 --> 01:00:44.415
IT INTO AN ENTIRE DATA PLATFORM.
01:00:44.415 --> 01:00:46.213
WE'RE GOING TO GIVE YOU THE ABILITY
01:00:46.213 --> 01:00:48.946
TO DELIVER A COMPREHENSIVE SET OF
01:00:48.946 --> 01:00:51.028
ANALYTICS SOLUTIONS, AS WELL. I
01:00:51.028 --> 01:00:51.913
HAVE STRUCTURED AND UNSTRUCTURED
01:00:51.913 --> 01:00:53.872
DATA. I'VE GOT APACHE SPARK SUPPORT.
01:00:53.872 --> 01:00:55.675
SO PRETTY MUCH EVERYTHING YOU'D
01:00:55.675 --> 01:00:57.605
EXPECT TO HAVE IN A MODERN VERSION
01:00:57.605 --> 01:01:00.074
OF A DATA BASE. AND SQL LITERALLY
01:01:00.074 --> 01:01:02.950
RUNS EVERYWHERE. WE HAVE BROUGHT
01:01:02.950 --> 01:01:04.758
SQL SERVER 2017 TO LINUX, AND IT
01:01:04.758 --> 01:01:07.680
WAS DOWNLOADED MORE THAN 30 MILLION
01:01:07.680 --> 01:01:09.777
TIMES. FOUR WE CONTINUE THAT ON
01:01:09.777 --> 01:01:11.300
WITH SQL SERVER 2019. OUR GOAL HERE
01:01:11.300 --> 01:01:13.688
IS TO MAKE SURE THAT YOU CAN RUN
01:01:13.688 --> 01:01:15.331
IT BEST ACROSS WHETHER YOU'RE RUNNING
01:01:15.331 --> 01:01:16.984
AT INFRASTRUCTURE OR RUNNING IT
01:01:16.984 --> 01:01:19.112
ON TOP OF THE -- THE ACTUAL DATA
01:01:19.112 --> 01:01:20.572
SERVICE ITSELF. IF YOU'RE RUNNING
01:01:20.572 --> 01:01:23.712
IN YOUR OWN PREMISES OR NOW IN MULTIPLE
01:01:23.712 --> 01:01:25.217
CLOUDS, IN ALL SORTS OF LOCATIONS
01:01:25.217 --> 01:01:27.668
WITH AZURE ARC AND WITH THE AZURE
01:01:27.668 --> 01:01:31.720
DATA BASE EDGE ON THE EDGE. SQL
01:01:31.720 --> 01:01:33.515
KEEPS GETTING BETTER. IT IS A PLACE
01:01:33.515 --> 01:01:36.396
WHERE WE'VE DONE FROM BUILT-IN ALE.
01:01:36.396 --> 01:01:37.850
SO I CAN GET PEAK PERFORMANCE AND
01:01:37.850 --> 01:01:39.590
WORK DIRECTLY WITH IT. I'VE GOT
01:01:39.590 --> 01:01:40.755
SERVERLESS WORKLOAD SUPPORT. WE
01:01:40.755 --> 01:01:42.169
CONTINUE TO GIVE YOU EVERGREEN SUPPORT.
01:01:42.169 --> 01:01:44.075
THAT MEANS YOU'RE NEVER OUT OF DATE
01:01:44.075 --> 01:01:46.113
ON YOUR VERSION OF SQL SERVER WHEN
01:01:46.113 --> 01:01:49.580
YOU'RE RUNNING IN AZURE. ALSO IF
01:01:49.580 --> 01:01:51.021
YOU LOOK AT WHAT HAS MEASURED HERE,
01:01:51.021 --> 01:01:52.693
IF I LOOK AT PRICE AND PERFORMANCE
01:01:52.693 --> 01:01:54.550
ESPECIALLY OVER THE THREE-YEAR PERIOD,
01:01:54.550 --> 01:01:57.049
WE CAN SEE THAT WE'RE UP TO 86 LESS
01:01:57.049 --> 01:01:58.629
EXPENSIVE TO RUN WITH THE DATA BASE
01:01:58.629 --> 01:02:00.764
AS A SERVICE, AZURE SQL D. B. ,
01:02:00.764 --> 01:02:03.530
AND UP TO 87 LESS EXPENSIVE WHEN
01:02:03.530 --> 01:02:05.036
YOU'RE RUNNING WITH AZURE SQL VIRTUAL
01:02:05.036 --> 01:02:07.847
MACHINES. SO IT'S NOT ONLY GREAT
01:02:07.847 --> 01:02:09.669
TECHNOLOGY, GREAT PERFORMANCE, BUT
01:02:09.669 --> 01:02:12.766
ALSO RUNNING AT A GREAT PRICE ON
01:02:12.766 --> 01:02:18.606
AZURE. NOW AS DAVID TE CONTINUES
01:02:18.606 --> 01:02:19.228
TO GROW IT'S GROWING EXPONENTIAL
01:02:19.228 --> 01:02:20.564
RATES. YOU NEED A CLOUD SOLUTION
01:02:20.564 --> 01:02:22.632
THAT CAN HELP YOU SCALE ACCORDINGLY.
01:02:22.632 --> 01:02:24.535
WITH THIS IT MIND WE HAVE ADDED
01:02:24.535 --> 01:02:26.766
HYPER SCALE ABILITIES TO ALL OF
01:02:26.766 --> 01:02:29.033
OUR RELATIONAL DATA BASES. WE HAVE
01:02:29.033 --> 01:02:30.880
AZURE HYPER SCALE DATA BASENESS
01:02:30.880 --> 01:02:31.932
THAT GOES FAR BEYOND WHAT OTHER
01:02:31.932 --> 01:02:33.737
CLOUD PROVIDERS ARE DOING. ESSENTIALLY
01:02:33.737 --> 01:02:36.580
THIS AMOUNTS TO THAT WE CAN DO DYNAMICALLY
01:02:36.580 --> 01:02:38.435
AND INDEPENDENTLY SCALE MEMORY,
01:02:38.435 --> 01:02:40.520
COMPUTE, AND STORAGE SO DEPENDING
01:02:40.520 --> 01:02:42.608
UPON THE SHAPE OF YOUR WORKLOAD
01:02:42.608 --> 01:02:44.036
AND HOW IT COMES THROUGH, WE'LL
01:02:44.036 --> 01:02:45.371
HANDLE IT FOR YOU. YOU CAN SEE THAT
01:02:45.371 --> 01:02:48.236
YOU CAN GET UP TO HUNDREDS OF TERABYTES
01:02:48.236 --> 01:02:51.017
WORTH OF DATA WITH AZURE SQL SCALE
01:02:51.017 --> 01:02:52.471
AND GO UP TO THOUSANDS OF CORES.
01:02:52.471 --> 01:02:54.546
WE DO ALL OF THAT WORK FOR YOU.
01:02:54.546 --> 01:02:56.471
SO IT WORKS ACROSS THESE. THAT'S
01:02:56.471 --> 01:02:57.767
AMAZING SUPPORT. NOW WE'RE ALSO
01:02:57.767 --> 01:03:01.036
PLEASED, THEREFORE, TO ANNOUNCE
01:03:01.036 --> 01:03:02.296
AZURE DATA BASE FOR CROSS SQL HYPER
01:03:02.296 --> 01:03:04.243
SCALE IN GENERAL AVAILABILITY TODAY.
01:03:04.243 --> 01:03:06.085
IT'S GOING TO GIVE THROUGH REALLY
01:03:06.085 --> 01:03:08.993
SUPER FAST SUPPORT, THAT HORIZONTAL
01:03:08.993 --> 01:03:09.717
DISTRIBUTION AGAIN ACROSS DATA AND
01:03:09.717 --> 01:03:12.942
ACROSS ALL OF THE DATA BASE CLUSTER.
01:03:12.942 --> 01:03:14.628
WE'LL HANDLE THAT FOR YOU. SCALING
01:03:14.628 --> 01:03:16.782
UP TO THOUSANDS OF CORES FOR MAXIMUM
01:03:16.782 --> 01:03:18.868
POWER. NOW LET'S TALK ABOUT NON-RELATIONAL.
01:03:18.868 --> 01:03:20.528
THIS IS CASES WHERE, OF COURSE,
01:03:20.528 --> 01:03:22.507
YOU WANT TO OPTIMIZE FOR PARTICULAR
01:03:22.507 --> 01:03:24.791
TYPES OF DATA. I MIGHT HAVE KEY
01:03:24.791 --> 01:03:26.545
VALUE STORE. I MIGHT HAVE DOCUMENTS,
01:03:26.545 --> 01:03:27.980
A GRAPH I NEED TAKE AND KEEP TRACK
01:03:27.980 --> 01:03:29.622
OF. WE WANT TO MAKE SURE THAT WE
01:03:29.622 --> 01:03:33.119
CAN SUPPORT ALL OF THOSE DATA TYPES,
01:03:33.119 --> 01:03:33.641
STORE THEM INDEX AND OPTIMIZE THEM
01:03:33.641 --> 01:03:36.590
AND BE ABLE TO QUERY EASILY AGAINST
01:03:36.590 --> 01:03:38.657
THEM. AND HYPER SCALE ISN'T JUST
01:03:38.657 --> 01:03:39.885
FOR THE RELATIONS ENGINES THAT WE'VE
01:03:39.885 --> 01:03:42.520
GOT. WE ALSO HAVE CUSTOMER THAT'S
01:03:42.520 --> 01:03:45.294
ARE BUILDING PLANET WIDE SCALE.
01:03:45.294 --> 01:03:47.375
AND DOING THIS WITH AZURE COSMOS
01:03:47.375 --> 01:03:50.708
AND D. B. THE WORLD'S FIRST GLOBALLY
01:03:50.708 --> 01:03:53.609
DISTRIBUTED SERVICE. I CAN HORIZONTALLY
01:03:53.609 --> 01:03:55.437
SCALE A DATA BASE AND PUT ALL THE
01:03:55.437 --> 01:03:57.726
DATA WHEREVER MY USERS ARE. NOW
01:03:57.726 --> 01:04:00.542
IT IS MULTIMODAL BY DESIGN. AND
01:04:00.542 --> 01:04:02.917
WE CAN ACTUALLY DO RELATIONAL, NON-RELATIONAL,
01:04:02.917 --> 01:04:06.085
I CAN RUN WITH CASSANDRA, TABLES,
01:04:06.085 --> 01:04:07.547
ANY OTHER SOLUTION THAT YOU'D WANT.
01:04:07.547 --> 01:04:09.389
AND THE COOL THING ABOUT THIS IS
01:04:09.389 --> 01:04:12.389
WE CAN GIVE YOU SINGLE-DIGIT MILLISECOND
01:04:12.389 --> 01:04:16.459
LATE SEE UP TO 9 -- LATENCY UP TO
01:04:16.459 --> 01:04:17.857
99 AND FIVE LINES OF FOUR SCALE
01:04:17.857 --> 01:04:20.929
THAT I REQUIRE. NOW THIS IS A TON
01:04:20.929 --> 01:04:23.707
OF MISSION CRITICAL WORKLOADS. EVERYONE
01:04:23.707 --> 01:04:24.882
FROM SYMANTEC, WALMART, JOHNSON
01:04:24.882 --> 01:04:25.957
CONTROLS. WE'RE USING IT AT MICROSOFT,
01:04:25.957 --> 01:04:28.059
AS WELL. IT'S PART OF THE CORE OF
01:04:28.059 --> 01:04:29.476
ZHUSZH ITSELF AND THE CONTROL PLANE.
01:04:29.476 --> 01:04:32.407
AND IT'S LEVERAGED BY XBOX, OFFICE
01:04:32.407 --> 01:04:34.821
365, AND GITHUB. SO WE THINK THE
01:04:34.821 --> 01:04:36.700
TECHNOLOGY IS FANTASTIC. AND WE'RE
01:04:36.700 --> 01:04:38.171
CONTINUED TO ADD NEW CAPABILITIES.
01:04:38.171 --> 01:04:40.103
IN THIS CASE, WITH AUTOPILOT. IN
01:04:40.103 --> 01:04:42.714
THIS CASE, WE'LL TAKE CARE OF THE
01:04:42.714 --> 01:04:44.685
CAPACITY PLAYING THAT'S REQUIRED.
01:04:44.685 --> 01:04:46.668
WE'LL DO THE AUTOMATIC SCALING WITHOUT
01:04:46.668 --> 01:04:49.049
COMPROMISING THE SLAS, ALLOWING
01:04:49.049 --> 01:04:51.277
YOU TO CONCENTRATE ON THE WORK YOU
01:04:51.277 --> 01:04:53.505
NEED AND ALLOW THE DATA BASE TO
01:04:53.505 --> 01:04:55.265
DO THE ACTUAL SCALE BIT. NOW AS
01:04:55.265 --> 01:04:56.503
WE MOVE FORWARD TO DATA ANALYTICS,
01:04:56.503 --> 01:04:58.976
WE KNOW THAT MODERN ENTERPRISES
01:04:58.976 --> 01:05:00.792
ARE ENTERTAININGLY DRIVEN BY --
01:05:00.792 --> 01:05:02.068
INCREASINGLY DRIVEN BY INSIGHTS.
01:05:02.068 --> 01:05:04.351
DRIVEN BY CUSTOMERS, PRODUCTS, SERVICES,
01:05:04.351 --> 01:05:05.608
INTERNAL PROCESSES. IT DOESN'T MATTER
01:05:05.608 --> 01:05:08.538
WHERE IT COMES FROM. I NEED AN EFFECTIVE
01:05:08.538 --> 01:05:10.409
SOLUTION TO REASON OVER IT AND BE
01:05:10.409 --> 01:05:14.300
ABLE TO INNOVATE. AND SO WE HAVE
01:05:14.300 --> 01:05:16.908
CREATED AZURE ANALYTICS. WHEN WE'RE
01:05:16.908 --> 01:05:18.037
IMPLEMENTING THIS WORK, THE PATTERN
01:05:18.037 --> 01:05:19.468
THAT WE SEE THAT PEOPLE LIKED IS
01:05:19.468 --> 01:05:21.127
BEING ABLE TO COME IN, FIRST OF
01:05:21.127 --> 01:05:23.018
ALL, LEVERAGING TECHNOLOGY. LIKE
01:05:23.018 --> 01:05:24.551
AZURE DATA FACTORIES THAT CAN WRANGLE
01:05:24.551 --> 01:05:26.357
MY DATA, GET IT MOVED AROUND, PULL
01:05:26.357 --> 01:05:28.192
IT IN FROM MULTIPLE PLACES AND ENSURE
01:05:28.192 --> 01:05:29.609
IT'S IN THE RIGHT SPOT. WHEN I GET
01:05:29.609 --> 01:05:31.045
IT THROUGH THE PIPELINE, I WANT
01:05:31.045 --> 01:05:32.974
TO LIGHT IT UP IN POWER BI SO THAT
01:05:32.974 --> 01:05:34.255
EVERYONE ON MY TEAM CAN START TO
01:05:34.255 --> 01:05:35.535
CREATE THEIR OWN DASHBOARDS AND
01:05:35.535 --> 01:05:37.280
GET THAT INSIGHT. AND AT THE HEART
01:05:37.280 --> 01:05:39.901
OF THIS PATTERN HAS BEEN AZURE SQL
01:05:39.901 --> 01:05:41.546
DATA WAREHOUSE. IN THE PAST YEAR
01:05:41.546 --> 01:05:44.645
ALONE, WE HAVE RELEASED OVER 140
01:05:44.645 --> 01:05:47.824
NEW FEATURES. AND WE'VE SEEN TREMENDOUS
01:05:47.824 --> 01:05:48.944
CUSTOMER ADOPTION. WHAT'S ALSO COOL
01:05:48.944 --> 01:05:51.227
ABOUT THIS, IF YOU LOOK AT THE STUDY,
01:05:51.227 --> 01:05:53.217
AZURE ANALYTICS IS SIMPLY UNMATCHED.
01:05:53.217 --> 01:05:57.307
IT CAN SEE THAT WE'RE UP TO 14 TIMES
01:05:57.307 --> 01:05:59.467
FASTER, AND COST UP TO 94 LESS THAN
01:05:59.467 --> 01:06:02.834
OTHER CLOUD COMPETITORS THAT ARE
01:06:02.834 --> 01:06:04.156
OUT THERE. SMALLER IS BETTER. THAT'S
01:06:04.156 --> 01:06:05.773
WHEN YOU'RE GETTING THE BEST PRICE
01:06:05.773 --> 01:06:07.229
PERFORMANCE OUT OF ALL OF THIS.
01:06:07.229 --> 01:06:09.076
AND IT ALLOWS YOU TO PULL THE PIPELINES
01:06:09.076 --> 01:06:10.965
THROUGH AND AGAIN TAKE THE AZURE
01:06:10.965 --> 01:06:12.139
ANALYTICS PLUS POWER BI AND GET
01:06:12.139 --> 01:06:14.105
THE INSIGHT BACK AND DELIVERED TO
01:06:14.105 --> 01:06:16.290
EVERYONE ON YOUR TEAM. WE DIDN'T
01:06:16.290 --> 01:06:18.708
WANT TO JUST STOP THERE. SO WHAT
01:06:18.708 --> 01:06:21.725
IF WE COULD ACTUALLY SIMPLIFY ANALYTICS?
01:06:21.725 --> 01:06:24.409
WE WOULD MAKE IT EASIER TO DO. AND
01:06:24.409 --> 01:06:25.365
ALSO WHAT IF WE COULD LEVERAGE THE
01:06:25.365 --> 01:06:26.916
SKILLS THAT YOU'VE ALREADY GOT.
01:06:26.916 --> 01:06:28.602
MAYBE YOU'RE NOT A DATA SCIENTIST,
01:06:28.602 --> 01:06:31.214
BUT YOU ARE A SQL PROFESSIONAL.
01:06:31.214 --> 01:06:32.672
HOW ABOUT WE BE LEVERAGE YOUR SKILLS
01:06:32.672 --> 01:06:34.513
IN YOUR EVERYDAY JOB? IN ADDITION,
01:06:34.513 --> 01:06:37.560
WE WANT TO APPLY A. I. WHERE THE
01:06:37.560 --> 01:06:38.549
DATA ACTUALLY LIVES, RATHER THAN
01:06:38.549 --> 01:06:40.745
TRYING TO MOVE IT ALL OVER THE PLACE.
01:06:40.745 --> 01:06:42.361
AND SO IN THIS WORLD, WE'VE OFTEN
01:06:42.361 --> 01:06:45.233
SEEN THAT THERE HAVE BEEN DATA WAREHOUSE
01:06:45.233 --> 01:06:46.129
SOLUTIONS AND BIG DATA SOLUTIONS.
01:06:46.129 --> 01:06:47.767
THEN I HAVE TO FIGURE OUT THE PLUMBING
01:06:47.767 --> 01:06:51.164
BETWEEN THEM. WE BELIEVE THAT GOING
01:06:51.164 --> 01:06:51.979
FORWARD THESE SOLUTIONS NEED TO
01:06:51.979 --> 01:06:54.155
CONTINUE TO CONVERGE. WHERE I HAVE
01:06:54.155 --> 01:06:55.767
STACKS THAT ACTUALLY FIGURE OUT
01:06:55.767 --> 01:06:55.768
I DON'T HAVE TO WORRY ABOUT WHERE
01:06:55.768 --> 01:06:58.689
THE DATA IS. LET THE TECHNOLOGY
01:06:58.689 --> 01:07:01.669
DO THAT WORK FOR YOU. AS FOR VERY
01:07:01.669 --> 01:07:03.420
PLEASED TO ANNOUNCE TODAY THE PREVIEW
01:07:03.420 --> 01:07:07.421
OF AZURE SYNAPSE ANALYTICS. IF WE
01:07:07.421 --> 01:07:10.258
LOOK AT THE SOLUTION FOR AZURE SYNAPSE
01:07:10.258 --> 01:07:11.280
ANALYTICS, THINK ABOUT THE STACK.
01:07:11.280 --> 01:07:12.964
IT STARTS WITH AZURE, DATA LINK
01:07:12.964 --> 01:07:14.855
STORAGE AT THE BASE. WHERE I CAN
01:07:14.855 --> 01:07:16.058
STORE ANY TYPE OF FOLLOWING THAT
01:07:16.058 --> 01:07:19.586
I WANT. WE DO EXABYTES OF STORAGE,
01:07:19.586 --> 01:07:21.766
EVEN IN MICROSOFT, PETA BYTE LEVEL
01:07:21.766 --> 01:07:23.305
QUERIES, HOW WYE RUN THE COMPANY.
01:07:23.305 --> 01:07:24.556
WE'RE TAKING THE SAME TECHNOLOGY
01:07:24.556 --> 01:07:25.905
AND MAKING IT AVAILABLE TO YOU.
01:07:25.905 --> 01:07:27.485
I CAN MOVE UP INTO ANALYTICS, AND
01:07:27.485 --> 01:07:30.045
I CAN RUN THINGS LIKE SQL AND SPARK.
01:07:30.045 --> 01:07:30.961
AND FIGURE OUT WHATEVER SOLUTION
01:07:30.961 --> 01:07:32.811
MAKES SENSE. AND I CAN MOVE INTO
01:07:32.811 --> 01:07:34.212
THE UNIFIED EXPERIENCE WITH SINCE
01:07:34.212 --> 01:07:37.691
OPS STUDIO WHERE I CAN ORCHESTRATE
01:07:37.691 --> 01:07:39.286
AND CREATE AND MANAGE AND MONITOR
01:07:39.286 --> 01:07:40.956
ALL THE WORK THAT'S REQUIRED IN
01:07:40.956 --> 01:07:43.855
ORDER TO DO NEW EXPERIMENTS AND
01:07:43.855 --> 01:07:45.246
EXPERIMENTATION. NOW WE'RE VERY
01:07:45.246 --> 01:07:47.183
PLEASED TODAY THAT WE'RE GOING TO
01:07:47.183 --> 01:07:49.299
GENERAL 'AVAILABILITY WITH PROVISIONED
01:07:49.299 --> 01:07:51.573
DATA WAREHOUSE FORMERLY KNOWN AS
01:07:51.573 --> 01:07:53.293
AZURE SQL DATA WAREHOUSE. AND WE'RE
01:07:53.293 --> 01:07:55.161
ANNOUNCING THE NEW ON-DEMAND QUERY
01:07:55.161 --> 01:07:56.561
AS A SERVICE THAT RUNS IN PREVIEW
01:07:56.561 --> 01:07:59.337
TO GIVE YOU ALL THE TECHNOLOGY.
01:07:59.337 --> 01:08:01.551
I WANT TO BRING JOHN MCINTYRE FROM
01:08:01.551 --> 01:08:03.521
THE TEAM UP AND SHOW US THE POWER
01:08:03.521 --> 01:08:06.715
OF AZURE SYNAPSE ANALYTICS. JOHN?
01:08:06.715 --> 01:08:08.894
>> THANKS. GOOD MORNING. GOOD AFTERNOON.
01:08:08.894 --> 01:08:11.420
IN THE KEYNOTE THIS MORNING, WE
01:08:11.420 --> 01:08:14.304
SAW A PRODUCT MANAGER AT A GAMING
01:08:14.304 --> 01:08:16.755
COMPANY USE AZURE SYNAPSE TO IMPROVE
01:08:16.755 --> 01:08:18.899
USER ENGAGEMENT. IMAGINE I'M A DATA
01:08:18.899 --> 01:08:21.801
ENGINEER AT THE SAME GAMING COMPANY,
01:08:21.801 --> 01:08:22.579
AND I'M WORKING WITH MY TEAM ON
01:08:22.579 --> 01:08:24.145
HOW DO I INCREASE PLAYER SESSION
01:08:24.145 --> 01:08:26.393
TIME. TO DO THAT, WE REALLY NEED
01:08:26.393 --> 01:08:28.151
TO UNDERSTAND HOW PLAYERS ARE USING
01:08:28.151 --> 01:08:31.087
OUR GAMES, AND WE ALSO NEED TO BE
01:08:31.087 --> 01:08:32.676
ABLE TO PREDICT WHAT FEELS AND CAPABILITIES
01:08:32.676 --> 01:08:33.985
OUR GAME USERS ARE GOING TO WANT
01:08:33.985 --> 01:08:36.486
TO USE. TO DO THAT, I'M BRINGING
01:08:36.486 --> 01:08:38.860
TOGETHER TONS OF DATA, I HAVE PLAYER
01:08:38.860 --> 01:08:42.500
SESSION DATA, I HAVE -- I CAN GET
01:08:42.500 --> 01:08:43.983
THE MOUSE WORKING -- I HAVE EVENT
01:08:43.983 --> 01:08:46.910
DATA STREAMING IN, I HAVE MARKETING
01:08:46.910 --> 01:08:48.814
CAMPAIGN DATA, I HAVE DEVICE DATA
01:08:48.814 --> 01:08:51.764
THAT MY DEVICE PARTNERS ARE SECURELY
01:08:51.764 --> 01:08:54.029
SHARING USING AZURE DATA SHARE.
01:08:54.029 --> 01:08:56.630
ALL IN ALL I HAVE JUST UNDER THREE
01:08:56.630 --> 01:08:58.600
PETABYTES OF DATA THAT I NEED TO
01:08:58.600 --> 01:09:00.272
ANALYZE. DOING ANALYTICS AT THIS
01:09:00.272 --> 01:09:03.722
SCALE IS EXTREMELY CHALLENGING.
01:09:03.722 --> 01:09:05.127
LET ME SHOW HOW AZURE SYNAPSE HELPED
01:09:05.127 --> 01:09:06.820
ME WITH THIS. FROM WITHIN THE SINCE
01:09:06.820 --> 01:09:09.717
OPS WORKSPACE, I GET ALL THE TOOLS
01:09:09.717 --> 01:09:13.522
I NEED TO INGEST, EXPLORE, ANALYZE,
01:09:13.522 --> 01:09:15.354
AND VISUALIZE DATA AT SCALE. I DON'T
01:09:15.354 --> 01:09:17.483
HAVE TO HOP ACROSS A MILLION DIFFERENT
01:09:17.483 --> 01:09:19.790
TOOLS JUST TO GET MY JOB DONE. I
01:09:19.790 --> 01:09:22.656
CAN GO TO THE DATA HUB TO GET ACCESS
01:09:22.656 --> 01:09:25.649
TO ALL MY DATA, MY FILE DATA, MY
01:09:25.649 --> 01:09:28.239
DATA BASE DATA, AND MY DATA SETS.
01:09:28.239 --> 01:09:30.288
I DON'T HAVE TO CONFIGURE SERVERS
01:09:30.288 --> 01:09:33.864
OR SET UP DATA BASES OR EVEN DEFINE
01:09:33.864 --> 01:09:35.716
A TABLE BEFORE I RUN PLY FIRST QUERY.
01:09:35.716 --> 01:09:40.035
I CAN SIMPLY RIGHT CLICK AND OPEN
01:09:40.035 --> 01:09:42.823
A NEW SQL SCRIPT OR OPEN A NOTEBOOK
01:09:42.823 --> 01:09:45.111
AND ANALYZE DATA USING APACHE SPARK.
01:09:45.111 --> 01:09:48.712
I'M A SQL GUY SO LET'S USE SQL SCRIPT.
01:09:48.712 --> 01:09:50.500
AZURE SINCE OPS WILL AUTOMATICALLY
01:09:50.500 --> 01:09:52.989
DETECT THE TYPE OF DATA THAT I'M
01:09:52.989 --> 01:09:54.864
ANALYZING. AND GENERATE A SQL STATEMENT
01:09:54.864 --> 01:09:58.346
TO SAMPLE THAT DATA. IF I CLICK
01:09:58.346 --> 01:10:00.069
RUN, SINCE OPS IS GOING TO USE THE
01:10:00.069 --> 01:10:02.634
NEW ON-DEMAND QUERY SERVICE TO ANALYZE
01:10:02.634 --> 01:10:04.840
THIS DATA THAT'S IN MY AZURE DATA
01:10:04.840 --> 01:10:06.110
LAKES STORAGE ACCOUNTS. YOU CAN
01:10:06.110 --> 01:10:08.208
SEE THAT WITHIN SECONDS WE HAVE
01:10:08.208 --> 01:10:11.121
RESULTS TO THAT QUERY. PRETTY IMPRESSIVE.
01:10:11.121 --> 01:10:13.600
BUT I'M ALSO THE GUY WHO GETS THE
01:10:13.600 --> 01:10:15.144
CALL WHEN PEOPLE'S QUERIES AREN'T
01:10:15.144 --> 01:10:17.913
RUNNING AS FAST AS THEY WANT TO
01:10:17.913 --> 01:10:19.322
THEM. TYPICALLY THIS IS BECAUSE
01:10:19.322 --> 01:10:20.788
PEOPLE INSIDE MY ORGANIZATION ARE
01:10:20.788 --> 01:10:23.049
COMPETING FOR THE SAME COMPUTE RESOURCES.
01:10:23.049 --> 01:10:26.170
WITH AZURE SINCEOMS, I CAN PROVISION
01:10:26.170 --> 01:10:28.719
DEDICATED COMPUTE POOLS TO SERVE
01:10:28.719 --> 01:10:29.556
DIFFERENT ORGANIZATIONS WITH INSIDE
01:10:29.556 --> 01:10:31.395
OF THE COMPANY. HERE YOU CAN SEE
01:10:31.395 --> 01:10:34.155
I HAVE COMPUTE POOLS FOR ENGINEERING,
01:10:34.155 --> 01:10:37.107
FINANCE, AND MARKETING. ALL OF THESE
01:10:37.107 --> 01:10:39.980
ARE ACCESSING THE SAME SHARED DATA.
01:10:39.980 --> 01:10:41.284
I'LL USE THE ENGINEERING POOL TO
01:10:41.284 --> 01:10:43.354
RUN MY NEXT QUERY. I'M GOING TO
01:10:43.354 --> 01:10:46.364
JOIN DATA ACROSS A SIN'S TABLE AND
01:10:46.364 --> 01:10:49.443
A SET OF PARKAY FILES. THIS IS A
01:10:49.443 --> 01:10:51.882
QUERY THAT I WROTE THAT INCLUDES
01:10:51.882 --> 01:10:54.085
DEVICE DATA, SESSION DATA, AND EVENT
01:10:54.085 --> 01:10:57.931
DATA. WHEN I CLICK RUN, WE'LL EXECUTE
01:10:57.931 --> 01:10:59.012
THAT QUERY. REMEMBER THAT WE HAVE
01:10:59.012 --> 01:11:01.156
MORE THAN A PETABYTE OF EVENT DATA.
01:11:01.156 --> 01:11:02.448
THIS IS WHEN WE WONDER HOW LONG
01:11:02.448 --> 01:11:03.919
IS THIS GOING TO TAKE, AND WHO'S
01:11:03.919 --> 01:11:05.364
GOING TO GETS COFFEE WHILE WE ALL
01:11:05.364 --> 01:11:07.799
WAIT. BUT THE GOOD NEWS IS, SYNAPSE
01:11:07.799 --> 01:11:11.908
CAN COMPLETE THIS QUERY IN 12 SECONDS.
01:11:11.908 --> 01:11:13.289
THAT'S PRETTY IMPRESSIVE. WITHIN
01:11:13.289 --> 01:11:15.960
PLY WORK SPACE, I CAN ACTUALLY START
01:11:15.960 --> 01:11:19.651
TO VISUALIZE THIS DATA. AZURE SYNAPSE
01:11:19.651 --> 01:11:22.483
FEATURES A CLOUD NATIVE NEW SQL
01:11:22.483 --> 01:11:23.311
DISTRIBUTED QUERY PROCESSING ENGINE.
01:11:23.311 --> 01:11:25.499
FOR THOSE OF YOU THAT LIKE TO DRAG
01:11:25.499 --> 01:11:26.614
RACE DATA BASES ON THE WEEKEND,
01:11:26.614 --> 01:11:30.077
I KNOW I'M ONE OF THEM, YOU'LL BE
01:11:30.077 --> 01:11:32.384
HAPPY TO KNOW THAT SYNAPSE CAN COMPLETE
01:11:32.384 --> 01:11:35.877
ALL QUEER EGGS AT PETABYTE SCALE.
01:11:35.877 --> 01:11:37.334
LET'S GET BACK TO THE RESULTS OF
01:11:37.334 --> 01:11:39.466
OUR QUERY. HERE YOU SEE FROM THE
01:11:39.466 --> 01:11:41.615
RESULTS THAT PLAYERS WITH SUPERPOWERS
01:11:41.615 --> 01:11:47.388
ACTUALLY HAVE LONGER PLAYER SESSION
01:11:47.388 --> 01:11:48.777
DURATION. PLAYERS ARE POWERS LIKE
01:11:48.777 --> 01:11:50.068
INVISIBILITY OR POWER UP ARE PLAYING
01:11:50.068 --> 01:11:52.200
MORE. WOULDN'T IT BE COOL IF WE
01:11:52.200 --> 01:11:53.636
COULD ACTUALLY PREDICT WHICH SUPERPOWER
01:11:53.636 --> 01:11:56.736
TO OFFER EACH OF OUR PLAYERS? I'M
01:11:56.736 --> 01:11:59.268
NOT A DATA SCIENTIST, BUT I'VE DONE
01:11:59.268 --> 01:12:00.673
ENOUGH ONLINE COURSES TO SEE, LET'S
01:12:00.673 --> 01:12:04.294
SEE HOW FAR THAT CAN TAKE ME. FORTUNATELY
01:12:04.294 --> 01:12:06.796
IN AZURE SYNAPSE, I CAN AUTOMATE
01:12:06.796 --> 01:12:09.271
THE ENTIRE BROSZ OF CREATING A PREDICTIVE
01:12:09.271 --> 01:12:11.649
MODEL. I SIMPLY JUST TO CLICK ON
01:12:11.649 --> 01:12:13.754
SOME DATA, AND I CAN CREATE A NEW
01:12:13.754 --> 01:12:15.034
EXPERIMENT. A NEW EXPERIMENT WILL
01:12:15.034 --> 01:12:18.567
HELP ME BUILD THAT MODEL. I'LL GIVE
01:12:18.567 --> 01:12:21.136
MY EXPERIMENT A NAME, CALL IT GAME
01:12:21.136 --> 01:12:23.361
FEATURE EXPERIMENT. AND THEN WE'LL
01:12:23.361 --> 01:12:26.610
SELECT OUR TARGET COLUMN FOR PREDICTIONS.
01:12:26.610 --> 01:12:29.538
WE SAID SUPERPOWERS, WE'LL SELECT
01:12:29.538 --> 01:12:30.957
THAT. AND I'M GOING TO CONDITION
01:12:30.957 --> 01:12:34.202
FIGURE MY EXPERIMENT TO RUN ON MY
01:12:34.202 --> 01:12:36.571
SYNAPSE SPARK POOL. I'LL GO AHEAD
01:12:36.571 --> 01:12:38.395
AND CLICK NEXT. AND I'M GOING TO
01:12:38.395 --> 01:12:39.840
LEAVE THE TASK TYPE AS CLASSIFICATION
01:12:39.840 --> 01:12:42.298
BECAUSE WE'RE WORKING FROM A FIXED
01:12:42.298 --> 01:12:45.243
SET OF SUPERPOWERS. I'LL CLICK CREATE
01:12:45.243 --> 01:12:47.719
AND SYNAPSE WILL RUN THE EXPERIMENT.
01:12:47.719 --> 01:12:48.809
WHILE THAT RUNS I'M GOING TO GO
01:12:48.809 --> 01:12:51.082
TO AN EXPERIMENT THAT I RAN EARLIER.
01:12:51.082 --> 01:12:52.903
HERE YOU CAN SEE ALL THE RESULTS
01:12:52.903 --> 01:12:54.563
FROM MY EXPERIMENT RUNS. AND I USE
01:12:54.563 --> 01:12:56.562
THIS DATA TO FIGURE OUT WHICH MODEL
01:12:56.562 --> 01:12:59.235
IS RIGHT FOR ME. I'M GOING TO FOCUS
01:12:59.235 --> 01:13:02.480
ON ACCURACY OVER HERE. I REALLY
01:13:02.480 --> 01:13:04.802
WANT TO PICK THE MOST ACCURATE MODEL.
01:13:04.802 --> 01:13:06.178
THERE'S NOTHING WORSE THAN GETTING
01:13:06.178 --> 01:13:08.376
THE WRONG SUPERPOWER. SO ONCE I
01:13:08.376 --> 01:13:10.221
FIND THAT RIGHT MODEL, I CAN REGISTER
01:13:10.221 --> 01:13:12.137
IT WITH AZURE MACHINE LEARNING.
01:13:12.137 --> 01:13:13.703
WITH THAT MODEL REGISTERED WITH
01:13:13.703 --> 01:13:15.066
AZURE MACHINE LEARNING, I CAN USE
01:13:15.066 --> 01:13:18.490
IT FROM A VARIETY OF PLACES INCLUDING
01:13:18.490 --> 01:13:21.031
DIRECTLY FROM WITHIN SQL. HERE YOU
01:13:21.031 --> 01:13:23.727
CAN SEE A SQL QUERY THAT I WROTE
01:13:23.727 --> 01:13:26.131
EARLIER. THIS QUERY IS INVOKING
01:13:26.131 --> 01:13:28.622
THE PREDICT FUNCTION. SO WE'RE ACTUALLY
01:13:28.622 --> 01:13:30.165
USING SQL TO PREDICT THE OUTPUT.
01:13:30.165 --> 01:13:32.870
I'M GOING TO RUN THIS QUERY, AND
01:13:32.870 --> 01:13:35.382
SYNAPSE WILL EXECUTE THE QUERY,
01:13:35.382 --> 01:13:36.966
GENERATE RESULTS, AND INCLUDING
01:13:36.966 --> 01:13:38.186
PREDICTED VALUES. SO THE COOL THING
01:13:38.186 --> 01:13:41.144
HERE IS I'M USING MY EXISTING SQL
01:13:41.144 --> 01:13:43.481
SKILLS TO NOW DO PREDICTIVE ANALYTICS.
01:13:43.481 --> 01:13:45.850
SO NOW WE HAVE ALL THIS GREAT DATA,
01:13:45.850 --> 01:13:47.374
WE HAVE THESE INSIGHTS, AND WE'RE
01:13:47.374 --> 01:13:49.582
ABLE TO DO THIS GREAT PREDICTION.
01:13:49.582 --> 01:13:50.427
LET'S TAKE IT ACROSS THE FINISH
01:13:50.427 --> 01:13:52.649
LINE. I WANT TO MAKE THIS AVAILABLE
01:13:52.649 --> 01:13:55.851
TO EVERYONE IN MY ORGANIZATION THAT'S
01:13:55.851 --> 01:14:00.502
USING POWER BI. BECAUSE WE -- SYNAPSE
01:14:00.502 --> 01:14:01.252
INTEGRATES DIRECTLY WITH POWER BI,
01:14:01.252 --> 01:14:03.320
I CAN INVOKE THE POWER BI DEVELOPER
01:14:03.320 --> 01:14:06.402
EXPERIENCE RIGHT FROM WITHIN SYNAPSE.
01:14:06.402 --> 01:14:07.678
WE'LL NAVIGATE TO THE POWER BI REPORT
01:14:07.678 --> 01:14:09.553
THAT I WAS WORKING ON EARLIER, AND
01:14:09.553 --> 01:14:11.691
I'LL LOAD THAT REPORT RIGHT FROM
01:14:11.691 --> 01:14:14.486
THE SYNAPSE WORKSPACE. I CAN MODIFY
01:14:14.486 --> 01:14:16.740
THAT REPORT, AND WE'LL ADD ADDITIONAL
01:14:16.740 --> 01:14:20.245
FIELDS HERE TO INCLUDE OUR RECOMMENDATION
01:14:20.245 --> 01:14:22.400
COUNTS AND OUR FEATURE TYPE, I'LL
01:14:22.400 --> 01:14:24.804
CLICK SAVE, AND WE'RE DONE. THAT
01:14:24.804 --> 01:14:27.680
REPORT IS NOW AVAILABLE TO ALL POWER
01:14:27.680 --> 01:14:29.382
BI USERS INSIDE MY ORGANIZATION.
01:14:29.382 --> 01:14:29.383
AND BECAUSE WE'RE STREAMING DATA
01:14:29.383 --> 01:14:34.190
DIRECTLY INTO SYNAPSE, IF I REFRESH
01:14:34.190 --> 01:14:36.303
MY REPORT, I'M GOING TO SEE THE
01:14:36.303 --> 01:14:39.024
LATEST AND GREATEST DATA. AZURE
01:14:39.024 --> 01:14:40.404
SYNAPSE HAS ENABLED ME TO DELIVER
01:14:40.404 --> 01:14:42.245
THERE SOLUTION FASTER THAN WAS EVER
01:14:42.245 --> 01:14:44.070
POSSIBLE. AND FOR OUR GAME TEAM,
01:14:44.070 --> 01:14:45.625
WE'VE LEARNED SOMETHING ABOUT OUR
01:14:45.625 --> 01:14:48.089
PLAYERS. IT TURNS OUT THAT ELITE
01:14:48.089 --> 01:14:49.924
OUTFITS AND LOOKING COOL IS MORE
01:14:49.924 --> 01:14:51.624
IMPORTANT THAN HAVING SUPERPOWERS.
01:14:51.624 --> 01:15:00.343
BACK TO YOU, JULIA. >> OKAY, JOHN.
01:15:00.343 --> 01:15:02.696
[ MUSIC ] I'M NOW THRILLED TO HAVE
01:15:02.696 --> 01:15:03.899
SHEREE FROM UNILEVER HERE TO TALK
01:15:03.899 --> 01:15:06.012
ABOUT THEIR DATA JOURNEY AND EVEN
01:15:06.012 --> 01:15:09.634
BEING AN EARLY CUSTOMER WITH AZURE
01:15:09.634 --> 01:15:11.485
SYNAPSE. THANKS FOR BEING HERE.
01:15:11.485 --> 01:15:13.621
>> THANKS FOR HAVING ME HERE. >>
01:15:13.621 --> 01:15:14.966
ABSOLUTELY. WHAT HAS UNILEVER BEEN
01:15:14.966 --> 01:15:16.735
DOING, THE BUSINESS GOALS YOU HAVE
01:15:16.735 --> 01:15:19.642
AROUND YOUR DATA CULTURE. >> ABSOLUTELY.
01:15:19.642 --> 01:15:21.601
AS YOU KNOW, UNILEVER IS ONE OF
01:15:21.601 --> 01:15:23.062
THE LARGEST CPG COMPANIES IN THE
01:15:23.062 --> 01:15:25.086
WORLD. OUR GOAL IS TO ACTUALLY CHANGE
01:15:25.086 --> 01:15:28.236
THE COMPANY CULTURE TO BE A DATA-DRIVEN
01:15:28.236 --> 01:15:29.132
DECISIONMAKING ORGANIZATION. LET'S
01:15:29.132 --> 01:15:31.301
TAKE A SIMPLE EXAMPLE OF A PRODUCT
01:15:31.301 --> 01:15:34.613
LAUNCH. SAY I WANTED TO LAUNCH A
01:15:34.613 --> 01:15:37.263
NEW DOVE SHAMPOO WITH A HIBISCUS
01:15:37.263 --> 01:15:38.490
FLAVOR. I'M MAKING IT UP. TO THINK
01:15:38.490 --> 01:15:41.031
ABOUT THE ACTIVITIES, THE PLANNING,
01:15:41.031 --> 01:15:43.284
THE DATA THAT IS REQUIRED TO LAUNCH
01:15:43.284 --> 01:15:44.635
A PRODUCT, OUR BUSINESS TEAM THINKS
01:15:44.635 --> 01:15:45.945
ABOUT HOW MUCH TO PRODUCE FOR THE
01:15:45.945 --> 01:15:47.492
LAUNCH. THEN OUR MARKETING TEAM
01:15:47.492 --> 01:15:49.237
RUNS A CAMPAIGN TO FIGURE OUT HOW
01:15:49.237 --> 01:15:51.066
EFFECTIVE THE CAMPAIGN IS GOING
01:15:51.066 --> 01:15:52.695
TO BE AFTER WE EARLY LAUNCH THE
01:15:52.695 --> 01:15:54.295
PRODUCT. THEN OUR FINANCE TEAM STARTS
01:15:54.295 --> 01:15:55.712
LOOKING AT, OKAY, HOW ARE WE GOING
01:15:55.712 --> 01:15:58.728
TO MEASURE THIS, THE SALES -- AND
01:15:58.728 --> 01:15:59.797
SOMEONE THINKS ABOUT HOW MUCH INVENTORY
01:15:59.797 --> 01:16:01.584
TO BUY TO MANUFACTURE AND LOGISTICS,
01:16:01.584 --> 01:16:03.732
ET CETERA. THINK ABOUT THAT AMOUNT
01:16:03.732 --> 01:16:06.287
THE DATA THAT WE NEED TO PROCESS
01:16:06.287 --> 01:16:07.480
TO GENERATE TO MAKE THIS HAPPEN.
01:16:07.480 --> 01:16:09.033
>> THAT'S THE GOAL WHICH MAKES SENSE.
01:16:09.033 --> 01:16:10.090
WHAT IS YOUR CURRENT DATA SITUATION
01:16:10.090 --> 01:16:11.683
LOOK LIKE, OR AS YOU STARTED ON
01:16:11.683 --> 01:16:16.100
THIS JOURNEY? >> YEAH. SO IF YOU
01:16:16.100 --> 01:16:18.040
LOOK AT THE CK CONTEXT, WE HAVE
01:16:18.040 --> 01:16:18.975
THREE INTERESTING CHALLENGES. ONE,
01:16:18.975 --> 01:16:21.243
BEFORE YOU STARTED THIS JOURNEY,
01:16:21.243 --> 01:16:23.969
IT WAS HARD TO GET ACCESS TO THE
01:16:23.969 --> 01:16:26.002
DATA BECAUSE WE HAD LARGE ENTERPRISE,
01:16:26.002 --> 01:16:27.914
ABOUT 30-PLUS TECHNOLOGY PLATFORMS.
01:16:27.914 --> 01:16:30.180
DATA IS STUCK IN THE SILO'D SYSTEMS.
01:16:30.180 --> 01:16:31.609
SO GETTING ACCESS TO INTERNET IS
01:16:31.609 --> 01:16:32.977
REALLY HARD FOR US. THEN ONCE YOU
01:16:32.977 --> 01:16:34.979
GET THE ACCESS TO THE READER, THE
01:16:34.979 --> 01:16:36.989
DATA IS NOT LINKED AT ALL. TRYING
01:16:36.989 --> 01:16:39.559
TO PUT TOGETHER WE SPEND MORE TIME.
01:16:39.559 --> 01:16:42.116
AND EVENTUALLY WHEN YOU STITCH IT
01:16:42.116 --> 01:16:43.425
TOGETHER, PEOPLE STILL DON'T TRUST
01:16:43.425 --> 01:16:46.079
THE DATA. AN INTERESTING CHALLENGE
01:16:46.079 --> 01:16:48.626
BECAUSE IT WAS SILO'D -- >> SOUNDS
01:16:48.626 --> 01:16:49.614
LIKE REAL OPPORTUNITY. WHAT WAS
01:16:49.614 --> 01:16:51.079
THE FIRST STEP FROM WHERE YOU WERE?
01:16:51.079 --> 01:16:53.004
>> THE FIRST STEP WAS AS YOU WENT
01:16:53.004 --> 01:16:54.915
IN TO JOURNEY EVEN IN THE DATA LAKE,
01:16:54.915 --> 01:17:00.621
AS YOU -- AS DATA, ALL OF OUR INTERNAL
01:17:00.621 --> 01:17:02.314
DATA INTO THE DATA LINK. AT THIS
01:17:02.314 --> 01:17:04.721
POINT, WE ARE ABOUT 80 COMPLETE.
01:17:04.721 --> 01:17:07.056
PRETTY MUCH ALL OF THE S. A. P.
01:17:07.056 --> 01:17:08.530
DATA AVAILABLE IN THAT. >> GOT IT.
01:17:08.530 --> 01:17:10.854
>> IT'S GROWING. IT'S ABOUT 400
01:17:10.854 --> 01:17:12.171
TERRA BYTES NOW AND GROWING SIGNIFICANTLY
01:17:12.171 --> 01:17:14.068
ON A DAILY BASIS. >> FIRST STEP
01:17:14.068 --> 01:17:16.260
GET EVERYTHING PULLED INTO THE DATA
01:17:16.260 --> 01:17:17.860
LINK. NOW WHAT? >> IT'S THAN WE
01:17:17.860 --> 01:17:19.523
JUST BROUGHT IN THE DATA, TRYING
01:17:19.523 --> 01:17:21.335
TO FIGURE OUT WHAT TO DO. WHAT YOU'VE
01:17:21.335 --> 01:17:24.757
DONE THIS IS -- IS BUILD A NUMBER
01:17:24.757 --> 01:17:26.488
OF PRODUCTS. NOW LET'S GET BACK
01:17:26.488 --> 01:17:28.359
TO THE EXAMPLE I JUST GAVE ABOUT
01:17:28.359 --> 01:17:31.520
PRODUCT LAUNCH. NOW, ABOUT 100 TEAMS
01:17:31.520 --> 01:17:33.093
NOW CAN PLAN BETTER IN TERMS OF
01:17:33.093 --> 01:17:34.480
HOW MUCH TO MANUFACTURER FOR THE
01:17:34.480 --> 01:17:36.670
NEW PRODUCT WE'RE GOING TO LAUNCH.
01:17:36.670 --> 01:17:38.144
THEY HAVE INTERFACE AVAILABLE TO
01:17:38.144 --> 01:17:40.208
THEM. SIMILARLY SUPPLY CHAIN TEAM
01:17:40.208 --> 01:17:43.472
HAS ACCESS TO THE SAME DATA TO FIGURE
01:17:43.472 --> 01:17:45.664
OUT HOW TO -- YOU KNOW, HOW MUCH
01:17:45.664 --> 01:17:49.321
TO SOURCE IN TERMS OF THE MANUFACTURING,
01:17:49.321 --> 01:17:50.777
AND EQUALLY THE LARGEST KNOWS EXACTLY,
01:17:50.777 --> 01:17:53.017
YOU KNOW, HOW THE PRODUCTS ARE GETTING
01:17:53.017 --> 01:17:54.555
SHIPPED IN REALTIME. SIMILARLY,
01:17:54.555 --> 01:17:57.056
EVEN OUR FINANCING, OUR SAME DATA
01:17:57.056 --> 01:17:59.416
TO PROCESS AND FIGURE OUT WHAT KIND
01:17:59.416 --> 01:18:00.810
OF -- WHAT YOU'RE EXPECTING OR ANTICIPATING
01:18:00.810 --> 01:18:04.372
FROM THE SLIDE. PRETTY MUCH, YOU'RE
01:18:04.372 --> 01:18:06.632
TAKING NOT ONLY THE DATA INTO THE
01:18:06.632 --> 01:18:09.185
LAKE BUT EQUALLY BUILT A NUMBER
01:18:09.185 --> 01:18:10.620
OF PRODUCTS GENERATING THE SAME
01:18:10.620 --> 01:18:13.049
COMMUNITY. >> GREAT. YOU WERE ONE
01:18:13.049 --> 01:18:15.236
OF THE EARLY CUSTOMERS WORKING WITH
01:18:15.236 --> 01:18:16.950
US AS WE DEVELOPED AZURE SYNAPSE
01:18:16.950 --> 01:18:18.504
ANALYTICS. THANK YOU. YOU'VE GONE
01:18:18.504 --> 01:18:19.705
YOUR JOURNEY WITH THAT. INTERESTING
01:18:19.705 --> 01:18:20.956
IN WHAT YOU'RE SEEING FROM THOSE
01:18:20.956 --> 01:18:22.645
RESULTS. >> ABSOLUTELY. IT'S BEEN
01:18:22.645 --> 01:18:24.676
IN EARLY DAYS AS WE SAID. ONE OF
01:18:24.676 --> 01:18:26.844
THE THINGS, YOU KNOW, OUR AMBITION
01:18:26.844 --> 01:18:30.428
IS WHILE WE BUILD A NUMBER OF DESCRIPTIVE
01:18:30.428 --> 01:18:34.088
AND DIAGNOSTIC OTHERS TO MAKE THE
01:18:34.088 --> 01:18:37.156
JOURNEY INTO -- WHAT YOU'RE SEEING
01:18:37.156 --> 01:18:40.204
IS GOING TO HELP OUR JOURNEY. THE
01:18:40.204 --> 01:18:43.696
OTHER AMBITION WE HAVE IS UP TO
01:18:43.696 --> 01:18:44.928
DEMOCRATIZE ANALYTICS THROUGH OUR
01:18:44.928 --> 01:18:46.811
CITIZEN -- SCIENTIST COMMUNITY.
01:18:46.811 --> 01:18:48.841
AND WE BELIEVE THAT WE'RE SUPER
01:18:48.841 --> 01:18:49.954
EXCITED WITH WHAT YOU'RE SEEING
01:18:49.954 --> 01:18:52.949
SO FAR. THAT SYNOPSIS WILL ENABLE
01:18:52.949 --> 01:18:55.605
FOR THE COMMUNITY. >> THANK YOU
01:18:55.605 --> 01:18:58.206
FOR YOUR PARTNERSHIP. THANK YOU
01:18:58.206 --> 01:20:02.178
FOR SHARING YOUR STORY. >> THANK YOU.
01:20:02.178 --> 01:20:03.396
THE THINGS I CAN ENTER WITHOUT HAVING
01:20:03.396 --> 01:20:05.201
TO WRITE A LOT OF CODE OR DO EXTRA
01:20:05.201 --> 01:20:06.900
WORK ON TOP OF IT. WITH THAT WE'RE
01:20:06.900 --> 01:20:09.165
ALSO PLEASED TO ANNOUNCE THAT WE'VE
01:20:09.165 --> 01:20:12.077
MADE GENERAL AVAILABILITY WITH A
01:20:12.077 --> 01:20:13.348
PERSONALIZED SUPPORT. PERSONALIZER
01:20:13.348 --> 01:20:15.004
IS THE INDUSTRY'S FIRST A. I. SERVICE
01:20:15.004 --> 01:20:17.229
BASED ON REINFORCEMENT LEARNING.
01:20:17.229 --> 01:20:19.687
NOW THIS SOLUTION'S ACTUALLY BEING
01:20:19.687 --> 01:20:21.694
USED ALREADY INSIDE OF MICROSOFT
01:20:21.694 --> 01:20:24.380
TODAY. XBOX IS DELIVERING THE SIX
01:20:24.380 --> 01:20:25.600
MILLION PERSONALIZED EXPERIENCES
01:20:25.600 --> 01:20:29.888
FOR ITS USER EVERY SINGLE DAY. WE
01:20:29.888 --> 01:20:31.426
CONTINUE TO ADD NEW CAPABILITIES
01:20:31.426 --> 01:20:33.381
INTO SPEECH, AS WELL, INCLUDING
01:20:33.381 --> 01:20:35.106
CUSTOM NEURAL VOICE. ALLOWS YOU
01:20:35.106 --> 01:20:36.819
TO CREATE PERSONALIZED VOICES THAT
01:20:36.819 --> 01:20:38.952
MATCH YOUR BRAND, THAT CAN USE DEEP
01:20:38.952 --> 01:20:40.826
NEURAL NETS IN ORDER TO DO THE TRAINING
01:20:40.826 --> 01:20:43.608
OF THE AUDIO AND THE WORK FOR THAT.
01:20:43.608 --> 01:20:45.902
YOU CAN PLUG IT IN WITH OFFICE 365,
01:20:45.902 --> 01:20:47.136
AND WHATEVER TERMINOLOGY THAT YOU
01:20:47.136 --> 01:20:50.183
HAVE. NOW MY TEAM HAS A LOT OF THREE-LETTER
01:20:50.183 --> 01:20:51.672
ACRONYMS. ANYBODY ELSE? JUST ME?
01:20:51.672 --> 01:20:53.785
WHAT'S THE DEAL? OKAY. MY TEAM USES
01:20:53.785 --> 01:20:57.240
A LOT OF TLAS. YOU THINK ABOUT THE
01:20:57.240 --> 01:20:59.200
DOCUMENTS AND TERMNOLOGIST, SOMETIMES
01:20:59.200 --> 01:20:59.975
SPEECH TO TEXT DOESN'T UNDERSTAND
01:20:59.975 --> 01:21:01.930
WHAT THAT MEANS. WITH OFFICE 365,
01:21:01.930 --> 01:21:03.295
THAT KIND OF INTEGRATION, WE CAN
01:21:03.295 --> 01:21:05.366
DO A GREAT JOB ON THAT. NOW LET'S
01:21:05.366 --> 01:21:07.802
TAKE A LOOK AT SOME OF THE BENEFITS
01:21:07.802 --> 01:21:09.772
THAT A CUSTOMER HAS GOTTEN BY LEVERAGING
01:21:09.772 --> 01:21:11.906
THESE SPEECH APIS TO CREATE BRAND-NEW
01:21:11.906 --> 01:21:16.260
FEATURES. LET'S RUN THE VIDEO. >>
01:21:16.260 --> 01:21:20.472
THE MISSION HAS ALWAYS BEEN ABOUT
01:21:20.472 --> 01:21:21.865
HELPING MILLIONS OF CREATORS TO
01:21:21.865 --> 01:21:24.054
LIVE OFF THEIR WORK. THE SOUND TRAP
01:21:24.054 --> 01:21:27.116
IS PART OF THAT MISSION. NOW WE'RE
01:21:27.116 --> 01:21:31.373
LAUNCHING STORY TELLERS FOR COLLABORATIVE
01:21:31.373 --> 01:21:49.273
PODCAST CREATION. YOU CAN CUT AND
01:21:49.273 --> 01:21:50.543
PASTE AND MOVE THINGS AROUND AND
01:21:50.543 --> 01:21:52.795
AUTOMATICALLY CUT AND PASTE FOR
01:21:52.795 --> 01:21:57.259
YOU. >> WE ARE EUROZONIE USING AZURE
01:21:57.259 --> 01:22:00.752
COGNITIVE SERVICES. WE NEEDED A
01:22:00.752 --> 01:22:02.691
PARTNER THAT COULD PROVIDE THE HIGHEST
01:22:02.691 --> 01:22:05.435
QUALITY POSSIBLE. >> WE WANTED SOMETHING
01:22:05.435 --> 01:22:09.718
SIMPLE TO USE. LET'S DEMOCRATSIZE
01:22:09.718 --> 01:22:14.076
STORAGE TOGETHER. >> THAT WAS A
01:22:14.076 --> 01:22:16.661
GREAT EXAMPLE OF BEING ABLE TO USE
01:22:16.661 --> 01:22:18.408
THE BUILT-IN SUPPORT. WE'VE ADDED
01:22:18.408 --> 01:22:19.373
SUPPORT OUTSIDE OF SPEECHES WELL
01:22:19.373 --> 01:22:21.316
INTO KNOWLEDGE MINING WITH COGNITIVE
01:22:21.316 --> 01:22:22.774
SEARCH. AND THIS CASE YOU CAN TAKE
01:22:22.774 --> 01:22:23.904
ALL SORTS OF DIFFERENT TYPES OF
01:22:23.904 --> 01:22:25.305
DOCUMENTS THAT YOU HAVE OUT THERE.
01:22:25.305 --> 01:22:27.584
WHETHER I'VE GOTTEN THE FACE, IMAGES,
01:22:27.584 --> 01:22:30.279
TEXT, I WANT TO EXTRACT KNOWLEDGE
01:22:30.279 --> 01:22:32.015
FROM THAT. WE CAN INGEST ALL OF
01:22:32.015 --> 01:22:33.973
THOSE TYPES OF COMMENTS INTO THE
01:22:33.973 --> 01:22:36.379
SERVICE, AND WE CAN ENRICH IT WITH
01:22:36.379 --> 01:22:37.917
BUILT-IN MODELS SO YOU CAN GET GOING
01:22:37.917 --> 01:22:39.753
RIGHT AWAY. YOU CAN EXPLORE THE
01:22:39.753 --> 01:22:40.566
IMEFB SEARCH EXPERIENCE THAT COMES
01:22:40.566 --> 01:22:42.044
WITH THAT, AND OF COURSE, YOU'VE
01:22:42.044 --> 01:22:45.344
GOT PROBABLY A TON OF OFFICE 365
01:22:45.344 --> 01:22:47.575
DATA AND OTHER ASSETS AT YOUR COMPANY.
01:22:47.575 --> 01:22:49.726
SOW BEING ABLE TO KNOWLEDGE MIND
01:22:49.726 --> 01:22:52.168
IS AN IMPORTANT KEY FEATURE AND
01:22:52.168 --> 01:22:56.134
CAPABILITY. NOW THOSE ARE OF THE
01:22:56.134 --> 01:22:57.259
BUILT-IN PIECES OF DEMOCRAT CRATIZE.
01:22:57.259 --> 01:22:58.959
AT THE SAME TIME, THERE ARE CASES
01:22:58.959 --> 01:23:00.287
WHEN YOU WANT TO DO THE MACHINE
01:23:00.287 --> 01:23:01.729
LEARNING YOURSELF. THAT'S WHERE
01:23:01.729 --> 01:23:01.730
WE'VE CREATED AZURE MACHINE LEARNING.
01:23:01.730 --> 01:23:04.976
WE'VE DESIGNED IT IN A WAY THAT
01:23:04.976 --> 01:23:07.269
YOU CAN START OFF AT ANY SKILL LEVEL.
01:23:07.269 --> 01:23:08.506
WE ALSO ARE MAKING SURE WE HAVE
01:23:08.506 --> 01:23:11.178
THE BEST TOOL CHAIN IN THERE WITH
01:23:11.178 --> 01:23:13.958
ML OPS. AND IT'S INTEROPERABLE.
01:23:13.958 --> 01:23:15.268
SO WHATEVER YOUR FAVORITE FRAMEWORK
01:23:15.268 --> 01:23:17.667
IS, YOUR FAVORITE TOOLS, YOU CAN
01:23:17.667 --> 01:23:24.405
INCORPORATE IT INTO THE SYSTEM.
01:23:24.405 --> 01:23:26.488
ONE OF THE IMPORTANT THING IN OPS
01:23:26.488 --> 01:23:28.702
IS SETTING UP THE CIDC PIPELINE.
01:23:28.702 --> 01:23:29.993
THIS IS WITH DATA SCIENTISTS, I.
01:23:29.993 --> 01:23:32.592
T. DEVELOPERS AND PROESHLS. THE
01:23:32.592 --> 01:23:33.524
OPS ENABLES US TO WORK TOGETHER
01:23:33.524 --> 01:23:34.970
IN THE SAME WAY THAT YOU'RE FAMILIAR
01:23:34.970 --> 01:23:37.892
WITH WITH THE CICD PIPELINE. WE
01:23:37.892 --> 01:23:42.436
CAN CREATE MODELS AND VERIFY THE
01:23:42.436 --> 01:23:43.103
REPRODUCIBILITY, DO VALIDATION,
01:23:43.103 --> 01:23:44.697
DO DEPLOYMENT. AND AS NEW DATA COMES
01:23:44.697 --> 01:23:46.220
IN AND WE CONTINUE TO DO TRAINING
01:23:46.220 --> 01:23:47.600
AND RETRAINING UNTIL WE GET THE
01:23:47.600 --> 01:23:50.190
RIGHT RESULTS THAT WE WANT. WE WANT
01:23:50.190 --> 01:23:53.972
TO MAKE SURE THAT WE'VE GOT THAT
01:23:53.972 --> 01:23:55.411
INVESTMENT ACROSS ALL TYPES OF ROLES
01:23:55.411 --> 01:23:56.698
AND THEY CAN WORK WELL TOGETHER.
01:23:56.698 --> 01:23:58.312
THAT GIVES US THE SAME SOLUTION
01:23:58.312 --> 01:23:59.657
THAT'S WE HAVE WITH DEVOPS TODAY
01:23:59.657 --> 01:24:02.677
BUT WITH MACHINE LEARNING OPS. IF
01:24:02.677 --> 01:24:04.760
YOU LOOK AT ALL THESE INVESTMENTS
01:24:04.760 --> 01:24:06.667
THAT WE'VE SHOWN TODAY FROM DATA
01:24:06.667 --> 01:24:08.747
AND WORKLOADS, ET CETERA, THEY'RE
01:24:08.747 --> 01:24:12.131
ALL FOR ENABLING BRAND-NEW SCENARIOS.
01:24:12.131 --> 01:24:14.146
REALLY COMPELLING AND INTERESTING
01:24:14.146 --> 01:24:15.144
SCENARIOS AND VERY EXCITED ABOUT
01:24:15.144 --> 01:24:17.338
WHAT WE CAN DO WITH THAT. LET'S
01:24:17.338 --> 01:24:21.388
TAKE A LOOK AT SOME FINAL EXAMPLES.
01:24:21.388 --> 01:24:24.628
>> LIKE NEVER BEFORE. OUR WORLD
01:24:24.628 --> 01:24:26.727
IS CHANGING. FACE WEDNESDAY SOME
01:24:26.727 --> 01:24:29.827
OF OUR MOST CRITICAL CHALLENGES,
01:24:29.827 --> 01:24:34.768
HUMAN INGENUITY TRIUMPHS. TODAY,
01:24:34.768 --> 01:24:36.876
THE MICROSOFT A. I. FOR GOOD INITIATIVE
01:24:36.876 --> 01:24:39.611
ENABLES A PERSON WITH AN IDEA TO
01:24:39.611 --> 01:24:42.175
ACCELERATE IT, TO GIVE IT SCALE,
01:24:42.175 --> 01:24:45.212
TO CREATE CHANGE FOR THE BETTER.
01:24:45.212 --> 01:24:46.728
>> MICROSOFT ALE. WILL HELP OUR
01:24:46.728 --> 01:24:49.371
WORK BY EMPOWERING PEOPLE TO TAKE
01:24:49.371 --> 01:24:51.096
ACTION. >> THROUGH ALE. FOR EARTH,
01:24:51.096 --> 01:24:54.542
PHOTOS CAN HELP SAVE A SPECIES.
01:24:54.542 --> 01:24:56.316
WITH A. I. FOR ACCESSIBILITY, THE
01:24:56.316 --> 01:25:00.324
VISUAL WORLD BECOMES AN AUDIBLE
01:25:00.324 --> 01:25:02.853
EXPERIENCE. WITH A. I. FOR HUMANITARIAN
01:25:02.853 --> 01:25:04.795
ACTION, FIRST RESPONDERS CAN TARGET
01:25:04.795 --> 01:25:07.645
THEIR EFFORTS FASTER THAN EVER BEFORE.
01:25:07.645 --> 01:25:10.454
>> IT FEELS HUMBLING TO KNOW THAT
01:25:10.454 --> 01:25:13.357
I'M ACTUALLY HELPING ANOTHER HUMAN
01:25:13.357 --> 01:25:16.037
BEING. >> TODAY WE ARE EMPOWERING
01:25:16.037 --> 01:25:18.252
OTHERS TO FORGE NEW PATHS, TO FIGHT
01:25:18.252 --> 01:25:21.012
FAMINE BEFORE CRISIS STRIKES AND
01:25:21.012 --> 01:25:23.736
PROTECT ECOSYSTEMS BY IDENTIFYING
01:25:23.736 --> 01:25:25.473
FORESTS DOWN TO A SINGLE TREE. >>
01:25:25.473 --> 01:25:26.895
WE HAVE THE FOREST THAT WE HAVE
01:25:26.895 --> 01:25:28.645
TODAY. WE CAN'T CHANGE THAT. WHAT
01:25:28.645 --> 01:25:31.119
WE CAN CHANGE IS THE FUTURE. >>
01:25:31.119 --> 01:25:32.331
MICROSOFT A. I. IS FUELING SOME
01:25:32.331 --> 01:25:34.615
OF THE MOST PASSIONATE AND CREATIVE
01:25:34.615 --> 01:25:36.953
PEOPLE ON OUR PLANET WITH THE HELP
01:25:36.953 --> 01:25:39.603
OF CITIZEN SCIENTISTS TO MAKE CHANGE
01:25:39.603 --> 01:25:42.320
ONCE THOUGHT IMPOSSIBLE REAL. >>
01:25:42.320 --> 01:25:45.270
A. I. WILL KNOW AND UNDERSTAND AND
01:25:45.270 --> 01:25:47.355
MODEL BASED ON THE INTERACTION.
01:25:47.355 --> 01:25:49.414
A. I. UNLEASHES NEW POSSIBILITIES
01:25:49.414 --> 01:25:51.611
TO IMPACT OUR WORLD. AND TOGETHER,
01:25:51.611 --> 01:25:56.026
WE'RE NOT JUST DREAMING IT, WE'RE
01:25:56.026 --> 01:26:01.949
DOING IT. >> I THINK THOSE WERE
01:26:01.949 --> 01:26:03.159
EXCITING SCENARIOS. I HOPE THAT
01:26:03.159 --> 01:26:05.328
TODAY YOU'VE SEEN ALL THE NEW TECHNOLOGY
01:26:05.328 --> 01:26:07.753
THAT WE'RE BRINGING TO YOU. WE CAN'T
01:26:07.753 --> 01:26:09.011
WAIT TO SEE WHAT YOU'RE GOING TO
01:26:09.011 --> 01:26:10.739
DO WITH IT. WE'VE GOT A FANTASTIC
01:26:10.739 --> 01:26:12.319
SHOW. THE ENGINEERING TEAM LIKE
01:26:12.319 --> 01:26:14.590
I MENTIONED, WE'RE HERE, WE'RE ENGAGED,
01:26:14.590 --> 01:26:15.676
WE WANT TO HEAR YOUR FEEDBACK. HAVE
01:26:15.676 --> 01:26:15.677
A GREAT CONFERENCE.THANK YOU SO MUCH.