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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Azure Mobile Engagement API?

Yes. Jentic One runs self-hosted on your own infrastructure, so your rules decide which operations and credentials the agent may use. Because the subscription, resource group, app collection, app, and campaign ids all travel in the request path, you can pin the agent to a single subscription, resource group, and app. You also pick exactly which operations it may call, so lifecycle actions like activating, pushing, or finishing a campaign are excluded unless you add them.