WEBVTT 1 00:00.000 --> 00:08.360 So now it's time to find out if that Azure application we made earlier is 2 00:08.360 --> 00:13.430 actually configured properly and we copied our four key pieces of information 3 00:13.430 --> 00:19.000 properly in order to get on ramp properly authenticated to the Azure 4 00:19.000 --> 00:20.000 environment. 5 00:20.000 --> 00:25.520 So that's exactly what we're going to do here. Let's jump in and configure the 6 00:25.520 --> 00:30.000 authentication for cloud on ramp to talk to our Azure environment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:30.000 --> 00:35.000 So let's begin here on the SD when monitor overview page. 8 00:35.000 --> 00:39.530 The main things we want to look at here. First, notice that all of our 9 00:39.530 --> 00:45.000 controllers are online. So we have our V bond RV smart and RV manage. 10 00:45.000 --> 00:52.130 And at the moment, we have one way an edge device, which is on Prem router one. 11 00:52.130 --> 00:55.000 So this is the device that's already configured. 12 00:55.000 --> 00:59.640 What we're looking for, of course, when this is all complete is we should 13 00:59.640 --> 01:04.850 actually have three way and edges, the one on Prem router and the two that are WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:59.640 --> 01:04.850 actually have three way and edges, the one on Prem router and the two that are 14 01:04.850 --> 01:08.000 going to be deployed into Microsoft Azure. 15 01:08.000 --> 01:13.280 But before we can do that, again, we need to start with configuring cloud on 16 01:13.280 --> 01:18.000 ramp. So to do this, let's begin by going to our main menu. 17 01:18.000 --> 01:24.000 We'll go to configuration and we'll go to cloud on ramp for multi cloud. 18 01:24.000 --> 01:29.020 Now the way we're going to be configuring this is using the workflows down here 19 01:29.020 --> 01:34.260 at the bottom of the page. So we're going to start on the far left with our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 19 01:29.020 --> 01:34.260 at the bottom of the page. So we're going to start on the far left with our 20 01:34.260 --> 01:35.000 setup. 21 01:35.000 --> 01:39.640 So we'll move down here and we'll go to associate a cloud account. The first 22 01:39.640 --> 01:43.840 thing we're going to have to do is select our cloud provider. So we'll come up 23 01:43.840 --> 01:46.000 here. We'll click on the drop down. 24 01:46.000 --> 01:51.570 And of course, we're going to be choosing Microsoft Azure. We'll give the cloud 25 01:51.570 --> 01:53.000 account a name. 26 01:53.000 --> 01:56.990 This is a local name. You can just call this whatever you want. So we'll just 27 01:56.990 --> 02:01.220 call it Azure off for Azure authentication. If you want, you can give it a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 01:56.990 --> 02:01.220 call it Azure off for Azure authentication. If you want, you can give it a 28 02:01.220 --> 02:04.000 description. That's, of course, optional. 29 02:04.000 --> 02:08.290 When it says to use this for the cloud gateway, we want to say yes, because we 30 02:08.290 --> 02:11.000 are going to be deploying a cloud gateway. 31 02:11.000 --> 02:16.000 And here's where we need to provide those four key pieces of information. 32 02:16.000 --> 02:23.350 The tenant ID, the subscription ID, the client ID, and the secret key, all of 33 02:23.350 --> 02:27.690 which we copied earlier. So let me go ahead and paste those in to our 34 02:27.690 --> 02:29.000 configuration. 35 02:29.000 --> 02:34.130 So now that we have this information pasted in here properly. Well, it's the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 02:29.000 --> 02:34.130 So now that we have this information pasted in here properly. Well, it's the 36 02:34.130 --> 02:38.000 moment of truth. Let's go ahead and hit add. 37 02:38.000 --> 02:44.380 As we can see, this has been successful. So we get the success message. We get 38 02:44.380 --> 02:49.000 information down here at the bottom telling us our cloud account ID. 39 02:49.000 --> 02:52.960 The cloud account name we created, of course, if we had put in a description, 40 02:52.960 --> 02:58.000 it would be here. It tells us that the cloud type is Azure. And of course, the 41 02:58.000 --> 03:02.000 credential type, the cloud gateway is enabled. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 02:58.000 --> 03:02.000 credential type, the cloud gateway is enabled. 42 03:02.000 --> 03:06.550 And notice it's already gone out and picked up on the fact that there are 90 43 03:06.550 --> 03:11.400 regions available. So this has been successful, which means that the 44 03:11.400 --> 03:15.000 application we created is configured properly. 45 03:15.000 --> 03:19.930 So now that our cloud authentication is working properly, we can now work on 46 03:19.930 --> 03:25.280 configuring the cloud global parameters, which is what we're going to do in the 47 03:25.280 --> 03:26.000 next video. 48 03:26.000 --> 03:26.500 Yeah.