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

API Evangelist conversational phrasing for Identity.SignIns Policies.federated Token Validation Policy…

4 actions 4 updates phrasing extends openapi/azure-ad-policies-federatedtokenvalidationpolicy-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 4

$.info
$.paths['/policies/federatedTokenValidationPolicy'].get
$.paths['/policies/federatedTokenValidationPolicy'].delete
$.paths['/policies/federatedTokenValidationPolicy'].patch

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 Identity.SignIns Policies.federated Token Validation Policy…
  version: 1.0.0
extends: openapi/azure-ad-policies-federatedtokenvalidationpolicy-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: 3
- target: $.paths['/policies/federatedTokenValidationPolicy'].get
  update:
    x-apievangelist-phrasing:
      intent: Get the federated token validation policy
      effect: read
      questions:
      - What is the federated token validation policy set to in my tenant?
      - Which validating domains are listed in the federated token validation policy?
      instructions:
      - text: Get the tenant's federated token validation policy.
      - text: Show the validating domains configured in the federated token validation policy.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/policies/federatedTokenValidationPolicy'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete the federated token validation policy
      effect: destructive
      questions:
      - Can I delete the federated token validation policy altogether?
      - How do I remove the tenant's federated token validation policy?
      instructions:
      - text: Delete the federated token validation policy.
      - text: Remove the federated token validation policy from the tenant.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/policies/federatedTokenValidationPolicy'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update the federated token validation policy
      effect: write
      questions:
      - How do I change which domains are validated for federated tokens?
      - Can I add a validating domain to the federated token validation policy?
      instructions:
      - text: Set the federated token validation policy's validating domains to {validatingDomains}.
        slots:
          validatingDomains: requestBody.validatingDomains
      - text: Update the validating domains for federated tokens to {validatingDomains}.
        slots:
          validatingDomains: requestBody.validatingDomains
      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-policies-federatedtokenvalidationpolicy-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.