MY NAME IS FABIAN. WITH ME HERE 
ON STAGE, MY FRIEND AND COLLEAGUE 
WILL. WE'RE PROGRAM MANAGERS FOR 
AZURE FILES AND AZURE FILES SYNC. 
I'M DELIGHTED HOW MANY OF YOU PEOPLE 
SHOW UP HERE ON A FRIDAY AFTERNOON, 
THE LAST DAY, LAST SLOT OF THE SHOW. 
THAT'S PRETTY COOL.
THANK YOU, EVERYBODY, FOR BEING 
HERE. SO WE ACTUALLY HAVE A VERY 
FULL PROGRAM. 45 MINUTES ISN'T A 
LOT OF TIME, SO LET'S DIVE RIGHT 
IN. I WANT TO TALK A LITTLE BIT 
TO YOU ABOUT AZURE FILE, WHAT'S 
NEW, WHAT HAVE WE DONE IN THE LAST 
YEAR, WHAT ARE WE GOING TO DO IN 
THE NEXT COUPLE OF MONTHS. BEFORE 
WE DO THART, I WANT TO TOUCH QUICKLY 
ON WHAT AZURE FILE SHARES ARE. SOME 
OF YOU ARE FAMILIAR WITH THEM, SOME 
OF YOU I'VE KIND OF TALKED TO YOU 
IN THE AUDIENCE SO FAR SO I KIND 
OF GET THE FEELING THAT THERE ISN'T 
KNOWING ABOUT THEM IN DETAIL SO 
I'LL JUST DIVE RIGHT IN. AN AZURE 
FILE SHARE IS A FULLY MANAGED SHARE 
IN AZURE. IT'S BASICALLY A PLATFORM 
AS A SERVICE OFFERING THAT MICROSOFT 
HAS WHERE YOU GO TO THE AZURE MARKETPLACE, 
DEPLOY A STORAGE ACCOUNT AND INSIDE 
YOU HAVE FILE SHARES. NO NEED FOR 
VM, NO NEED TO PATCH, UPDATE, CONFIGURE 
STORAGE. ALL THIS IS TAKEN CARE 
OF. YOU JUST GET A FILE SHARE. ON 
PREMISE FOR INSTANCE, ON A CLIENT 
I CAN USE THE S AND B PROTOCOL AND 
ACCESS MY FILE SHARE AS I WOULD 
ANY OTHER FILE SHARE. I CAN ALSO 
TUNNEL THIS THROUGH A VPN. WE ALSO 
HAVE AZURE FILE SIYNC. IT USES A 
DIFFERENT PROTOCOL AND USING 443. 
AS PAFRT OF THE SESSION WE'RE ALSO 
GOING TO ANNOUNCE NFS 4. 1 FOR FILE 
SHARES. THIS IS A REALLY GOOD OFFERING 
THAT WE WANT TO GIVE YOU A SNEAK 
PEEK AND WILL HAS A GREAT DEMO IN 
JUST A MOMENT. ALL THE PROTOCOLS 
THAT YOU CAN USE FROM ON PREMISE, 
OF COURSE YOU CAN USE THEM IN AN 
IS SOLUTION AS WELL OR IF YOU LIKE 
TO BUILD A PLATFORM AS A SERVICE 
APPLICATION, THE REST PROTOCOL IS 
AVAILABLE SO YOU CAN GO AHEAD AND 
USE THAT. NOW THAT WE KNOW WHAT 
IT IS, WHAT CAN YOU DO WITH THEM? 
THEY'RE PRETTY MUCH S&P SHARES. 
USE THEM FOR WHAT YOU USE TODAY. 
THE TWO MAIN SCENARIOS ARE FOR US, 
UPLIFT AND SHIFT. YOU TAKE YOUR 
PREMISE APP, LIFT IT TO THE CLOUD, 
PUT IT IN A VM AND IF YOUR APP REQUIRES 
AN S AND B ACCESS, IF YOU WANT TO 
MOUND A FILE SHARE TO VM JUST AS 
YOU WOULD ON PREMISE, YOU CAN DO 
THAT WITH AN AZURE FILE SHARE, NO 
PROBLEM. THE OTHER SCENARIO IS THE 
GENERAL PURPOSE FILE SCENARIO. IN 
THE GENERAL PURPOSE SCENARIO WE 
ARE BASICALLY LOOKING AT OFFICE 
DOCUMENTS, CAT DRAWINGS. WE'RE LOOKING 
AT VDI INFRASTRUCTURE THAT YOU WANT 
TO RUN IN THE CLOUD SO YOU CAN USE 
AN AZURE FILE SHARE THERE. OF COURSE 
WE WILL OFFER YOU WITH AZURE FILE 
SYNC AN ON PREMISES WHERE YOU NEED 
IT. LET'S QUICKLY TOUCH BASE ON 
WHAT AZURE FILE SYNC IS. WE RELEASED 
THAT SERVICE ABOUT TWO YEARS AGO. 
IT'S AN IN-MARKET OFFERING. YOU 
CAN USE IT TODAY. AZURE FILE AND 
AZURE FILE SYNC BASICALLY HAS TO 
FILE SHARE IN ITS CENTER AND YOU 
WILL BE ABLE TO DO MULTIPLE ON-PREMISE 
SERVICE. IF YOU'RE AT HEADQUARTERS 
AND THE SERVER IS IN BRANCH OFFICE, 
YOU CAN INSTALL THE AZURE FILE SYNC 
AGENT AND YOU'LL BE ABLE TO CONNECT 
TO AN AZURE FILE SHARE. OF COURSE 
YOU CAN CONNECT A SINGLE SERVER 
TO MANY FILE SHARES JUST AS YOU 
NEED. WE ALSO JUST WORK ON A FILE 
SERVER WHICH MEANS ALL THE STUFF 
YOU USE THE FILE SERVER FOR TODAY 
JUST TRANSPARENTLY KEEP WORKING. 
IF YOU'RE SHARING ACCESS WITH YOUR 
USERS AND APPLICATIONS, YOU CAN 
LET THEM CONNECT TO THE FILE SERVER 
AS THEY DO TODAY AND AS AN ADMIN 
YOU USE FILE SYNC AND NOTHING IS 
DIFFERENT TO THE USER. ANOTHER IMPORTANT 
ASPECT IS CLOUD TIERING. WE'RE STARTING 
TO TRANSFORM YOUR SERVER INTO SOMETHING 
VERY DIFFERENT. BASICALLY WE'RE 
TRANSFORMING IT FROM THE STORAGE 
HUNGRY BEAST WHERE EVERY YEAR YOU 
HAVE TO BUY NEW DISCS, ADD NEW STORAGE 
TO YOUR FILE SERVER BECAUSE YOUR 
DATA SET IS GROWING. YOU CAN NOW 
WITH CLOUD TIERING EVALUATE ON YOUR 
NAME SPACE AND FIGURE OUT WHAT ARE 
THE HOT FILES, WHICH FILES SHOULD 
YOU KEEP ON PREMISES, WHICH FILES 
SHOULD YOU TIER TO THE CLOUD. YOUR 
SERVER IS GOING TO BUILD A HEAT 
MAP AND IT DOES EXACTLY THAT USING 
THE LAST -- TRACKS ACCESS, FREQUENCY 
OF ACCESS AND BUILDS THE MAP THAT 
WAY. OVER TIME IF YOUR SERVER RUNS 
OUT OF SPACE, PRIORITIZES HOT DATA 
TO KEEP IN YOUR LOCAL CACHE AND 
TIERS THE COLD DATA TO THE CLOUD. 
ANOTHER IMPORTANT ASPECT IS BACK-UP. 
NOW THAT YOU'RE SYNCING ALL OF YOUR 
FILE SHARES TO THE CLOUD, YOU NO 
LONGER HAVE TO BACK UP ON PREMISES 
BECAUSE IF SYSTEM BACK-UP IS OFTEN 
NOT NECESSARY, YOU CAN JUST HAVE 
A SYSTEM IMAGE LYING AROUND, REBUILD 
YOUR SERVER NO PROBLEM BUT WHAT 
ABOUT THE DATA? THE DATA SITS IN 
THE AZURE FILE SHARE AND YOU CAN 
PROTECT THAT VIA AZURE BACK-UP AND 
MANY OTHER BACK-UP VENDORS THAT 
YOU MIGHT BE FAMILIAR WITH OR MIGHT 
BE HAVING EXISTING RELATIONSHIPS 
WITH. 
SO WHAT ABOUT DISASTERS? WELL, WE'VE 
BUILT A PERFORMANCE CACHE. THE DATA 
SITS IN THE CLOUD. THAT DOESN'T 
REALLY -- WE DON'T REALLY LOSE ANYTHING 
WHEN WE LOSE THE SERVER. WITH FAST 
DISASTER RECOVERY, YOU CAN BRING 
IN A BRAND NEW SERVER, BRAND NEW 
STORAGE, NOTHING ON IT, AND THE 
FIRST THING THAT HAPPENS WHEN YOU 
CONNECT IT TO FILE SHARE IS THE 
WHOLE NAME SPACE COMES DOWN, JUST 
THE NAME SPACE, NONE OF THE FILE 
CONTENT. THAT MAKES THE WHOLE SERVER 
AVAILABLE TO YOUR USERS VERY, VERY 
QUICKLY SO YOU DON'T HAVE TO WAIT 
UNTIL A WHOLE RESTORE HAPPENED OR 
A WHOLE DOWNLOAD OF ALL YOUR DATA 
HAPPENED. YOU CAN BASICALLY OPEN 
UP THE SERVER FOR CONSUMPTION RIGHT 
AWAY. AS YOUR USERS DO THAT, YOUR 
CACHE IS STARTING TO FORM AND WE'RE 
STARTING TO SEE WHICH FILES ARE 
HOT AND THESE THINGS ARE JUST BEING 
CACHED. SO LET'S TALK ABOUT WHAT'S 
NEW IN AZURE FILE SHARES SINCE OUR 
LAST IGNITE PRESENTATION. THERE'S 
A LOT OF STUFF THAT HAS HAPPENED 
SO I WANT TO START WITH A VERY, 
VERY IMPORTANT ASPECT OF AZURE FILE 
SYNC WHICH IS WE'VE GROWN THE FILE 
SHARE SIZE FROM 5 TERABYTES TO 100 
PER FILE SHARE. RIGHT NOW IT'S AVAILABLE 
IN 14 REGIONS AND WE KEEP ROLLING 
THIS OUT ACROSS THE WORLD. IT'S 
AN OPT IN SO YOU CAN TRANSFORM YOUR 
EXISTING TERABYTE SHARE TO 100 TERABYTE 
SHARE BUT IT'S AN OPT IN. YOU HAVE 
TO DO THAT MANUALLY. WHEN YOU DO 
OPT IN YOU ALSO GET HIGHER PERFORMANCE. 
WE'RE INCREASING PERFORMANCE FOR 
OUR STANDARD STORAGE OFFERING. SPEAKING 
OF STANDARD, WE ALSO HAVE A PREMIUM 
TIER FOR AZURE FILE SHARES AND THAT 
ONE GOES UP TO 100, 000 I OPS AND 
IT'S A REALLY GOOD PLACE FOR YOU 
TO RUN DATABASE APPLICATIONS OR 
APPLICATIONS THAT HAVE BURSTING 
BEHAVIOR FOR INSTANCE. LAST BUT 
NOT LEAST, WE HAVE AZURE ACTIVE 
DIRECTOR THROUGH MAIN SERVICES INTEGRATION 
WHICH WE GA'ED A COUPLE WEEKS AGO. 
THERE'S NO NEED TO SET IT UP IF 
YOU DON'T HAVE ANOTHER USE FOR IT 
BECAUSE WILL IS GOING TO SHOW YOU 
HOW YOU CAN DO INTEGRATION IN JUST 
A MOMENT. WHAT ARE THE NEW THINGS 
THAT WE'RE GOING TO TALK ABOUT IN 
AZURE FILE SHARES AT THIS SHOW? 
SO, THE FIRST THING I WANT TO MENTION 
IS WE ARE -- WE WANT TO CATER TO 
THE FILES IDEALLY SUITED TO BE STORED 
ON THE FILE SERVER SO WE NEED TO 
CONSIDER THE FILE SIZES THAT YOU 
CAN STORE ON AZURE FILE SHARES. 
WE INCREASED THAT RECENTLY FROM 
ONE TO FOUR TERABYTES PER FILE. 
WE'RE ALSO VERY CLOSE TO ANNOUNCE 
AZURE BACK-UP GA. THAT MEANS YOU 
CAN SCHEDULE YOUR SNAPSHOTS, GET 
HELP AND HAVE THE FULL FUNCTIONALITY 
OF THAT BACK-UP SOLUTION IF YOU 
WOULD LIKE TO SET THAT UP. WE'RE 
ALSO GOING TO TALK ABOUT AD JOIN 
AND WILL WILL HAVE THE DEMO IN A 
MOMENT SO I'LL LEAVE THAT FOR HIM 
TO TALK ABOUT, AS WELL AS NFS INTEGRATION. 
WILL HAS A GOOD DEMO FOR THIS TOO. 
SO WE'LL GO THERE IN A MOMENT. BEFORE 
I MOVE ON, THERE'S ONE MORE VERY, 
VERY IMPORTANT ANNOUNCEMENT THAT 
I WANT TO MAKE WHICH IS WE'RE GOING 
TO INTRODUCE ADDITIONAL TEIERS FOR 
FILE SHARES AND THEY WILL HELICOPTER 
YOU HELP YOU OPTIMIZE COST AND PERFORMANCE. 
SOME OF YOUR SHARES PROBABLY SEE 
HEAVY USAGE, SOME MIGHT BE VERY 
COLD. YOU SHOULD BE ABLE TO SELECT 
THE RIGHT STORAGE TIER IN AZURE 
TO YOU HAVE THE BEST COST PERFORMANCE 
RELATIONSHIP. WHEN WE CONSIDER THE 
SPECTRUM OF HIGH PERFORMANCE TO 
LOW COST, LONG-TERM STORAGE, WE 
HAVE OUR PREMIUM FILE SHARES THAT 
WE JUST TALKED ABOUT. THEY'RE REALLY 
GOOD FOR DATABASE OFFERINGS OR FOR 
STORING DATABASES OR HIGHER PERFORMANCE 
APPLICATION WORKLOADS. THEN WE ALSO 
HAVE OUR STANDARD SHARE THAT'S IN 
MARKET FOR A WHILE. STANDARD IN 
THE WAKE OF THESE NEW TIERS IS GOING 
TO GET RENAMED. WE'RE GOING TO GIVE 
IT A TYPICAL MICROSOFT NAME, TRANSACTION 
OPTIMIZED. IT REALLY IS A FITTING 
NAME BECAUSE IT IS OPTIMIZED FOR 
TRANSACTIONS. IF YOU HAVE AN APPLICATION 
WORKING AGAINST IT THAT DOESN'T 
QUITE NEED THE PERFORMANCE OF A 
PREMIUM SHARE, YOU'RE REALLY GOING 
TO GET A GOOD RELATIONSHIP BETWEEN 
STORAGE AT REST COST AND VERY, VERY 
LOW TRANSACTION COSTS. THE NEW TIERS 
THAT WE'RE GOING TO ANNOUNCE ARE 
HOT TIER AND A COOL TIER. SO THE 
HOT TIER IS REALLY SOMEWHERE IN 
THE MIDDLE. THE COOL TIER IS WHAT 
WE CALL AN ONLINE ARCHIVE. THERE'S 
NO RECALL DELAY. YOU CAN INSTANTLY 
OR EASILY SWITCH BETWEEN THOSE TIERS. 
SO YOU SELECT A TIER FOR YOUR ENTIRE 
SHARE AND ONCE THEY BECOME AVAILABLE 
YOU CAN GO TO THE AZURE PORTAL AND SAY 
MY EXISTING STANDARD FILE SHARE 
THAT I HAVE TODAY, I JUST WANT TO 
MAKE THAT A COOL SHARE AND YOU CAN 
DO THAT WITH THE CLICK OF A BUTTON. 
THERE WILL BE NO COPYING HAPPENING 
IN THE BACKGROUND, NO DOWN TIME. 
YOU CAN EASILY SWITCH BETWEEN THEM 
AND AS YOUR WORKLOAD REQUIREMENTS 
CHANGE, MAYBE YOU START WITH SOMETHING 
THAT'S VERY WARM, YOU MOVE TO COOL, 
OR YOU HAVE SOMETHING THAT'S COOL 
THAT SUDDENLY BECOMES MORE INTERESTING 
TO YOUR USERS AND APPLICATIONS, 
YOU CAN MOVE THAT UP THE TIER JUST 
TO MATCH THE COST AND PERFORMANCE 
EQUATION. SO WHEN WE TALK ABOUT 
PRICE, THE PREMIUM TIER THAT WE 
HAVE AT 24 CENTS IN THE U. S. PER 
GIGABYTE, YOUR TRANSACTION OPTIMIZED 
OR STANDARD TIER, WE SET AT 6 CENTS 
PER GIGABYTE. AND THE NEW TIERS, 
THE HOT TIER IS GOING TO REDUCE 
THE COST OF STORAGE AT REST BY MORE 
THAN HALF. AT 2. 55 CENTS, THIS 
IS A REALLY GOOD PRICE POINT WITH 
REASONABLE TRANSACTION COSTS. THEN 
WE HAVE OUR ONLINE ARCHIVE TIER, 
THE COOL TIER, AT JUST 1. 5 CENTS 
PER GIGABYTE AT REST. THAT IS A 
VERY, VERY GOOD PRICE FOR STORAGE. 
AND WE HAVE HIGHER TRANSACTION COSTS. 
SO THIS IS REALLY A QUESTION OF 
BALANCING YOUR ACCESS VERSUS YOUR 
STORAGE AT REST COSTS. SO, NOW THAT 
I HAVE COVERED SORT OF THE BASICS, 
I WANT TO GIVE IT OVER TO WILL. 
HE'S GOING TO TALK ABOUT HOW WE 
CAN DIRECTLY ACCESS THE FILE SHARE 
AND WHAT CHALLENGES WE CAN
SOLVE. 
>> THANKS, FABIAN. SO I JUST WANT 
TO TAKE A BRIEF MOMENT TO ECHO FABIAN. 
I THINK WE'RE SO EXCITED TO SEE 
ALL OF YOU HERE, LAST DAY OF THE 
SHOW. WHEN WE TALK ABOUT OUR FILE 
SHARE ACCESS -- WHAT I JUST SAID 
WAS THANK YOU FOR COMING. WE'RE 
EXCITED THAT YOU'RE HERE. WHEN WE 
TALK ABOUT DIRECT FILE SHARE ACCESS 
WE'RE THINKING ABOUT USING THAT 
SERVERLESS FILE SHARE DIRECTLY AGAINST 
THE FILE SHARE WITHOUT HAVING AN 
ON PREMISES SERVER. FILE SYNC, WE'VE 
SEEN A LOT OF GROWTH AND A LOT OF 
SATISFIED CUSTOMERS BUT WE DON'T 
WANT TO HAVE TO FORCE YOU TO USE IT. 
TODAY THERE ARE THREE MAIN WAYS, 
SO WE GIVE YOU THIS SHARED KEY OR 
WE OFTEN REFER TO IT AS THE STORAGE 
ACCOUNT KEY MECHANISM. BECAUSE THIS 
IS THE KIND OF THING THAT'S A SHARED 
PASSWORD EFFECTIVELY TO YOUR FILE 
SHARE, IT'S REALLY MORE FOR ADMIN 
USE BECAUSE YOU CAN GET INTO THE 
SHARE, YOU CAN CREATE, DELETE NEW 
SHARES, MODIFY ANY FILE. NOT IDEAL 
FOR THE ON-PREM USER SCENARIO. WITH 
SHARED ACCESS SIGNATURES WE GIVE 
YOU THE ABILITY TO DO SCRIPTING. 
THIS IS LETTING YOU SORT OF CON 
TRAIN YOUR STRAIN YOUR ACCESS BUT 
IT'S 
ACTUALLY ONLY A REST CONSTRUCT. 
AN END USER USING A REST API VIA 
POWER SHELL IS NOT WHAT MOST PEOPLE 
HAVE IN MIND WHEN THEY THINK REPLACING 
THE ON-PREM FILE SE SERVER. WE FOUND 
CUSTOMERS WANT A CORPORATE IDENTITY 
AND NOT JUST TO ANY ACTIVE DIRECTORY 
BUT SPECIFICALLY TO AN ACTIVE DIRECTORY 
THAT THEY DOMAIN JOIN THEIR LAPTOPS 
TO ON PREM. WE HAVE A DEMO OF THIS. 
LET ME SWITCH OVER. HERE'S MY STORAGE 
ACCOUNT AND INSIDE THIS STORAGE 
ACCOUNT I HAVE A FILE SHARE, PROJECT 
X, AND I'D LIKE TO USE MY CORPORATE 
IDENTITY TO ACCESS THIS FILE SHARE. 
LET ME JUMP OVER TO MY MAIN CONTROLLER 
HERE AND I HAVE THIS POWER MODULE 
THAT I'M GOING TO USE TO DOMAIN 
JOIN THE SHARE. I HAVE THIS COMMAND 
THAT WILL JOIN AZ STORAGE AND I'LL 
TYPE IN MY RESOURCE GROUP AND STORAGE 
ACCOUNT NAME. THIS IS HOW WE FIND 
THE FILE 
SHARE IN AZURE. THEN I 
JUST HIT ENTER. SO IN A COUPLE OF 
SECONDS HERE, YOU SEE I'VE CREATED 
A SERVICE ACCOUNT IN THE DOMAIN 
CONTROLLER. I CAN ACTUALLY VERIFY 
THIS BY SAYING AD USER, SO QUICKLY 
HERE WE HAVE THE IDENTITY. THIS 
IS THE STORAGE ACCOUNT NAME. IN 
A WAY WE'VE DONE THE OFF LINE DOMAIN 
JOIN PROCESS THAT YOU MAY BE FAMILIAR 
WITH IN WINDOWS. NOW THERE'S ONE 
FINAL STEP THAT I NEED TO DO WHICH 
IS GIVE A SHARE ACTLE SO I CAN ACCESS 
THE SHARE. I DO THAT THROUGH ACCESS 
CONTROL. I'M GOING TO CLICK ADD. 
ADD ASSIGNMENT. I'LL GIVE THE CONROLE 
OF THE ELEVATED CONTRIBUTOR WHICH 
IS THE SAME AS FULL CONTROL ON A 
WINDOWS FILE SHARE. THERE'S THE 
ELEVATED CONTRIBUTOR AND I'LL TYPE 
IN MY USER NAME. NOW THAT THE SHARE 
HAS BEEN CREATED, I CAN OPEN IT 
JUST LIKE I EXPECT. I'LL OPEN FILE 
EXPLORER AND I'LL TYPE OUT THE STORAGE 
ACCOUNT N NAME. FILE. CORE. WINDOWS. 
NET. HERE'S MY FILE SHARE. YOU SEE 
THAT IT DIDN'T ASK ME FOR A USER 
NAME AND PASSWORD. IT'S SINGLE SIGN-ON. 
IF I NAVIGATE THIS DIRECTLY LIKE 
YOU WOULD EXPECT I CAN SEE MY FILES 
AND EVEN OPEN A FILE. IN A WAY THIS 
IS REALLY SOLVING THE REPLACEMENT 
FOR WHAT YOU NEED FOR AN ON-PREM 
FILE SERVER. SO I THINK GIVEN HOW 
MANY FOLKS HAVE ASKED FOR THIS FEATURE, 
PROBABLY THE FIRST QUESTION THAT 
COMES TO MIND IS HOW DO I GET ACCESS. 
WE'RE GOING TO BE LAUNCHING A LIMITED 
PREVIEW FOR THIS. THERE'S THE SURVEY 
LINK THAT YOU'LL NEED TO FILL OUT. 
WE'LL HAVE THIS AT THE END SO DON'T 
WORRY SO MUCH ABOUT TAKING A QUICK 
SCREEN SHOT. THEN WE'LL DO A BROAD 
PREVIEW VERY SOON, SO HOPEFULLY 
BY THE END OF THE YEAR OR VERY EARLY 
NEXT YEAR WE'LL BE IN BROAD PUBLIC 
PREVIEW SO YOU CAN DO IT WITHOUT 
HAVING TO DO THE SIGNUP. [ APPLAUSE 
] THANK YOU. NOW THAT WE'VE BROUGHT 
THIS TO THE TABLE, REPLACING THE 
ON-FILE SERVER IS A PRACTICAL THING 
THAT WE CAN DO. THE FIRST THING 
YOU WANT TO BE ABLE TO DO IS MOUNT 
THE FILE SHARE ON PREMISES. IF YOU'VE 
BEEN IN THE GAME A LITTLE BIT YOU 
MIGHT KNOW THAT PROBABLY MOST CUSTOMERS 
AND MOST ISP S DON'T LET PORT 4-5 
BE OPEN AND THIS IS TO PROTECT AGAINST 
THE OLDER PROTOCOLS. I'D LIKE TO 
POINT TO NED IN THE FRONT ROW. NED 
WILL TELL YOU YOU SHOULD NOT BE 
USING OLDER PROTOCOLS BUT EVEN THOUGH 
WE GIVE YOU WAYS TO DISABLE THESE, 
NETWORK SECURITY ADMINS ARE VERY 
CONCERNED THAT THEY EXIST SO BLOCK 
PORT 4-5 OUT OF ABUNDANCE OF CAUTION. 
YOU'RE NOT GOING TO GET AROUND THAT. 
ARGUING WITH YOUR NETWORK SECURITY 
ADMIN IS PROBABLY LIKE ARGUING WITH 
A BRICK WALL SO YOU NEED A WAY TO 
GET THROUGH THE 445 TO TUNNEL AROUND 
IT. TO DO THAT YOU WANT TO BE ABLE 
TO USE VPN. AZURE OFFERS THREE BIG 
VPN SOLUTIONS. OBVIOUSLY POINT TO 
SITE, SO THIS IS GREAT FOR THE ROAD 
WARRIOR AND YOU NEED ACCESS TO YOUR 
FILE SHARE. THE SITE TO SITE WHICH 
IS FOR THE BRANCH OFFICE OR THE 
MAIN OFFICE WHERE YOU DON'T NECESSARILY 
WANT TO HAVE TO GO PUSH THE INDIVIDUAL 
POINT TO SITE VPN CONNECTION TO 
EACH COMPUTER TO BE ABLE TO GET 
ACCESS TO YOUR FILE SHARE. AND OBVIOUSLY 
EXPRESS ROUTE WHERE YOU HAVE A DIRECT 
CONNECTION BETWEEN YOUR ON-PREMISES 
DATA CENTER AND YOUR V NET AND THE 
CLOUD. IF YOU'VE BEEN AROUND THE 
BLOCK A LITTLE BIT WITH AZURE NETWORKING, 
YOU MAY ALREADY SORT OF SEE THIS, 
BUT IF YOU'RE NEW TO AZURE FILES YOU MAY 
NOT, WHICH IS BY DEFAULT, AZURE 
FILES AS FABIAN MENTIONED IS A PLATFORM 
AS A SERVICE OFFER SO OUR SOLUTION 
IS OPEN TO THE INTERNET. WITH AN 
AUTHENTICATED CREDENTIAL, THE STORAGE 
ACCOUNT KEY OR THE IDENTITY WHEN 
YOU'RE LOGGING INTO YOUR FILE SHARE, 
YOU CAN GET AT THIS STORAGE ACCOUNT 
FROM ANYWHERE. A LOT OF CUSTOMERS 
DON'T WANT THAT AND SPECIFICALLY 
IF I'M TUNNELLING INTO MY NETWORK, 
I WANT TO BE ABLE TO OPEN TO JUST 
MY RESOURCES. THE NETWORKING TEAM 
IS GIVEN TWO MAIN CONTRACTS THAT 
HELP CONTROL THIS, THE SERVICE END 
POINT CONSTRUCT WHICH LOGICALLY 
PUTS YOUR STORAGE ACCOUNT INSIDE 
OF A V NET. YOU STILL HAVE THE PUBLIC 
IP, STILL HAVE THE PUBLIC DNS BUT 
ONLY REQUESTS COMING FROM INSIDE 
THAT V NET, INSIDE ONE OF THE SUB 
NETS THERE, ARE GOING TO BE ACCEPTED. 
EVEN WITH THE AUTHENTICATION COMING 
IN, UNLESS YOU'RE COMING FROM WITHIN 
THAT V NET, YOU WOULDN'T BE ABLE 
TO GET ACCESS TO THE STORAGE ACCOUNT. 
THE OTHER BIG ONE IS PRIVATE END 
POINT. THIS IS NEW WITHIN THE LAST 
COUPLE OF WEEKS. MANY OF YOU HAVE 
GONE TO THE SESSION ON PRIVATE END 
POINTS AND PRIVATE LINKS AND BASICALLY 
THIS IS SORT OF THE INVERSE OF THE 
SERVICE END POINT. YOUR STORAGE 
ACCOUNT IS STILL TECHNICALLY OUTSIDE 
OF THE V NET BUT IT HAS ACTUALLY 
A VIRTUAL NETWORK INTERFACE INSIDE 
ONE OF YOUR SUB NETS THAT CAN BE 
ACCESSED FROM THAT INSIDE OF THAT 
V NET WITH THE IPS ADDRESS THAT 
YOU SEE ON THE DIAGRAM. YOU WANT 
TO ACTUALLY COMBINE THESE TWO THINGS, 
RESTRICT YOUR V NET, RESTRICT YOUR 
STORAGE ACCOUNT TO A V NET AND PROVIDE 
A PRIVATE IP TO IDENTIFY THE STORAGE 
ACCOUNT AND THEN YOU CAN SET UP 
A VPN. I'VE GOT A QUICK DEMO OF 
THAT AS WELL. BEFORE THE SESSION 
ON THIS VM I HAD BLOCKED PORT 445 
AND RUN MY TEST AGAINST THE STORAGE 
ACCOUNT THAT I USED IN THE LAST 
DEMO. SO NOW I WANT TO ACTUALLY 
SET UP THE VPN. I'VE GOT THIS HANDY 
SCRIPT THAT I'VE MADE THAT DOES 
ALL THE STEPS, SO THIS GOES AND 
GRABS ALL THE STUFF AND SETS IT 
UP THE WAY THAT WINDOWS EXPECTS. 
THIS ISN'T HIDDEN THOUGH. WE HAVE 
A DOC THAT EXPLAINS HOW TO DO THIS. 
I LITERALLY COPIED THESE STEPS INTO 
THE SCRIPT. YOU SEE HERE I HAVE 
SITE TO SITE VPN, POINT TO POINT 
FOR WINDOWS AND LYNN IX AND WE'LL 
PROVIDE THE INFORMATION AFTER THE 
SESSION SO YOU CAN LEARN HOW 
TO DO THIS STEP BY STEP. I'LL RUN 
THIS SCRIPT, NAVIGATE TO MY DESKTOP 
AND QUICK RUN THE SCRIPT. AT A HIGH 
LEVEL WHAT'S HAPPENING WHEN I RUN 
THE SCRIPT IS THAT I'M CREATING 
A SERVICE END POINT FOR MY STORAGE 
ACCOUNT AND CONFIGURING WINDOWS 
TO USE THE ALWAYS ON VPN FUNCTIONALITY 
THAT EXISTS WITHIN WINDOWS. LOOKS 
LIKE THIS IS NOW DONE AND IF I ACTUALLY 
POP OPEN THE NETWORK INFORMATION 
I CAN CONNECT TO MY NEW VPN AND 
IT WORKED. NOW I'M GOING TO POP 
OVER TO MY STORAGE ACCOUNT AND SHOW 
YOU WHAT WE ACTUALLY DID. IF I CLICK 
INTO THE RESOURCE GROUP, YOU'LL 
SEE HERE'S MY RESOURCE GROUP AND 
MY STORAGE ACCOUNT. THEN YOU SEE 
I HAVE A PRIVATE END POINT AND THE 
NETWORK INTERFACE. REALLY YOU CAN 
THINK ABOUT THAT PRIVATE END POINT 
OBJECT AS CONNECTING YOUR STORAGE 
ACCOUNT AND YOUR VIRTUAL NETWORK 
INTERFACE THAT HAS YOUR IP ADDRESS. 
IF I CLICK INTO THAT YOU'LL SEE 
I HAVE THE IP ADDRESS. I'M GOING 
TO COPY AND PASTE THAT. QUICK COPY 
IT. NOW I'M GOING TO DO A ONE-TIME 
STEP THAT'S REQUIRED FOR THIS DEMO 
IN LIMITED PREVIEW. I'M ACTUALLY 
GOING TO ADD THIS TO MY HOST FILE 
AND THIS IS JUST A LIMITATION WITH 
HOW WE'VE DONE THE AUTHENTICATION 
IN THE PRIVATE PREVIEW OF THE AD 
FEATURE. WE WON'T REQUIRE THIS WHEN 
YOU GO TO PUBLIC PREVIEW. I'LL PASTE 
IN THE STORAGE ACCOUNT NAME. AND 
SAVE THE FILE. NOW IF I RUN THIS 
TEST NET CONNECTION YOU'LL SEE THAT 
IT ACTUALLY WORKS. LET ME TYPE IT 
OUT HERE. COMPUTER NAME. AND PORT 
445. GOOD. AND IT WORKS INSTANTLY 
AND YOU SEE THAT IT ACTUALLY WENT 
OVER THE VPN ADAPTER THAT I HAD 
JUST CREATED. BUT LET'S LOOK AT 
HOW THIS ACTUALLY WORKS IF I OPEN 
UP FILE EXPLORER. JUST LIKE I EXPECT, 
I CAN SELECT THE STORAGE ACCOUNT 
AND GO TO THE SHARE JUST LIKE I 
DID BEFORE AND EVERYTHING STILL 
WORKS. THIS IS GOING OVER MY VPN 
AND JUST LIKE BEFORE I CAN SEE MY 
FILES. [ APPLAUSE ] THANK YOU. SO 
HERE'S THE RESOURCES I MENTIONED. 
WE'LL HAVE THESE AGAIN AT THE END 
SO YOU CAN TAKE A QUICK SCREEN SHOT 
NOW BUT DON'T WORRY IF YOU MISS 
IT BECAUSE WE'LL HAVE IT IN A MINUTE 
AGAIN. THE FINAL THING I WANTED 
TO TALK ABOUT BEFORE I HAND THE 
MIC BACK TO FABIAN IS THE FACT THAT 
WE ARE ABLE TO DO THE APPLICATIONS. 
SO, ONE OF THE GREAT EXAMPLES OF 
THIS IS THIS IDEA OF RUNNING THE 
SQL SERVER OVER THE FILE SHARES 
MOUNTED OVER SMB AND THEY'VE SUPPORTED 
THIS FOR A VERY LONG TIME AGAINST 
A SCALE OUT FILE SERVER. NOW THEY'RE 
ALSO SUPPORTING IT AGAINST AZURE 
FILE SHARES PREMIUM FILE SHARES. 
ONE OF THE GREAT THINGS THAT THIS 
LETS YOU DO IS ENABLES REALLY EFFICIENT 
USE OF STORAGE BECAUSE NOT ONLY 
DOES PREMIUM FILE SHARE SUPPORT 
BURSTING, ALSO IT SUPPORTS EASY 
SCALE UP AND SCALE DOWN. SO YOU 
CAN IMAGINE A JOB THAT YOU'RE GOING 
TO RUN ONCE A WEEK, SCALE UP YOUR 
INSTANCE, RUN IT OVER THE WEEKEND 
AND THEN SCALE DOWN AT THE END AND 
LET IT SIT IN A SMALLER STATE SO 
YOU'RE NOT PAYING FOR A TON OF STORAGE. 
I'M NOT GOING TO DEMO THIS. I WOULD 
LOVE TO BUT WE DON'T HAVE TIME IN 
A 45-MINUTE SESSION. THERE'S THE 
LINK. IT'S IN OUR TABLE OF CONTENTS 
FOR AZURE FILE. THE FINAL THING 
I WANT TO TALK ABOUT IS REALLY THE 
LYNN IX APPLICATIONS. ONE OF THE 
THINGS WE FOUND, NO MATTER HOW GREAT 
S AND B IS, SOME OF THE CUSTOMERS 
JUST SAY, HEY, I CAN'T BECAUSE MY 
APP WAS WRITTEN FOR LOCAL FILE SYSTEM 
ON LYNN IX OR MAYBE I DON'T HAVE 
THE SOURCE CODE ANYMORE OR MAYBE 
MY THIRD PARTY PROVIDER DIDN'T CERTIFY 
IT FOR S AND B OR MAYBE I HAVE A 
HARD REQUIREMENT AND THE WIN 32 
BEHAVIOR YOU GET WITH AZURE FILE 
SHARE ISN'T ENOUGH. SO WE WANTED 
YOU TO BE ABLE TO EASILY MOVE THE 
CLOUD AND ADOPT THE CLOUD FOR THESE 
THINGS SO WE'RE PROVIDING SUPPORT. 
I HAVE A QUICK PREVIEW OF THIS THAT 
I WANT TO SHARE. LET ME FLIP TO 
MY PC HERE. I HAVE SSH'ED INTO A 
BOX IN THE CLOUD AND JUST TO PROVE 
IT I'LL QUICK SHOW YOU THAT THIS 
ISN'T ACTUALLY POWER SHELL LIKE 
IT LOOKS. THIS IS REAL LYNN IX. 
I'M GOING TO QUICK COPY IN MY INFORMATION 
THAT I NEED TO MOUNT THIS SO THE 
STORAGE ACCOUNT NAME FIRST. THE 
FILE SHARE NAME, AND I'LL PUT AS 
WELL THE MOUNT PATH UNDER THE MOUNT 
FOLDER. CREATE THAT. FINALLY I'LL 
COPY THE MOUNT COMMAND IN. THE MOUNT 
COMMAND WILL MOUNT THE FILE SHARE 
WITHIN NFS. PASTE IT, THERE WE GO. 
IT MOUNTED. NOW, ONE OF THE THINGS 
BEFORE I MOVE ON THAT I WANT TO 
POINT OUT IS IF YOU'VE DONE THIS 
FOR S AND B BEFORE, YOU WOULD HAVE 
PRESUMABLY USED THE STORAGE ACCOUNT 
KEY TO DO THIS AND YOU DON'T SEE 
A STORAGE ACCOUNT KEY IN THIS MOUNT 
COMMAND. THIS IS BECAUSE THE NFS 
IMPLEMENTATION ON AZURE FILES IS 
RELIANT ON THE VIRTUAL NETWORKS 
AND THE SERVICE END POINTS TO PROVIDE 
THE AUTH. NFS DOESN'T HAVE BUILT 
IN THE SAME AUTHENTICATION AND AUTHORIZATION 
THAT S AND B DOES. I CAN PROVE TO 
YOU QUICK THAT THIS IS ACTUALLY 
MOUNTED SO I'LL LOOK AT MY MOUNT 
AND IT APPEARS IN THE LIST. NOW 
LET'S START TO DO SOMETHING INTERESTING 
WITH IT. I'LL NAVIGATE TO THE MOUNT 
AND THIS IS A BRAND NEW FILE SHARE 
THAT I CREATED FOR THIS DEMO. I 
DON'T ACTUALLY HAVE ANY FILES IN 
IT YET. LET ME GO AHEAD AND CREATE 
A FILE. THERE I HAVE CREATED A FILE 
AND LET ME JUST CREATE A LINK TO 
THAT FILE. I'M GOING TO DO TWO INTERESTING 
THINGS HERE. FIRST I DID A HARD 
LINK. A HARD LINK IS A FEATURE THAT 
WE DON'T CURRENTLY SUPPORT FOR S 
AND B ON AZURE FILES. THEN THE SECOND 
INTERESTING THING THAT I DID WAS, 
IF YOU'LL NOTICE, I ACTUALLY DID 
AN UPPER CASE AND LOWER CASE FILE. 
SO ON WIN 32 FILE SYSTEMS, YOU ACTUALLY 
HAVE CASE PRESERVING BUT CASE INSENSITIVITY. 
SO THESE WOULD BE THE SAME FILE 
ON WINDOWS. IF I LOOK AT THIS YOU'LL 
SEE THAT NOT ONLY DO I HAVE TWO 
DIFFERENT FILES, BUT I ACTUALLY 
HAVE THE LINK JUST LIKE I EXPECT. 
IF I GO IN AND MODIFY ONE OF THE 
LINKS, I'LL DO THAT HERE. TEST MODIFICATION, 
COOL. NOW, NOT ONLY DID THE SOURCE 
FILE CHANGE JUST LIKE THIS, BUT 
THE ACTUAL LINKED FILE WILL 
CHANGE AS WELL. 
THERE'S THE ORIGINAL FILE. IN THIS 
WAY NFS 41 CAN BE USED ON AZURE 
FILES. NOW THAT WE'VE SHOWN THIS 
I WANT TO HIT A FEW OF THE LIMITATIONS 
YOU'LL SEE WHEN WE TAKE THIS TO 
OUR INITIAL LIMITED PREVIEW. FIRST 
WE'RE GOING TO BRING THIS TO SSD 
PREMIUM FILE STORAGE TO BEGIN WITH. 
THIS IS REALLY JUST BECAUSE OF THE 
SCENARIOS WE'RE TARGETING LOOKING 
FOR PEOPLE TO RUN DATABASES AND 
THE KIND OF STUFF THAT FABIAN MENTIONED 
PREMIUM SHARE FILES ARE USEFUL FOR. 
I ALREADY MENTIONED THE RESTRICTION 
TO VIRTUAL NETWORKS. THIS ALSO INCLUDES 
EN DESCRKRIPGS. OFTENTIMES FOLKS 
WILL USE PLUG-INS TO PROVIDE THOSE 
FUNCTIONALITIES. FINALLY, LIKE WE 
HAVE ON S AND B, WE HAVE A REST 
API FOR S AND B. WE WON'T HAVE THAT 
TO START FOR NFS. THE CONSEQUENCE 
OF NOT HAVING IT AT THE INITIAL 
PREVIEW IS THINGS LIKE AZURE BACK-UP 
OR AZ COPY WON'T BE THERE ON DAY 
ONE. THERE'S THE LINK AT THE BOTTOM. 
AGAIN, WE'LL HAVE THIS LATER IF 
THIS IS SOMETHING THAT INTERESTS 
SO. FOR NOW I'LL HAND IT BACK TO 
FABIAN. >> THANK YOU, WILL. AWESOME. 
[ APPLAUSE ] GREAT GDEMOS. I THINK 
WILL HAS REALLY SHOWN YOU SOME OF 
THE CORE FUNCTIONALITY THAT WE WERE 
REALLY HOPING TO GET VERY, VERY 
QUICKLY INTO AZURE FILE SHARES, 
AND THIS IS GOING TO MAKE RUNNING 
A FILE SHARE AS A SERVER REPLACEMENT 
REALLY A VIABLE OPTION. NOW LET'S 
DIVE A BIT BACK INTO FILE SYNC AND 
LET'S LOOK AT WHAT'S NEW IN FILE 
SYNC. IN THE LAST COUPLE OF MONTHS 
OR SINCE THE LAST IGNITE, WE HAVE 
BASICALLY FOCUSED A LOT ON PERFORMANCE. 
WE NOW HAVE PARALLEL UPLOAD, DOWNLOAD. 
WE HAVE STEADILY INCREASED THE NUMBER 
OF ITEMS PER SECOND WE'RE PROCESSING 
WITH VIRTUALLY USING THE SAME AMOUNT 
OF RESOURCES ON YOUR SERVER. SO 
IT'S BEEN COMING MORE AND MORE PERFORMANCE 
SERVICE AS WE GO. IN THE NEXT SEMESTER 
WE'RE FOCUSING MORE ON PERFORMANCE 
AS WELL. WE HAVE ADDED A TON OF 
HEALTH METRICS TO AZURE FILE SYNC. 
THERE ARE AZURE MONITORS, THERE'S 
ALERTING THAT YOU CAN NOW DO. ONE 
OF THE COOL NEW THINGS THAT IS GOING TO 
COME UP IS WE TALKED ABOUT THIS 
ON PREMISES PERFORMANCE CACHE. WHEN 
YOU'RE CACHEING YOU WANT TO KNOW 
IS IS IT BIG ENOUGH? WE WILL GIVE 
YOU A CHART THAT SHOWS THE CACHE 
HIT RATE FOR THAT PARTICULAR SERVER 
AND IF IT DOESN'T LOOK GOOD I CAN 
ADD A LITTLE MORE STORAGE. I CAN 
CACHE MORE FILES WHICH MEANS I'M 
GETTING TO THE APPROPRIATE LEVEL 
OF HOT FILES IN MY ORGANIZATION 
AND YOU CAN SEE THAT CACHE HIT RATE 
INCREASE. WHEN I GET A LITTLE BIT 
MORE STORAGE, I SUDDENLY DON'T SEE 
AN INCREASE IN CACHE HIT RATE ANYMORE. 
THAT MEANS THE ADDED STORAGE WASN'T 
NECESSARY SO I CAN SCALE THAT BACK 
AND I FOUND MY OPTIMUM SIZE FOR 
THAT PARTICULAR FOLDER AS A CA K 
CACHE. THAT'S ONE EXAMPLE OF THE 
AMOUNT OF INSIGHTS THAT WE'RE GOING 
TO ENABLE IN THE NEXT COUPLE OF 
WEEKS AND THAT WE HAVE ALREADY ENABLED. 
WE INCREASED SCALE. THESE ARE NOT 
HARD LIMITS. THESE ARE SOFT LIMITS. 
THERE'S NOTHING ENFORCING THEM AND 
THE SYSTEM WON'T FALL OVER IF YOU 
HAVE 101 MILLION ITEMS IN YOUR FILE 
SHARE BUT THESE ARE ALL TESTED LIMITS. 
THIS IS WHAT WE TEST WITH AND WE 
FEEL PRETTY CONFIDENT THAT AT 100 
MILLION ITEMS IN A FILE SHARE WE 
PROBABLY WILL COVER A GOOD CHUNK 
OF YOUR USE CASES. ANOTHER VERY 
IMPORTANT ASPECT THAT WE'VE GOTTEN 
QUESTIONS ABOUT OVER AND OVER IS 
YOU'VE PROBABLY TRAINED YOUR USERS 
TO COULD SELF-SERVICE RESTORE. YOU 
DON'T WANT TO GET A TICKET EVERY 
NOW AND THEN WHEN A CUSTOMER WANTS 
TO RESTORE A PREVIOUS VERSION OF 
A FILE. SO HOW DO WE DO SELF-SERVICE 
RESTORE? RIGHT NOW YOU'RE DOING 
IT WITH PREVIOUS VERSIONS AND I 
WANT TO DIVE IN THERE AND BASICALLY 
TALK A BIT ABOUT THAT AZURE FILE 
SYNC IS GOING TO BECOME AWARE AND 
WORKING, COMPATIBLE WITH THE PREVIOUS 
VERSIONS IN WINDOWS SERVER. WHAT 
IS PREVIOUS VERSIONS? FOR THOSE 
OF YOU THAT DON'T KNOW, YOU HAVE 
A MOUNTED FILE SHARE ON A CLIENT 
MACHINE. I CAN LOOK AT ANY FILE 
HERE AND IF I RIGHT CLICK ON THAT 
FILE AND I GO TO PREVIOUS VERSIONS, 
I'LL GET MY PREVIOUS VERSIONS TAP 
AND THAT TAP LISTS THE AVAILABLE 
VERSIONS I CAN EITHER RESTORE FROM 
OR OPEN. WHAT YOU CAN SEE IS THESE 
ARE CLEARLY TWO DIFFERENT VERSIONS 
OF THE FILE THAT I CAN HAVE THE 
USER RESTORE FROM. SO, THIS IS THE 
FUNCTIONALITY THAT YOU WANT TO ENABLE 
BUT HOW DOES PREVIOUS VERSIONS ACTUALLY 
WORK? PREVIOUS VERSIONS BASICALLY 
IS SUPPORTED BY THE VOLUME SHADOW 
COPY SERVICE OF VSS. WHEN YOU SET 
UP VSS ON YOUR VOLUME YOU'RE GOING 
TO TAKE AS MANY SNAPSHOTS AS YOU 
CAN STORE ON THAT VOLUME AND WHAT 
YOUR SCHEDULE DICTATES. SO FAR SO 
GOOD. THIS IS HOW PREVIOUS VERSIONS 
WORKS TODAY. NOW LET'S ADD SYNC 
TO THAT SERVER. IF WE ADD SYNC TO 
THIS, NOTHING IS REALLY DIFFERENT 
BECAUSE JUST ADDING SYNC MEANS YOU 
HAVE THE SAME SET OF FILES IN A 
FILE SHARE AS YOU HAVE ON THE SERVER. 
EVERYTHING'S THE SAME. IT ACTUALLY 
BECOMES INTERESTING WHEN YOU ADD 
CLOUD TIERING TO THIS MIX. LET'S 
ADD TIERING. WHEN WE ADD TIERING 
WE'LL START TO TIER SOME FILES OFF 
TO THE CLOUD. THEY WON'T ACTUALLY 
BE LOCAL TO YOUR CACHE ANYMORE. 
WHEN THEY'RE NOT, WHAT DOES THIS 
MEAN TO A PREVIOUS VERSION OF A 
FILE THAT IS NO LONGER REALLY LOCAL? 
OUR LIVE VERSION OF THE FILE REFERENCES 
THE FILE IN THE SHARE SO WE CAN 
ALWAYS TRANSPARENTLY RECALL IT AND 
SERVE IT TO THE USER WHEN THEY WANT 
TO ACCESS IT. BUT IF A USER WANTS 
TO RESTORE FROM A PREVIOUS VERSION, 
WHERE IS THAT LINKING TO? WHERE 
IS THAT CONTENT STORED? SO THIS 
IS A MISSING FUNCTIONALITY WE HAD 
UNTIL VERY RECENTLY IN THE AZURE 
FILE SYNC VERSION 9 THAT ACTUALLY 
FIXED THAT ISSUE AND WE'VE BROUGHT 
IN NEW FUNCTIONALITY THAT WILL ALLOW 
YOU TO ENABLE PREVIOUS VERSION COMPATIBILITY 
ON VOLUMES WHERE YOU USE CLOUD TIERING 
AND YOU BASICALLY SIMPLY RUN THIS 
COMMAND, AND WHEN YOU RUN THIS COMMAND 
WE'LL MAKE SURE THAT WE KEEP A STABLE 
FILE VERSION IN THE CLOUD FOR AS 
LONG AS YOU HAVE THE VSS SNAPSHOT 
ON PREMISE. YOU OR YOUR USERS WILL 
BE ABLE TO REFERENCE THAT TRANSPARENCY 
AND CLICK ON THE RESTORE BUTTON 
OR THE OPEN BUTTON JUST AS I HAVE 
DONE AND BE ABLE TO GET 
THAT PREVIOUS VERSION BACK. 
SO THAT'S A REALLY IMPORTANT ASPECT 
OF ENABLING ADMINISTRATORS TO PROVIDE 
SELF-SERVICE RESTORE. ALL RIGHT, 
SO NOW ONE VERY IMPORTANT ASPECT 
OF AZURE FILE SYNC HAS ALWAYS BEEN 
SIMPLICITY. ONE OF THE THINGS THAT 
WE'VE DONE VERY EARLY ON WAS WE'VE 
INTEGRATED AZURE FILE SYNC INTO 
WINDOWS ADMIN CENTER. AT THE SHOW 
WITH THE LATEST VERSION OF WINDOWS 
ADMIN WE'RE ACTUALLY SHIPPING A 
NEW VERSION OF OUR EXTENSION AS 
WELL. I WANT TO GIVE YOU A QUICK 
DEMO OF IT BECAUSE I THINK YOU'RE 
GOING TO LIKE IT. IT IS MAKING DEPLOYING 
AZURE FILE SYNC REALLY, REALLY SIMPLE. 
HERE I AM ON MY MACHINE. IT'S JUST 
A CLIENT LAPTOP AND I AM LOOKING 
AT MY AZURE SUBSCRIPTION. LET'S 
LOOK INSIDE THAT AZURE SUBSCRIPTION. 
WE'RE GOING TO LOOK AT RESOURCE 
GROUPS. THERE'S THE DEFAULT RESOURCE 
GROUPS. THIS SUBSCRIPTION IS COMPLETELY 
EMPTY. NO RESOURCE EXISTS. WE WANT 
TO DEPLOY AZURE FILE SYNC SO LET'S 
FIND THE SERVER THAT WE WANT TO 
DEPLOY IT TO. LET'S PICK THAT ONE. 
THE ONLY ONE WE HAVE. ON THE LEFT-HAND 
SIDE THERE YOU CAN SEE THE AZURE 
FILE SYNC EXTENSION TO ADMIN CENTER. 
IT'S REALLY BUILT IN. HERE WE CAN 
SEE THIS SERVER HASN'T BEEN SET 
UP SO WE CLICK SETUP. WHAT WE'LL 
DO NOW IS ONLY ASK YOU ONE QUESTION. 
WHERE WOULD YOU LIKE TO DEPLOY -- 
WHICH REGION WOULD YOU LIKE TO CHOOSE. 
YOU CAN SEE YOUR SUBSCRIPTION. YOU 
CAN SEE THE RESOURCE GROUP. YOU 
CAN CHANGE THAT IF YOU WANT. LET'S 
PICK A REGION HERE. YOU CAN ALSO 
SEE AGENT SETTINGS. I COULD SET 
UP AT THIS POINT. I'M JUST GOING 
TO SHOW THIS TO YOU REAL QUICK. 
THERE ARE OPTION THAT CAN PROVIDE 
AN AUTO UPDATE FEE SURVEILLANCE 
SO AS SOON AS A NEW GA VERSION BECOMES 
AVAILABLE, UPDATE YOURSELF. I CAN 
SET A PROXY SERVER. LET'S HIT SETUP. 
WE'RE ACTUALLY NOW MAKING YOUR SUBSCRIPTION 
READY. WE'RE GOING TO LOOK AT YOUR 
RESOURCE GROUP. WE'RE GOING TO CREATE 
THE STORAGE SYNC SERVICE WHICH IS 
THE BACKBONE FOR AZURE FILE SYNC. 
WE'RE DOWNLOADING THE AGENT TO THAT 
REMOTE SERVER AND AS WE'RE DOING 
THAT AFTER THE DOWNLOAD HAS FINISHED 
WE START INSTALLING IT. AFTER INSTALLATION 
WE CREATE THAT TRUST RELATIONSHIP 
BETWEEN YOUR SERVER AND YOUR STORAGE 
SYNC SERVICE SO YOU CAN START MANAGING 
THAT SERVER FROM THE CLOUD. THAT 
JUST TAKES A LITTLE MOMENT HERE. 
ONCE THAT'S DONE, WE CAN NOW ACTUALLY 
LOOK INTO THE EXTENSION, AND HERE 
WE SEE THAT'S THE STORAGE SYNC SERVICE 
THAT WAS CREATED AND WE CAN GO TO 
THE AZURE PORTAL TO LOOK AT THAT. 
THIS IS THE STORAGE LINK SERVICE 
THAT WE'VE CREATED. WE SEE OUR FILE 
SERVER THAT WE JUST DEPLOYED TO. 
IN ORDER TO SET UP SYNC, WE NEED 
SYNC GROUPS BUT WE DON'T WANT TO 
DO THAT IN THE AZURE PORTAL. WE 
WANT TO COULD FROM FROM ADMIN CENTER. 
ALL WE NEED TO DO IS BROWS TO A 
LOCATION THAT HAS A FOLDER THAT 
WE'RE INTERESTED IN SYNCING, AND 
NOW WE PROVIDE A FEW RESOURCE NAMES 
BECAUSE EVERYTHING'S NEW. THERE'S 
NOTHING IN MY SUBSCRIPTION. CREATE 
A SYNC GROUP THAT DICTATES WHERE 
STUFF IS SYNCING TO. LET'S CREATE 
A FILE SHARE IN AZURE, CREATE A 
STORAGE ACCOUNT THAT CONTAINS THAT 
FILE SHARE. THIS NAME NEEDS TO BE 
GLOBALLY UNIQUE, SO I'M GOING TO 
GIVE IT A SLIGHTLY DIFFERENT NAME. 
DOWN HERE I CAN PICK A PERFORMANCE 
OPTION AND A RESILIENCY OPTION OR 
REDUNDANCY OPTION. I CAN HIT SET 
UP SYNC. NOW ALL THESE RESOURCES 
ARE GOING TO BE AUTOMATICALLY DEPLOYED. 
THERE IS NOTHING THAT I NEED TO 
DO FROM AN AZURE FILES PERSPECTIVE 
OR AZURE FILE SYNC PERSPECTIVE OTHER 
THAN JUST SIT THERE AND WAIT AND 
SEE IT HAPPEN. WHILE THIS IS GOING 
ON, IN THE BACKGROUND I'VE ALREADY 
SHOWN YOU THE STORAGE SYNC SERVICE 
THAT WAS CREATED AND WE'VE REGISTERED 
OUR SERVER TO THAT STORAGE SYNC 
SERVICE. THAT WAS THE TRUST RELATIONSHIP 
WE HAD TO CREATE. IN THIS LAST STEP 
WE'RE CREATING THE STORAGE ACCOUNT 
AND WE'RE CREATING THE FILE SHARE. 
SO ALL WE NEED TO DO IS WE NEED 
TO CONNECT OUR REGISTERED SERVER 
AND OUR FILE SHARE, BASICALLY THE 
LOCATION THAT WE WANT TO SYNC TO 
THE AZURE FILE SHARE AND WE DO THAT 
BY DEPLOYING A SYNC GROUP. ALL OF 
THESE STEPS ARE BEING TAKEN CARE 
OF AUTOMATICALLY. NOW WE CAN MOVE 
ON. AS THIS IS FINISHING UP I CAN 
SEE MY SERVER END POINT HERE. I 
CAN SEE INTO THE SYNC GROUP. I CAN 
SEE THAT WE ARE ACTUALLY HAVING 
A CLOUD END POINT AND SERVER END 
POINT CONNECTING. THE FILE SHARE 
IS GOING TO THE SERVER AND WITH 
VERY LITTLE TIME WE'RE ALREADY SEEING 
SOME FILES HERE COMING IN. IT'S 
NOT COMPLETE YET BUT SOME FILES 
HAVE ALREADY STARTED TO SYNC. IT'S 
A PRETTY QUIK PRO SAYS. ALL OF THIS 
JUST FROM WITHIN THAT CENTER. I 
DIDN'T HAVE TO LEAVE ADMIN CENTER 
AT ALL. THAT ALLOWS YOU TO DO PROOF 
OF CONCEPT OR ANYTHING ELSE THAT 
YOU'RE LOOKING FOR. [ APPLAUSE ] 
NOW A QUICK TOPIC THAT MAY OR MAY 
NOT AFFECT ALL OF YOU WHICH IS STORE 
SIMPLE. CAN I GET A RAISE OF HANDS 
OF WHO HAS STORE SIMPLE OR HAS HEARD 
OF STORE SIMPLE? THERE'S A COUPLE 
OF PEOPLE HERE. I'M GOING TO KEEP 
THIS REALLY SHORT BUT I WANT TO 
INCLUDE IT BECAUSE IT'S A REALLY 
IMPORTANT TOPIC FOR THOSE OF YOU 
THAT HAVE A STORE SIMPLE BECAUSE 
THEY HAVE ANNOUNCED END OF LIFE. 
YOU HAVE ABOUT TWO YEARS TO MOVE 
OFF OF IT. STORE SIMPLE IS REALLY 
FROM A FUNCTIONALITY PERSPECTIVE 
A SUBSET. AZURE FILE SYNC IS AN 
IDEAL REPLACEMENT AND WE HAVE A 
CLOUD SITE MIGRATION STAEJ RATEGY 
FOR THAT. IF YOU HAVE A STORE SIMPLE, 
COME SEE US AFTERWARDS. WE'RE GOING 
TO GIVE YOU AN EMAIL ADDRESS. YOU 
CAN REACH OUT TO US AND WE'LL HELP 
YOU IN YOUR MIGRATION. SO THE BASIC 
FUNCTIONALITY HERE IS WE DO A CLOUD 
SITE MIGRATION THROUGH A VIRTUAL 
APPLIANCE. WE SET UP AZURE FILE 
SYNC ON A VM THAT WILL TRANSPORT 
THE FILES TO AN AZURE FILE SHARE 
THAT YOU CAN CONNECT TO A WINDOWS 
SERVER AS A LOCAL CACHE AND THAT 
WILL DO THE SAME THING.
IT'S THE SAME FUNCTIONALITY, 
JUST MORE FEATURE RICH AND YOU CAN 
CONNECT MULTIPLE SERVERS TO THE 
SAME LOCATION, WHICH YOU COULDN'T 
DO WITH STORE SIMPLE. AFTER THIS 
INITIAL SYNC WE'RE BASICALLY GOING 
AHEAD AND REMOVING USER ACCESS. 
WE WANT TO KEEP THE MIGRATION VERY 
-- LET'S SAY WE WANT TO KEEP IT 
AVAILABLE TO USERS TO USE AND WE'RE 
GOING TO KEEP THE DOWN TIME MINIMAL. 
AT SOME POINT IN TIME WE HAVE TO 
CUT OFF. WE TAKE ONE MORE VOLUME 
COLLONE AND MOUNT THAT VOLUME CLONE 
AND SYNC JUST THE DELTA. SO THAT 
DELTA WILL BE VERY SMALL AND WE'LL 
BE FINISHING QUICKLY. SO YOU CAN 
MOVE YOUR USERS OVER SO THAT IN 
THE END YOU CAN DEPROVISION ALL 
THE PIECES THAT YOU HAVE IN YOUR 
STORE SIMPLE DEPLOYMENT AND IN THIS 
MIGRATION DEPLOYMENT AND YOU'RE 
SET WITH JUST A NORMAL AZURE FILE 
SYNC DEPLOYMENT FOR YOU TO ENJOY 
AND MOVE FORWARD WITH. SO EMAIL 
US IF YOU HAVE A STORE SIMPLE AND 
YOU WANT TO DO A MIGR MIGRATION. 
PLEASE GO AHEAD AND DO THAT AND 
WE'LL HELP YOU. ONE MORE THING BEFORE 
WE FINISH OUR PRESENTATION. I JUST 
WANT TO CALL OUT THAT A WINDOWS 
SERVER HAS BEEN A VERY APPLICABLE 
SOFTWARE OS FOR YOU GUYS BECAUSE 
IT'S VERY EXTE EXTE EXTENSIBLE. 
THERE'S A LARGE ECOSYSTEM OF PARTNERS 
THAT HAVE BEEN EXTENDING THE WINDOWS 
SERVER FUNCTIONALITY AND FOR US 
IN AZURE FILE SHARE, WE'RE SAYING 
WE CAN ACTUALLY REPLACE SOME OF 
THE WINDOWS SERVER FUNCTIONALITY 
BEING ESPECIALLY SURROUNDING THE 
FILE SERVER SPACE. WE WANT TO MAKE 
SURE THAT WE SEND THE MESSAGE WE 
ARE AN ECOSYSTEM. WE ARE A PLATFORM 
AS WELL FOR ECOSYSTEM PARTNERS TO 
TIE INTO. THIS IS BY NO MEANS ALL 
OF THEM. IT JUST PICKS TWO PASS 
SERVICES THAT ARE INTEGRATING WITH 
US, AZURE BACK-UP OBVIOUSLY IS VERY 
IMPORTANT. MCAFEE HAS JUST ANNOUNCED 
AN ANTI-VIRUS AND TLP SOLUTION AS 
A PASS OFFERING SO THIS IS SOMETHING 
THAT I JUST WANTED TO QUICKLY TOUCH 
BASE. THERE ARE WAY MORE PARTNERS. 
I JUST PICKED A COUPLE OF PASS SERVICES 
HERE. SO HERE'S THE SLIDE THAT WILL 
WAS REFERRING TO. THIS HAS ALL THE 
PREVIEW LINKS IN HERE. THIS WOULD 
BE A GOOD SLIDE TO LOOK UP AFTER 
THE SHOW OR TAKE A QUICK PICTURE 
OF. I REALLY WANT TO LEAVE YOU WITH 
THE IDEAS AROUND FILE SHARE BEING 
THE CENTER OF YOUR NEW FILE SERVICES 
IN AZURE AND THEN BEING ABLE TO 
USE THE FILE SHARE DIRECTLY THROUGH 
VPN WITH AD INTEGRATION ALL WHERE 
YOU NEED IT WITH AN ON PREMISES 
CACHE WITH FILE SYNC AND YOU CAN 
MODERNIZE YOUR FILE SERVING INFRASTRUCTURE 
AND LAST BUT NOT LEAST, WE HAVE 
FANTASTIC INTEGRATION WITH NETS, 
STORAGE MIGRATION SERVICE, AND THE 
STORAGE MIGRATION SERVICE HELPS 
YOU MOVE OFF OF OLDER WINDOWS SERVER 
OPERATIONS. IF YOU'RE LOOKING AT 
RETIRING A WINDOWS SERVER 2008 WHICH 
IS A REALLY IMPORTANT TOPIC, THEN 
WITH THE STORAGE MIGRATION SERVICE 
YOU CAN VERY EASILY MOVE THIS TO 
A MORE MODERN SERVER WHERE YOU DEPLOY 
MINIMAL STORAGE AND YOU BASICALLY 
MOVE THIS OVER AND HAVE A CLOUD 
TIERING AWARE COPY ENGINE BUILT 
INTO THE STORAGE MIGRATION SERVICE. 
THAT'S SOMETHING THAT ALLOWS YOU 
TO DO THAT MIGRATION FROM A BIG 
STORAGE FOOTPRINT TO A SMALL STORAGE 
FOOTPRINT USING AZURE FILE SYNC 
IN THE MIX. WITH THAT, THANK YOU, 
EVERYBODY, FOR JOINING US.
[ APPLAUSE 
