WEBVTT 00:00:03.729 --> 00:00:08.438 Good afternoon everyone and welcome back to the next session 00:00:08.438 --> 00:00:13.528 of Microsoft Azure What's Doing, the March 2017 Edition. 00:00:13.528 --> 00:00:18.213 We have two very interesting announcement which 00:00:18.213 --> 00:00:23.023 were done this month, so let's start with that. 00:00:23.023 --> 00:00:28.038 The first one we have is Azure Relay Hybrid Connections 00:00:28.038 --> 00:00:30.338 general availability. 00:00:30.338 --> 00:00:31.553 So basically, 00:00:31.553 --> 00:00:35.800 Azure Relay was one of the first core Azure services. 00:00:35.800 --> 00:00:43.745 It helps connectivity from on-premise assets to the cloud. 00:00:43.745 --> 00:00:48.250 And it gives you a lot of network management and stuff. 00:00:49.500 --> 00:00:52.585 So until now, those of you who have used the WCF Relay, 00:00:52.585 --> 00:00:54.810 they will be familiar with it. 00:00:54.810 --> 00:01:00.720 But Azure Relay was dependent on WCF Relays for its service. 00:01:00.720 --> 00:01:05.645 Going forward, we have announced the Hybrid Connection feature 00:01:05.645 --> 00:01:06.996 for Azure Relay. 00:01:06.996 --> 00:01:10.818 So now, if the dependency is not on Windows Communication 00:01:10.818 --> 00:01:14.802 Foundation, because not everybody uses Windows, right? 00:01:14.802 --> 00:01:20.040 So now, we are basically using all these Hybrid Connection. 00:01:20.040 --> 00:01:23.330 They will be able to help you with secure connectivity between 00:01:23.330 --> 00:01:25.046 on-premise and cloud assets. 00:01:25.046 --> 00:01:28.276 You can have five offline databases because it is very 00:01:28.276 --> 00:01:30.742 different common outcome pools. 00:01:30.742 --> 00:01:37.522 But it also is based on the open standards made for the protocol. 00:01:37.522 --> 00:01:42.003 So it's based on web sockets, what is being based on WCF, 00:01:42.003 --> 00:01:45.963 hybrid connections are, again, cross platform. 00:01:45.963 --> 00:01:49.528 So you can use Windows in the current platform that supports 00:01:49.528 --> 00:01:50.389 web sockets. 00:01:50.389 --> 00:01:55.565 You can use Azure Relay and the connection support .NET Core, 00:01:55.565 --> 00:01:57.722 JavaScript, Node.js. 00:01:57.722 --> 00:02:02.666 And multiple other RPC programming models to 00:02:02.666 --> 00:02:04.362 achieve this. 00:02:04.362 --> 00:02:07.146 So, if you want to get started with 00:02:07.146 --> 00:02:10.507 Azure Relay Hybrid Connections, you can 00:02:10.507 --> 00:02:15.501 just go on the documentation on Microsoft Azure and search for 00:02:15.501 --> 00:02:16.668 Azure Relay. 00:02:16.668 --> 00:02:22.045 That was our first announcement this month. 00:02:22.045 --> 00:02:24.183 Let's move ahead. 00:02:43.683 --> 00:02:47.964 Having some technical issues, just stay here with me for 00:02:47.964 --> 00:02:48.773 a second. 00:03:10.773 --> 00:03:14.866 Okay, so I'm going to just start talking about the next one, 00:03:14.866 --> 00:03:17.701 which is Geographic Routing capability in 00:03:17.701 --> 00:03:19.367 Azure Traffic Manager. 00:03:19.367 --> 00:03:21.851 I hope you can see it now. 00:03:21.851 --> 00:03:25.275 So Azure Traffic Manager is basically a service, 00:03:25.275 --> 00:03:28.215 which gives you external load balancing. 00:03:28.215 --> 00:03:31.093 So for example, if you want to load balance your traffic 00:03:31.093 --> 00:03:34.419 between different data centers, if you have global audience. 00:03:34.419 --> 00:03:37.459 You could do that with Azure Traffic Manager. 00:03:37.459 --> 00:03:42.049 It could also act as a failover mechanism between different data 00:03:42.049 --> 00:03:42.814 centers. 00:03:42.814 --> 00:03:46.671 But with this Geographical Routing capability, 00:03:46.671 --> 00:03:48.688 what we are giving you is, 00:03:48.688 --> 00:03:52.470 now you can customize content based on regions. 00:03:52.470 --> 00:03:59.330 So for example, depending on where your user is coming from. 00:03:59.330 --> 00:04:01.670 What a Traffic Manager could earlier do was, 00:04:01.670 --> 00:04:06.820 it would basically point your user to the nearest data center. 00:04:06.820 --> 00:04:10.770 But now you can also create different 00:04:10.770 --> 00:04:13.780 regions with localized content. 00:04:13.780 --> 00:04:17.119 And your Traffic Manager will point your results to their 00:04:17.119 --> 00:04:18.378 localized content. 00:04:18.378 --> 00:04:21.150 As you know, if you have any requirement, 00:04:21.150 --> 00:04:24.692 you have a specific policy mandate that requires a data 00:04:24.692 --> 00:04:28.010 access restriction within a specific geography. 00:04:28.010 --> 00:04:31.609 So all these places you can easily use 00:04:31.609 --> 00:04:34.054 Azure Traffic Manager. 00:04:34.054 --> 00:04:37.517 So that was the next announcement we had, 00:04:40.718 --> 00:04:43.107 Can you move to the next slide please? 00:05:11.420 --> 00:05:14.558 I'm having issues with my machine, so 00:05:14.558 --> 00:05:16.560 just give me one second. 00:05:51.360 --> 00:05:55.621 One second, I'm going to come back. 00:06:28.400 --> 00:06:31.160 Okay, so the next one you have is Azure Data Factory. 00:06:32.615 --> 00:06:34.397 Which now offers the SAP HANA and 00:06:34.397 --> 00:06:36.645 Business Warehouse data integration. 00:06:36.645 --> 00:06:41.180 So let's first start with, what is Azure Data Factory? 00:06:41.180 --> 00:06:45.492 So Azure Data Factory is one of our cloud-based integration 00:06:45.492 --> 00:06:49.430 services which helps you create different data pipelines. 00:06:49.430 --> 00:06:50.368 So for example, 00:06:50.368 --> 00:06:53.991 if you have different databases from where you need to get data. 00:06:53.991 --> 00:06:58.416 Or you are ingesting data from on-prem databases. 00:06:58.416 --> 00:07:02.583 Or if you are ingesting data from Hadoop Cluster, so 00:07:02.583 --> 00:07:06.210 you want to integrate all that data. 00:07:06.210 --> 00:07:10.480 You can use Azure Data Factory to create data pipelines, right? 00:07:10.480 --> 00:07:14.624 So with this new announcement, now Azure Data Factory 00:07:14.624 --> 00:07:17.776 enables you loading data from SAP HANA and 00:07:17.776 --> 00:07:22.206 SAP Business Warehouse directly into Azure data stores. 00:07:22.206 --> 00:07:25.598 So that you can do advanced analytics and reporting. 00:07:25.598 --> 00:07:30.136 So what's new, for those of you who have used SAP, you know that 00:07:30.136 --> 00:07:34.105 it's one of the most widely used enterprise software. 00:07:34.105 --> 00:07:38.980 And I mean, the most used 00:07:38.980 --> 00:07:44.324 stack in SAP is SAP HANA BW. 00:07:44.324 --> 00:07:49.032 So with this we have a new SAP HANA connector. 00:07:49.032 --> 00:07:53.274 So it supports copying data from HANA information models such as 00:07:53.274 --> 00:07:55.559 C analytical calculation views. 00:07:55.559 --> 00:07:57.715 As well as you can do the row and 00:07:57.715 --> 00:08:00.227 column tables using SQL queries. 00:08:00.227 --> 00:08:03.513 All you need to do to establish connectivity, 00:08:03.513 --> 00:08:07.052 you need to install the data management gateway, 00:08:07.052 --> 00:08:09.167 and the SAP HANA ODBC driver. 00:08:09.167 --> 00:08:12.155 So you can connect to the Azure Data Factory. 00:08:12.155 --> 00:08:15.539 The second connector is SAP BW connector. 00:08:15.539 --> 00:08:18.654 Which supports, again, copying data from 00:08:18.654 --> 00:08:23.546 SAP Business Warehouse version 7.x, info cubes and query cubes. 00:08:23.546 --> 00:08:27.980 And you can use these queries to copy the data. 00:08:27.980 --> 00:08:30.880 Again, to establish connectivity, 00:08:30.880 --> 00:08:34.778 you need to install the Data Management gateway and 00:08:34.778 --> 00:08:36.695 the SAP native library. 00:08:36.695 --> 00:08:39.415 So if you want to know how you want to do that, 00:08:39.415 --> 00:08:42.175 just go to our Azure documentation. 00:08:42.175 --> 00:08:47.195 And find SAP HANA connector for Azure Data Factory, 00:08:47.195 --> 00:08:50.765 and you should be able to find it. 00:08:50.765 --> 00:08:56.280 The next one we have is Instant File Recovery 00:08:56.280 --> 00:08:59.760 from Azure Linux VM backup using Azure Backup. 00:09:01.260 --> 00:09:05.523 So we had this Instant File Recovery option from 00:09:05.523 --> 00:09:10.746 Azure Windows VM backups which have all been available for 00:09:10.746 --> 00:09:12.677 quite some time now. 00:09:12.677 --> 00:09:17.121 What it does is, you can restore files instantly from your 00:09:17.121 --> 00:09:21.837 Azure Recovery Services Vault without any additional cost or 00:09:21.837 --> 00:09:23.300 infrastructure. 00:09:23.300 --> 00:09:26.656 So you create an Azure Recovery Services Vault. 00:09:26.656 --> 00:09:30.570 You enable your backup on your virtual machine, 00:09:30.570 --> 00:09:34.108 and now you can instantly record the files. 00:09:34.108 --> 00:09:37.808 So for example, if you are backing up your entire VM, 00:09:37.808 --> 00:09:41.687 you do not have to mount your drive back to see the files. 00:09:41.687 --> 00:09:45.451 You can instantly recover files from Azure VM. 00:09:45.451 --> 00:09:47.298 And so for example, 00:09:47.298 --> 00:09:51.976 if you have a C Azure Linux VM which is only MongoDB. 00:09:51.976 --> 00:09:56.366 And you are doing data dumps at a particular data 00:09:56.366 --> 00:09:59.455 recovery point in Azure backup. 00:09:59.455 --> 00:10:02.296 So if you quickly want to validate what happened say 00:10:02.296 --> 00:10:05.864 yesterday or you want to Validate the specific detail or 00:10:05.864 --> 00:10:08.054 you want to individual items. 00:10:08.054 --> 00:10:12.478 You don't have to download the entire data dam you can just go 00:10:12.478 --> 00:10:16.644 and download the point in time recording whatever you had 00:10:16.644 --> 00:10:17.527 stored it. 00:10:17.527 --> 00:10:22.854 And this option wasn't available for Linux VM before, 00:10:22.854 --> 00:10:28.422 but if you go to the Azure portal, you can enable this now. 00:10:36.021 --> 00:10:38.750 Moving on, the next one is basically, 00:10:38.750 --> 00:10:41.480 this one's in California, San Jose, 00:10:41.480 --> 00:10:45.300 Strata conference which is data related conference. 00:10:45.300 --> 00:10:49.186 And we announced [INAUDIBLE] So 00:10:49.186 --> 00:10:54.161 let's go to those announcements, so 00:10:54.161 --> 00:10:59.607 let's first start with the DocumentDB. 00:10:59.607 --> 00:11:03.864 DocumentDB is the key of globally distributed data 00:11:03.864 --> 00:11:04.755 service. 00:11:04.755 --> 00:11:08.128 It's multiqual, database as a service so 00:11:08.128 --> 00:11:12.822 if you have been using MongoDB or you know other Microsoft. 00:11:12.822 --> 00:11:16.505 MongoDB is very similar to it, except for the fact that it is 00:11:16.505 --> 00:11:19.757 a PAAS service so it's a completely valid service. 00:11:19.757 --> 00:11:24.571 It allows you to logically scale both true put, as well as your 00:11:24.571 --> 00:11:28.657 storage across any number of geographical region. 00:11:28.657 --> 00:11:31.709 So this service was basically, 00:11:31.709 --> 00:11:36.230 we have a lot of connectors of this service, for 00:11:36.230 --> 00:11:41.203 example, the first announcement we have this month 00:11:41.203 --> 00:11:45.966 is now you have a Spark connector for DocumentDB. 00:11:45.966 --> 00:11:49.277 So now, say for example, you have a lot of data in your 00:11:49.277 --> 00:11:52.885 DocumentDB which you want to analyze using Apache Spark, 00:11:52.885 --> 00:11:56.788 you can directly connect your Apache Spark to DocumentDB using 00:11:56.788 --> 00:12:00.567 Spark Collector and analyze your data directly from there. 00:12:00.567 --> 00:12:04.567 We also have the ability of MongoDB and 00:12:04.567 --> 00:12:10.450 we will look a little deeper into this in our next slide. 00:12:10.450 --> 00:12:11.989 Also, we announced 00:12:11.989 --> 00:12:16.182 the Cloud-first Hortonworks Data Platform 2.6. 00:12:16.182 --> 00:12:18.815 What I mean by Cloud-first is, 00:12:18.815 --> 00:12:23.600 the newest Hortonworks Data Platform, which is 2.6. 00:12:23.600 --> 00:12:26.738 It's called [INAUDIBLE] on Cloud. 00:12:26.738 --> 00:12:31.125 So it's not even available yet on on premise release but 00:12:31.125 --> 00:12:35.525 that's Hortonworks commitment to being cloud first. 00:12:35.525 --> 00:12:39.500 So basically, any time you want to use one of the latest version 00:12:39.500 --> 00:12:43.105 of Hortonworks, you can directly use it on Azure cloud. 00:12:43.105 --> 00:12:45.905 It's not that you have to wait for 00:12:45.905 --> 00:12:49.806 the on premise release to come on it for cloud. 00:12:49.806 --> 00:12:51.778 We also announced or 00:12:51.778 --> 00:12:55.957 fully managed Apache path to the that one. 00:12:55.957 --> 00:13:00.590 So basically, the Apache Spark is again, it's a stream managed 00:13:00.590 --> 00:13:05.155 analytics service, 2.1 is the latest release that we have. 00:13:05.155 --> 00:13:10.050 So that is again available right now with the HDInsight cluster 00:13:10.050 --> 00:13:12.922 and we have introduced capability. 00:13:12.922 --> 00:13:16.670 So for example if you wanted to do Spark integration with 00:13:16.670 --> 00:13:20.577 Azure Event Hub, and you want to get that Data flowing from 00:13:20.577 --> 00:13:23.708 Event Hub directly to Spark, you can do that. 00:13:23.708 --> 00:13:26.722 You also have a streaming connector from Kafka to 00:13:26.722 --> 00:13:28.330 HDInsight. 00:13:28.330 --> 00:13:31.501 Those are the new announcement. 00:13:31.501 --> 00:13:35.582 We also announced SQL Server community technology preview 00:13:35.582 --> 00:13:39.417 wonderful, which will be available on both Windows and 00:13:39.417 --> 00:13:41.540 Linux very soon. 00:13:41.540 --> 00:13:44.764 You can try the preview of your choice 00:13:44.764 --> 00:13:48.098 of development driven environment. 00:13:48.098 --> 00:13:52.994 You can just search for what's new in SQL server Linux and 00:13:52.994 --> 00:13:58.710 you can go to the terminal recommendation to Try using it. 00:14:03.840 --> 00:14:10.280 And that was the HDInsight and DocumentDB. 00:14:10.280 --> 00:14:12.940 The next one we have is DocumentDB API for MongoDB. 00:14:12.940 --> 00:14:17.692 So DocumentDB SQL Service which is very 00:14:17.692 --> 00:14:20.670 Similar to MongoDB, right? 00:14:20.670 --> 00:14:24.568 So there are a lot of developers who use MongoDB and they 00:14:24.568 --> 00:14:29.146 are tool change and libraries that they use to develop or 00:14:29.146 --> 00:14:31.480 to connect to MongoDB, right? 00:14:31.480 --> 00:14:34.627 So now with these agenda liability or 00:14:34.627 --> 00:14:39.001 for DocumentDBS or MongoDB, you can use all that. 00:14:39.001 --> 00:14:43.251 So your goal stays the same, you can use the same [INAUDIBLE] you 00:14:43.251 --> 00:14:46.195 will use to connect to work availability, 00:14:46.195 --> 00:14:48.750 you can use that for marketability. 00:14:48.750 --> 00:14:52.411 So this feature have been available in preview for 00:14:52.411 --> 00:14:55.985 sometime now but it lacks some features such as, 00:14:55.985 --> 00:15:00.603 you could do only one collection on the global leader this is not 00:15:00.603 --> 00:15:01.580 available. 00:15:01.580 --> 00:15:04.225 So now with general availability, 00:15:04.225 --> 00:15:08.377 we have introduced a number of major feature releases. 00:15:08.377 --> 00:15:10.611 So now you can have sharded collections. 00:15:10.611 --> 00:15:14.725 You can have more than one collection shard for 00:15:14.725 --> 00:15:17.898 a DocumentDB with MongoDB API's. 00:15:17.898 --> 00:15:20.223 You can have a global data Databases so 00:15:20.223 --> 00:15:23.494 you can replicate your data across multiple region so 00:15:23.494 --> 00:15:26.580 that you can have high availability. 00:15:26.580 --> 00:15:27.928 You can have these. 00:15:27.928 --> 00:15:30.990 So now these APIs support but 00:15:30.990 --> 00:15:36.043 you will only allow the data Operations on MongoDB. 00:15:36.043 --> 00:15:40.048 And also, we have also added some additional portal metrics. 00:15:40.048 --> 00:15:44.689 So now when you go to that Azure portal for DocumentDB, you can 00:15:44.689 --> 00:15:49.330 see there are different metrics, such as number of request or 00:15:49.330 --> 00:15:52.020 request charges or error request. 00:15:52.020 --> 00:15:55.634 And all that you can manage you see all those statistics and 00:15:55.634 --> 00:15:57.272 metrics on Azure portal. 00:15:57.272 --> 00:16:02.330 So that was MongoDB API's, sorry DocumentDB API for Mongo DB. 00:16:06.910 --> 00:16:11.208 The next one is Azure SQL Database Premium RS. 00:16:11.208 --> 00:16:18.180 So this is something that we are releasing in preview. 00:16:18.180 --> 00:16:23.668 Azure SQL Database servers are SQL server Azure service, 00:16:23.668 --> 00:16:24.904 [INAUDIBLE]. 00:16:24.904 --> 00:16:29.391 We have a lot of different tiers of services from 00:16:29.391 --> 00:16:32.316 Basic to Standard to Premium. 00:16:32.316 --> 00:16:36.536 And Premium RS is the latest edition. 00:16:36.536 --> 00:16:40.398 It is a 4TB increase on the storage unit for 00:16:40.398 --> 00:16:43.320 Premium P11 and P15. 00:16:43.320 --> 00:16:48.340 And it also comes with it, enhanced portal experience for 00:16:48.340 --> 00:16:51.580 selecting and managing service tiers and performance levels. 00:16:52.660 --> 00:16:56.120 So now you can use up to 4 TB of storage. 00:16:57.390 --> 00:17:00.300 So it's, you can have a, you 00:17:02.450 --> 00:17:06.280 can have a P11 or P15 premium databases and you can I had up 00:17:06.280 --> 00:17:11.166 to 40 [INAUDIBLE] storage at no additional charge. 00:17:11.166 --> 00:17:14.440 And right now we do not have the worldwide availability. 00:17:14.440 --> 00:17:20.794 The 4 TB option that we selected for the database is located 00:17:20.794 --> 00:17:27.033 in some region some of them are the [INAUDIBLE] and [INAUDIBLE] 00:17:33.309 --> 00:17:37.630 So moving on, that was Azure SQL Database Premium RS. 00:17:40.770 --> 00:17:45.170 The next one we have is, Azure SQL Stream Analytics tools for 00:17:45.170 --> 00:17:46.530 Visual Studio. 00:17:46.530 --> 00:17:51.730 So, if you're not familiar with Azure Stream Analytics, 00:17:51.730 --> 00:17:56.930 it is again an A platform as a services where you can manage or 00:17:56.930 --> 00:17:59.429 analyze data as it comes in. 00:17:59.429 --> 00:18:04.204 So it gives you a way to analyze your data in 00:18:04.204 --> 00:18:08.168 sync rather analyzing it at rest. 00:18:08.168 --> 00:18:12.127 Now we have this one [INAUDIBLE] the public 00:18:12.127 --> 00:18:15.977 preview version of [INAUDIBLE] studio. 00:18:15.977 --> 00:18:19.502 So, you know, if you, I mean of the see all the goodness 00:18:19.502 --> 00:18:21.720 [INAUDIBLE] just like being God. 00:18:21.720 --> 00:18:27.786 It is market [INAUDIBLE] it's all there. 00:18:27.786 --> 00:18:31.429 But these tool are designed to provide An experience where 00:18:31.429 --> 00:18:34.329 you can do Azure stream analytics development 00:18:34.329 --> 00:18:36.422 workflow inside Visual Studio. 00:18:36.422 --> 00:18:42.422 So this will help you if you want to alter query, 00:18:42.422 --> 00:18:45.872 if you want to write query, 00:18:45.872 --> 00:18:50.972 if you want to quickly test, debug, and 00:18:50.972 --> 00:18:56.072 diagnose your stream analytics job that 00:18:56.072 --> 00:19:03.434 all now available as a part of your regional studio tools. 00:19:06.776 --> 00:19:11.456 Moving on, the next one is, Azure brings digital analytics 00:19:11.456 --> 00:19:15.691 and regional capabilities to US government. 00:19:15.691 --> 00:19:19.476 So if you know Azure US Government Cloud, 00:19:19.476 --> 00:19:24.020 it's cloud for basically Azure Government Cloud 00:19:24.020 --> 00:19:29.010 is a part of cloud which we use it for global customers. 00:19:29.010 --> 00:19:34.504 So this month, we announced the general availability of 00:19:34.504 --> 00:19:41.400 HDInsight and Power BI Pro for Microsoft Cloud for Government. 00:19:41.400 --> 00:19:47.329 So if you have any government customer where you want to use 00:19:47.329 --> 00:19:52.538 the Cognitive tools, you capabilities. 00:19:52.538 --> 00:19:56.699 We are also going to announce a preview of Cognitive Services 00:19:56.699 --> 00:19:58.255 in Azure Government. 00:19:58.255 --> 00:20:01.876 So we have enabled scenarios such as for example, if you want 00:20:01.876 --> 00:20:05.218 to do Audio and text translation into other languages. 00:20:05.218 --> 00:20:08.530 We want to do emotion recognition with computer 00:20:08.530 --> 00:20:10.000 vision. 00:20:10.000 --> 00:20:14.743 And it's that all these service we're offering a preview on 00:20:14.743 --> 00:20:16.329 Azure governance. 00:20:25.886 --> 00:20:29.924 Okay the next one is the Real-time Geospatial Analytics 00:20:29.924 --> 00:20:31.950 in Azure Stream Analytics. 00:20:33.130 --> 00:20:36.640 The Mm-hm we only talk about Azure Stream Analytics right? 00:20:36.640 --> 00:20:44.360 It lets you analyze data in real time and stream as it comes in. 00:20:45.610 --> 00:20:48.640 So this month we've announced the general availability of 00:20:48.640 --> 00:20:50.290 Geospatial Function. 00:20:50.290 --> 00:20:53.970 So what it gives you is say, for example you have scenarios where 00:20:53.970 --> 00:20:57.620 you want to do fleet monitoring or you want to track any assets, 00:20:57.620 --> 00:20:59.620 or you want to do any kind of geofencing, or 00:20:59.620 --> 00:21:04.730 you want to do phone tracking across different cell sites. 00:21:04.730 --> 00:21:06.530 Or you want to do a solution for 00:21:06.530 --> 00:21:10.360 something like work pool where you want to do ridesharing. 00:21:10.360 --> 00:21:13.760 There basically you want to get a location at a real 00:21:14.850 --> 00:21:19.270 time from any device that is sending database cloud. 00:21:20.560 --> 00:21:24.120 Now we have Azure analytics in Azure team. 00:21:24.120 --> 00:21:30.200 And let it query where you can analyze the telemetry during and 00:21:30.200 --> 00:21:31.040 after the. 00:21:31.040 --> 00:21:35.910 So for example A scenario where you want to generate an event or 00:21:35.910 --> 00:21:39.660 you want to send an alert where a gas station is less than 10 00:21:39.660 --> 00:21:40.460 kilometers from the car. 00:21:40.460 --> 00:21:41.500 So you and 00:21:41.500 --> 00:21:45.160 your cars location which is then second cloud constantly. 00:21:45.160 --> 00:21:48.664 And the cloud has a list of stored location 00:21:48.664 --> 00:21:52.091 case that this is a gas station at this location. 00:21:52.091 --> 00:21:56.483 So basically you can write a query where you can select from 00:21:56.483 --> 00:22:01.416 your gas location you can select whichever installed gas station 00:22:01.416 --> 00:22:04.235 in less than 10 kilometer radius. 00:22:04.235 --> 00:22:06.980 Send you an alert whenever there is a gas station. 00:22:06.980 --> 00:22:10.189 So the result of these all kinda different queries. 00:22:10.189 --> 00:22:13.800 Now, you can go over the geospatial function. 00:22:13.800 --> 00:22:16.960 If you get the geo-adajacent standard for 00:22:16.960 --> 00:22:20.510 bringing this geospatial data. 00:22:20.510 --> 00:22:21.790 It look does a lot of extension. 00:22:21.790 --> 00:22:25.390 You can do create point, you can create a polygon. 00:22:25.390 --> 00:22:27.710 You can data mine the distance. 00:22:27.710 --> 00:22:31.910 You can see if one polygon overlaps with others and 00:22:31.910 --> 00:22:34.320 lot of other things that you can do. 00:22:34.320 --> 00:22:38.126 To for again for all of this go to our documentation page 00:22:38.126 --> 00:22:39.960 humanity for do a function 00:22:46.973 --> 00:22:51.130 Okay, the next one we have is Azure Site Recovery Planner for 00:22:51.130 --> 00:22:51.795 VMware. 00:22:51.795 --> 00:22:55.520 So Azure Site Recovery is 00:22:55.520 --> 00:22:59.710 one of our service where it gives you a way to 00:23:01.290 --> 00:23:06.460 Create a complete disaster recovery solution on Azure. 00:23:06.460 --> 00:23:09.601 Where you can protect hundreds of your virtual machines to 00:23:09.601 --> 00:23:11.985 reach out on on-Prem or any other. 00:23:11.985 --> 00:23:16.197 You could create a complete disaster recovery solution 00:23:16.197 --> 00:23:17.580 within ASR. 00:23:17.580 --> 00:23:21.230 But to do this ASR, you need deployment planners. 00:23:21.230 --> 00:23:25.919 Basically before you do any ASR cutoff exercise or 00:23:25.919 --> 00:23:30.607 successfully draw distribution you need to first 00:23:30.607 --> 00:23:34.744 understand what even it was in department. 00:23:34.744 --> 00:23:39.687 How you are going to do your test failure and all that right? 00:23:39.687 --> 00:23:44.099 So this Site Recovery Deployment Planner tool is actually does 00:23:44.099 --> 00:23:45.270 a lot of things. 00:23:45.270 --> 00:23:47.410 It gives you compatibility assessment. 00:23:47.410 --> 00:23:51.660 So which of your on-Prem access server can be moved to Azure 00:23:51.660 --> 00:23:54.140 with ASR and which can be. 00:23:54.140 --> 00:23:56.700 It will give you. 00:23:56.700 --> 00:23:59.720 It will tell you that Microsoft Azure like how many storage 00:23:59.720 --> 00:24:01.530 accounts you will need. 00:24:01.530 --> 00:24:03.880 Whether you need standard accounts or 00:24:03.880 --> 00:24:05.630 premium storage accounts. 00:24:05.630 --> 00:24:09.970 Regard how many virtual machine capacities you will need. 00:24:11.030 --> 00:24:13.340 It will also factor in future growth. 00:24:13.340 --> 00:24:16.960 So how, how did the Deployment Planner work then? 00:24:16.960 --> 00:24:19.420 It has three different modes of application. 00:24:19.420 --> 00:24:20.096 One is for 00:24:20.096 --> 00:24:24.440 filing where it profiles all the servers that you want to protect 00:24:24.440 --> 00:24:29.060 from the next thirty days and it will record everything. 00:24:29.060 --> 00:24:31.290 Like different performance monitors, 00:24:31.290 --> 00:24:33.665 counters like they dry die off. 00:24:33.665 --> 00:24:36.744 The right die offs, data join, 00:24:36.744 --> 00:24:41.916 what is the number of course days, how many weeks you have. 00:24:41.916 --> 00:24:45.680 Right now, this planner is only available from VMware. 00:24:45.680 --> 00:24:50.060 So you can connect to VMware Vcenter server or 00:24:50.060 --> 00:24:55.310 VMware Vsphere server where all the videos are hosted. 00:24:55.310 --> 00:24:57.370 So that is the profiling mode. 00:24:57.370 --> 00:24:59.460 You can also do report generation. 00:24:59.460 --> 00:25:03.015 So in this Mode the tool will use the provide data we can 00:25:03.015 --> 00:25:03.755 build a report. 00:25:03.755 --> 00:25:08.085 So it will inputs, it will have recommendation, 00:25:08.085 --> 00:25:10.945 it will have virtual machine to storage placement, 00:25:10.945 --> 00:25:13.675 it will have the number of compatibility in it. 00:25:13.675 --> 00:25:16.025 It will also tell you the number of incompatible VM's. 00:25:16.025 --> 00:25:18.995 And in the last thing it will 00:25:18.995 --> 00:25:20.925 also help you do the through put calculation. 00:25:20.925 --> 00:25:27.490 So It will find the network to put that can be achieved from 00:25:27.490 --> 00:25:32.210 your on-premise environment to Microsoft Azure for a edition. 00:25:32.210 --> 00:25:36.710 So right now this tool, this planner, is available only for 00:25:36.710 --> 00:25:40.428 VMware and it's also available in copy. 00:25:47.890 --> 00:25:51.628 And with this you're actually coming towards the last slide 00:25:51.628 --> 00:25:52.440 that I have. 00:25:53.740 --> 00:25:58.792 It's Azure Stack TP3, Technical Preview 3, it actually. 00:25:58.792 --> 00:26:04.209 And now type the application innovation 00:26:04.209 --> 00:26:08.314 pay-as-you-use pricing model. 00:26:08.314 --> 00:26:12.920 So what is Azure Stack Technical Preview 3, right? 00:26:12.920 --> 00:26:19.219 So Azure Stack is you could prioritize your Azure-in-a-box. 00:26:19.219 --> 00:26:22.940 So for example, if you want to have your own 00:26:22.940 --> 00:26:26.570 private implementation of Azure in your own data center, 00:26:26.570 --> 00:26:28.920 you can use the Azure Stack. 00:26:28.920 --> 00:26:34.810 Technical Preview 3 is basically right now we are releasing. 00:26:34.810 --> 00:26:39.100 To use the stack and model generally available. 00:26:39.100 --> 00:26:41.360 The TP3 available for download. 00:26:44.670 --> 00:26:49.074 What it gives you with this announcement is the TP3 00:26:49.074 --> 00:26:51.580 cloud economy model on. 00:26:51.580 --> 00:26:55.500 So basically you will appear you use pricing that you have on 00:26:55.500 --> 00:26:58.880 Cloud, you will now get that with Azure Stack TP3. 00:26:58.880 --> 00:27:02.990 In the next road map, if you look at the road map. 00:27:02.990 --> 00:27:05.950 You will have Azure Functions 00:27:05.950 --> 00:27:08.920 which will soon be available to run on TP3. 00:27:08.920 --> 00:27:10.870 It will be followed by Blockchain, 00:27:10.870 --> 00:27:14.310 Cloud Foundry, and Mesos templates. 00:27:14.310 --> 00:27:19.330 So as you can see we are delivering in last few 00:27:19.330 --> 00:27:23.150 months we've had three different Techinal Preview, Azure Stack. 00:27:24.460 --> 00:27:29.030 That will keep going on till general availability and beyond. 00:27:30.210 --> 00:27:34.890 TP3 is the final plan measure Technical Preview before 00:27:34.890 --> 00:27:38.880 it will be available as the general availability for 00:27:38.880 --> 00:27:45.720 older 3 by 17 somewhere in 70 we are going to have 00:27:45.720 --> 00:27:50.810 Azure Stack in general availability, okay. 00:27:50.810 --> 00:27:53.580 So what are the different use cases? 00:27:53.580 --> 00:27:57.510 See for example if you want to have a consistent hybrid 00:27:57.510 --> 00:28:01.350 application, there's no many you can On premise or 00:28:01.350 --> 00:28:05.170 you want to do any purpose bill system for operational expenses 00:28:05.170 --> 00:28:10.290 that you want some of the cloud benefits on your on frame 00:28:10.290 --> 00:28:15.365 infra you can view the address tag for that. 00:28:15.365 --> 00:28:17.730 >> [INAUDIBLE] >> With that I think I had, 00:28:17.730 --> 00:28:21.730 this was the last >> lat announcement I had, 00:28:21.730 --> 00:28:24.210 we did not have a lot of different new things but 00:28:24.210 --> 00:28:27.160 we have some really interesting things this month. 00:28:27.160 --> 00:28:30.221 So with this, I'm now open for question and answer, 00:28:30.221 --> 00:28:33.566 you can type your question and I will get to them one by one. 00:28:49.019 --> 00:28:52.736 So there is one question from Abdul Kalim, any update 00:28:52.736 --> 00:28:58.045 on government community clouds, GPV for Indian Government? 00:28:58.045 --> 00:29:03.769 So right now, we do not have any update for Indian government but 00:29:03.769 --> 00:29:08.355 let me go back to our roadmap to connect with me. 00:29:08.355 --> 00:29:12.880 I'm going to share my I'm sorry I'm going to show you my 00:29:12.880 --> 00:29:19.620 tutorial to you all and this question, please read it to me. 00:29:19.620 --> 00:29:23.120 I really check out Road Map and if we have 00:29:23.120 --> 00:29:27.470 anything available in our Road Map I'll share it with you. 00:29:27.470 --> 00:29:28.543 So as we 00:29:33.163 --> 00:29:40.122 Called as Price User ID 00:29:40.122 --> 00:29:46.722 presented to you on. 00:29:54.807 --> 00:29:56.250 Okay, any other question? 00:29:56.250 --> 00:29:57.445 I'm gonna wait for 00:29:57.445 --> 00:30:00.587 few minutes if you have any questions you post them