Engagement.ManagementClient

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationoauth237 EndpointsREST

For Agents

Manage Azure Mobile Engagement app collections, push campaigns (announcements, polls, data push, native push), and device or activity export tasks across the full campaign lifecycle.

Connect the Engagement.ManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Engagement.ManagementClient, 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 Engagement.ManagementClient API.

Create push campaigns for announcements, polls, data push, and native push

Activate, suspend, finish, or test a campaign already saved

Push a saved campaign on demand to targeted devices

Query devices running a Mobile Engagement-instrumented app

GET STARTED

Start building with Engagement.ManagementClient API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Engagement.ManagementClient, keeping it validated and agent-ready. Microsoft Azure Mobile Engagement was a managed mobile-app engagement service that powered targeted push campaigns, in-app announcements, polls, and device-level analytics. The Engagement.ManagementClient API exposes 37 endpoints covering app collections, applications, push campaigns of every kind (announcement, poll, data push, native), campaign lifecycle (create, activate, suspend, finish, push, test), device queries, and export tasks for activities and devices. Use it where existing Mobile Engagement deployments still need programmatic management.

Use Cases

Patterns agents use Engagement.ManagementClient API for, with concrete tasks.

★ Targeted Mobile Push Campaign Lifecycle

Marketing teams running Mobile Engagement-instrumented apps need to draft a campaign, test it on a small device set, activate it, monitor live statistics, and finish it cleanly. The Engagement.ManagementClient API exposes the full lifecycle through Campaigns_Create, Campaigns_TestNew, Campaigns_Activate, Campaigns_GetStatistics, and Campaigns_Finish — so an automation can drive an entire campaign without touching the legacy portal.

Create an announcement campaign on app myapp in collection prod, test it on a 100-device cohort, activate it after the test passes, and return the campaign ID.

On-Demand Promo Push from a Saved Template

Operational teams keep pre-approved campaign templates for time-sensitive promos. The Campaigns_Push endpoint sends a previously saved campaign to its target audience on demand — the agent does not need to recreate the payload, just call push with the campaign ID. Combined with Campaigns_GetStatistics this supports rapid iteration during a flash sale.

Call Campaigns_Push for the saved campaign with id 12345 of kind announcement on app myapp.

Device and Activity Analytics Export

When integrating Mobile Engagement into a larger analytics warehouse, teams need to export device-level and activity-level data. The API exposes ExportTasks_CreateActivitiesTask and ExportTasks_List, plus Devices_List, so a scheduled job can request a fresh export, poll for completion, and pull the result into BigQuery, Synapse, or Snowflake for unified analysis.

Create an activities export task for app myapp covering 2026-06-01 to 2026-06-09 and poll ExportTasks_List until the task state reads Succeeded.

AI Agent Campaign Operations via Jentic

An automation agent integrated through Jentic can resolve a request like push a discount announcement to all iOS users in France end-to-end. It searches Jentic for create azure mobile engagement campaign, loads Campaigns_Create with the right payload shape, calls Campaigns_Activate, and reports completion. Credentials never leave the Jentic vault.

Through Jentic, search for create azure mobile engagement announcement campaign, load Campaigns_Create, and create a campaign of kind announcement on app myapp targeting devices with locale=fr_FR.

Key Endpoints

37 endpoints — jentic publishes the only available openapi specification for engagement.

METHOD

PATH

DESCRIPTION

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}

Create a push campaign of a given kind

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}/{id}/activate

Activate a saved campaign

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}/{id}/push

Push a saved campaign on demand

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}/{id}/finish

Finish a running campaign

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}/{id}/statistics

Get statistics for a campaign

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/devices/exportTasks/activities

Create an activities export task

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}

Create a push campaign of a given kind

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}/{id}/activate

Activate a saved campaign

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}/{id}/push

Push a saved campaign on demand

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}/{id}/finish

Finish a running campaign

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 short-lived bearer token scoped to management.azure.com — the underlying secret stays out of agent context.

Intent-based discovery

Agents search by intent (e.g. 'create azure mobile engagement campaign' or 'push notification azure') and Jentic returns the matching Campaigns_* operation with its full input schema, so the agent picks the right endpoint without browsing legacy ARM docs.

Time to first call

Direct integration with a deprecated service: 2-3 days to find current docs, set up AAD auth, and handle the campaign lifecycle. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

EngagementFabric

Microsoft Customer Engagement Fabric — manages multi-channel engagement accounts and channels rather than mobile push campaigns

Choose when the agent needs to manage EngagementFabric channels (SMS, email) rather than legacy Mobile Engagement push campaigns

Complementary

EventGrid Management Client

Wire engagement events into downstream Azure consumers

Use to fan out campaign or device events across Azure services

Complementary

Diagnostics API Client

Diagnose App Service workloads that may host the engagement back end

Use when the issue is App Service health rather than engagement campaigns

FAQs

Specific to using Engagement.ManagementClient API through Jentic.

Why is there no official OpenAPI spec for Engagement.ManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Engagement.ManagementClient 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 the Engagement.ManagementClient 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 sees a scoped bearer token.

Can I send a push campaign without recreating it every time?

Yes. Once a campaign is saved with Campaigns_Create, POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MobileEngagement/appcollections/{appCollection}/apps/{appName}/campaigns/{kind}/{id}/push pushes it on demand to its targeted device set without changing the campaign payload.

What are the rate limits for the Engagement.ManagementClient?

Standard Azure Resource Manager subscription-scoped throttling applies (broadly 12,000 reads per hour and 1,200 writes per hour). Push delivery itself is bounded by Mobile Engagement quotas on campaign volume — confirm your account-level limits before bursting bulk campaigns.

How do I create and activate a campaign through Jentic?

Run pip install jentic, search for create azure mobile engagement campaign, load Campaigns_Create, supply appCollection, appName, kind (announcement, poll, dataPush, or nativePush), and the campaign body, then execute. Once it returns an id, call Campaigns_Activate with the same id.

Is Azure Mobile Engagement still accepting new customers?

Microsoft retired Azure Mobile Engagement in 2018. This API serves customers maintaining historical deployments and migration tooling — for new mobile push needs use Azure Notification Hubs or a third-party engagement platform.