Microsoft Entra ID (formerly Azure AD) · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Applications Service Principals.delegated Permission…

7 actions 7 updates phrasing extends openapi/azure-ad-serviceprincipals-delegatedpermissionclassification-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Microsoft Entra ID (formerly Azure AD)'s API. It is a proposal applied on top of the contract, not a document Microsoft Entra ID (formerly Azure AD) publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 7

$.info
$.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications'].get
$.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications'].post
$.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications/{delegatedPermissionClassification-id}'].get
$.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications/{delegatedPermissionClassification-id}'].delete
$.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications/{delegatedPermissionClassification-id}'].patch
$.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications/$count'].get

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Applications Service Principals.delegated Permission…
  version: 1.0.0
extends: openapi/azure-ad-serviceprincipals-delegatedpermissionclassification-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 6
- target: $.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications'].get
  update:
    x-apievangelist-phrasing:
      intent: List delegated permission classifications
      effect: read
      questions:
      - Which delegated permissions exposed by my API have been classified?
      - Can I see all permission classifications configured on a service principal?
      instructions:
      - text: List delegated permission classifications for service principal {sp}.
        slots:
          sp: path.servicePrincipal-id
      - text: List permission classifications on {sp} matching {filter}.
        slots:
          sp: path.servicePrincipal-id
          filter: query.$filter
      method: generated
      generated: '2026-10-01'
- target: $.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications'].post
  update:
    x-apievangelist-phrasing:
      intent: Classify a delegated permission
      effect: write
      questions:
      - How do I classify a delegated permission as low impact?
      - Can I classify a permission by its name instead of its ID?
      instructions:
      - text: Classify permission {permission} on service principal {sp} as {classification}.
        slots:
          permission: requestBody.permissionName
          sp: path.servicePrincipal-id
          classification: requestBody.classification
      - text: Add a {classification} classification for permission ID {permissionId} on {sp}.
        slots:
          classification: requestBody.classification
          permissionId: requestBody.permissionId
          sp: path.servicePrincipal-id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications/{delegatedPermissionClassification-id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a delegated permission classification
      effect: read
      questions:
      - Can I read a single delegated permission classification?
      - What classification is set on one specific permission entry?
      instructions:
      - text: Get classification {classificationId} on service principal {sp}.
        slots:
          classificationId: path.delegatedPermissionClassification-id
          sp: path.servicePrincipal-id
      - text: Show delegated permission classification {classificationId} of {sp}, selecting {select}.
        slots:
          classificationId: path.delegatedPermissionClassification-id
          sp: path.servicePrincipal-id
          select: query.$select
      method: generated
      generated: '2026-10-01'
- target: $.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications/{delegatedPermissionClassification-id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Remove a delegated permission classification
      effect: destructive
      questions:
      - How do I remove a classification from a delegated permission?
      - Can I delete a permission classification I set earlier?
      instructions:
      - text: Delete classification {classificationId} from service principal {sp}.
        slots:
          classificationId: path.delegatedPermissionClassification-id
          sp: path.servicePrincipal-id
      - text: Remove delegated permission classification {classificationId} on {sp} if ETag {etag} matches.
        slots:
          classificationId: path.delegatedPermissionClassification-id
          sp: path.servicePrincipal-id
          etag: header.If-Match
      method: generated
      generated: '2026-10-01'
- target: $.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications/{delegatedPermissionClassification-id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update a delegated permission classification
      effect: write
      questions:
      - Can I change a delegated permission's classification after setting it?
      - Is it possible to repoint an existing classification at another permission name?
      instructions:
      - text: Change classification {classificationId} on {sp} to {classification}.
        slots:
          classificationId: path.delegatedPermissionClassification-id
          sp: path.servicePrincipal-id
          classification: requestBody.classification
      - text: Update classification {classificationId} of {sp} to cover permission {permission}.
        slots:
          classificationId: path.delegatedPermissionClassification-id
          sp: path.servicePrincipal-id
          permission: requestBody.permissionName
      method: generated
      generated: '2026-10-01'
- target: $.paths['/servicePrincipals/{servicePrincipal-id}/delegatedPermissionClassifications/$count'].get
  update:
    x-apievangelist-phrasing:
      intent: Count delegated permission classifications
      effect: read
      questions:
      - How many delegated permission classifications does a service principal have?
      - Can I count classified permissions matching a filter?
      instructions:
      - text: Count delegated permission classifications on {sp}.
        slots:
          sp: path.servicePrincipal-id
      - text: Count permission classifications of {sp} where {filter}.
        slots:
          sp: path.servicePrincipal-id
          filter: query.$filter
      method: generated
      generated: '2026-10-01'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/azure-ad-serviceprincipals-delegatedpermissionclassification-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.