{"id":8739,"date":"2024-01-18T00:11:18","date_gmt":"2024-01-18T00:11:18","guid":{"rendered":"https:\/\/cheapwindowsvps.com\/blog\/managing-azure-resources-using-powershell-cmdlet-invoke-azrestmethod-in-azure-rest-api\/"},"modified":"2025-01-20T10:32:29","modified_gmt":"2025-01-20T10:32:29","slug":"managing-azure-resources-using-powershell-cmdlet-invoke-azrestmethod-in-azure-rest-api","status":"publish","type":"post","link":"https:\/\/cheapwindowsvps.com\/blog\/managing-azure-resources-using-powershell-cmdlet-invoke-azrestmethod-in-azure-rest-api\/","title":{"rendered":"Managing Azure Resources Using PowerShell cmdlet Invoke-AzRestMethod in Azure REST API"},"content":{"rendered":"
Sometimes, managing certain Azure resources using PowerShell can be challenging due to the absence of specific cmdlets for those operations or services. This is where the Invoke-AzRestMethod cmdlet comes into play, which allows PowerShell scripts to communicate with Azure services by sending HTTP requests to Azure’s REST API. It acts as a bridge between PowerShell and Azure services that still need to be integrated with cmdlets.<\/div>\n

Using Invoke-AzRestMethod with a GET method<\/h2>\n

As an example, let\u2019s try to get the diagnostics settings of a management group using a GET method in our request. We have two options here.<\/p>\n

    \n
  1. We can individually specify each parameter.<\/li>\n
  2. We can use PowerShell splatting, a method where we create a collection of parameters and pass them to the cmdlet as the parameter set. Doing so can streamline the process and make commands in your scripts easier to read.<\/li>\n<\/ol>\n

    Let\u2019s use option one.<\/p>\n

    ((Invoke-AzRestMethod -Method 'GET' -Path ( 'providers\/microsoft.management\/managementGroups\/{0}\/providers\/microsoft.insights\/diagnosticSettings?api-version=2020-01-01-preview' -f 'IT')).content | convertfrom-json).value | fl *<\/pre>\n
    Using a GET method with Invoke-AzRestMethod to pull data from Azure<\/a><\/p>\n
    And here is option two:<\/p>\n
    <\/pre>\n
    $params = @{<\/p>\n
    method = ‘GET’<\/p>\n
    path = ‘providers\/microsoft.management\/managementGroups\/{0}\/providers\/microsoft.insights\/diagnosticSettings?api-version=2020-01-01-preview’ -f ‘IT’<\/p>\n
    }<\/p>\n
    ((Invoke-AzRestMethod @params).content | convertfrom-json).value | fl *<\/p>\n
    The result will be the same.<\/p>\n
    Using PowerShell splatting with Invoke-AzRestMethod<\/a><\/p>\n
    Using Invoke-AzRestMethod with a POST method<\/h2>\n
    We can gather information from Azure by employing an Azure Resource Graph query with the use of Invoke-AzRestMethod<\/em>. To deliver our query to the Azure Resource Graph Service, we require the POST method to provide Azure with the said query. The Services processes it and brings back the results as expected.<\/p>\n
    We start with creating a Resource Graph Query. In the following demonstration, the query is intended to retrieve all resources within a certain resource group of a subscription. We can include the query in our request by placing it in the “payload”.<\/p>\n
    <\/pre>\n
    $query = @’<\/p>\n
    {<\/p>\n
    “query”: “resources<\/p>\n
    | where type contains ‘virtualnetworks’<\/p>\n
    | where resourceGroup == ‘devcenter’<\/p>\n
    | join kind=inner (<\/p>\n
    resourcecontainers<\/p>\n
    | where type == ‘microsoft.resources\/subscriptions’<\/p>\n
    | project subscriptionId, subscriptionName = name)<\/p>\n
    on subscriptionId<\/p>\n
    | where subscriptionName contains ‘2023’<\/p>\n
    | project subscriptionName, resourceGroup, name, type”<\/p>\n
    }<\/p>\n
    ‘@<\/p>\n
    $Params = @{<\/p>\n
    path = ‘\/providers\/Microsoft.ResourceGraph\/resources?api-version=2022-10-01’<\/p>\n
    Method = ‘POST’<\/p>\n
    Payload = $($query)<\/p>\n
    }<\/p>\n
    Invoke-AzRestMethod @Params | select -ExpandProperty CONTENT | convertfrom-json | select -ExpandProperty data<\/p>\n
    Using a POST method to send a query to Azure<\/p>\n
    Enabling features using a PUT method<\/h2>\n
    Let’s examine how we can use the cmdlet with PUT methods.<\/p>\n
    In certain scenarios, enabling a feature on a service using a PowerShell module is impossible. For such cases, the Invoke-AzRestMethod<\/em> cmdlet is handy. By adding the necessary settings to the request’s payload and using the PUT method, we can send the request to the ARM endpoint for the desired settings to be applied to the Azure service.<\/p>\n
    In the following example, we will enable diagnostics settings on a management group using the Invoke-AzRestMethod <\/em>cmdlet. As we need to specify values for the new settings on the management group, we will use a PUT method. As a result, the request must include a BODY in the payload, which will contain all the required settings in the request. These settings will then be applied to the service when enabling diagnostics settings on the management group.<\/p>\n
    Subscribe to 4sysops newsletter!<\/h2>\n
    <\/pre>\n
    $Body = [string](<\/p>\n
    @{<\/p>\n
    ‘properties’ =@{<\/p>\n
    ‘workspaceId’ = ‘\/subscriptions\/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx\/resourceGroups\/loganalytics\/providers\/Microsoft.OperationalInsights\/workspaces\/la01’<\/p>\n
    ‘logs’ = [array](<\/p>\n
    @{<\/p>\n
    ‘category’ = [string] ‘Administrative’<\/p>\n
    ‘enabled’ = [bool] $true<\/p>\n
    },<\/p>\n
    @{<\/p>\n
    ‘category’ = [string] ‘Policy’<\/p>\n
    ‘enabled’ = [bool] $false<\/p>\n
    }<\/p>\n
    )<\/p>\n
    }<\/p>\n
    } | ConvertTo-Json -Compress -Depth 3<\/p>\n
    )<\/p>\n
    $params = @{<\/p>\n
    method = ‘PUT’<\/p>\n
    path = ‘\/providers\/microsoft.management\/managementGroups\/{0}\/providers\/microsoft.insights\/diagnosticSettings\/{1}?api-version=2020-01-01-preview’ -f ‘IT2′,’setting01’<\/p>\n
    payload = $body<\/p>\n
    }<\/p>\n
    Invoke-AzRestMethod @params<\/p>\n","protected":false},"excerpt":{"rendered":"
    Sometimes, managing certain Azure resources using PowerShell can be challenging due to the absence of specific cmdlets for those operations or services. This is where the Invoke-AzRestMethod cmdlet comes into play, which allows PowerShell scripts to communicate with Azure services by sending HTTP requests to Azure’s REST API. It acts as a bridge between PowerShell […]<\/p>\n","protected":false},"author":1,"featured_media":8740,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[92,107,126,117],"tags":[],"class_list":["post-8739","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-articles","category-azure","category-cloud-computing","category-powershell"],"_links":{"self":[{"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/posts\/8739","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/comments?post=8739"}],"version-history":[{"count":3,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/posts\/8739\/revisions"}],"predecessor-version":[{"id":10387,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/posts\/8739\/revisions\/10387"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/media\/8740"}],"wp:attachment":[{"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/media?parent=8739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/categories?post=8739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/tags?post=8739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}