Microsoft Azure

Azure Monitoringservice: Pipeline Groups

Provides operations for working with Azure Monitor Pipelines

Developer tools#openapi

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Provides operations for working with Azure Monitor Pipelines

Endpoints 7

Operations

  • GETOperations_List/providers/Microsoft.Monitor/operationsList the operations for the provider

PipelineGroups

  • GETPipelineGroups_ListBySubscription/subscriptions/:subscriptionId/providers/Microsoft.Monitor/pipelineGroupsLists all workspaces in the specified subscription
  • GETPipelineGroups_ListByResourceGroup/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Monitor/pipelineGroupsLists all workspaces in the specified resource group
  • GETPipelineGroups_Get/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Monitor/pipelineGroups/:pipelineGroupNameReturns the specific pipeline group instance.
  • PUTPipelineGroups_CreateOrUpdate/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Monitor/pipelineGroups/:pipelineGroupNameCreate or update a pipeline group instance.
  • DELETEPipelineGroups_Delete/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Monitor/pipelineGroups/:pipelineGroupNameDelete a pipeline group instance.
  • PATCHPipelineGroups_Update/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Monitor/pipelineGroups/:pipelineGroupNameUpdates a pipeline group instance

API details

Base URL
https://management.azure.com
Authentication
OAuth 2.0 (implicit flow) with 1 scope
Operations
7 operations on 4 pathsGET 4PUT 1PATCH 1DELETE 1
Main resources
PipelineGroups 6Operations 1
Response formats
application/json
Description format
Swagger 2.0, API version 2026-04-01

How to test the Azure Monitoringservice: Pipeline Groups in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Azure Monitoringservice: Pipeline Groups collection, without the publisher's secrets.
  3. Add your credentialsThis API uses OAuth 2.0 (implicit flow) with 1 scope. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Operations_List” (GET /providers/Microsoft.Monitor/operations), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Azure Monitoringservice: Pipeline Groups?

Provides operations for working with Azure Monitor Pipelines It is listed under Developer tools and has 7 endpoints.

Who publishes the Azure Monitoringservice: Pipeline Groups?

It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Azure Monitoringservice: Pipeline Groups?

Requests go to https://management.azure.com. Endpoint paths are added to this base URL.

How do I authenticate with the Azure Monitoringservice: Pipeline Groups?

With OAuth 2.0 (implicit flow) with 1 scope.

How many endpoints does the Azure Monitoringservice: Pipeline Groups have?

7 operations on 4 paths (4 GET, 1 PUT, 1 PATCH, 1 DELETE). The largest groups are PipelineGroups, Operations.

Is forking the Azure Monitoringservice: Pipeline Groups free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.