2.3 Azure Resource Providers
Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »

Video Transcription
00:01
Let's talk about the actual research providers.
00:05
Each Asher service implements their own resource provider.
00:12
The lease is provided implementation. Miss. Comply with the arm requirements.
00:16
You can consider this the contract between the service and any external clients.
00:22
The reserves provider implements all business logic that this applicable for that particular service.
00:28
One example could be that Windows Virtual machines cannot have names longer than 15 characters.
00:34
Another one is that azure storage account names can only use letters and numbers and so on.
00:40
The resource provider also implements the AP eyes for the service that, once again forced three guidelines to ensure consistency. Between service is.
00:51
Here is a list of resource providers and how they map to each as your service.
00:58
The documentation is pretty extensive.
01:00
If you click on the left side on Rest Resource Manager, you'll find complete documentation of the rest. AP Eyes for resource manager,
01:08
including each resource provider.
01:11
Let's find out how to power off a virtual machine using the rest ap ice,
01:17
so you need to find the
01:19
compute
01:23
resource providing you click on Compute.
01:26
That is the virtual machine resource.
01:30
You click on virtual machine and you find powered off
01:34
This is the rest call that you need to make in orderto power off the virtual machine.
01:42
Let's look at the rest a p i n point structure
01:47
using the virtual machine power off rest. Cough us example. Here is how the Resco is structured.
01:53
You kept posed us tomato.
01:57
Next, you have the Ascher Resource Manager
02:01
and Point,
02:02
which is always http. Colon slash slash management daughter jules dot com
02:08
After that force, the resource identifier,
02:13
the resource identifier has occurred article structure, and it is always the same. It starts with subscriptions, the subscription i D. Then resource groups, the name of the resource group
02:24
providers,
02:27
actual resource provider and then the resource, and some identifier for the resource.
02:34
For example, if you need to identify a Sequels database server resource, you can easily build identifier. You will always start with the subscription, the subscription I D. The name of the resource group
02:46
and the providers. However, you need to change the provider from Microsoft dot compute to Microsoft DOT sequel.
02:54
Then you will have a sequel server, and then you have the name of the sequel server.
03:00
Quite simple schema. That is easy to remember
03:02
when performing actions on the resource is like power off.
03:07
You got the action at the end. You can see how this is done in the U. L.
03:14
The last one is the A P I version that you want to use for the rest. Call
03:19
the A P I version is specified. That's a query string. Part of matter.
03:23
Keep in mind that the FBI version is important because certain operations may not be available in order a p I versions.
03:35
You can always find the AP I version. If you go to the arm, rest reference and look at the top of the page.
03:45
Make sure that you remember the structure of the resource identifier in the FBI version because you won't need those when you develop arm templates for automation
03:54
because we mentioned arm templates, let's look at some more terminology. That will be good to be familiar with when you're working with arm
Up Next
Instructed By
Similar Content