EngagementFabric

Name: EngagementFabric API
Brand: EngagementFabric
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat Messagingoauth216 EndpointsREST

For Agents

Manage Microsoft EngagementFabric accounts, attached communication channels, and account access keys for customer messaging deployments on Azure.

Connect the EngagementFabric to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EngagementFabric, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with EngagementFabric API.

Create or update an EngagementFabric account in a subscription

Attach a communication channel (SMS, email, chat) to an account

List the channel types available to a given account

Rotate or list the access keys for an EngagementFabric account

GET STARTED

Start building with EngagementFabric API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for EngagementFabric, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for EngagementFabric, keeping it validated and agent-ready. Microsoft Customer EngagementFabric is the resource provider that hosts engagement accounts and the channels (SMS, email, chat, social) that route customer-facing messages. The API exposes 16 endpoints covering account CRUD, channel CRUD, channel-type discovery, account key listing and rotation, and resource name availability checks. Use it where existing EngagementFabric accounts still drive messaging flows.

Use Cases

Patterns agents use EngagementFabric API for, with concrete tasks.

★ Multi-Channel Customer Messaging Platform

Operations teams running an EngagementFabric account often add multiple channels — SMS, email, chat — to reach customers across the right surface. The API exposes Accounts_CreateOrUpdate, Channels_CreateOrUpdate, and Accounts_ListChannelTypes, so an automation can stand up a fresh account, query the supported channel types, and attach the right channels in one run rather than clicking through the portal.

Create an EngagementFabric account named promo-eng in resource group marketing-rg, list the available channel types via Accounts_ListChannelTypes, and attach an SMS channel.

Programmatic Access Key Rotation

Security policy commonly requires API-key rotation every 90 days. EngagementFabric exposes Accounts_ListKeys and Accounts_RegenerateKey on the account resource, so a scheduled job can pull the current keys, rotate them, update consuming applications, and confirm the new key is live without human intervention.

Call Accounts_ListKeys on EngagementFabric account promo-eng, then Accounts_RegenerateKey for the secondary key, and return the new value.

Channel Hygiene Across the Tenant

EngagementFabric accounts collect channels over time. By listing accounts via Accounts_List and then enumerating channels with Channels_ListByAccount, an agent can identify channels that are no longer used and call Channels_Delete to clean up. This keeps the messaging surface tight and reduces accidental sends.

List every channel on EngagementFabric account promo-eng, identify any with no traffic in the past 30 days, and delete them.

AI Agent Engagement Setup via Jentic

An agent integrated through Jentic can resolve a request like spin up an EngagementFabric account with SMS and email channels end-to-end. It searches Jentic for create engagementfabric account, loads Accounts_CreateOrUpdate and Channels_CreateOrUpdate, and applies the right configuration. Credentials never leave the Jentic vault.

Through Jentic, search for create engagementfabric account, load Accounts_CreateOrUpdate, and provision the account, then call Channels_CreateOrUpdate to attach an SMS channel.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for engagementfabric, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}

Create or update an EngagementFabric account

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}/Channels/{channelName}

Create or update a channel

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}/listKeys

List account access keys

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}/regenerateKey

Regenerate an account access key

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}/listChannelTypes

List channel types available on an account

POST

/subscriptions/{subscriptionId}/providers/Microsoft.EngagementFabric/checkNameAvailability

Check availability of an EngagementFabric resource name

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}

Create or update an EngagementFabric account

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}/Channels/{channelName}

Create or update a channel

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}/listKeys

List account access keys

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}/regenerateKey

Regenerate an account access key

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD client credentials are stored encrypted in the Jentic vault (MAXsystem). The agent receives a bearer token scoped to management.azure.com only — the underlying secret stays out of agent context.

Intent-based discovery

Agents search by intent (e.g. 'create engagementfabric account') and Jentic returns the matching Accounts_* or Channels_* operation along with its full input schema, so the agent picks the right endpoint without browsing ARM docs.

Time to first call

Direct integration: 1-2 days for AAD token acquisition, ARM URL construction, and async LRO polling on account creation. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Engagement.ManagementClient

Legacy Azure Mobile Engagement push campaign API rather than channel-based messaging

Choose when the workload uses Mobile Engagement push campaigns rather than EngagementFabric channels

Complementary

EventGrid Management Client

Wire EngagementFabric events into downstream Azure subscribers

Use to fan out engagement events to consumers like Azure Functions

Complementary

DNS Management Client

Manage DNS records that may front EngagementFabric-driven services

Use when the agent needs DNS changes for the customer-facing services using EngagementFabric

FAQs

Specific to using EngagementFabric API through Jentic.

Why is there no official OpenAPI spec for EngagementFabric?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call EngagementFabric via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does EngagementFabric use?

It uses Azure Active Directory OAuth 2.0 (azure_auth) against https://management.azure.com/. The principal needs at least Contributor on the target resource group. Through Jentic the underlying client secret stays in the Jentic vault and the agent only receives a scoped bearer token.

Can I attach more than one channel to a single EngagementFabric account?

Yes. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EngagementFabric/Accounts/{accountName}/Channels/{channelName} is keyed on channelName, so you can attach multiple channels per account. Check supported types for the account first via Accounts_ListChannelTypes.

What are the rate limits for EngagementFabric?

Standard Azure Resource Manager subscription-scoped throttling applies (broadly 12,000 reads per hour and 1,200 writes per hour). The API itself returns the usual ARM throttling headers — message-throughput limits live with the upstream channel provider rather than this control-plane API.

How do I rotate account keys through Jentic?

Run pip install jentic, search for rotate engagementfabric account keys, load Accounts_RegenerateKey, supply accountName and the keyName (Primary or Secondary), then execute. Confirm the rotation by calling Accounts_ListKeys and verifying the new value.

Does this API send messages on a channel directly?

No. EngagementFabric is a control-plane API for managing accounts, channels, and keys. Sending the actual SMS, email, or chat messages happens against the channel provider's data plane using the keys returned by Accounts_ListKeys.